Software Developing: SnipSnap and Snip It 
Well it seems that a few days ago Leo
announced what everyone already knew, SnipSnap Development has ceased. I already knew it, but it's with great sadness that I've read the announcement.
I also must say that I was surprised to see that someone mentioned me on the comments as a "side developer", it seems there are more people aware of my work with snip it than I thought.

Regarding the snip it development a new version has been deployed and for the first time I actually put as version 1.0-snipit. The major differences are the suggestions that
derjohn gave about the weblog are now implemented.
A "Next Page" - and also a "Previous Page" when appliable - link is present now at the top and the bottom of the blog, it allows any reader to navigate among older posts, being able to go from page to page until the end of the blog, or come back until the first one again.
Besides this idea of navigation - which was a really good one -
derjohn also suggested that there should be a way to shorten blog entries. Now, this isn't as simple as it seems because, we can't limit:
- The HTML render length since that could generated invalid HTML.
- The raw text length because it could generated invalid wiki tags.
After putting some thought on it I realised that a good way would be to limit by paragraphs number, even if can originate some slight variations between posts size it's a good measure - as probably many other that I haven't think of - and does not generate invalid HTML nor invalid wiki tags.
To use such feature, it's only needed to define
numberOfParagraphs variable in the weblog macro.
Unfortunately the Access Control isn't yet fully finished, so I'll keep that subject for another post.
The modifications can be downloaded from SVN.
Anyone with more feature request or interesting ideas is invited to register and comment or edit the
my_snipsnap_fork_feature_list.
- To make it possible to run two "snip its" in the same server
- To improve the preview feature
:)How can such tools help a company in one or more projects? Well it's not that hard, a wiki by definition is a collaborative tool that can be used for knowledge sharing and collaborative developing. The blog plataform can also help in such cases like milestones publishing, change logs, etc where the team wants to give a special focus - and meaning - to a given page (being just a simple wiki page as any other can make it blend in the background).Another interesting feature is that SnipSnap allows in its core to be created Taxonomies and map any content you want inside the system into that taxonomy, although the interface isn't the best to do it, the functionality and the idea it's there.Also another interesting functionality, and that in my opinion is pretty handy, is that any snip within the wiki can have comments. This is interesting because a wiki only can generate collaborative content, although, to generate collaborative content and discussion about that content it's not that easy, snipsnap does it very well.It supports extension through macros and filters, both types can be easily created by anyone with the basic knowledge of Java.These were the points I can recall now… but I'm sure there are probably many more.