[phpWebApp-commits] CVS: documentation/templates about.html,1.11,1.12
Brought to you by:
dashohoxha
Menu
▾
▴
[phpWebApp-commits] CVS: documentation/templates about.html,1.11,1.12
|
From: Dashamir H. <das...@us...> - 2002-01-17 04:22:14
|
Update of /cvsroot/phpwebapp/documentation/templates
In directory usw-pr-cvs1:/tmp/cvs-serv8650/templates
Modified Files:
about.html
Log Message:
Index: about.html
===================================================================
RCS file: /cvsroot/phpwebapp/documentation/templates/about.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -d -r1.11 -r1.12
*** about.html 2001/12/28 19:56:32 1.11
--- about.html 2002/01/17 04:22:11 1.12
***************
*** 18,21 ****
--- 18,80 ----
</p>
+ <p>
+ Some of the features of the 'phpWebApp' framework, and the advantages and
+ benefits of using it for building web applications, are these:
+ <ul>
+
+ <li> The framework separates the layout from the logic of the
+ application, so a graphical designer can easily improve the
+ layout of the application without getting messed with the logic
+ and without having to understand it. It makes easier the work
+ of both the graphical designer and the programer.
+ This also facilitates an iterative and incremental development
+ approach for web application projects.
+
+ <li> The framework gives the possibility to divide a page into several
+ parts which can be used in other pages as well. This makes the
+ user interface of the application (the layout, the graphical part)
+ more structured and easier to understand and maintain and makes
+ easier the work of the graphical designer.
+
+ <li> The framework looks at web applications from a new point of
+ view. From this point of view, a web application is a state machine,
+ which can be represented and described by one or more statechart
+ diagrams. Each page of the application that is displayed, represents
+ the application in a certain state. Clicking to a link causes a
+ transition to another state of the application. This simplifies
+ the design and the implementation of web applications. Later, if this
+ point of view is formalised and elaborated enough, it may provide
+ the theoretical bases for automatic code generation of web applications
+ from state chart diagrams (e.g. from UML state chart diagrams), and
+ for reverse engineering.
+
+ <li> The framework supports an event based programing model. When a
+ transition from one state of the application to another happens,
+ it may trigger an event as well, which is handled by a function
+ (event handler). This makes the logic of the application easy to build,
+ understand and maintain, and makes easy the work of the web programer.
+
+ <li> The framework gives to the web programers the possibility to create
+ independent web components (called WebBox-es) which have their own
+ user interface (graphical design), client side behaviour, server
+ side behaviour, states, events, event handlers, etc. These components
+ can be very easily reused in other web applications and thus provide
+ code reusability to web programers. This means that if you have
+ constructed something once, you don't have to re-construct it again
+ when you need it another time, but use it ready.
+
+ <li> The framework brings closer the client-side and the server-side
+ logic of a web application. E.g. the session variables (which are
+ usually used to keep the state of various parts of the application),
+ are available and can be accessed both on client side and on server side.
+
+ <li> The framework makes the interaction with the database almost
+ database independent. This means that in case that you decide
+ to change the database on which your application is based (e.g.
+ switching from MySQL to Oracle), then the application itself
+ doesn't need to be changed at all, it will work all the same.
+ </ul>
+ </p>
+
<h3>Installation</h3>
<p>
***************
*** 44,48 ****
</p>
<h3>Related Links</h3>
- <p>
<ul>
<li> <a href="http://sourceforge.net" target="_new"> SourceForge.net
--- 103,106 ----
***************
*** 50,55 ****
<li> <a href="http://sourceforge.net/projects/phpwebapp/" target="_new">
phpWebApp Project</a> at SourceForge
! <li> <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phpwebapp/" target="_new">Browse the CVS</a> at SourceForge
! <p>
<li> <a href="/documentation/browse.php" target="_new"> Browse the
Documentation templates </a>
--- 108,112 ----
<li> <a href="http://sourceforge.net/projects/phpwebapp/" target="_new">
phpWebApp Project</a> at SourceForge
! <li> <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phpwebapp/" target="_new"> Browse the CVS</a> at SourceForge
<li> <a href="/documentation/browse.php" target="_new"> Browse the
Documentation templates </a>
***************
*** 57,63 ****
<li> <a href="/app1/browse.php" target="_new"> Browse the Sample
Application templates </a>
-
</ul>
! </p>
<h3>License</h3>
<p>
--- 114,119 ----
<li> <a href="/app1/browse.php" target="_new"> Browse the Sample
Application templates </a>
</ul>
!
<h3>License</h3>
<p>
***************
*** 70,74 ****
</p>
<p>
! LGPL is a free software llicense Like GPL, it allows anybody to use,
redistribute and/or modify this software, but at his own risk, and without
restricting its freedom. Different from GPL, it allows the software to
--- 126,130 ----
</p>
<p>
! LGPL is a free software license. Like GPL, it allows anybody to use,
redistribute and/or modify this software, but at his own risk, and without
restricting its freedom. Different from GPL, it allows the software to
***************
*** 81,86 ****
By choosing LGPL over GPL I believe that I have chosen collaboration over
confrontation. I think that collaboration is better than confrontation.
! My philosophy is: Live and let live, and let the God decide which one is
! in the right way.
</p>
<br>
--- 137,142 ----
By choosing LGPL over GPL I believe that I have chosen collaboration over
confrontation. I think that collaboration is better than confrontation.
! My philosophy is: "Live and let live, and let the God decide which one is
! in the right way."
</p>
<br>
|
