We don't need an {{import}} you can already do that with {{include}}.
{{include functions.html}} # which defines child_page_items
{{for page_item in child_page_items(page_items):}}
etcetc.
As far as layout, thats just a variable
if (user.preferences.layout == 3): extend layout3col.html
if (user.preferences.layout == 2): extend layout2col.html
Also, as a note, {{extend}} will take a varaibel, so you can do something like..
return dict(pages=pages, layout=user.preferences.layout)
{{extend layout}}
--
Thadeus
On Thu, May 6, 2010 at 2:15 PM, Yarko Tymciurak
<resultsinsoftw...@gmail.com> wrote:
>
> 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.
>
> .... more:
>
> App has layout with header, status bar, body, footer.
> Any app page can use a body layout (within the main site page layout)
> this is application designers decision / choice.
>
> One page (main) uses standard 3-panel template;
> Most detail activity pages use 2-panel template for body;
> Maybe admin, or "heaving interaction" / busy pages use 1-panel body.
>
>>
>> --
>> 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
>
