Re: [Openinteract-dev] What is OpenInteract2 ?

[Salve J N. <sal...@me...>]

Antti M Vähäkotamäki wrote:
> Well to make this clear from the beginning - I'm not in any way against 
> you building new templates. They will be needed for sure. I'm just 
> trying to look at the bigger picture.
> 
> Salve J Nilsen wrote:
> 
>> Urgh... I'm sorry about that. OI2 is definitly a application framwork 
>> (where of "CMS" is only a minor part.) I didn't mean to cause this 
>> confusion. :-\
> 
> Well what I was thinking was more in the lines of OI2 not being even 
> partly a CMS.

I'm sure you can mold OI2 into whatever you want it to be... :-)


> Sure I would heartly welcome a package which would implement all kinds 
> of CMS functionality on top of OI2, and an another package which would 
> provide a bucketfull of general TT2 templates which are easily themable 
> by pure CSS, but I'm not sure if either of these should be included in 
> the base packages IF they are to provide a general base for applications.

I think having a functional website with CMS, news and security features as
part of the "base" is not only good, but the Sensible Thing to Do. OI2's CMS
features (e.g. page management and publishing, user/group management, interface
consistency features, templates, logging framework, etc.) may be a bit lacking
(in consistency, standards compliance, visual beauty and so on.) but having
them available from a basic install quite important. Who do you think would be
impressed by a application framwork one can't test and experiment with?


> So probably the bigger question here is the meaning of base packages - 
> what are they for?

They're there so you can get a notion of what's possible to do OI2, and when
you've seen _that_, the _real_ big questions show up: How can I use OI2? How
can I improve OI2? What should be improved? How easy is it to improve OI2? How
can I make it easier to improve OI2? What should be improved so OI2 becomes
easier to improve?


> Also currently the building block TT2 templates for OI2 website aren't 
> even in a base package but they are directly in the website's template 
> directory. This makes them impossible to be substituted or modified 
> through the management system with packages. I'm not sure if the current 
> theme implementation can be used to override these (we are using it only 
> to load a single theme which causes a constant 50ms addition to each 
> request ;-) ), but if we are getting rid of the current theming for a 
> CSS only theming, we can't do this anymore and the whole thing should be 
> rethought.

I'm sure you can find or formulate some bug reports that describe what your
problems are. <http://jira.openinteract.org/> ;-)

(And yes, the theme implementation sucks :)


- Salve

-- 
Salve J. Nilsen <salvejn at met dot no> / Systems Developer
Norwegian Meteorological Institute           http://met.no/
Information Technology Department / Section for Development