Note that wiki links are generated in many places, most notably the timeline, and if those links also have to work or the solution is only a partial one.
(sent from a mobile device - please excuse brevity, typos, and top-posting) ----- stephan beal http://wanderinghorse.net On Oct 3, 2014 6:02 PM, "Ron W" <ronw.m...@gmail.com> wrote: > On Fri, Oct 3, 2014 at 11:18 AM, Stephan Beal <sgb...@googlemail.com> > wrote: > >> On Fri, Oct 3, 2014 at 4:56 PM, Gour <g...@atmarama.net> wrote: >> >>> OK, no problem. I, somehow, thought that teaching Fossil to just render >>> using JS in the browser should not be so hard... >>> >> >> It can do so already, but... >> ... >> c) there isn't currently a mechanism which would allow wiki-generated and >> such to integrate with that, so it requires a completely custom front-end. >> The core only knows about one type of wiki like, and would send all >> generated links to the built-in wiki rendering mechanism. >> > > It could be as simple as a <inbrowser> tag that Fossil treats the same as > <verbatim> with the addition of wrapping the raw wiki content with a <div > class="rawWiki"> or similar. > > Maybe Joe's new feature can help with this. Did not have a chance to look > at it as my field trip got extended. > > While some JS would be needed, I think the foundation could be fairly > simple: Find the div then feed its content to the user's chosen renderer. > > The main potential complication being that the contained wiki mark-up > might confuse the browser's HTML parser. But, I would think that a mark-up > that has a browser-based renderer (JS, Java or other) would already address > this issue. > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
