On May 6, 1:52 pm, Thadeus Burgess <thade...@thadeusb.com> wrote:
> I need an example of "dynamic skin behavior".
>
> Code. (even if pseudocode). I need some code to understand.
Ach! as usual, you seem to ask the right questions....
I will think on this - but your question raises this (?) revelation:
between {{extend}} and {{include}} :
I have to think about the specific abstraction elements, but
{{extend}} sets up the blueprint (parent, builder, however you want to
talk about it);
{{include}} just (I think) should be textual inclusion (but need to
think more) ...
What your request (here) raised for me: we need something like
{{import}} --- which is like {{extend}}, with the exception that
nothing is activated, i.e. not put on an output tree --- only in a
library of contents (not used)
So - dynamic would look something like this:
---- example dynamic.html file ------
{{ extend 'layout.html' }}
{{ import 'page_components.html }} # import, but don't use yet - just
have them, if you want them
{{ for page_item in client_page_elements: }}
place page item in extend template's location for this page
"module", i.e. calendar; my avatar; my favorite menu;
remove any "standard" page elements, which the app allowed to
be optional;
apply to all displayed items (i.e. "decorate") whatever styles
have been set
apply any style modifications for user, which this app allows
user to set.
......
I'll think about this more; have to get to other stuff now
- Yarko
>
> --
> Thadeus
>
> On Thu, May 6, 2010 at 1:48 PM, Yarko Tymciurak
>
> <resultsinsoftw...@gmail.com> 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
