jamie@xxxxxxxxxxxxxxxxxxx schrieb:
> 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.
My actual hack defines a new action. To overwrite the 'admin' action,
it's not enough.
I think it would make sense to have a Configuraion File which enables to
overwrite special DokuWiki Command with own Plugins. I guess most
Plugins work as Extenstion not as a type of replacement.
> 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.
An Admin Plugin would be very nice. I also thought about a this with the
Functionality of a installer and a Page which lists all installed
Plugins and the ability to change Settings of Plugins directly via a GUI.
> 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.
Absoloutly a type of DB Abstraction is needed. One of the Problems I
have in my actual code is the need to make most IO by hand.
Rainer
