On May 6, 2:25 pm, Thadeus Burgess <[email protected]> wrote:
> So you can already accomplish that
>
> ------------example.html
>
> {{ extend "layout.html" }}
> {{ block body }}
>    {{ include "functions/body_2panel.html" }}
>    ...
> {{ end body }} # this is fine, the parser already ignores the second value.
>

yes - but I want a way to read in a file with logically related
blocks / js / etc.,
but _not_ place them (only have them available to place)

With this ( {{include}} ) I need a directory to organize related, and
one thing at a time
in a file ---- but this is good enough for now.

Ok - good enough.

Thanks,
- Yarko
> --
> Thadeus
>
> On Thu, May 6, 2010 at 2:22 PM, Yarko Tymciurak
>
> <[email protected]> wrote:
> > On May 6, 1:52 pm, Thadeus Burgess <[email protected]> wrote:
> >> I need an example of "dynamic skin behavior".
>
> >> Code. (even if pseudocode). I need some code to understand.
>
> > .... continuing w/ the body panel discussion:
>
> > --------example.html:
>
> > # I'll pick what out of this grab bag I place,
> > # some possibly by conditional code, i.e. {{ if .... }}
> > # I'll pick what out of this grab bag I place
>
> > {{ import tool_widgets }}
>
> > {{ extend layout.html }}
> >  {{ block body }}
> >     {{ include body_2panel }}
> >     ...
> >   {{ end body }}
> > {{ end layouthtml }}
>
> > ----------
> >  I know you don't use the tag on end; lets leave it as syntactic
> > sugar, for readability; it can just be ignored by the parser
>
> > .....
>
> > I'm thinking of a view file structure like this, with potentially
> > details using all the other block actions I pointed out.
>
> > - Yarko
>
> >> --
> >> Thadeus
>
> >> On Thu, May 6, 2010 at 1:48 PM, Yarko Tymciurak
>
> >> <[email protected]> wrote:
> >> > ther than fixing the point of responsibility point, and making the
> >> > actions naturally there to try to enable effective skinning, I have no
> >> > pre-insights... I am exploring...   I think more than include is
> >> > needed for dynamic skin behavior (at a higher level than simply
> >> > manipulating css - you can do

Reply via email to