Security model

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.

New features of DB and dsql planned for ATK 4.0

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.
• Clone-friendly
• 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.

Lightweight CMS in ATK (video)

As my designer says – best way to break a great web design is to give CMS access to the client. Without any consideration for style they will star moving things around and break stuff. Often not willing to pay for a proper update they will continue to tweak themselves. So what’s the alternative?

There is some – contextual editing. In this post i’ll show how you can do it in ATK

Reloading…

I receive a lot of questions about how to reload page with ATK in certain conditions. There are many approaches and I wanted to write a blog post just about that.