On Mon, 2002-10-21 at 08:52, Frank Barknecht wrote: > Hi, > Stephan Diehl hat gesagt: // Stephan Diehl wrote: > > > What irks me every time I'm looking a some Wiki is the fact that everyone is > > using a different markup (besides the WikiWords of course). Maybe it's time > > to let the author decide what markup he wants to use and provide different > > wiki dialect plugins. > > This is a great idea, but probably needs to be part of a greater > project. I think, I'll have a look at the OriginalWiki-Markup (from > c2.com) and make PyDiddy compatible to a least this one. > > Or to StructuredText???
Very cool. I messed around with a Wiki some as well, though I haven't really done much with it for a while. I think StructuredText would be a definite possibility -- I've started using it for documentation, and I'm pretty pleased. There may definitely be some speed issues -- but I think these could easily be solved by caching the HTML. I've never liked Wiki markups that much. TEXTAREA is a crappy editor, WikiWords bug me, and rules like "three spaces then a *" seem really arbitrary to me (not to mention error-prone). 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. IE has some neat features for editing pages inline, and I wanted to take advantage of them (and someday I hope Mozilla has analogous features -- there's some work on that in 1.2, I think). Reversible translations were important for that. If that interests you, feel free to use that code or look at it for ideas. 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. Ian ------------------------------------------------------- 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;7576298;k?http://www.sun.com/javavote _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
