Re: Giapeto usage - who relies on it?

Quoting Chuck Hagenbuch <[email protected]>:

>> 2) Some kind of block level templates (in addition to pagelevel
>> templates) should be nice (e.g. when you give the block a title at the
>> moment you get another block layout). However we should make it in such
>> a way that CSS from one block doesn't spillover into another
>
> Unless we do search and replace on classnames, this is technically
> impossible, the way CSS works.
There is one other way; If you can create these block templates with 
the (future) Giapeto theme editor only; you can auto generate the CSS 
stylenames. In this way you can prevent a collision of styles.


>> ** Templates **
>> I don't know if we should include a template editor. Mine are actually
>> quite complex, you wouldn't want to build an editor for those ;-). And
>> editor for block level templates would be quite handy though. Same goes
>> for storage in VFS. I would prefer the global page templates to be on
>> disk (this is handier for development; if you really need access to it
>> you can always use gollem) and the block level templates to be in VFS
>> (I think the latter would also be more dynamic)
>
> I want to move away from the assumption that the person using Giapeto
> is the server admin, which almost requires putting all templates in the
> VFS. I'd also like Giapeto to be able to serve multiple sites - again,
> need to get away from the filesystem. That's the main reason for the
> move to put templates into VFS.

OK, I understand. But then we do need to be able to set permissions on 
who can modify the theme. (I'm already feeling a sick thinking about 
our commercial guys are able to chnage the theme ;-) )

Cheers,
Roel.



-- 
giapeto mailing list - Join the hunt: http://horde.org/bounties/#giapeto
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]