Just wondering what the plan was with regard to linking diazo themes
more directly to css/js bundles, skin layers and browserview concept
of a theme?
---
Dylan Jay
Technical Solutions Manager
PretaWeb: Multisite Performance Support
P: +612 80819071 | M: +61421477460 | twitter.com/djay75 | linkedin.com/
in/djay75
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Plone-developers mailing list
Plone-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-developers
I'd say "desirable", but not really "designed" yet.
One thought is to use the new adapter indirection for resource lookup
in ResourceRegistries to allow plone.app.theming to 'inject' new
resources into the merged composition by scanning the theme HTML.
plone.app.themingplugins provides a bridge between Diazo themes and
browser layers.
Martin
The adapter change Martin is talking about would help here
> On 20 January 2012 04:55, Dylan Jay <dj...@pretaweb.com> wrote:
>> Hi,
>>
>> Just wondering what the plan was with regard to linking diazo themes
>> more directly to css/js bundles, skin layers and browserview concept
>> of a theme?
>
> I'd say "desirable", but not really "designed" yet.
>
> One thought is to use the new adapter indirection for resource lookup
> in ResourceRegistries to allow plone.app.theming to 'inject' new
> resources into the merged composition by scanning the theme HTML.
Don't much about that but clients have started asking about aligning
portal registery entries with their diazo theme.
Is it technically possible to have something like the following:
1. Admin can create a new theme id in under Site setup > theme
2. In new theme they can pick a skin, a browserlayer, a diazo theme,
js resource bundle and css resource bundle.
3. add domains to each theme
Idea being that it would be easy for a user TTW to create a new theme
variation based on existing filesystem theme like sunburst or
plonebasic and have that used for a public url, and have another theme
used for the editing url.
>
> plone.app.themingplugins provides a bridge between Diazo themes and
> browser layers.
haven't really needed this yet unfortunately. jbot is simple enough by
itself but would be nice to link jbot plus any other normal views,
viewlets etc to a diazo theme via GS. or rather other way round, make
a diazo theme depend on that layer.
We haven't had need for a theme specific new view that couldn't
handled by installing an existing plugin and transforming viewlets or
portlets. It nice to know that easy way to add in a new view is there
however but its a pity it's only usable with a diazo theme. jbot
simplicity for creating new views is a great idea.
>
> Martin
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2