1. Joe Chrzanowski

2.  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.  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.  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.  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.  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.  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.  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