Travis Low wrote:
I have very similar views on it as you Travis...
> > > There is something I don't like about WebMacroSiteLayout. It uses ECS to
> > generate
> > > <head> part of the page.
> >
> > I see this as a strength.
> Would you mind expanding on this a bit? I've been trying, and failing, to think
> of a situation in which ECS is a better idea than templating. On the surface,
> ECS doesn't seem much better than embedded HTML. The only advantage I can think
> of is that you don't have to rework templates when the HTML standards change,
> but it seems more likely that the site would become obsolete before that
> happens.
I find ECS exactly as easy to maintain as embeded HTML, only uglier. And the advantage
I can think off is manipulation of markup generated by one entity by anoter one.
For example - one method creates a html table, then another method is stickig a row
between te 16th & 17th row. It's certainly easier to do with ECS that with plain
HTML. I sincerely hope that my projects will never need such tricks ;-)
> > The original thinking was to limit the available information in the layout
> > context, so that it is used appropriately and did not contain a lot of
> > dynamic content.
> This too. Why would you limit the capability to put dynamic content in the
> layout? I understand that it's usually undesirable for one site to have wildly
> differing layouts, but shouldn't that decision be left to the designer instead
> of the application developer?
Portal-like applications with decent amount of customization are 100% candidates
for having wildly dynamic layouts. We want these to be easy to build with Turbine,
don't we?
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
