SnipSnap development has ceased…

Not actually news, but an important information for anyone who comes to this site. We have stopped development of SnipSnap as a whole. We still use it in several projects and use some components for a wiki toolbox in other projects, but the product itself will stay as it is right now.

The reasons are simple, the two main developers have changed their work. While Stephan left FIRST for various reasons, Leo has moved to South Korea to take up a job as Representative for the Institute.

SnipSnap binaries of the latest version and the source code is still available and you are free to work on it. Everything is available. Leo will try to answer questions and help if needed.

The development of our base component Radeox is not affected by this!

We thank all our users and those who have taken part in making SnipSnap quite successful. If anyone has the time and would like to take over, please contact for work out the details.

Your SnipSnap Team.

SnipSnap @ WikiSym 2006

We will be attending the WikiSym 2006 from Monday till Wednesday.

Stephan gives a talk on the Radeox Wiki Render Engine.

SnipSpace Access Example

I wrote a small example how to use the SnipSnap Space directly without all the gui stuff. Its not yet optimized to only include the relevant jars and classes, but serves as an example how to access a snip space.

Java 1.4 compatible packages

I have recompiled the download packages using a target JVM mode for 1.4. This should remove some of the compatibility problems we have had for some time. SnipSnap should now run on Java 1.4 systems.

Basic Auth for Uttoxeter

I have patched the Basic Browser Authentication back to SnipSnap Uttoxeter and put together a package that contains the new feature:

SnipSnap 1.0b3-uttoxeter (with Basic Authentication)

SnipSnap picking up speed again …

What a nice thing it can be to use the train. I used the time to put a hand on our biggest problem: a non-functional development branch, the trunk. I have managed to fix a lot of bugs related to redundancy. It is a big move away from the monolithic system to more components.

In addition to that I took the opportunity and implemented some pending authentication schemes like Basic authentication (what you know from your browser) and added a version of X509 Certificate authentication. Its configurable from the Expert pane in SnipSnaps setup.

The biggest change that separates uttoxeter from the main trunk is the introduction of a permission framework to allow for fine grained security. Now that I have most of the other code running we will get faster to the next SnipSnap release.

Currently, this is all in our Subversion Repository.

JSR 283

As I' currently adding support for JSR 170, I wanted to let you know that we are on the JSR 170 successor expert group

http://www.jcp.org/en/jsr/detail?id=283

Java wikis should all use the content repository API as (one of) their backend (JCR) and use the same name tags, this would make it much easier to switch wikis or work with different wikis on the same content.

WikiSym Wiki

There is some talk on the wikisym wiki,

http://www.wikisym.org/wiki/

were we are discussing wiki topics, especially wiki standards.

Releases

I thought a lot how to do releases with plugins and components from different developers. Should the developers vote when to release? Say 5 sub-projects vote for a new release, there will be a new release. Something like that.

svk works

I followed the short svk tutorial and it worked. The .dmg of svk works very nice out of the box.

svk feels good, I can have several local repositories or branches for different features, svk will build patches/diffs for changes so I can merge my local branches at will. Great! Others can still use svn with the central repository.