[dokuwiki] Re: Plugin writing questions / recursive parser

Hi,

thanks for your comments, my comments are inline.

Chris Smith schrieb:
> Its a little more complex than you have outlined.
> 
> Dokuwiki caches rendered wiki content and then either delivers or doesn't
> deliver the whole wiki page based on the user/acl configuration.  There is
> no mechanism to determine that the page needs to be rendered differently for
> different users.  This would mean any page with your conditional syntax
> needs to turn caching off.

Yes, I expected that. For the purpose, I have in mind, this would not matter
very much, because my intention would be to use the wiki only as a writing
environment for a small group of editors and then export it as static HTML. So
the end users would never see the actual wiki.

> As you mention you also have an issue with show source.

Yep, no problem either, for the same reason.

> I think you could go someway to overcoming both problems using a modified
> template.

Yeah, maybe I should ditch the plugin idea and do it all in a special export
template. I would also allow me to leave out all the unneeded buttons. But if I
want my tool, that exports the wiki, to work from a remote computer, I would
need a way to change the template on per-request basis. Is there a way to set
the template per-user?

> (b) instead of a syntax plugin, (in the template) you capture the output of
> tpl_content and post process it, simply removing any content that shouldn't
> be delivered.

But then I would have to parse XHTML, right? Should be not too hard, but I
still need to be able to set some markers in the wiki page, so I know what to
filter out.

> If you do go the plugin route, you can call the renderer recursively.  Its
> expensive in terms of resource and time.   In the long term it may be better
> to come up with a solution (modification) that allows the plugin to capture
> a stream of instructions/inject a stream of instructions.
> 
> [..] 
> Something like this would neatly sidestep the overhead having to instantiate
> a second renderer.

Now you lost me. I'm still new to DokuWiki and havn't looked at the way the
parser works in detail yet (though I read the respective wiki pages). Isn't
there a way a plugin can just feed back raw wiki page text it isn't interested
in, back to the parser?

> Then again, perhaps a wiki ( a collabrative document generator ) is not the
> ideal for a job like this.  I'll leave that questions to others :)

IMHO the whole point of a documentation generator is to produce documentation
which can be *distributed* eventually. DokuWiki currently lacks support for
this out-of-the-box.

> I hope this helps some,

Again, thanks for your opinions!

Chris

Other related posts: