On Mon, 10 Dec 2001, Jeb Bateman wrote:
> I had some ideas on supporting different patterns for wiki, based on
> experience I had long ago creating something called the 'patterns
> plugin' for a web authoring enviornment I don't use anymore...
> Anyway, the idea of that code was very similar to wiki, in that you
> use simple shorthand markup to write html. The main difference was
> that users had the ability to create their own patterns, based on the
> needs of their specific page or website.
> I was thinking something similar could be done for wiki, to support
> multiple "sets" of patterns, via a popup menu in the EditText page, or
> individual patterns via checkboxes. Of course, the drawback to this
> type of flexability is the possibility that pages could be broken by a
> change in pattern selection, for example. There might also be ways to
> work around that problem. Anyway, just a thought I've been meaning to
> share, and I might have time to work on in the future...
Hmm. I guess in an ideal world, the default markup the user sees is the
one we feel is easiest to understand; but in user options, they could
choose any markup scheme they like (those of other wikis, or limited html,
or roll their own.)
This would, again, require storing the page content in some intermediate
format, like xml, and converting to the user-chosen markup whenever they
decide to edit a page.
Just thinking out loud.
> On Fri, Dec 07, 2001 at 12:14:53AM -0500, Steve Wainstead wrote:
> > I'd like to move (again) to a syntax like the NBTSC Wiki, which is in line
> > with suggestions by many users over the last two years. Ali went for
> > syntax that is a lot like how people do things in plain text elsewhere:
> > *bold*
> > /italic/
> > I think are two examples. Ali's reasoning was the marked up page language
> > should be as easy to read/understand as the rendered page.
> > Now, the one thing that has troubled me about both the plugin syntax and
> > the proposed plain text tags is they are not consistent with the markup to
> > date... and inconsistency is not good for the user. As PhpWiki grows in
> > features, though, I understand it gets harder to maintain consistency.
> > I'd like to see some proposals that are consistent with our current
> > syntax, or some way that would be compatible with NBTSC syntax.
> > ~swain
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
-- Frank Zappa