The classes are based on the DB and IntegratedTemplate classes.
They currently still have my class prefix "IFW_" (=IntranetFrameWork).
I'd like to have comments - especially about the class names and whether and
where to put the classes in the PEAR tree.
Hello,
I am very interested by your class. Could you describe the future of your class and what you intend to do? This will help me understand in what extent I can help you.
1) Templates-configuration
Do you see any possibility in the future to provide an HTML-less solution. In products like Oracle Web Portal or PhpLens, configuration can be performed on-line and code is generates automatically. Are you moving towards an integrated product or are you planning to stay at class-level?
2) Database integration
The advantage of an HTML less configuration is that you can easily move your configuration parameters to a database, thus providing an on-the-shelf solution to rapidly create browsing interfaces. If you know Oracle Web Portal, this rocks. Consider that many potential PEAR users have very little SQL knowledge.
3) Do you integrate or plan to integrate with HTML_OOH_Form? There is a real need to modify a record when browsing a database. Are there plans to do so?
In PEAR, we need a real application that does anything (database design, list browsing, page edition). Is this on someone's list?
Best regards,
Jean-Michel POURE