Hi, Ian Bicking hat gesagt: // Ian Bicking wrote: > In my own Wiki, I tried to create a Wiki markup that was translatable to > HTML and back again -- so that the Wiki markup wasn't the canonical > representation, the HTML was. There were some bugs in it (with lists, I > think) -- you can see a bit more at http://wiki.colorstudy.com -- but it > seemed like something of a beginning.
I know your Wiki a bit, but unfortunately I couldn't install it correctly. There were some errors with modules not found, that I could solve somehow with symbolic links like "Local -> lib/Local", I don't remember the details. But then I didn't dig deeper, because on my webspace I don't have the MySQL Python module and the Python devel packages neither: my webmaster is a Perl guy :( That's why I looked for a simple, DB-less solution. I'm actually not too happy with PyDiddy, because everything is so tied up into one class. I like your modular, more OO'ish approach more, it's easier to extend. I do like the name of my Wiki more, of course :) > My interest in Wikis has been revived lately, and I'm particularly > interested in using them as the basis for a CMS system. I'd like to see > the richness of something like MoinMoin, in with the added functionality > being more encapsulated... instead of creating an extensible Wiki > language, creating a richer namespace where all pages aren't Wiki-style > pages (e.g., to create a comment board, maybe you'd "transclude" a > another page, and that target page would be plugged into a comment > module). As a CMS, of course, you'd also have to offer some sort of > hardening, templates, and all sorts of other features... but while those > are all work, they all seem pretty straight-forward. This sounds very interesting, although there might be some fundamental differences between a Wiki and a CMS. For example in a CMS you have a Workflow and Delayed Publishing, something you could of course build into a Wiki, but it would somehow be against the whole idea of a Wiki. Then in a CMS you need (invisible) meta information, while in a Wiki the only meta information is always visible in the form of embedded links. But I think, that a Wiki could form a great demonstration app for Webware in general. Webware is something, that is easily explained to developers, but if a normal user installs Webware, there is nothing to see right away. Is this a CMS, how do I use it? - he might ask, but other than the Example pages there is nothing to see. Maybe Webware should come with a Wiki or something similar right from the start? ciao -- Frank Barknecht _ ______footils.org__ ------------------------------------------------------- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v? http://www.sun.com/javavote _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
