== Forms Refactoring ==
First phase of Kexi Forms Module refactoring.
The main reason is to simplify the codebase and prepare it to future enchancements like subforms, reports integration, and tabbed main window design.

Detailed reasons for refactoring:
--The process of instantiating a form (the Form class) is very complicated now what makes it very hard to properly implement subforms
--The code full of interdependencies and thus is fragile when adding new functionality or fixing bugs
--The FormManager class centralizes a number of operations that shall belong to Form itself
--The naming of methods and classes can be improved, e.g. Form -> FormController
--The ObjectTree* classes introduce redundancy as we already have QWidget hierarchy, and extensible property system; this complicates the code

See Also:
<a href="http://wiki.koffice.org/index.php?title=Kexi/Porting#Forms_Refactoring">http://wiki.koffice.org/index.php?title=Kexi/Porting#Forms_Refactoring</a>;