# ATK Framework
ATK Framework is a special purpose PHP framework targeted at business applications.
It's targeted at developers who wish to focus on business logic, instead of coding HTML. Where other application frameworks mainly provide a large set of utility classes, ATK provides a complete framework that requires only small amounts of code to get usable applications, while maintaining full flexibility.
ATK was originally developed by Ivo Jansch and iBuildings back in 2000. It's been actively developed until 2011 (version 6.6).
This repo is managed by Sintattica. We still have some active projects based on various versions of ATK. Since we didn't find a true alternative to ATK yet, we opted to keep it alive.
We currently have 4 branches:
## 8.2 We call this the "classic" ATK, i.e. the closest to iBuildings' version. It's largely backward compatible, with no additional functions:
- lots of bug fixes
- added a Bootstrap theme
- improvements to Steelblue/Stillblue themes
- improvements to attributes (atkAttribute, atkDateAttribute, atkListAttribute, atkNumberAttribute, atkFieldSet...)
- improvements to relations (especially atkManyToOneRelation)
- improvements to search functionality
- better handling of dependencies
- better handling of form buttons and submit
- refactoring of meta fetching
- added a couple of utility functions
This is a deeply refactored version that's not backward compatible. It's been developed with the following objectives:
- composer support and PSR-4 compatibility
- a modern class system (PSR-1/PSR-2)
- PHP7 compatibility
- better handling of modules
- removal of deprecated functions
- no more themes, GUI is now Bootstrap-based
- Smarty 3 integration
- Select2 integration
Version like 9.0, but with jQuery only
This is the head of development. Currently it points to 9.1
Since we use both branches in production projects, pull requests for bug fixes are welcome, but we cannot guarantee to accept new features. Please get in touch before submitting such requests.
We kindly ask you to:
- Make pull requests by creating a feature branch from 8.2 or 9.0
- Don't branch from master
- Avoid redundant comments
- Keep PSR-2 formatting
- Make the PR's topic "tight", don't modify dozens of classes or the whole app
- Only add or fix a well-defined feature, keeping your changes small
9.0 and 9.1
Currently there's no documentation for v. 9. Maybe we'll manage to write some docs in the future. If you have one, please tell us.