Scott Laird wrote: > 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 >
Well, that's always the way. Just today I was modifying another CMS at work, and realized just how tiny and simple it was compared to the behemoth I had borrowed a lot of the code from. The secret, of course, is that the new tiny system only had to please me, wheres the behemoth was built to be configurable to the ever-changing whims of a wider user population. I do feel, though, that you should either stabilize and document the plugin frameworks, or rip them out. At the moment, nobody uses them because it's an undocumented moving target, but you have all that complexity there anyway. I say either lose the complexity, or document and stabilize it so people will use it and you'll get some actual benefit from having it there. > The whole text filter and > sidebar frameworks need to be rewritten to use Rails's native plugin > support. Oh. *sigh*. mathew _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
