From: <an...@io...> - 2005-06-30 22:15:08
|
Salve referred to OpenInteract2 as a CMS in his post.. I personally don't see OI2 as a CMS, but an application framework. These are two quite separate things in my opinnion.. You can build a CMS on top of OI2 but I think that OI2 should not even strive to be in itself a CMS. This doesn't make it wrong to design a new HTML widget set for OI2, but I think we should keep in mind that OI2 as an application framework does not impose any specific template engine to the developer. How are we supposed to distribute html widgets which are independent to templating engine? Ofcourse we can implement these templates to only one engine, for example TT2, as a base package, but this raises an even more interesting question: What are base packages for? Are they trying to implement: * a CMS on top of OI2? * a base for a CMS to grow on top of OI2? * a generic but technology specific (TT2 and WWW) base for applications? * a generic base for applications? * a base for Chris' blog? (;)) What if somebody builds an application with OI2 which is not a CMS? And why should we even be doing yet another CMS or even a customizable CMS engine? And as AJAX is now a hot topic - what if somebody would want to use OI2 just as a AJAX backbone (for which it would suit quite well in my opinnion), what role would the base packages play? So what is OI2 and what is the purpose of base packages in your opinnion? - Antti PS. This relates somewhat to the JIRA issue to allow creating an website wihout base packages and I will comment on that more after this discussion :) |