[phpwebapp-commits] CVS: web_app/doc changes_2.txt,1.4,1.5 ToDo.txt,1.4,1.5
Brought to you by:
dashohoxha
From: Dashamir H. <das...@us...> - 2003-09-30 07:11:26
|
Update of /cvsroot/phpwebapp/web_app/doc In directory sc8-pr-cvs1:/tmp/cvs-serv20128/doc Modified Files: changes_2.txt ToDo.txt Log Message: 'free events' modified Index: changes_2.txt =================================================================== RCS file: /cvsroot/phpwebapp/web_app/doc/changes_2.txt,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** changes_2.txt 24 Sep 2003 14:22:50 -0000 1.4 --- changes_2.txt 30 Sep 2003 07:11:20 -0000 1.5 *************** *** 103,105 **** --- 103,125 ---- dynamic recordsets. --------------------------------------------------------------- + * Free events are handled by the file 'on.eventName.php' which is + placed in the same folder as 'sourcePage'. This file now contains + global code (not the function on_eventName()). + + ToDo: Find another name (terminology) for free events. E.g. they + may be called 'independent events' (because the handler is not a + member function on any webbox), 'global events' (because they are + handled globally and before any page construction has started), + 'switches' or 'conditionals' (because they usually switch on some + conditions and decide which page to construct), etc. + --------------------------------------------------------------- + --------------------------------------------------------------- + --------------------------------------------------------------- + --------------------------------------------------------------- + --------------------------------------------------------------- + --------------------------------------------------------------- + --------------------------------------------------------------- + --------------------------------------------------------------- + --------------------------------------------------------------- + --------------------------------------------------------------- --------------------------------------------------------------- Index: ToDo.txt =================================================================== RCS file: /cvsroot/phpwebapp/web_app/doc/ToDo.txt,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** ToDo.txt 4 Aug 2003 12:06:13 -0000 1.4 --- ToDo.txt 30 Sep 2003 07:11:20 -0000 1.5 *************** *** 359,362 **** --- 359,366 ---- {{class_name}} to {{Class}} + - {{CurrentRecNr}} to {{RecNr}} + {{CurrentRowNr}} to {{RowNr}} + etc. + - Rename path constants from 'XYZ_PATH' to 'XYZ/'. (!?) *************** *** 370,382 **** like this. (Why is it better? Does it have any disadvantages?) ------------------------------------------------------------- ! * Improve the structure of the framework and the application so ! that two independent applications can comunicate easily with ! each other. E.g. one of the applications can include the other ! (like a webbox that can include another webbox) and both of them ! work independently in the same window. One of the applications ! can check or modify the state of the other application, can ! modify its behaviour, can use its resources (images, templates, ! etc.), etc. Such a capability would be useful for applications like "browse", --- 374,394 ---- like this. (Why is it better? Does it have any disadvantages?) + + - Find another name (terminology) for free events. E.g. they may be + called 'independent events' (because the handler is not a member + function on any webbox), 'global events' (because they are handled + globally and before any page construction has started), 'switches' + or 'conditionals' (because they usually switch on some conditions + and decide which page to construct), etc. + ------------------------------------------------------------- ! ! * Improve the structure of the framework and the application so that ! two independent applications can comunicate easily with each ! other. E.g. one of the applications can include the other (like a ! webbox that can include another webbox) and both of them work ! independently in the same window. One of the applications can check ! or modify the state of the other application, can modify its ! behaviour, can use its resources (images, templates, etc.), etc. Such a capability would be useful for applications like "browse", |