Getting started

For Kit Builders

Loading a library Kit

Webappkit archive should be unzipped at the root of your website. Before including a Kit, insert once this line into your script :

// loading Webappkit core files include('webappkit/include-me.php');

When you need a library kit, like example, load it with :

// loading example kit library files webappkit::loadKit('example');

Webappkit allows Kits nesting and use a dot syntax to access nested kits. If you need only a subkit, let's say hello within example, load it with :

// loading hello subkit from example kit files webappkit::loadKit('example.hello');

In this example, example.hello require example.base. But you don't have to worry about that, thanks to internal dependancies handling.

How it works

When you load a kit, Webappkit searches into the kits root folder (usually webappkit/) a folder with this name plus .wak, And reads its meta-data file wak.ini. This file describes kits dependancies which will be loaded, then own kit's files to load.

If you target a subkit, Webappkit will crawl through physical kits tree to find the targeted kit. So example.hello.world references the kit folder example.wak/hello.wak/world.wak/.