Projects Hierarchy

Some input about projects hierarchy...

Most programmers I've talked to does not understand the positive effects a multi-project architecture can provide, I do not intend to get too much into details here, but lets just name some in short:

• Eliminates dumb uses of Dual-Coupling.
• Forces development in layers, thus enabling easy cross projects refactoring.
• Forces modular coding.
• Following the above, with proper syntax rules, redundant's bugs, spaghetti code, language abuse, code duplications, and more!  

So here is an abstract view of my entire projects hierarchy layers, I would not get into details, as there are nearly 200 projects involved, and it goes cross platforms, Android, J2ME, J2EE,J2SE...

You like this, +1 it!.

DBator

DBator is a generic instance to DataBase development infrastructure utility, something like hibernate only far simpler, which allows with a bit of code, to define classes as Database rows, and read and write objects instances from and to the Database respectively, it supports partial fields reading and writing for performance.

DBator can read and write from and to sub-tables, if it has been told to.

DBator is a part of what we call ART(Annotation Reflective Technology) projects.

Editall

Editall a generic instance editing development infrastructure utility, which allows with a bit of code, to define classes as Editing beans, where each field in the class may be edited according to its specification, thus allowing an auto-generated generic editing panel, which also to updates the values of the instance supplied for editing.

Editall is designed in such manner that developers may extend it, and change the editing models, panels, and dialogs, as they see fit.

Editall also supports external editors, so a developer may create external importers, to import specific types, which cannot be edited with the default models supported, for example: Image importer, File chooser, etc.. 

Editall is a part of what we call ART(Annotation Reflective Technology) projects