[dokuwiki] Re: Future Plugin Interfaces ?

I originally tried that, but the problem is that then the resulting output 
isn't marked as a section. It isn't in the TOC, and there's no section edit 
button.

So it doesn't work as a syntax plugin.

Alan

On 7/22/05, Jamie Wilkinson <jamie@xxxxxxxxxxxxxxxxxxx> wrote:
> 
> Alan + list,
> 
> Think this could be already be done with a plugin_syntax that looked
> for "h1. $title\n". See Esther Brunner ( http://qwik.ch/esther_brunner
> ) and his ::include:: plugin for some good examples: (
> http://qwik.ch/include_plugin )
> 
> Jamie
> 
> p.s. Esther - any comments on 'officially' making it {{include}} ?
> Seems more similar to the {{rss>...} syntax which I based a
> {{word>...}} plugin on.
> 
> 
> 
> Jamie M. Wilkinson
> jamiew@xxxxxxx
> http://www.tramchase.com
> 
> 
> On Jul 21, 2005, at 11:32 PM, Alan Liu wrote:
> 
> > Hi Jamie,
> >
> > Have you done modification to the core parser and html generation PHP?
> > I'd like to have a modular (plugin) way of changing the parser and
> > html generation. For example, if I want "h1. xx" to be a level-1
> > heading, represented in the TOC, etc., I currently have to modify the
> > core source. It would be *great* to do this via a plugin architecture.
> >
> > I realize this would be an involved change, but I think it's feasible.
> > I believe another wiki (EnfurtWiki?) has a modular parser.
> >
> > Alan
> >
> > On 7/21/05, jamie@xxxxxxxxxxxxxxxxxxx <jamie@xxxxxxxxxxxxxxxxxxx>
> > wrote:
> >>> On Mon, 18 Jul 2005 14:06:19 +0000
> >>> Rainer Weinhold <inforw@xxxxxx> wrote:
> >>>
> >>>> Next I need a Plugin extend the Edit-page. So the question is now,
> >>>> are
> >>>> there any Design or something for such, say extended Plugins ?
> >>>
> >>> Not yet. There were some ideas floating around but no one has coded
> >>> the
> >>> needed things yet.
> >>
> >> I've been kicking around ideas for exactly the same thing and would
> >> love
> >> to get some other developer's input before I write anything. My
> >> current
> >> design involves developing 'plugin_action' and 'plugin_admin', which
> >> have
> >> stemmed from a large number of hacks and mods I've done to the
> >> DokuWiki
> >> source. I'd like to be able to farm everything out to plugins (and
> >> templates) so that I can keep my DokuWiki core code clean and - most
> >> importantly - easy-to-update!
> >>
> >> plugin_action's inspiration comes from a DHTML html_index()
> >> replacement I
> >> wrote -- alternatively I could simply use an actionLink() in my
> >> template
> >> to, say, 'index_dhtml' in my template and have a plugin do the work.
> >> I've
> >> also integrated FCKeditor+html2wiki -- I'd love to have an 'edit_gui'
> >> action plugin. I suppose this somewhat relates to the original issue
> >> of
> >> "extending the edit page" although I'm not sure.
> >>
> >> I havn't actually written any admin-style stuff yet but I imagine
> >> having
> >> plugins in that department could be really useful. I would personally
> >> write a Template Admin plugin so I could make changes to the wiki
> >> from the
> >> wiki (!) I could see great use for, say, a "plugin installer", a
> >> local.php
> >> editor, User admin, Page admin, etc.
> >>
> >> One concern is standardizing access to our "database" from inside the
> >> plugins, since a lot of I/O would be necessary. Perhaps a light DB
> >> abstraction layer is in order? I don't plan on ever moving from
> >> flatfiles
> >> but it'd be nice to have hooks for that option in the future.
> >>
> >> Jamie
> >> jamie (a) internetofdeath.com <http://internetofdeath.com>
> >>
> >> --
> >> DokuWiki mailing list - more info at
> >> http://wiki.splitbrain.org/wiki:mailinglist
> >>
> > --
> > DokuWiki mailing list - more info at
> > http://wiki.splitbrain.org/wiki:mailinglist
> 
> --
> DokuWiki mailing list - more info at
> http://wiki.splitbrain.org/wiki:mailinglist
>

Other related posts: