Posts in category trac

Upcoming WMI2 internals (and new repo in Trac)

The following schema tries to explain how the future WMI2 is working. This architecture is already fully functionnal in our development repository and will enter stable branch soon (official due date: March 5th, 2012). We are currently in the process of polishing it before releasing the patch.

The new WMI will be a huge step forward interactive and web-2.0-like interface ; everything can be handled asynchronously, and the WMI can update any part of its interface without refreshing the whole page. It is even a fully-featured Django + Jinja2 + jQuery application, which runs on top of our new webserver. The webserver is fully WSGI compliant, and built on top of the great gevent co-routine-based library.

RPC Events Arch for WMI2

As a side note, I've now integrated the WMI2 repository into Trac to help follow the changes and global Licorn® activity. Without this, one could think that Licorn® development is halted, because it all happens in this separate branch, until its merged into the stable one.

Switch back to darcs (and forth to Trac 0.12)

After having used bzr for a few months, we switched back to our beloved darcs. Bzr is not bad per se, but darcs is much more smooth, easy and powerfull when it comes to merges, which is what we do most of the time: small corrections of small bugs, pushed and pulled from/to dev branches. The concept of branches in bzr is a little bit more, we can't forward patches on branches with uncommitted code, which is a pain (darcs does this magically if the patch concerns untouched files). The concept of selective pull/push is a great help, too.

I used the pretext to upgrade Trac to 0.12 (migrated from 0.11.7 which was in production only since a few days, migrated from 0.11.1).

Everything seems to work very fine (at least in Trac), but I haven't commited since darcs migration. I will do in the next hours.