G
Gavin Kistner
As noted in passing in another post, I'm writing a library (like =20
RedCloth) for turning a specific text markup syntax into HTML/XML. =20
OWLScribble is this work in progress, and it's working pretty well =20
right now!
For information on the markup syntax itself:
http://phrogz.net/RubyLibs/rdoc/OWLScribble/markup.html
For information on using the OWLScribble class:
http://phrogz.net/RubyLibs/rdoc/OWLScribble/doc/index.html
=46rom the intro documentation:
"OWLScribble converts a specific set of text markup into HTML. (The =20
syntax used in the markup is a knockoff of the markup used by =20
OpenWiki, so the =91OWL=92 in OWLScribble means "OpenWiki-like".)
The tree of elements created during parsing is made available, along =20
with collections for specific types of elements, such as a list of =20
all wiki-commands or wiki page links. This lets you modify the =20
element tree (e.g. perform a database lookup on pages and replace the =20=
links with html anchors to your URL) after parsing, but before =20
creating the HTML string."
I'm not yet cool enough to know how to make this into a gem. I hope =20
to do that in the next week or so as I get near release quality. =20
(Right now, there aren't enough unit tests for me to feel good about =20
calling this ready for the wild, and there are a couple minor tweaks =20
I may want to make to the markup syntax.)
I certainly appreciate all feedback -- positive and negative -- =20
regarding the quality of the documentation, efficiency of the code, =20
or features/interface in the class.
RedCloth) for turning a specific text markup syntax into HTML/XML. =20
OWLScribble is this work in progress, and it's working pretty well =20
right now!
For information on the markup syntax itself:
http://phrogz.net/RubyLibs/rdoc/OWLScribble/markup.html
For information on using the OWLScribble class:
http://phrogz.net/RubyLibs/rdoc/OWLScribble/doc/index.html
=46rom the intro documentation:
"OWLScribble converts a specific set of text markup into HTML. (The =20
syntax used in the markup is a knockoff of the markup used by =20
OpenWiki, so the =91OWL=92 in OWLScribble means "OpenWiki-like".)
The tree of elements created during parsing is made available, along =20
with collections for specific types of elements, such as a list of =20
all wiki-commands or wiki page links. This lets you modify the =20
element tree (e.g. perform a database lookup on pages and replace the =20=
links with html anchors to your URL) after parsing, but before =20
creating the HTML string."
I'm not yet cool enough to know how to make this into a gem. I hope =20
to do that in the next week or so as I get near release quality. =20
(Right now, there aren't enough unit tests for me to feel good about =20
calling this ready for the wild, and there are a couple minor tweaks =20
I may want to make to the markup syntax.)
I certainly appreciate all feedback -- positive and negative -- =20
regarding the quality of the documentation, efficiency of the code, =20
or features/interface in the class.