Login | Register
My pages Projects Community openCollabNet

Discussions > cvs > CVS update: /interphace/www/

Discussion topic

Back to topic list

CVS update: /interphace/www/


Author futuraworkz
Full name Marcus Whitney
Date 2004-10-18 15:09:38 PDT
Message User: futuraworkz
Date: 04/10/18 15:09:38


 updating home page.

File Changes:

Directory: /interphace/www/

File [changed]: index.html
Url: http://interphace.ti​gris.org/source/brow​se/interphace/www/in​dex.html?r1=1.1&​r2=1.2
Delta lines: +24 -73
--- index.html 17 Oct 2004 20:06:08 -0000 1.1
+++ index.html 18 Oct 2004 22:09:38 -0000 1.2
@@ -13,93 +13,44 @@
-<p>This is the initial web content for your project. Please customize
-this to fit your project. You dont need to anwser all these questions
-or follow this exact format, but we do like to see this kind of
-information before we approve projects for public viewing.
+<p>Interface is a PHP User Interface Object Model and Framework. It provides a lifecycle and common interface
-<p>Until your project is approved, only you can view it and work on
-<li>This index.html will be used if and only if you have the "Use
-Project Home Page" option checked on the "Adminster Project" page
-(click the "Admin" tab).</li>
-<li>To edit this file, check out your project via CVS and edit www/index.html.
-<li>You can 'cvs add' and commit other files under the project's "www"
-directory and they will published to your project web site.</li>
-<li>Also, consider starting a thread in the "dev" mailing list to get
-thes discussion started. A good one is an "introduction" thread where
-people post messages about themselves and their interest in the
-<li>You can add a "Highlights:" line to the top of all web pages by adding a file www/project_highlights.html </li>
+<h3>Why is this useful to me?</h3>
-<p>What is the goal of this project?
+<p>Interphace primary function is providing a Component Object model to build your PHP applications. While Interphace components are usually used for As User Interface tools, this is not the only use for a component. Thus, the purpose of the component can be a Web Service, Command Line utility etc. Developers using Interphace are always writing reusuble code, because each component you write becomes part of your tool kit. Interphace's features include:
-<p>What is the scope of this project?
-<p>For example:</p>
+ <li>Component Life-Cycle</li>
+ <li>View Trees</li>
+ <li>Broadcasts and Listeners</li>
+ <li>Inherited Component Binding</li>
+ <li>Session Engine Object (which contains the navigation mapping and application logic)</li>
+ <li>Cascading Identified Logging</li>
-<li>Develop just enough functionality to scratch a particular itch</li>
-<li>Build a tool just like XYZ, but less broken</li>
-<li>Build the best XYZ-tool ever!</li>
+<li>The Object Model and facilities in Interphace are inspired by Java Server Faces and Tapestry. Interphace components are not tied to a particular data object package or template engine, although it is likely that there will be extensions of Interphace that bind Propel data objects and compile HTML_Template_Flexy to Interphace components. Hopefully, it won't stop there.</li>
-<p>What are high-level features you are sure to build?
-<li>What would you write on a billboard about your project? Users
-might only look for a few seconds.</li>
-<li>Use the issue tracker to track features and enhancement
-requests. It is not just for bugs, pre-populate it with feature
-descriptions so that potential contributors know what you would like them
-to work on.</li>
-<p>What are the high-level assumptions or ground rules for the project?
-<p>For example:
+To be the standard object model implemented for PHP5 Components, web UI or otherwise.
-<li> we will use programming language X on operating system Y for now.
-<li>We will, or will not, consider certain functional areas like
-internationalization, high security, concurrency, etc. The list of
-functional areas will depend on what you are trying to do.
-<li>Try to keep this part short.
+<h3>What is the scope of this project?
+<p>Completely cover the necessary object-oriented interfaces in PHP5 to implement flexible, listening and embeddable components.</p>
 <h3>Related resources</h3>
-<li>Link to other stuff that you know about. It will help you
-research requirements and provide a useful resource to potential
-<li>Why reinvent the wheel? What is better about this wheel? Is there
-any existing project that you can partner with or reuse?</li>
-<li>Where would you go to try to find potential contibutors?</li>
+<li><a href="http://java.sun.com/​j2ee/javaserverfaces​/index.jsp">Java Server Faces</a></li>
+<li><a href="http://jakarta.apach​e.org/tapestry/">Tapestry</a​></li>
+<li><a href="http://wact.sourceforge.net/">WACT (PHP Web Application Component Toolkit)</a></li>

To unsubscribe, e-mail: cvs-unsubscribe@inte​rphace.tigris.org
For additional commands, e-mail: cvs-help at interphace dot tigris dot org

« Previous message in topic | 1 of 1 | Next message in topic »


Show all messages in topic

CVS update: /interphace/www/ futuraworkz Marcus Whitney 2004-10-18 15:09:38 PDT
Messages per page: