On 7/20/06, Gary Shewan <[EMAIL PROTECTED]> wrote: > I'd love to see a plugin architecture so those of use who were > attracted to the lean and speedy aspects in the beginning don't have > to bulk up on 'functionality'. Added features draws users though it > has to be said.
I have mixed feelings on this. On one hand, Typo's pretty clearly over-complex, at least in some areas. On the other hand, most of the really painful complexity in Typo has to do with plugin frameworks :-(. Fortunately, a lot of the pain that we've went through lately should pay off once we ship 4.0, because we can start removing old cruft. Pier's blog_id code will let us get rid of a ton of special-case code that lurks in the text filter framework. The whole text filter and sidebar frameworks need to be rewritten to use Rails's native plugin support. It won't be a big change for the plugins themselves, but we'll be able to dump a lot of complex (and slow!) infrastructure code. It'll be *really* nice to get rid of components. A side effect of this is that we'll be able to dump quite a few of the sidebars in the trunk out into their own packages. Presumably we'll be able to make something like 'rapt install typo41-sidebar-xbox' work seamlessly, although I haven't played with any of the Rails plugin tools enough yet. We can also prune the size of our tree back quite a bit--there's a lot of stuff in vendor/ that we can delete and replace with .gem requirements eventually. > If I ever get the time after 4.0 and when life calms down, I'm going > to look at ripping out the excess from a copy to see how light it can > go. I mean I don't even own an xbox ;) > > I've been busy, but a belated 'Woo hoo' for the speed improvements > Scott. Thanks. Scott _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
