<div><div>On Nov 25, 2009, at 12:20 PM, Marcus Ramberg [via mojomojo] wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
On Wed, Nov 25, 2009 at 2:08 PM, hoelzro <<a href="http://n2.nabble.com/user/SendEmail.jtp?type=node&node=4066662&i=0" target="_top" rel="nofollow">[hidden email]</a>> wrote:
<div class="shrinkable-quote"><div class='shrinkable-quote'><br>>
<br>> I don't know how well this idea fits with MojoMojo's objectives, but I
<br>> figured I'd get it out into the ether for critiquing, and if people like it,
<br>> slated for a future release.
<br>>
<br>> I was thinking MM could use an extension mechanism similar to MediaWiki's.
<br>> Here's a summary of my ideas:
<br>>
<br>> - Additional page actions. I don't have a concrete example of how this
<br>> would be used, but I can see how it would come in handy.
<br>> - Modification of existing page actions. I don't know how this would work,
<br>> and if an overriden/augmented action were provided by another extension, we
<br>> would have to deal with the fun that is plugin load order.
</div>I am a bit of a sceptic to these two. Granted, the comment plugin adds
</div>some page actions, but the implementation of it is a bit of an
<br>abdomination in my opinion. What I really would like is support for
<br>external applications getting embedded at certain nodes of the wiki
<br>tho, for instance giving control to Angerwhale or mojolicious at /blog
<br>for instance, but still wrapped in the general design of the wiki. I'm
<br>not sure how feasible this is though.
<br></blockquote><div><br></div>I understand your trepidation with this variety of plugin; we could definitely hold off on that.</div><div><br><blockquote type="cite"><br>> - Additional syntax. This seems to be provided by the formatter stuff
<br>> already.
<br><br>Yepp
<br><br>> - Special pages. These could all be under /special/, or they might exist
<br>> anywhere in the hierarchy (I think all existing under /special/ and adding
<br>> redirects if you want them would be a good option). Special pages just
<br>> dispatch to extension controllers to deliver custom content, and can even
<br>> take arguments (ex. /special/calenders/home/Nov 2009).
<br><br>This seems somewhat similar to what I am talking about above.
<br></blockquote><div><br></div>Excellent. Well, I think I'll start on an implementation of special pages because it interests me greatly.</div><div>As soon as I can log in to <a href="http://mojomojo.org" target="_top" rel="nofollow">mojomojo.org</a>, I'll write my notes on special pages there for critiquing and review.</div><div>For now, special pages will only reside under /special/, as that would be easier to implement; how does that sound?</div><div><br></div><div><blockquote type="cite"><br>With regards
<br>Marcus Ramberg
<br><br>_______________________________________________
<br>Mojomojo mailing list
<br><a href="http://n2.nabble.com/user/SendEmail.jtp?type=node&node=4066662&i=1" target="_top" rel="nofollow">[hidden email]</a>
<br><a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/mojomojo" target="_top" rel="nofollow">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/mojomojo</a><br>
</blockquote></div><br><div>-Rob</div>
<br><hr align="left" width="300">
View this message in context: <a href="http://n2.nabble.com/MojoMojo-extensions-tp4064862p4069107.html">Re: [MojoMojo] MojoMojo extensions</a><br>
Sent from the <a href="http://n2.nabble.com/mojomojo-f2358427.html">mojomojo mailing list archive</a> at Nabble.com.<br>