Agile Toolkit’s Form implementation comes a long way from probably 2006. There were some changes along the way and currently we are looking to implement a new default way of form submission. Please provide your feedback.form
Today – any desktop software is able to re-draw itself from a callback by operating system. However many Web Frameworks today do not keep track of objects and cannot selectively produce pieces of HTML code.
I believe that ability to have control over objects on HTML pages is very essential to have in the Framework. Here is why:add-ons, ajax, form, grid
While we are still debating, most probably Agile Toolkit 4 will be available under the General Public License. It will be dual-licensed under commercial license if you wish to use it in commercial applications. The same principle will apply on all the code, plugins, modules.support
Thanks for your feedback on “File Mapping” post. We respect your feedback and have decided on the basic set of rules regarding class naming.grid, news
We have been discussing this internally but I’d like to hear your feedback on this matter.
It is Class to File mapping and use of upper / lower cases.add-ons
Up till now we had to either pile up functions in API class formatted as page_user, page_user_add, page_user_del, or we had to create all those classes, each in it’s own file.
Well – not anymore. Now any page class can have sub-pages. Here how it works:page
Some discussions prompted me to focus on security goals of ATK4. This post is about how we are approaching security and human-factor as well as flexibility in dealing with external systems.
Based on our current usage and user feedback we are preparing to start development on a new database layer. Thanks to new cool features in PHP (PDO) it’s going to be real easy. However we plan to add some exciting new features such as:
- Rely on PDO, DSN format will change
- Single-table dsql. You can still use joins, which will create multiple dsql instances and make them work together seamlessly.
- Automatic alias management.
- Database driver decides when to fetch data and how.
- Multi-table update() and insert(). MySQL have some support for multi-table update, but this feature will take it to a whole new level.
- Support for simple storage such as SimpleDB. Database engine will allow to compensate for missing [R]DB features.
- dsql Implementation of Iterator, Countable, Seekable and more for nice syntactic sugar.
- Much stricter towards field use. Do not allow developers to slip in any SQL logic.
- Support for expression objects. Similar to $this->js(), this will allow you to build sql operators and functions dynamically
- Proper support for sub-selects. Sub-select being another dsql query.
- Better debugging
- Automated tests
- Transaction support.