Comments on: Thinking about wiki backends http://codemonkeyism.com/thinking-about-wiki-backends/ Wed, 09 May 2012 22:39:34 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: stephan http://codemonkeyism.com/thinking-about-wiki-backends/comment-page-1/#comment-141 stephan Tue, 01 Aug 2006 05:21:28 +0000 http://stephan.cintoo.org/archives/2006/07/28/thinking-about-wiki-backends/#comment-141 @Olli: 100% ack. @Olli: 100% ack.

]]> By: Olli http://codemonkeyism.com/thinking-about-wiki-backends/comment-page-1/#comment-140 Olli Mon, 31 Jul 2006 08:24:29 +0000 http://stephan.cintoo.org/archives/2006/07/28/thinking-about-wiki-backends/#comment-140 JCR is nice, the spec covers lot's of stuff and with 2-3 days work I was able to use versioning and metadata (with jackrabbit) and had my wiki prototype using radeox up and running. I need to check back again for the xpath queries in jackrabbit it had some problems as I tried it otherwise I will use JCR for everything wiki/blog/cms related I might do. I just don't want to deal with databases, object mappings or something like that anymore. JCR is nice, the spec covers lot’s of stuff and with 2-3 days work I was able to use versioning and metadata (with jackrabbit) and had my wiki prototype using radeox up and running. I need to check back again for the xpath queries in jackrabbit it had some problems as I tried it otherwise I will use JCR for everything wiki/blog/cms related I might do. I just don’t want to deal with databases, object mappings or something like that anymore.

]]> By: stephan http://codemonkeyism.com/thinking-about-wiki-backends/comment-page-1/#comment-138 stephan Fri, 28 Jul 2006 18:15:38 +0000 http://stephan.cintoo.org/archives/2006/07/28/thinking-about-wiki-backends/#comment-138 I think JCR is quite simple, and has a simple and clean concept. For my feeling though, Jackrabbit is a bit of a gorilla and could be thinner. A small JCR-driver over JPA would be nice. With JCR and Radeox it's very simple to start your own wiki. Yes, trac tries to be a wiki bugtracker, though the concept doesn't work with me. But a bug tracker on top of a meta data wiki might be easy to write. Something along #bug{ Posting does not work with Tomcat } somewhere in the page. Not too far. I think JCR is quite simple, and has a simple and clean concept. For my feeling though, Jackrabbit is a bit of a gorilla and could be thinner. A small JCR-driver over JPA would be nice.
With JCR and Radeox it’s very simple to start your own wiki.

Yes, trac tries to be a wiki bugtracker, though the concept doesn’t work with me. But a bug tracker on top of a meta data wiki might be easy to write. Something along

#bug{ Posting does not work with Tomcat } somewhere in the page.

Not too far.

]]> By: Tom Palmer http://codemonkeyism.com/thinking-about-wiki-backends/comment-page-1/#comment-137 Tom Palmer Fri, 28 Jul 2006 18:02:43 +0000 http://stephan.cintoo.org/archives/2006/07/28/thinking-about-wiki-backends/#comment-137 I personally think that JCR is too complicated. I don't mind the arbitrary metadata and versioning and stuff. That's great. I would just rather have a simpler core. Stated otherwise, the spec seems way too large to be the core that I want. And I'm also usually fonder Subversion-style versioning and atomic changesets and so on. I've hypothesized how I might like to see it, but I haven't dedicated any time to it. Maybe someday. I do like the idea of a combined wiki/blog like SnipSnap. I just don't like SnipSnap itself. I also wonder at JIRA and Confluence. Seems to me like a bug tracking system could almost just be a very simple module on top of a wiki. But I haven't much used JIRA or Confluence, so I can't speak much to them. And I've also gotten sidetracked from your original subject, but maybe not <i>too</i> far. Use cases are helpful in thinking about implementation. I personally think that JCR is too complicated. I don’t mind the arbitrary metadata and versioning and stuff. That’s great. I would just rather have a simpler core. Stated otherwise, the spec seems way too large to be the core that I want. And I’m also usually fonder Subversion-style versioning and atomic changesets and so on.

I’ve hypothesized how I might like to see it, but I haven’t dedicated any time to it. Maybe someday. I do like the idea of a combined wiki/blog like SnipSnap. I just don’t like SnipSnap itself. I also wonder at JIRA and Confluence. Seems to me like a bug tracking system could almost just be a very simple module on top of a wiki. But I haven’t much used JIRA or Confluence, so I can’t speak much to them.

And I’ve also gotten sidetracked from your original subject, but maybe not too far. Use cases are helpful in thinking about implementation.

]]>