webAppKit blog - Tag - code

doc updated, 0.8.1 onwork

J.Ducastel — Tue, 29 May 2007 19:10:00 +0200

Almost everything is in the title.

Code documentation has been updated and is still available at code.webappkit.net.

Version 0.8.1 is onwork. Here's the news :

Kits resources loading is now separated from kit instance retrieval. Methods $webappkit->load() and webappkit::loadkit($id) have been added, which are not called by webappkit constructor.
webappkit::timecounter() and $webappkit->loadedWeight() have been added to help optimization.
Admin index (when calling url /webappkit from your app root) is not static anymore. It still includes micro tutorials, but provided kits list is now dynamically built from actual kits.
A new pathnodes subpackage is being worked on : webappkit/pathnodes/od which stands for Open Document.

more big changes

J.Ducastel — Fri, 13 Apr 2007 23:09:00 +0200

(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

Generic resources

J.Ducastel — Wed, 11 Apr 2007 20:38:00 +0200

The previously announced move has been started. Packages resources will be made generic, so their access and management will not be devoted to packages directly but to type-specific implementations of a generic resource class. Here's a changelist :

A new interface : wakResource, and a first, incomplete, implementation : wakResource_class. wakResource_service, wakResource_template to follow.
Changes have been made to wakPkg methods
The package metadata file format has also changed.
As a side note, the trunk compability will now include both PHP4 and PHP5, with an automatic switch between resource instances. Current move has still to be ported to php5, though.

Some activity

J.Ducastel — Thu, 11 Jan 2007 13:19:00 +0100

In no particular order :

Home page has been updated, with links to googlecode pages.
Branch 0.5 has been added to subversion, for history purposes, and because some web apps are still using it.
Some minor work has been done to the source and wiki documentation.

svn moving to googlecode

J.Ducastel — Thu, 21 Dec 2006 14:31:00 +0100

As a good google slave, i've decided to move webappkit from sourceforge to googlecode, which has been recently improved. => webappkit on googlecode.

Google added a wiki and downloads to their open-source projects hosting offer. Coupled with their faster subversion server, issue tracking and neat web interface, it's now a good choice for project hosting.

I took the chance to change folders struture a bit. Legacy branches are now under branches/ as 0_7_php4 (the old php4, microkernel architecture) and 0_8_php4/ (the new packages architecture, but php4 version). Under trunk/ is the onwork php5, packages architecture, which may be released as 0.8 later.

Additionaly, some pages are available on the google-hosted webappkit wiki. The old, self-hosted one will be trashed soon.

first rebuilt version available

J.Ducastel — Thu, 14 Dec 2006 20:28:00 +0100

I've just added php5 to repository (revision 150). As announced, there are some huge changes in process. Basically, WAK is moving from a generic micro-kernel for web apps, to a packages architecture for web apps.

Packages are the new central interface. A package is a folder containing an index/metadata file (wakpkg.yml) describing provided resources. Thoses resources will be accessed through a wakpkg instance. Resources can be :

class definition files
services (named singleton within the package namespace, extending from wakservice class)

Class dependancies will be handled provided they are described within the metadata file.

Massive refactoring

J.Ducastel — Wed, 06 Dec 2006 11:41:00 +0100

After some doubts on project future, i have decided to keep on working on webappkit rather than dropping it for some existing frameworks. I've been looking at Django, Symfony and CakePHP. Django is by far my favorite, and i use it to practice my python. However PHP is still the most used language, and i think that webappkit approach still makes sense.

But i'm going to rewrite big parts of the project, focusing on packages since the beginning rather than a virtual layer on the top of the internal structure. Packages will have a physical representation as directories, and may provide their own libraries, services etc. They may have their own request handler.

The core components will theirselves be shipped as a package. It will provide a small api giving access to packages, services and libraries. Some basic requests handling libraries and services will be provided, but this task may be forwarded to one or more package(s). Think to webappkit as a meta-framework.