webAppKit blog

To content | To menu | To search

Tag - code

Entries feed - Comments feed

Tuesday 29 May 2007

doc updated, 0.8.1 onwork

By J.Ducastel on Tuesday 29 May 2007, 19:10 - news

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.

Friday 13 April 2007

more big changes

By J.Ducastel on Friday 13 April 2007, 23:09 - news

(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

Wednesday 11 April 2007

Generic resources

By J.Ducastel on Wednesday 11 April 2007, 20:38 - news

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.

Thursday 11 January 2007

Some activity

By J.Ducastel on Thursday 11 January 2007, 13:19 - news

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.

Thursday 21 December 2006

svn moving to googlecode

By J.Ducastel on Thursday 21 December 2006, 14:31 - news

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

Continue reading...

Thursday 14 December 2006

first rebuilt version available

By J.Ducastel on Thursday 14 December 2006, 20:28 - news

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.

Continue reading...

Wednesday 6 December 2006

Massive refactoring

By J.Ducastel on Wednesday 6 December 2006, 11:41 - news

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.

Continue reading...

3 comments