Tommie Podzemski wrote:
I 100% agree with your argument that templating-system are
resource-hogs on a high-volume site, that said - i'm very curious on
your thoughts in regard of the hook-system.
How far done is the hook-system and could you give us some further
insight on how the plans are to implement it?
Well, depending on your perspective, it's either 0% or 50% done.
I wrote the hooks system for MediaWiki, which seems to have worked out
pretty well. See here for documentation:
http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/docs/hooks.txt?view=markup
http://www.mediawiki.org/wiki/Manual:MediaWiki_hooks
I think that's probably how we'd do it in Laconica, too. Probably the
only thing I'd want to revisit is the error-reporting mechanism, which
would probably work better with exceptions rather than returning a string.
So, we'd probably start off with hooks for some of the key "business
logic": posting a notice, sending a message, showing a notice list.
We'd also have hooks for user-interface events, like showing menus or
sidebars.
Finally, we'll probably use a completely different system -- PEAR::Auth
-- for doing login/profile hooks. It's a little confusing to have two
different plugin systems, but PEAR::Auth seems pretty complete and it'd
be a leeetle bit dumb to rewrite it from scratch.
All that said, this is only in the design phase. I anticipate that it'll
be part of our system for version 0.8, although that release remains
undefined.
-Evan
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
