I’ve put quite a bit of effort as of late getting hcOPF ready for Win64 compilation, and as part of that effort, re-factoring it to support FireMonkey. The actual code and package changes were relatively minor when compared with trying to understand what was required. To me this validates the design of the framework that it can be adapted rather easily to support new frameworks and platforms.
There are no new recommended guidelines for DesignTime and RunTime packages AFAIK now that XE2 supports FMX and VCL. To complicate things further, add in Unit Scope Names, the fact that the IDE automatically renames FMX package projects when you target the OS/X, and all the conditional directive permutations, and it can drive you bananas!
On top of that, the IDE does not provide default guidance when upgrading packages from earlier IDE versions. It does not default the unit output directory to .\$(platform)\$(config) as it does for new ones, so when you compile for one platform you overwrite your DCUs for another, and really confuse things. For this reason, you might notice that for All configurations - All platforms hcOPF uses a unit output directory of $(hcOPF)\Lib\D16\$(Platform)\$(Config) where $(hcOPF) points to the root directory of the framework. It would be great if there was an environment variable for the IDE version. Then you could use something like $(hcOPF)\Lib\$(DelphiVersion)\$(Platform)\$(Config).
I am pleased to announce that hcOPF now supports FireMonkey (Win32/64 and OSX32) as well as VCL Win32/64 targets with a few caveats:
1) when compiling for the Mac or any 64 bit target you must skip compilation of the design time packages.
2) The HengenOPFValidatorsFMX/VCL packages do not support 64 bit targets since it uses the open source PerlRegEx component instead of the RegEx support present in XE and above.
3) Certain packages of course cannot be used on certain platforms like ADO and the Validators on the Mac since they have Windows specific implementations.
4) As always some packages require third party commercial libraries, such as the HengenDevExpressXXX packages which require the Developer Express Quantum Grid suite (highly recommended).
5) Win32 BPLs go into the default $(BPLDir) and those for OSX32 and Win64 go into their respective subdirs
In a future version I hope to add support for iOS as well as providing validator support for FMX. Currently hcOPF will not compile using FPC because it does not support the implements interface delegation syntax that EMB’s compiler does. Eventually I plan to support FPC and SQLite.
If you want to start Monkeying around with hcOPF, check out the FireMonkey SVN branch.