Things we love and things we hate about tiOPF

Love:

Simplicity - very few concepts to remember;
Flexibility - Performance tuning opportunities, database backend, GUI - all
flexible;
Code base - All the "hard" stuff is done;
Behaviour modification - enforces good coding style - use of OO; Scaleable - Seems little in the backend that cannot be extended or changed as/if required;
Portability - Conceptually easy to migrate to .Net using reflection and same Visitor pattern;
Open-source - Collective/ collaborative ... sense of being a part of a good piece of work;
Design Patterns - Visitor pattern is amazingly useful; Independent - Innovative;
Dunit - Greatly improves code quality;
Speed of development - Its very, very easy to get a basic app up and running.
The most powerful feature of the tiOPF has to be the Visitor. For us the
business, and the model of that business, is everything and the Visitor pattern allows us to painlessly traverse the 'model' and perform a specific action across a hierarchy of related entities. As a result, it assists in allowing us to focus more on the business and less on the technical code.

Having one day to migrate to .Net while Win32, Delphi and tiOPF are such a good combo.
Coding a routine to find it in the framework, coded better and Dunit tested already.
Lack of good UI controls
No built in class editor
Will not auto create a database schema an keep the schema in sync with the object model
It's based on RTTI and published properties. Some OPF zealots think this is bad. Published properties do, however make for very easy to read and understand object models