phpWebApp presentation
0 likes692 views
The document discusses phpWebApp, a PHP web application framework, and the SEE-GRID Resources Web Application built with it. phpWebApp separates application logic from layout using templates, supports modularity and reusable components, and facilitates database interaction. The SEE-GRID Resources Web App displays resource data for each country and cluster, and allows admins to edit data through a password-protected interface. Future work may include framework documentation improvements and tools to support phpWebApp development.
phpWebApp presentation
- 1. phpWebApp and SEEGRID Resoures phpWebApp and SEEGRID Resoures Dashamir Hoxha dhoxha@inima.al Dashamir Hoxha Elda Nallbani enal@inima.al Elda Nallbani Institute for Informatics and Applied Mathematics INIMA http://www.inima.al The phpWebApp Framework http://phpwebapp.sourceforge.net/ The SEEGRID Resources Web Application http://seegrid.inima.al/gridrc/
- 5. Why Not Use Plain PHP Mixing HTML, CSS, JS, PHP, SQL codes ✗ Editing becomes difficult (code colorization, etc.) ✗ The maintenance of the application becomes difficult. ✗ Makes difficult the team work. ✗ Increases the complexity of web applications. There are no persistent variables. Lack of modularity.
- 6. Choosing a Framework Possible Tools: ✗ Any template system or web application framework (look at http://sourceforge.net/search/?type=soft) ✗ ColdFusion, Smarty, etc. Why phpWebApp? ✗ It is free (GNU GPL). ✗ Better than the others (more flexible, powerful, etc.). ✗ We know it better than the others.
- 7. What is the phpWebApp Framework A Web Application Framework Built with PHP and used for PHP apps Easy interface to DB Can be used for eContent, eGovernment, eCommerce, etc.
- 10. phpWebApp Components Templates Database Template variables WebBoxes State Variables WebClasses and Transitions WebObjects Events
- 11. phpWebApp: Templates XHTML files with some additional tags and variables: <include>, <if>, <repeat>, <recordset>, <var>, <!# comments >, <webbox>, etc. <include src="{{./}}edit/cluster_edit.html" /> <if condition="!{{admin}}"> <a class="button" href="javascript:edit()"> Edit</a> </if>
- 12. phpWebApp: Templates <table> <repeat rs="clusters"> <tr><td>{{cluster_name}}</td></tr> </repeat> </table> <recordset id="country"> <query> SELECT country_name FROM countries WHERE country_id = '{{country>id}}' </query> </recordset>
- 13. phpWebApp: Template Variables Slots in template files, denoted like this: {{var_name}} Get their value in the php code, like this: WebApp::addVar(var_name, var_value); The framework gets its value from a state variable, from a global php variable or from a php constant that has the same name as the template variable.
- 14. phpWebApp: State Variables Persistent variables (don' t loose their value from one page to another); similar to session variables. Keep the state of the application and its webbox es (which are considered as a state machine). Stored inside the webpage itself. Example: $user_id = WebApp::getSVar('user_list>selected_user');
- 15. phpWebApp: Transitions and Events A transition is the move of the application from one state to another. It is done by the function: GoTo('page.html') An event is usually sent as well. An event can be sent like this as well: SendEvent('targetBox', 'eventName', 'arg1=val1;arg2=val2'); It is handled by the php function: targetBox::on_eventName($event_args)
- 17. phpWebApp: WebBoxes A WebBox is a tpl which has its own php code. It can also have its own JS, CSS, DB code, etc. It can be selfcontained and independent, and can be included easily in other pages or in other applications. <webbox id="box_id"> <! content of WebBox > </webbox>
- 18. phpWebApp: WebBoxes The other files are: box_id.php, box_id.js, etc. box_id.php is like this: <?php class box_id extends WebObject { . . . } ?> It can have functions: onParse(), onRender() These override the functions of WebObject.
- 19. phpWebApp: WebClasses An attempt to use the concept of ' Class' for the templates of the framework. Several WebObjects of the same class can be used in the same page. <WebObject class=”listbox” name=”books” rs=”books” /> Some predefined webclasses are: ✗ listbox: a list of values from a recordset ✗ datebox: select the date from a calendar ✗ tabs: horizontal tablike menu
- 21. Conventions of Web Applications Web Apps should follow some conventions: Files index.php, webapp.php, browse.php, etc. are the same for all the applications. The configuration of the application is placed in the folder ' config/' (const.Options.php, const.Paths.php, const.Debug.php, etc.) Templates (webboxes etc.) are usually placed in the folder ' templates/' .
- 22. Future Work Improvement of the docs of the framework. Improvements to the framework itself. Tools for working with the framework: ✗ Emacs mode, Quanta plugin, etc. Building reusable WebBoxes and WebClasses; they can be even organized in higherlevel frameworks for apps of a certain kind. Code generation and reverse enginnering from UML models.
- 23. phpWebApp and SEEGRID Resoures phpWebApp and SEEGRID Resoures Dashamir Hoxha dhoxha@inima.al Dashamir Hoxha Elda Nallbani enal@inima.al Elda Nallbani Institute for Informatics and Applied Mathematics INIMA http://www.inima.al The phpWebApp Framework http://phpwebapp.sourceforge.net/ The SEEGRID Resources Web Application http://seegrid.inima.al/gridrc/