Hm … nur ein armer oo consultant … der das snipsnap.war nicht runter laden kann :-/
Hehe, der aber mittlerweile schon mehrere SnipSnaps erfolgreich aufgesetzt hat :D
You can reach my via mail as
angelo dot schneider at visualsphere dot deI'm chairman of VisualSphere Software Tools AG (
http://www.visualsphere.com) currently working mainly on Ivy/Ant build files and configuration/dependency descriptions for Enterprise Repositories. Besides that I'm an OO consultant teaching OOA/OOD/UML and Java as well as component architectures and SCRUM. I have a "private" web site on
http://www.oomentor.de. Finally I'm practicing and teaching an martial art called aikido and teach in the dojo: www.jiyukan.de.
You can find me here:
http://www.xing.com/profile/Angelo_Schneider.Another nice Wiki I'm experimenting with is a Wiki based one
prevayler (former
http://prevayler.org) here:
http://wiki.com.br/ (Site currently down?)
Proposed Improvements on Snip Snap.
Portlets
- more portlets
- several header horizontal portlets going from left to right
- several footer portlets going from left to right
- several portlets on the left side and several on the right side
- context sensitive portlets that overwrite the "default" wiki wide portlets
Rename the portlets
Portlets should be called e.g. snipsnap-portlet-left-X, where X is just an arbitrary numeric value.
The right side portlets are called snipsnap-portlet-right-X whereas the top would be snipsnap-portlet-header-X and the bottom snipsnap-portlet-footer-X.
Positioning the portlets
All portlets with the name snipsnap-portlet-left-X would be rendered top down on the left side according to the numbers, lowest first, highest last. All portlets with the name snipsnap-portlet-right-X, would be rendered on the rigth side accordingly. The snips with the names snipsnap-portlet-header-1 to snipsnap-portlet-header-5, would be rendered top down just above the standard wiki line with "Start | Index | log on … ". The snips with the names snipsnap-portlet-header-6 and higher would be rendered just below that line of links.
In the same way the snips with names snipsnap-portlet-footer-X would be rendered top to down starting with 1 below the page.
Overwriting the wiki portlets
The wiki owner defines the left and right portlet. But the creator of a snip should be able to overwrite any portlet (probably restricted by configurations).
So if an author creates a snip called "myTopic" he could create child snips called "myTopic/snipsnap-portlet-left-1" etc. to get the wiki wide portlets replaced by his own portlets. Just like in an OO language where derived classes redefine override base classes behaviour.
this users snips: (27)
1-1, 1-15, 1-23, 1-24, 1-25, 1-3, 1-31, 1-4, 1-4, 1-8, 1-9, Groovy Scripting-5, How-To link to files attached to a Snip-3, aos, comment-Core Technology-1, comment-FAQ-83, comment-Groovy-17, comment-Groovy-18, comment-Papers-2, comment-UML Sketching-4, comment-User management-4, comment-Web Services-7, comment-aos-1, comment-juri-1, comment-snipsnap-download-18, graph macro test-11, snip revision history-2