Hi!

>> During the Sorrento Sprint we worked on plone.app.localconf which's aim
>> is to provide a general infrastructure for local configuration, maybe
>> have a look at it:
>>
>> http://svn.plone.org/svn/plone/plone.app.localconf/trunk/
>>
>> and here is an example:
>>
>> http://svn.plone.org/svn/plone/plone.app.localconf/trunk/plone/app/localconf/tests/README.txt
> 
> Can we move this into collective repository?
>  Not all developers have write acces into plone repository.

Right, maybe a mistake to put it there. Is there an easy way to move it 
over (with history staying alive?).

>> What it does is to make the folder on which is configured a site and
>> adds a local utility to it which then can be retrieved (also from nested
>> folders).
>>
>> What is missing is a way to put the UI together. My idea was to create
>> some sort of local control panel and have defaults defined in the global
>> one. I guess this can be nicely done with some adapters and maybe formlib.
> 
> or z3c.form ;)

Yes, some example on that might also be nice to have. There was also 
some experimentation from Alec during the Sorrento Sprint.

-- Christian

-- 
Christian Scholz                         video blog: http://comlounge.tv
COM.lounge                                   blog: http://mrtopf.de/blog
Luetticher Strasse 10                                    Skype: HerrTopf
52064 Aachen                              Homepage: http://comlounge.net
Tel: +49 241 400 730 0                           E-Mail cs@...
Fax: +49 241 979 00 850                               IRC: MrTopf, Tao_T

connect with me: http://mrtopf.de/connect

Hi!

>> During the Sorrento Sprint we worked on plone.app.localconf which's 
>> aim is to provide a general infrastructure for local configuration, 
>> maybe have a look at it:
>> http://svn.plone.org/svn/plone/plone.app.localconf/trunk/
> 
>> So maybe that would be an idea to use instead of inventing yet another 
>> way of storing stuff locally ;-)
> 
> That's beautiful.  If it'd realised five.localsitemanager would defer to 
> the parent if the interface was unknown I'd have written my product this 
> way.  As it is I'm piggybacking on the event that's supposed to be for 
> traversal over the manager and shoving my information into the request.  
> How uncouth.

I was also doing it differently by putting a marker interface on the 
object which had the config and then walking up acquisition until I 
found it. Alec came up with using utilities and sites though as they 
know their parent sites already. So that's what I mainly changed at the 
last sprint.

> I'm happy for my way to die.  I'll refactor collective.sectionsubskin to 
> use this.

Cool.

If somebody wants to work on localconf, feel free to do so. I think the 
most needed part might be some infrastructure similar to the global 
controlpanel but for a local configuration.
I will also be around on IRC at least today and on sunday (mrtopf).

cheers,

Christian




-- 
Christian Scholz                         video blog: http://comlounge.tv
COM.lounge                                   blog: http://mrtopf.de/blog
Luetticher Strasse 10                                    Skype: HerrTopf
52064 Aachen                              Homepage: http://comlounge.net
Tel: +49 241 400 730 0                           E-Mail cs@...
Fax: +49 241 979 00 850                               IRC: MrTopf, Tao_T

connect with me: http://mrtopf.de/connect

Hi,

Thanks to Matthew, Gilles and Christian for your good ideas, i'm really 
happy  to work with you on this kind of utility.

I think this product will be useful to design skins quickly, at less for 
demo purposes.

Here what i want to do ...

Structure of the form for a theme variation :

Portal Properties :
- portal width or 100%
- portal height or auto
- overflow or nothing
- portal background
- Column one width
- Column two with
- Content width
- header height
- header background
- footer height
- footer background

Colors :
Same colors as base properties

Fonts :
Same fonts as base properties


Icons :
- Do you want icons for special links (external, ftp, etc ....)
- do you want to disable portal_types icons in all portlets ?
- Do you want to disable portal_types icons in #content ?
- do you want to disable portal_types icons in navtree portlet ?
- do you want to disable portal_types icons in sitemap ?


Portlets properties :
- colors
- border yes/not
- border color
- background color
- background image


Navtree properties
- Navtree link color
- Selected Item font color
- Selected Item Background color
- Selected Item Background icon (or portal_type icon)
- parent Item selected font color
- Parent Item Background color
- Parent item selected icon (or portal_type icon)

Sitemap properties :
- same as navtree ?
- let's go


Addons Css :
- load your own css for this theme variation

Addons Flashs :
- for a theme variation we could have a flash presentation at first 
visit (a viewlet) over the page > load the file
- in header we could have a flash banner (viewlet) > idem
- in these two options we must indicate flash width and height

Addons navigation :
- drop down menus in place of global sections (viewlet) ?








The widgets :

- For colors and dimensions we will use jquery gadgets
- For flash we will use swfobject.js
- super widget : when changing a property > the skin is changing (in 
javascript) i don't know if it's possible ... otherwise we need a 
"Preview" action.


Images and other files :
- i think PloneFlashUpload is a good solution for upload, if flash is 
not installed we also provide a zip upload solution
- when uploading files in a theme variation, if a file with the same 
name exists in plone skin (or another skin) it will be replaced by this 
new file (important)
- In the form, in a first time, we will use files names to indicate 
backgrounds or icons, in a second time perhaps a browser to link the 
file will be useful.

That's all !

Many things already exist for these features, we just need to make the 
glue and we will have a good utility.


Bye

Jean-mat (macadames)


Matthew Wilkes a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> On Heisei 0020-04-24, at 163726BST, Gilles Lenfant wrote:
> 
>> So we're in the same baseline... The last thing is to provide the 
>> merged CSS into a viewlet pushed after the css registry call, but 
>> caching this CSS should be somehow tricky.
> 
> It was the caching that I thought would be difficult so I took the 
> coward's way out and inlined it in a viewlet.  I'm sure it'd be possible 
> to hash something and give the css a unique filename though.
> 
> Matt
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> 
> iD8DBQFIEKrAZnKd+ctxHMoRAia4AJ9iXFp2PnK1MC3ZCzvBSxRQndUNbACggdsh
> nAer4CSAuVpS8H9K8b9z5Ao=
> =AbZd
> -----END PGP SIGNATURE-----
> 
> 
> -- 
> Archive: 
> http://www.openplans.org/projects/plone-3-paris-sprint/lists/plone-3-paris-sprint-discussion/archive/2008/04/1209051852030 
> 
> To unsubscribe send an email with subject unsubscribe to 
> plone-3-paris-sprint-discussion@....  Please contact 
> plone-3-paris-sprint-discussion-manager@... for questions.
> 
> 


-- 
Jean-mathieu Grimaldi
INGENIWEB (TM) - SAS 50000 Euros - RC B 438 725 632
Bureaux de la Colline - 1 rue Royal - Bâtiment D - 9ème étage
92210 Saint Cloud - France
Phone : 01 78 15 24 05 / Fax : 01 47 57 39 14
web : www.ingeniweb.com - une société du groupe Alter Way