Font size:

Jim's history (technical issues)

End of summer 2008: Jim 2.0.0

Internal restructure of Jim based on OSGi to replace the old dirty plugin system.
Seperation of JimGui and the core part (the GUI is now a plugin).
The other two plugins (JimFileOrganizer and JimSearch) are adapted to the new plugin system.
Only change for end users: An improved about dialog of JimGui now showing all version numbers of Jim, OSGi, and all plugins of Jim.

JimFileOrganizer is a plugin that helps to organize your images on file system level. This is done by format strings.
JimSearch is a plugin that implements a basic search engine: In JimSearch tags can be connected with an AND and JimSearch finds every image that is tagged with all selected tags (directly or indirectly: if you search for a parent tag you will also find all images tagged with child tags of that tag.

Jim and Jim's GUI kept closely connected.
New database technology: Hibernate made database handling much more easy. Since then for example one Image object knows the tags it is tagged with and a Tag knows it's Images and child tags and so on.
Highly improved tagging technology: Tags can now be structured in a tree.
The GUI knows when tags are added or removed by using a subject-observer-pattern. This means there are no more problems with refreshing the tag tree - it is automatically done for you!
Plugin system

Jim and Jim's GUI were comparatively close connected.
Database: Derby, using the JDBC-Drivers to handle it.
Basic tagging: Images could be tagged, but structuring tags in a tree was not supported.
Problems with updating the GUI when tags were added or removed (most times a manual refresh was needed).