Keith Hodges | 23 Apr 07:11
Picon

Cool Idea!

Hello Lukas,

The hierarchy of choices available as swappable replacements for 
PRPierFrame, is starting to mature.

The first, PRPierFrameCentral, implements the wiring in order for it to 
be the centre of attention as I suggested yesterday. It aims to preserve 
the existing behaviour, however it has a nice innovation:

If your site has no environment at all, it caches one for you. i.e. your 
layout can be provided as part of your PRPierFrame subclass, and does 
not need to be user visible or editable. If you edit the code that 
generates your layout directly, it will get used for the next session.

And that's not all. If you add an empty page, and set that as an 
environment in a structure's settings, it will automatically populate.

==
The second class PRPierBasicBP moves the layout to:

/environment/layout
/environment/style

Again it will be cached for you "off-site" until an environment is added.

==
A third class PRPierBasicCWS is a first attempt at an alternative to 
blueprint.
==
A fourth class is PRPierAdmin provides a non edittable environment for 
(Continue reading)

Lukas Renggli | 23 Apr 14:54
Picon
Picon
Favicon

Re: Cool Idea!

> The hierarchy of choices available as swappable replacements for
> PRPierFrame, is starting to mature.

I don't really know if changing PRPierFrame is the right way to go?  
After all this is a rather low-level Seaside component. Maybe it would  
be better to have some property in the kernel?

> The second class PRPierBasicBP moves the layout to:
>
> /environment/layout
> /environment/style
>
> Again it will be cached for you "off-site" until an environment is  
> added.

I guess I'll have to look at the source code. I don't understand how  
different are supposed to work then? For example seaside.st uses 4  
different environments, my personal site uses 2.

Cheers,
Lukas

--

-- 
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

(Continue reading)

Keith Hodges | 23 Apr 20:12
Picon

Re: Cool Idea!


>> The second class PRPierBasicBP moves the layout to:
>>
>> /environment/layout
>> /environment/style
>>
>> Again it will be cached for you "off-site" until an environment is  
>> added.
>>     
>
> I guess I'll have to look at the source code. I don't understand how  
> different are supposed to work then? For example seaside.st uses 4  
> different environments, my personal site uses 2.
>
>   
No different... perhaps I should have written:

The path that a page uses to find its layout is:

*<one of my parent's local environment>*/environment/layout
*<one of my parent's local environment>*/environment/style

So I can have

/site/environment-1/layout
/site/environment-1/style

/site/environment-2/layout
/site/environment-3/style
/site/environment-4/layout
(Continue reading)


Gmane