(i'm evil)

As i was not happy with previous packages/resources system, i've trashed and recoded it - again. It was starting to be bloated and complex, and not that agile. So, to summary :

Packages are renamed to kits. A single class, webappkit, is used both as kit instances and global API (through its static methods). Kits can contain kits themselves, and kit names are made upon the physical tree (databeans/datetime for example).

A INI metadatafile, named wak.ini is required at the root of the kit. With this we take care of dependancies, both internal and external. For more flexibility, a wak.init.php may be included, if present, when the kit instance is built. A wak.run.php may also be present, and will be executed upon call of its run() method.

Services and non-code objects storage have to be implemented at this point. But various library packages have been converted to the new standard :

  • databeans
  • pathnodes
  • djangotpl
  • Spyc