So, I promised some updates on BlueJ development plans. Let’s see whether I can keep my good intentions at least for a day, and tell you something about what’s going on.
The most interesting new bit of functionality that we are working on for BlueJ is team work support. When this is done, student teams should be able to cooperate easily by using BlueJ.
The support for team work is the only large bit of functionality that is currently planned for release in the near future.
The team work support is based on CVS (with subversion support planned for some time in the future). BlueJ will integrate a simplified interface to CVS, so that some of CVS’s nastier sides are hidden.
The BlueJ team functionality will concentrate on the file sharing aspect of CVS, and ignore other functionality (such as version rollback). As with other BlueJ tools, the aim is to have an interface that is easy to understand, and gives you the 90% most used functionality.
BlueJ will support setting up projects as “shared projects” (by creating a repository on a CVS server) and the usual commit/update functions. Files that are added or deleted will be automatically included in the commit/update, and the BlueJ diagram layout can optionally be included as well.
The team work support was first investigated by Kasper Fisker as part of his Masters degree, and the implementation is now being finished by Bruce and Davin, our Australian branch of the BlueJ team. So expect the CVS commands to come across with an Australian accent.
We are planning to release a beta version of the teamwork support first (in a couple of weeks) and then have a full version available some time later.