Comments on Codeholic's Codex: JavaScript Creole 1.0 Wiki Markup Parser

Hi folks, this is a very nice parser for Creole 1...

2010-06-04T14:55:57.574-07:00

Hi folks,

this is a very nice parser for Creole 1.0. I'm using it too and I've writen an online editor for Creole Markup language. If you want to add it to your Wiki- or CMS-Software please feel free to visit Creoledit homepage to get an equivalent editor.

Hello, thor! You can either make a subclass of Par...

2010-01-30T01:42:45.135-08:00

Hello, thor! You can either make a subclass of Parse.Simple.Creole or just make a Parse.Simple.Creole instance and override some grammar rules, e. g.:

g = this.grammar;
g.leftPanel = { tag: 'div', attrs: { class: 'left_panel' }, regex: /(^|\n)[ \t]*<<([\S\s]*?)<</, capture: 2 };
// other rules here ...
g.root.children.push(g.leftPanel, g.rightPanel, g.horzPanel);

DISCLAIMER. The code above hasn't been tested and is not supported. Particularly, it clashes against some proposed WikiCreole standards, see http://wikicreole.org/wiki/CreoleAdditions

thor, you are welcome to publish your final code here (or give a link to an external page) to illustrate how one can add his own grammar rules.

I've just come across this parser and it's...

2010-01-29T12:55:45.811-08:00

I've just come across this parser and it's working great for me. I would like to be able to customise it by adding DIV's though - 3 simple div's with set classes, but having looked at the code for a while I'm still none the wiser as to how to implement that...

Anybody able to give me a few pointers in the right direction?

What I want is:

Markup: << content <<
HTML: < div class="left_panel">content

Markup: >> content >>
HTML: < div class="right_panel">content

Markup: ^^ content ^^
HTML: < div class="horz_panel">content

Any help would be greatly appreciated!

Thanks

In fact it does... sorry ! keep up the good work !...

2009-10-29T21:19:59.288-07:00

In fact it does... sorry !
keep up the good work !

Hello ! Heading tags don't seem to work ! Than...

2009-10-29T21:17:38.183-07:00

Hello !
Heading tags don't seem to work !
Thank you !

Wow, this is awesome. I hope more wikis adopt the ...

2009-10-25T09:13:52.759-07:00

Wow, this is awesome. I hope more wikis adopt the WikiCreole standard.

Thanks for sharing!

~Mikeumus

I've spent a few hours this morning adding mor...

2009-07-27T18:30:16.437-07:00

I've spent a few hours this morning adding more improvements to your creole parser. Mainly I've added the ability to have pre-processors, eg:
{{{
#!html
<p>Hello World</p>
}}}

etc...

Can we converse via email instead of clogging up your blog ? :)

My email is prologic at shortcircuit dot net dot au

cheers
JamesMills

I did something very similar :)

2009-07-27T15:21:13.975-07:00

I did something very similar :)

An easy way to implement extensions is like this: ...

2009-07-27T13:28:20.473-07:00

An easy way to implement extensions is like this:

if (options && options.extension instanceof Function) {
g.extension = { capture: 1, regex: /<<(.+?)>>/,
build: options.extension };
g.root.children.push(g.extension);
}

Then you can use it like this:

options: {
extension: function(node, r, options) {
data = eval(r[1]);
if (options && options.forIE) {
// workaround for bad IE
data = data.replace(/\n/g, ' \r');
}
node.appendChild(document.createTextNode(data));
}
}

input: "<<'some' + 'text';>>"

output: 'sometext'

Oh one more thing. I think your code could benefit...

2009-07-27T12:54:37.327-07:00

Oh one more thing. I think your code could benefit (very much so) if you were to use the mootools library. Just the core mootools library that provides classes and far nicer ways of extending and writing interfaces.

I don't know enough about your code to help you, but I'll be integrating it into a mootools Class and adding extra bits and pieces to it.

cheers
JamesMills

Okay I look forward to it! I've just finished ...

2009-07-27T12:20:28.832-07:00

Okay I look forward to it!
I've just finished the latest version of my wiki (I rewrite the UI in mootools): http://124.171.217.91:8000/

Source: http://124.171.217.91:8000/source/

I look forward to a new and flexible creole parser - I especially need Plugin support :)

Would you mind taking a look at my wiki engine ... I (as yet) don't have any idea how I'm going to implement Plugin extensions

--JamesMills

pyparsing is too complicated. I found Spark, that's almost what I looked for. I'll try to translate it into JavaScript.

> Can we not make it simpler and define some as...

2009-07-24T02:07:35.430-07:00

> Can we not make it simpler and define some assumptions

Yes, I thought about it too...

Thanks, I'll take a look.

2009-07-24T02:03:24.008-07:00

Thanks, I'll take a look.

Also in regards to your earlier comment ... Can we...

2009-07-24T02:02:17.606-07:00

Also in regards to your earlier comment ... Can we not make it simpler and define some assumptions (if it's too hard to implement the plugin extension according to the spec ?)

For example, in Trac's wiki I don't believe it's possible to have [[FooMacro(...)]] in any other markup.
Trac's wiki also allows you to use those same macros in processors:

{{{
#!FooMacro
...
}}}

cheers
James

I'm a Python developer (hence my project circu...

2009-07-24T02:00:32.552-07:00

I'm a Python developer (hence my project circuits and circuits.web). Have you looked at pyparsing ?

cheers
James

The only problem with extensions, and the only rea...

2009-07-23T22:38:23.621-07:00

The only problem with extensions, and the only reason I still have not implemented them yet, is that according to the specification, "the content of the extension element may contain any text, including line breaks, except for the opening and closing extension element markup-codes".

The parser used in this Creole markup implementation requires that you describe all possible content elements may contain. (It's why Chris Purcell called this parser "regular language" recursive descent parser.)

According to the spec, "the extension element markup may be nested in any other markup". It means it may contain the text, identical to closing markup-up codes for other elements.

So, in order to implement the extension element in accordance with the spec, you have to assume in your regexp, that virtually any container element may contain extension elements, which may contain any text, including closing markup for the parent element. It's quite a task to implement, you know.

I had enough puzzles working with this parser engine, and sometimes I thought that it would be easier to implement a toothier parser engine than to describe the grammar, that this parser engine can chew. Do you know maybe a simple implementation of context-free grammer parser generator in any imperative programming language? I would translate it to JavaScript then. Please don't recommend JS/CC, it's an overkill. I don't like such solutions.

FYI, I'm developing a heavily client-side (usi...

2009-07-23T21:20:09.748-07:00

FYI, I'm developing a heavily client-side (using jquery) based wiki with a restful backend and mercurial storage using circutis.web

Demo: http://124.171.217.91:8000/ (may be intermittently offline)

cheers
James

I meant the "Plugin" addition - yes. Of ...

2009-07-23T21:13:07.929-07:00

I meant the "Plugin" addition - yes. Of the form:
<<Plugin(arg1=foo arg2=bar)>&ht;

I've managed to extend your parser to do this in the simplest possible way by adding the following:

plugin: { regex: '\\<\\<((?!\\<)[^ >\\n]*(?:}(?!})[^|}\\n]*)*)>>',
build: function(node, r, options) {
if (options && typeof(options.plugin) != "undefined") {
options.plugin(node, r, options);
}
} },

My low-level JavaScript ain't that great though and I'm unfamiliar with your parser design (not necessary recursive descent parsers).

I look forward to your improvements :)

--JamesMills (prologic)

Yes, I'm planning to implement additions. Shall I let you know when it is available?

Or did you mean something else by "* Plugins"?

Hi, Is it possible to extend this JavaScript creol...

2009-07-20T10:07:45.023-07:00

Hi, Is it possible to extend this JavaScript creole parser to include support for creole additions such as:
* Plugins ?

--JamesMills

sbarkdull, I've supposed that Creole requires a ti...

2009-02-03T15:13:00.000-08:00

sbarkdull, I've supposed that Creole requires a title for an image to be set, since there's no example for an image w/o a title anywhere on WikiCreole. Perhaps, it should be clarified.

For now, you can insert an image with an empty title instead, for instance, {{http://www.performancebike.com/images/hd_teamp_07.gif|}}

Hi Ivan,

Thank you for the parser! Nice job...

2009-02-03T13:49:00.000-08:00

Hi Ivan,

Thank you for the parser! Nice job.

It looks like the image element is broken. When I paste this:
{{http://www.performancebike.com/images/hd_teamp_07.gif}}

into the creole markup, it doesn't generate an HTML image.

BTW, here's original Chris Purcell's parser.

It is! See http://jscreole.svn.sourceforge.net/viewvc/jscreole/

Comments on Codeholic's Codex: JavaScript Creole 1.0 Wiki Markup Parser

Hi folks, this is a very nice parser for Creole 1...

Hello, thor! You can either make a subclass of Par...

I've just come across this parser and it's...

In fact it does... sorry ! keep up the good work !...

Hello ! Heading tags don't seem to work ! Than...

Wow, this is awesome. I hope more wikis adopt the ...

I've spent a few hours this morning adding mor...

I did something very similar :)

An easy way to implement extensions is like this: ...

Oh one more thing. I think your code could benefit...

Okay I look forward to it! I've just finished ...

pyparsing is too complicated. I found Spark, that's almost what I looked for. I'll try to translate it into JavaScript.

> Can we not make it simpler and define some as...

Thanks, I'll take a look.

Also in regards to your earlier comment ... Can we...

I'm a Python developer (hence my project circu...

The only problem with extensions, and the only rea...

FYI, I'm developing a heavily client-side (usi...

I meant the "Plugin" addition - yes. Of ...

Yes, I'm planning to implement additions. Shall I let you know when it is available?Or did you mean something else by "* Plugins"?

Hi, Is it possible to extend this JavaScript creol...

sbarkdull, I've supposed that Creole requires a ti...

Hi Ivan,Thank you for the parser! Nice job...

BTW, here's original Chris Purcell's parser.

It is! See http://jscreole.svn.sourceforge.net/viewvc/jscreole/

Yes, I'm planning to implement additions. Shall I let you know when it is available?

Or did you mean something else by "* Plugins"?

Hi Ivan,

Thank you for the parser! Nice job...