the layers of SRJRCFrames

The grounding of the framework - it contains the baseclasses for data abstraction, services and data handling. I assumed, that it is quite common for richclient applications to present data with an editor to the user to let him change the data. As JGoodies was my first choice for GUI handling, I took its model class as a superclass for all persistence. That way, the effort to code an editor for a given entity is reduced to a minimum.

Respect to persistence, I was attracted by the principle of Entity and EntityManager, but I had to adopt it to the needs of richclient applications. One major goal was to cut of all differences between storage systems from application, so an EntityManager can be registered for an Entity, it should care about. The registered EntityManager will also care for all children of the registered class. VdrAssistant for example uses three different EntityManager: one for JDBC, one for java preferences and one for data migration, which means, this EntityManager reads from one storage and writes to another - and all that fully transparent for the application and the application developer!

The base classes for the graphical user interface, like window manager, editors, listviews and of cause it has a lot of extended standard dialogs like color selection, font selection and the like.

Baseclasses for the applications, the startup-classes which take care of configuration handling, loading of extensions and offer application services.