Improvement over MadKit 4.0
- MadKit 4.1 comes with a new Designer agent which allow
- A new Designer agent, which allows the user to easily develop new programs
in MadKit. Very handy to start an application, test agents, etc. (unfortunately
this feature does not work properly on Mac OS 10.3, due to a gui problem.
We have not tried in Tiger..)
- New interface for turtlekit....
- SEdit is now able to work either as a component of MadKit or as a standalone
interface.
- There is now a launcher for Mac OS
- A new Editor agent, the JSynEditor has been developped specially for MadKit
by a group of students of the University of Montpellier. This editor is component
based and has all the features of the previous EditorAgent with added capabilities:
syntax coloring, full search, replace, undo/redo, java browsing facilities,
templates, etc...
Improvement over MadKit 3.0
- MadKit 4.0 comes with a new software architecture based on plugins. It is
now possible to add and remove plugins to adapt MadKit to suit your needs.
- The Desktop has been totally rewritten. It is now totally possible to easily
add and remove icons, to change from a single window like display to a multi-window
environment.
- Installation directly from the network: the PluginManager is an installer
specifically built for MadKit which uses agents to install and upgrade the
MadKit platform. So you just have to install MadKit once.
- It is possible to build agents and recompile a Java project without quitting
MadKit, due to the integration of ant to MadKit.
- The communicator is now programmable. It is possible to ask it to connect
to another kernel by sending it a message.
- There is also a new NetComm agent which allows for new features in Communication.
- The Share plugin allows different user to share document over a MadKit network.
You may use it to share documents (agents scripts, etc..)
- DocBrowser agent which allow for a better display of MadKit documentation.
- The Warbot environment is now totally integrated to MadKit.
- It is easier to build Java Applets with MadKit inside..
General features
- MadKit is based on the AGR (Agent/Group/Role) organizational model, but
you may develop your own agents without considering organizations if you do
not want to.
- MadKit general architectue is based on micro-kernels which provide only
the basic facilities: messaging to local agents, management of groups and
roles, launching and killing of agents. All other features (distant messages,
display, monitoring and control of agents) are performed by agents.
- MadKit agents may be programmed in different languages: Java, Scheme (Kawa),
Jess (a rule based engine), Pyhton (Jython), BeanShell (interpreted java).
- No specific agent architecture is assumed. Plugins with different architecture
may be added to MadKit to program agents with different architecture.
- Agents display may be programmed as independant components. It is possible
to use the same agents in GUI mode or in text (console) mode.
- MadKit may be used as a GUI oriented platform or as a server.
- MadKit comes with a very friendly user interface, which may be parameterized,
to launch, display and monitor agents.
- Simplicity: MadKit is considered as a very simple platform to use for developping
multiagent applications.
- Possibility to develop both thread based agents and scheduled agents for
multiagent based simulation using the "synchronous" engine.
- You may run MadKit in different execution contexts: JSP, Applet, Console
mode, GUI desktop, etc..
Future features which should come soon (we are currently working on it)
- Description of organizations, i.e. types of groups and roles via XML files.
It will be possible to add information to groups and roles.
- Agent migration
- Better integration with data bases
- Integrated development environment for building organizations and agents
- FIPA compliance of MadKit