I'm sure I missed something in the above, I was skimming pretty fast...
I have, for example, a pretty hefty macro to create a navigation menu
(corporate standards for look/feel, plus some pretty fun prototype
stuff to add in dynamic bits.. ). It's a pretty awesome piece of
code.. but it is 100%
On Sep 20, 2007, at 5:14 PM, Sergiu Dumitriu wrote:
Sorry for the late reply, I didn't see your mail.
HTMLParser: I think all parsers above need to support HTML since
the wiki syntaxes can be mixed with HTML
I don't understand this. What does manually entered HTML have to do
with wiki
Vincent Massol wrote:
Hi Sergiu,
On Sep 18, 2007, at 2:32 AM, Sergiu Dumitriu wrote:
[snip]
Different Syntaxes
As a general observation, we should have support for loose document
metadata. We currently define all the properties inside the java
class, like author, creationDate,
Hello!
I tried to response to your questions below from the point of view of a
WikiModel developer :-)
On 9/20/07, Sergiu Dumitriu [EMAIL PROTECTED] wrote:
Sorry for the late reply, I didn't see your mail.
HTMLParser: I think all parsers above need to support HTML since
the wiki
Hello!
Just some words about what the wiki model is and what it is not.
The main goal of the WikiModel is the creation of an API giving access and
control to the internal structure of individual wiki documents.
Some features of the WikiModel:
- WikiModel itself does not depend on any particular
On Sep 11, 2007, at 6:36 PM, Jean-Vincent Drean wrote:
Two possible solutions:
1. Have a WikiSyntax Object (A simple class with one property: a
combox box with different syntaxes: XWiki Legacy, Creole, MediaWiki,
Confluence, JSPWiki, etc) that users can attach to pages to tell the
6 matches
Mail list logo
