1 / 9

WISP PHP Framework

Joe Chrzanowski. WISP PHP Framework. Current Progress. Changed previous method of page creation to make a lot more sense Required a rewrite of most of the core libs Development process for a web page takes considerably less time

chavi
Télécharger la présentation

WISP PHP Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Joe Chrzanowski WISP PHP Framework

  2. Current Progress • Changed previous method of page creation to make a lot more sense • Required a rewrite of most of the core libs • Development process for a web page takes considerably less time • Had to break data binding to fix other areas (not working at this time) • Huge code cleanup • Taking some time to plan for the summer • Possible project name change

  3. Over the Summer • Fix Data Libraries for multiple data types • Build data object library • Linking with JavaScript • Start work on the WISP Repository • Start work on the WISP Administration interface once the framework is ready

  4. High-Priority Packages • Authentication/Sessions • DataBinding • Databases • XML Data Objects • Serialized PHP Objects / TextFiles • DataGrid • Basically scaffolding in other frameworks • Allows CRUD functionality on a dataset • Easy Administration • Allow for easily creating administration interfaces for applications • Wizard • For making step-based applications (installers for example)

  5. Linking With JavaScript • Provide bindings to JavaScript for easy communication between JS and PHP • Use prototype.js for the basic JavaScript functionality • Use Scriptaculous for the Effects libraries and added control libraries • Optimally would allow any JavaScript code to be inserted anywhere in the document tree and attached to any object with an ID

  6. WISP Administration • Install / Uninstall Packages and Themes • WISP “Registry” / Central Configuration • Run Tests • Application Management/Overview/Config • Templating Tools • Live Template views as you edit • Possible a drag/drop editor similar to Visual Studio

  7. Exporting Applications • Would like the ability to export a WISP app to run on a server without a WISP install • Allows for increased portability of WISP apps • Would grab only the necessary files then reorganize in a runnable fashion • Requires a lot of code-analysis • Not a high priority right now

  8. Security & .htaccess • JavaScript interop is the biggest security hole • Prototype already takes care of some XSS vulns • Establish sessions and user verification into the framework to avoid manual calls • .htaccess • Deny access to .xml files (template files) • Deny access to some PHP and resource files • Mod_Rewrite • Make routing easy • Because everyone else does

  9. Live Demo

More Related