[phpwebapp-commits] CVS: web_app/doc to_do.txt,1.12,1.13 ToDo.txt,1.7,1.8

[Dashamir H. <das...@us...>]

Update of /cvsroot/phpwebapp/web_app/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19096/doc

Modified Files:
	to_do.txt ToDo.txt 
Log Message:


Index: to_do.txt
===================================================================
RCS file: /cvsroot/phpwebapp/web_app/doc/to_do.txt,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** to_do.txt	23 Jul 2004 10:17:07 -0000	1.12
--- to_do.txt	29 Jul 2004 14:46:54 -0000	1.13
***************
*** 1,5 ****
  
! - fix some bugs in the documentation application (codeReview)
! - add the forth tutorial
! - update documentation
! - remove the downloads from the page of the framework
--- 1,31 ----
  
! * - Add this functionality to the framework: any webobject can
!     handle an event sent to another webobject, if it defines the
!     event handler "on_className_eventName()" (usually the event 
!     handlers are named like this: "on_eventName()"). 
!     Here 'eventName' is the name of the event, and 'className' is 
!     the class of the webobject that receives or sends the event 
!     (whichever is more appropriate).
!     This may make obsolete the "event_target='any'", which was used
!     to allow a webbox to handle the events of another webbox.
!  
! * - Add a switch at const.Settings.php, which tells the framework
!     to print debug information for the functions that are executed
!     in the order that they are executed. Such functions can be
!     onParse, onRender, init, eventHandler, on_event, etc.
! 
! * - Add a function: WebApp::reloadPage($new_page) which stops
!     processing the current page and starts loading the new
!     page. This may be usefull when a webox redirects the event
!     to another webbox or sends a new event to another webbox.
!     E.g. in login, the login webox, after checking that the
!     password is wrong, reloads another page.
!     Probably is better to call it: WebApp::GoTo("tpl.html?etc"),
!     to be consistent with the GoTo() JS function.
! 
!   - Add a function: WebApp::toHtml($tpl_page) which loads the
!     given template, renders it (using any egzisting variables)
!     and returns the HTML code.
! 
! * - Factor out from the classes all the debuging functions and
!     put them in a separate class or file.

Index: ToDo.txt
===================================================================
RCS file: /cvsroot/phpwebapp/web_app/doc/ToDo.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** ToDo.txt	29 Jul 2004 07:58:16 -0000	1.7
--- ToDo.txt	29 Jul 2004 14:46:54 -0000	1.8
***************
*** 1,32 ****
- * - Add this functionality to the framework: any webobject can
-     handle an event sent to another webobject, if it defines the
-     event handler "on_className_eventName()" (usually the event 
-     handlers are named like this: "on_eventName()"). 
-     Here 'eventName' is the name of the event, and 'className' is 
-     the class of the webobject that receives or sends the event 
-     (whichever is more appropriate).
-     This may make obsolete the "event_target='any'", which was used
-     to allow a webbox to handle the events of another webbox.
-  
- * - Add a switch at const.Settings.php, which tells the framework
-     to print debug information for the functions that are executed
-     in the order that they are executed. Such functions can be
-     onParse, onRender, init, eventHandler, on_event, etc.
- 
- * - Add a function: WebApp::reloadPage($new_page) which stops
-     processing the current page and starts loading the new
-     page. This may be usefull when a webox redirects the event
-     to another webbox or sends a new event to another webbox.
-     E.g. in login, the login webox, after checking that the
-     password is wrong, reloads another page.
-     Probably is better to call it: WebApp::GoTo("tpl.html?etc"),
-     to be consistent with the GoTo() JS function.
- 
-   - Add a function: WebApp::toHtml($tpl_page) which loads the
-     given template, renders it (using any egzisting variables)
-     and returns the HTML code.
- 
- * - Factor out from the classes all the debuging functions and
-     put them in a separate class or file.
  
  A non-exhaustive list of things that are to be done
--- 1,2 ----