Stylesheets in Pier demo

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Stylesheets in Pier demo

keith1y
(repost)

Perhaps you would be interested to take a look at the first shot of my
approach to handling styles entirely within pier. As a first go, it may
have some rough edges but let me know what you think of the concept.

http://create.seasidehosting.st

you may login as per normal to have a look around.

----
1. I moved the layout from "/environment" to "/environment/layout" which
frees up "/environment" for some contextual information, instructions
and presentation of environment features, which now include a
stylesheet, and color tables.
(I think that a user manager should go in here also, so as to avoid
cluttering up the rest of the interface. A save image (copy) action
button might be a useful administrative tool which could go in here too)

2. I wrote a visitor that collects the text in a page, includes the
content text of any embedded pages, and  inserts a url for  any embedded
images. This is used beginning at "/environment/stylesheet/main", and
the visitor assembles a stylesheet. Embedded text pages can be used as
variables (see see "/environment/colors" ).

3. The stylesheet is collated into the htmlRoot by PRPierFrame, which
currently has things like environmentSelector, layoutSelector,
stylePageSelector, hard coded.

The plan is to take all of this configuration and refactor it into a
decorator (PRManager and sons). The PRPierDefaultEnvironmentManager
decorator is applied to the root page by default, and it uses this to
tell where to find its environment (because when localized it might be
called something else).

4. (planned) PRManagers may be applied to any page in the wiki tree to
override styles and layouts for siblings.
Sibling environments should only need to modify bits of the environment
since they are inherited from the parent environment.

PRManagers will be able to do lots of other useful functions, such as
maintaining an alias list, colour -> color, for example, or managing the
"new page as sibling", "new page as child" policies.

I haven't made any effort to present the stylesheet correctly, at the
moment it is at the mercy of wiki syntax when displayed. (hence comments
are spread across two lines to avoid double stars /*not a link*/ being
interpreted as links)

I have a notion of micro content (which I implemented in a thing called
tiddlypom) where sub parts of a page are marked and tagged. They may
even use different parsers. With this in place, the stylesheet
information could be a subpart of a page (what I call a "tiddle") with
its own non-wiki-syntax parser. And colors could be listed in a single
page because links such as "/environment/colors//broken" would resolve
to a marked "tiddle" part of the "/environment/colors" page.

I am really impressed with seaside and pier too now I have had a chance
to get my teeth into it.

best regards

Keith


               
___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki
Reply | Threaded
Open this post in threaded view
|

Re: Stylesheets in Pier demo

Lukas Renggli-2
> 1. I moved the layout from "/environment" to "/environment/layout"  
> which
> frees up "/environment" for some contextual information, instructions
> and presentation of environment features, which now include a
> stylesheet, and color tables.
> (I think that a user manager should go in here also, so as to avoid
> cluttering up the rest of the interface. A save image (copy) action
> button might be a useful administrative tool which could go in here  
> too)

I very much like the color tables. Great idea!

> PRManagers will be able to do lots of other useful functions, such as
> maintaining an alias list, colour -> color, for example, or  
> managing the
> "new page as sibling", "new page as child" policies.

Great, I am looking forward to see all those management tools appearing.

Cheers,
Lukas

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



_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki
Reply | Threaded
Open this post in threaded view
|

Re: Re: Stylesheets in Pier demo

keith1y

> I very much like the color tables. Great idea!
>
>  
Thank you, we just need squeak to re-render the images with a
color-table defined color on demand! I'll bet that there arent many cms
frameworks capable of that.

Keith

       
       
               
___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki