Yesterday night I added some great functionality in zephyr. Developers can use âFiltersâ? in zephyr packages. In primary stage I just implemented two type of filters, one is âpre-filterâ? and another is âpost-filterâ?. Pre filters are a simple object which is invoked when visitors input data. Before passing these data to actions, zephyr will call âprocess()â? method of pre filter object. After processing them, these data will be passed to action.
Pre filters are of great use of you want to implement some sort of input filtering. Beside submitted data from users, Prefilters will also receive the action name which is responsible to handle those data. So it will remain flexible to developers.
Second type of filter that I implemented is âpostfilterâ?. After rendering the view, this filter is invoked with the rendered content and action name. So developers can polish the rendered output if they need to.
Day by day I will also add filter in different execution level of zephyr core. I am also planning to implement JSON support in zephyr. Here is a comprehensive list of implemented features for upcoming version of zephyr beta 2.0
1. Multiple Database Support (For both same provider and different provider)
2. SQLite support
3. Prototype is now a part of zephyr. So users can take advantage of this great library.
4. Automatic display of âloadingâ? image when an action is called.
5. Multiple PHP file loading capability
7. Multiple pre action processors
8. Supports exchanging non printable characters as response and request.
9. Easy loading of PEAR packages.
10. Package Initializer, a special object that will be invoked while loading the package for first time.
11. Abstract DBInfo class, to simplify sharing db information.
12. flexible execute() method in DAO
13. Better exception management.