Skip to main content
Last updated June 13, 2011 10:04, by magnum

The aim of this project is to provide a ready-to-use architecture to ease the creation of this style of applications in Java :

  • taking care of the overall architecture of the main window of the application, with a tabbed architecture, the presence of an html printable message area, and so on
  • providing a generic API to manage lengthy actions, keeping the interface responsive, and taking care that actions are performed one at a time, without having to bother about it
  • Adding Metadatas to already opened files
  • managing loading and unloading of external plugins at runtime

Maybe you will say: Why not using Eclipse ? Well Eclipse is a huge framework. When you develop with Eclipse in mind, you are in the Eclipse ecosystem, and you end with a lot of Eclipse dependencies. That can be a good thing, but if you want to keep control on your work, and avoid to bear the burden of too many dependencies (or limit the size of your install), you should look elsewhere. Plus Eclipse does not handle everything for you. But why not using appframework ? Unfortunately (for the moment) appframework does not manage several things that are handled by MDIFramework:

  • Plugins
  • dynamic menus
  • storing / retrieving non GUI parameters between sessions
  • managing FileTypes

And MDIFramework was created before appframework even existed on the Web (2006).

Documentation index

A series of tutorials are here: tutorials

About the contents of each release, the Changes page present the modifications for each release.

Please Confirm