5 Apr
2006
5 Apr
'06
4:05 p.m.
Hi, Lukas!
I can understand that a simple syntax keep it easy writing some content.
My intention was keeping fingertips writing my ideas in the wiki. On the other
side the idea using some sort of XML-tags bring us the possibility write
some extensions like a building set.
I'm not so familiar with XML but in my understanding of this we could bring
the translation to other formats into the tags. With an open repository of
these buildingblocks everybody can decide what he want.
The loosers in this kind of solution are my fingers ;-).
My mistake. Is it possible to add a comment "Do not touch, it's generated"?
Cheers,
Frank
Sure I can use
HTML but writing of such things written above is
much easier.
I tried to keep the syntax as simple as possible. However there were
several requests lately for that kind of things. I don't really know,
how we could implement that the simplest without bloating the wiki-
syntax and while keeping the visitors small that transform the AST
into different output-formats (HTML, Text, Latex, etc).
The best idea I cam up so far is to add some sort of XML-Tags that
can be parsed in a generic fashion, so that extensions can register
their own tags. Something along ...
<pier:indented>
The time is now: <pier:smalltalk>Time now</pier:smalltalk>
</pier:indented>
Would that help? Is something like that of generic interest?
I've been searching in the code for the place
of translation from
*..* and others to HTML and coming down to PRDocumentScanner
scanForToken and see the scannerDefinitionComment on class-side.
The next step to define a new element would be very interesting.
The scanner and parser is automatically generated from the respective
definitions using SmaCC, so you probably don't want to change these
methods manually ;-) If you only want to do some simple string
transformations when
generating HTML you could simply patch the methods from the protocol
#visiting-document in the class PRViewRenderer.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch