Personal tools
You are here: Home   Blog   Archive   2006   July   03   Report from mini-sprint  
Document Actions

Report from mini-sprint

by Balazs Ree last modified 2006-07-03 12:49
Filed Under:

The Azax core developers featuring Godefroid Chapelle and Balázs Reé have had a 3-days mini-sprint on KSS in Belgium, in the BubbleNet headquarters. We would like to report about the work done since the Archipelago sprint.

  1. We were looking for a new name to replace 'kukit" : we have decided to call it officially "KSS" since this is the most visible part of the framework. The Zope support is still called Azax and the Plone product PloneAzax. (The javascript file keeps its name "/blog/archive/2006/07/03/report_from_mini_sprint/view/kukit.js".)
  2. We revised Balázs's KSS2 format. KSS2 had improvements to the syntax proposed at the archipelago. It had grown out the implementation of the first use cases. We have kept large part of the improved semantics of KSS2 but we have switched back to a syntax closer to the original proposal. We think we have come to a stable KSS syntax.
    We have put the new implementation on the trunk and updated all sample products to work with it. Docs will be brought up to date as well.
  3. We fulfilled our promise made at the Archipelago sprint, and showed how existing programs written with prototype, without any previous consideration to KSS, can be transparently hooked into KSS event binding and KSS's command marshalling architecture. At the moment it just works with a single example. The same can be done with existing Bling components, although we have not demonstrated that yet. The codename of the project is "bluekit".

There is a lot to be done on the framework:

  • refactor the code
  • add missing features
  • evaluate with use cases
  • wrap up scriptaculous and Bling components into kss plugins to have some "effect lib"
  • finalize the plugin API
  • write tutorials, documentation

But it is now finalized to the level that other developers can start experimenting with it. And so the most important part begins: start to use it with real Plone usecases, and find out if additional support is needed from the framework. Also design a consistent look and feel of ajax for Plone.

It would be nice to have a sprint on this subject, where the main focus would be the Plone UI itself, but with the framework developers present to support the different teams. Nothing has yet been decided but it's in the plans.

Please visit this page to have information about the current bundles.