Basic version works in CVSWe thought about adding unified
Namespace support to
SnipSnap. This will look like this:
start/2002-02-01 for posts
JDBC/ResultSet
SnipSnap/Documentation
Funzel/comment-1
The flat namespace has to be integrated to keep linking easy. This namespace support makes it easier for us to support multi weblogs in one space. Could be extended to
/C2/WikiWiki instead of WikiWiki@C2
The problem is, how to integrate our P2P ideas for SnipSnap federation with the namespace support for SnipSnap federation. /P2P-Domain/WikiWiki should show all snips with WikiWiki in the P2P-Domain "P2P-Domain" ?
More thoughts on namespaces
(added by ejoftheweb, 11 nov 04)
Namespaces enable much better structure in snipspace, but it would be helpful if there could be an editing shorthand for them. There's an anomolous behaviour: the new button creates a snip as a child of the current snip, but snips created during editing as links from a current snip are created in the root namespace.
I would suggest the following:
while editing start/foo/bar/snip :
- [newsnip] creates or links to start/foo/bar/snip/newsnip;
- [~newsnip] creates or links to start/foo/bar/newsnip;
- [~~newsnip] creates or links to start/foo/newsnip;
- [/newsnip] creates or links to start/newsnip;
thus, by default, links create child snips although you could have a theological discussion as to whether it would be better to create siblings.
Shouldn't we use "." in place of "~" to mirror the de facto behavior of URLs?Yes, good idea, it doesn't really matter what character you use so long as no one is likely to want to use it to start a snip name. Besides, two tildes are already used to open italics! Probably the syntax should be either exactly the same as, or completely different from, the unix shorthand, to avoid confusion.
Web Start Demo!Resources
Powered by SnipSnap 1.0b3-uttoxeter 
