[cvs] [Wiki] changed: RampageFramework

[Wiki Guest]

guest [65.19.150.231]  Sun, 21 Aug 2005 20:08:51 -0700

Modified page: http://wiki.horde.org/RampageFramework
New Revision:  5.0
Change log:  Revert

@@ -57,17 +57,13 @@
 
 need basic classes for each backend (SQL, LDAP, Kolab, IMSP, etc) that provide a unified api
 try hard not to use more than that api; write specific adapters when necessary (Whups with encapsulated specialized Mapper objects, etc.).
 
-++ Display and templates, Views and Components
+++ Display and templates
 
-* views/components should be nestable
-* need a concept of "slots" - where can a view put sub-views
-* copy java's layout managers? or is that too heavy? want to keep it simple
-* How much effort should be put into formats other than XHTML? probably different for data vs. components. Data should be available as a pdf, as rss feeds, in export formats. Components will still be xhtml, maybe wml for mobile device support, maybe php-gtk - more limited set.
-* Fields
-* html/xhtml/xml renderers
-* php5 xsl?
+- Fields
+- html/xhtml/xml renderers
+- php5 xsl?
 
 !ViewBuilder/!PageBuilder custom views
 Web services, command line, GET/web layout should be identical
 App/Method/Params?