[cvs] [Wiki] changed: RampageFramework

[Wiki Guest]

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

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

@@ -19,11 +19,8 @@
 * Context::appname::method($params) - this doesn't work, Rampage::app->method would. Already implemented in Registry class.
 * Session object for managing data we expect to find in $_SESSION
 * base Rampage on: ulaform, giapeto, wicked, should replace those ... ? jonah?
 * Iterators! Only loop through data once!
-* Page/URL design: the back button should work where possible
-* use POST for anything that's an edit or delete. really.
-* Make use of stream wrappers for easy fopen/fwrite/fgets with data sources. VFS wrappers at least.
 
 Encapsulated globals in Rampage:: namespace. Goal to avoid global $conf, $prefs, etc. variables and to do lazy-loading of conf and prefs so they're not loaded when they're not needed. Maybe encapsulate prefs in a User object/namespace?
 
 everything else pear installable
@@ -59,14 +56,8 @@
 take interfaces that implement Iterator wherever possible
 
 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.).
-
-Should be a way to cache table meta data
-
-Need a way to specify which fields to load (for example like Turba only loads fields being displayed). When this is done, the rest should be lazy-loaded.
-
-Should be possible to greedy-load related objects (lazy is the default).
 
 ++ Display and templates, Views and Components
 
 * views/components should be nestable
@@ -75,23 +66,8 @@
 * 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?
-
-+++ What's good about Horde_Template
-
-* fast
-* simple
-
-+++ What's bad about Horde_Template
-
-* does not result in valid XML templates because of nested < inside tags
-* hard to debug
-* no builtin support for htmlspecialchars(), so the code using the template has to know what to encode
-
-Potential replacements:
-
-* http://wiki.bitflux.org/Templates_TAL (see http://php5.bitflux.org/xsltal/slide_25.php for example PHP code)
 
 !ViewBuilder/!PageBuilder custom views
 Web services, command line, GET/web layout should be identical
 App/Method/Params?