[cvs] [Wiki] changed: RampageFramework

[Wiki Guest]

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

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

@@ -38,28 +38,8 @@
 Methods/
 Pages/?
 Config/?
   xml files
-
-Dir structure for distributable apps:
-
-www.sitename.tld
-  cron/
-  htdocs/
-    .htaccess
-    themes/
-      screen.css
-      graphics/
-      sounds/
-    javascript/
-    index.php
-  includes/
-    pear/ ?
-  logs/
-  scripts/
-  templates/
-
-Use .phar (php archive) files for installing rampage sites?
 
 Rampage::log() - just for admin messages
 Rampage::message() or Rampage::notify()
 For user level notification - html alerts, ajax, send email, jabber, etc. Can be triggered by an Observer but doesn't implement object relationshps. What should? Workflow...
@@ -114,21 +94,8 @@
 
 !ViewBuilder/!PageBuilder custom views
 Web services, command line, GET/web layout should be identical
 App/Method/Params?
-
-++ RSS
-
-FeedBuilder - strategy interface for building multiple kinds of feeds (atom, rss versions, etc.) Takes any object that implements a Feedable interface, or a result set that implements FeedableCollection. Should RDO_Result implement that? Or should we use a more general Describable interface, like below?
-
-++ FormBuilder
-
-Interface with different form building implementations.
-takes an RDO_ResultSet or a single RDO object and builds a form based on that (array is for row based renderers, etc). Or use a more general Describable interface. Need anything besides describe()? Have a DescribableCollection, too, and have RDO_ResultSet implement that?
-
-RampageObject
-DescriableObject
-  |- describe()
 
 ++ Things to remember
 
 MVC is 30 years old