2011/4/28 Lluís Batlle i Rossell <virik...@gmail.com>
> I like the wiki syntax, and I don't want to use HTML only, and even less,
> repository-wide.
>
Fossil's wiki syntax doesn't offer all that much simplification over plain
HTML. Only creation of lists and wiki-links is simplified, vis-a-vis raw
HTML, when using fossil's syntax (e.g. as opposed to _underline_, *bold*,
`fixed-width`, and similar common wiki conveniences). The fossil wiki parser
is primarily an HTML sanitizer, in that is only allows a "safe subset" of
HTML tags/attributes through and elides the rest. Instead of dumbing-down
the markup (which is what wikis do so well (and differently/incompatibly)),
Richard chose the approach of "don't make them learn another markup
language, but instead sub-set the single most common format and import a
small handful of the most common wiki conventions" ("small handful" == 2, i
think: links and lists).
So, I leave it as a 'Feature Request'.
>
My biggest request for the wiki would be the optional ability to serve them
in unparsed form so that we can render them client-side using a
JavaScript-based wiki parser of our choice. That would also allow us to
store "complete" HTML (including embedded JavaScript and whatnot) in our
wikis. (Obviously such use is unsafe/unwise for publicly-writable wikis.)
i'm currently in the process of porting over several fossil-based wikis to a
system which serves raw text pages to a JS client app which then takes over
responsibility for the rendering (which it does based on a contentType field
associated with each wiki page entry).
http://fossil.wanderinghorse.net/demos/whiki/
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
