Matt Rose <[EMAIL PROTECTED]> writes: > On Mon, 21 Aug 2006, John Wang wrote: > >> Is there a way to make the gallery a pluggable option so it's easy to load >> for people that want it but not installed by default? Right now, a growing >> number of sidebar plugins ship with Typo and, from what I've seen, the vast >> majority of Typo installs don't use most of them. It seems that Typo needs a >> way to have pluggable modules that don't ship with Typo. This type of >> architecture would make the bloat argument a non-issue and possibly even >> reduce the code by moving sidebars out of the core distribution. > > I think this is what the aim is in 4.1 All of the sidebars are in the > vendor hierarchy, which would make installing new ones simple, > theoretically. I haven't looked into the sidebar code itself, to see what > kind of database tie-ins exist, and how they work, but I think this is one > of the goals. > >> Seems like making the gallery an optional add-on to Typo would satisfy both >> camps: (a) those that want a gallery feature in Typo and (b) those that want >> a Typo w/o the gallery. Is there an good way to do this? > > That's the goal of a plug-in architecture. Hopefully, this can be > achieved, without re-writing my sidebars too many more times ;)
I *think* the current bleading edge API's going to be pretty constant for a while. And porting (the core) sidebars was a fairly painless process. I couldn't work out how to do it programmatically, but apart from that it was fine. -- Piers Cawley <[EMAIL PROTECTED]> http://www.bofh.org.uk/ _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
