> > > 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.
>
The only ECS I am referring to here is the Document. Which gives you
objects for the Head and Body. This makes it very convenient for a Screen
to add elements/attributes to the <head> and <body> tags. The Layout is
only concerned with the skeletal structure of the <body> tag. All page
elements can add things to the <head>, and the Layout does not have to take
on the responsibility of handling every other objects needs.
I am not quite sure yet how Rafal's layout handles a navigation templates
requirements regarding <head> content.
Beyond that and not really relevant here, ECS can be useful for form field
generation. A Select with multiple items being initially selected, for
example, is trivial to build with ECS. You can do it with a template as
well, but I don't think it adds much. It is still probably going to have to
be coded by an engineer, so in my mind the details should be hidden from the
designer.
>
> > > 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?
>
You are correct. I still do not like placing the Navigation adaptor object
that is in the Layout context into a context available for navigations and
screens. It should be possible to build a dynamic layout without combining
the layout's context with that for the navs and screen.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
