Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/e22dcd02a4ee266a#
One of key concepts used in In-Portal are Unit Configs.
They are large arrays, that hold all unit related configuration. Because of large setting count it's pretty hard to keep unit config as readable and clean as first time it was created.
Also some settings always defaults to same values and typing (copy/pasting) them each time also is a waste of time.
I'm proposing to create a class, that would represent a unit config with basic methods for setting entry and "dump" method, that will create resulting unit config file as we see now.
This way from one side we have all flexibility of OOP (object oriented programming) with IDE assisted auto-complete on unit config definition stage and, thanks to "dump" method, we don't have performance degradation because in fact only dumped (complied) unit configs will be used.
At the end compiled unit configs will be located under /system/cache folder.