<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel">
    <title>gmane.comp.web.zope.plone.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32719"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32718"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32717"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32716"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32715"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32714"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32713"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32709"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32708"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32707"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32706"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32705"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32704"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32703"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32701"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32700"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32699"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32698"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32697"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32696"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32719">
    <title>Re: Introducing plonetheme.diazo_sunburst</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32719</link>
    <description>&lt;pre&gt;

I have some ideas on new a new kind of rules that would simplify most
rules. We tend to find complex rules often related to iteration and
looping. For example changing one navtree into another. We'd like more
direct support for that so the HTML of the theme navtree and lots of
xsl doesn't end up in the rules.xml



------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
&lt;/pre&gt;</description>
    <dc:creator>Dylan Jay</dc:creator>
    <dc:date>2013-06-19T22:33:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32718">
    <title>Introducing plonetheme.diazo_sunburst</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32718</link>
    <description>&lt;pre&gt;Hi,

I needed this package for a client; moreover, I needed to better understand
the status quo in Plone wrt to a various theming and front-end
issues/concepts, so I made this, a "port" of Plone 4's default theme
"Sunburst" to Diazo:

- https://pypi.python.org/pypi/plonetheme.diazo_sunburst/0.0.1

I hope it's helpful/useful. A few observations/comments:

- I love how Diazo/plone.app.theming converts relative URLs to absolute URLs
for theme resources as well as other resources. But I wonder if this feature
is clear enough. I'm often tempted to insert relative links to e.g.
"++theme++my.theme" which are not converted.

- This theme should function almost exactly as the "real" Sunburst, please
let me know if it doesn't:
https://github.com/aclark4life/plonetheme.diazo_sunburst/issues

- Patches happily accepted and appreciated.

- Complex rules.xml frighten me. I had a look at quintagroup.theme.schools
during development and it's impressive. However, it strikes as being "too
customized". I think we should encour&lt;/pre&gt;</description>
    <dc:creator>Alex Clark</dc:creator>
    <dc:date>2013-06-19T22:06:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32717">
    <title>Re: [Plone-Users] Hotfix Posted for security vulnerability 20130618</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32717</link>
    <description>&lt;pre&gt;I've seen this issue on versions 4.1 to 4.3 so far. I'll debug this
tomorrow and give more detail - we still have some sites to patch
before we can look into this in more detail.

--
Roché Compaan
Upfront Systems                   http://www.upfrontsystems.co.za


On Wed, Jun 19, 2013 at 10:01 PM, Nathan Van Gheem &amp;lt;vangheem-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
&lt;/pre&gt;</description>
    <dc:creator>Roché Compaan</dc:creator>
    <dc:date>2013-06-19T20:23:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32716">
    <title>Re: [Plone-Users] Hotfix Posted for security vulnerability 20130618</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32716</link>
    <description>&lt;pre&gt;I've heard of a couple people saying this but have not been able to
reproduce myself.

It seems like, if it can't find the user, this error will occur. The
problem is, what isn't it finding the user?

What version of plone are you on?


-Nathan


On Wed, Jun 19, 2013 at 2:06 PM, Roché Compaan
&amp;lt;roche-kb4xc5yObU3kQYj/0HfcvhBnub05S5/X&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
&lt;/pre&gt;</description>
    <dc:creator>Nathan Van Gheem</dc:creator>
    <dc:date>2013-06-19T20:01:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32715">
    <title>Re: [Plone-Users] Hotfix Posted for securityvulnerability 20130618</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32715</link>
    <description>&lt;pre&gt;After patching today we are suddenly seeing the following error across
a few different Plone instances:

Traceback (innermost last):
  Module ZPublisher.Publish, line 60, in publish
  Module ZPublisher.mapply, line 77, in mapply
  Module ZPublisher.Publish, line 46, in call_object
  Module Products.CMFCore.FSPythonScript, line 127, in __call__
  Module Shared.DC.Scripts.Bindings, line 322, in __call__
  Module Products.PloneHotfix20130618.spamProtect, line 35, in
_patched_bindAndExec
  Module Products.PloneHotfix20121106.python_scripts, line 63, in
_patched_bindAndExec
  Module Shared.DC.Scripts.Bindings, line 359, in _bindAndExec
  Module Products.PythonScripts.PythonScript, line 344, in _exec
  Module script, line 5, in mail_password
   - &amp;lt;FSPythonScript at /emas/maths/mail_password&amp;gt;
   - Line 5
  Module Products.PloneHotfix20130618.mail_password, line 45, in mailPassword
AttributeError: 'NoneType' object has no attribute 'getId'

I haven't debugged this but tested password reset on a few Plone
instances a&lt;/pre&gt;</description>
    <dc:creator>Roché Compaan</dc:creator>
    <dc:date>2013-06-19T19:06:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32714">
    <title>Re: Dexterity Items cannot be imported using GS</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32714</link>
    <description>&lt;pre&gt;I just added support in plone.dexterity for GS import/export, based on 
the existing rfc822 serialization support for WebDAV: 
https://github.com/plone/plone.dexterity/commit/a028c264d3f8749654b17818083de5992ff8b5ad

David

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
&lt;/pre&gt;</description>
    <dc:creator>David Glick (Plone</dc:creator>
    <dc:date>2013-06-19T02:49:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32713">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32713</link>
    <description>&lt;pre&gt;now that i've read, what OOCSS measn, i'm also totally in favor of it.
i'll start using it's principles for my next css works right away.

for those who don't know: it's an methodology, that's the first thing
i've had to learn. and as a sucht it summarizes how css should be
written to create reusable classes.

here is an good overview:
http://coding.smashingmagazine.com/2011/12/12/an-introduction-to-object-oriented-css-oocss/

less or sass can immensely help creating easy to maintain css files. if
you ask me, i'm in favor of less, since i know it and i can't remember
that i was missing something from it.

best,
johannes


On Mon, 2013-06-17 at 10:41 -0700, Elizabeth Leddy wrote:

&lt;/pre&gt;</description>
    <dc:creator>Johannes Raggam</dc:creator>
    <dc:date>2013-06-18T21:28:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32709">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32709</link>
    <description>&lt;pre&gt;I've given LESS another look, but It doesn't have all the built-in mixins
and functions that Compass brings (which brings major speedup to all the
CSS3 stuff).


On Tue, Jun 18, 2013 at 10:40 AM, Rok Garbas &amp;lt;rok-k5+lt39nHzj1KXRcyAk9cg&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
&lt;/pre&gt;</description>
    <dc:creator>Thijs Jonkman</dc:creator>
    <dc:date>2013-06-18T17:43:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32708">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32708</link>
    <description>&lt;pre&gt;+ 100 to OOCSS + (less or sass). FYI, the SF Plone meet up group is meeting up next month (in a couple of weeks) to rewrite a piece of plone in both methodologies to see what it feels like. Hopefully we can post samples of both at the end to help make decision.  

Liz 

&lt;/pre&gt;</description>
    <dc:creator>Elizabeth Leddy</dc:creator>
    <dc:date>2013-06-18T17:23:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32707">
    <title>Re: Workaround for download.zope.org</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32707</link>
    <description>&lt;pre&gt;


No problem! I've further refined this to make PythonPackages'
4.3.1-versions.cfg include all of the relevant version specs in a single file:

-
https://github.com/pythonpackages/buildout-plone/blob/master/4.3.1-versions.cfg
[1]

It probably makes some sense for Plone to do this with its release version
config files (as an alternate to mirroring Zope's version configs).

[1] According to Jim Fulton, "if an option is repeated, later occurences
override earlier ones" which presumably handles the case of Plone's version
spec overriding something in Zope2/ZTK. (Why is zopeapp differentiated here?
I assumed every zope package not in Zope2 was part of ZTK) In other words:
if you import the versions from the extended files in the same file before
the versions in the current file, you should get the same effect i.e. all
the correct versions.


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/wind&lt;/pre&gt;</description>
    <dc:creator>Alex Clark</dc:creator>
    <dc:date>2013-06-18T13:33:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32706">
    <title>Re: JavaScript module loading</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32706</link>
    <description>&lt;pre&gt;plone.app.widgets is meant to be the plone 4.3 integration of mockup.


On Tue, Jun 18, 2013 at 7:40 AM, Sean Upton &amp;lt;sdupton-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
&lt;/pre&gt;</description>
    <dc:creator>Nathan Van Gheem</dc:creator>
    <dc:date>2013-06-18T12:44:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32705">
    <title>Re: JavaScript module loading</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32705</link>
    <description>&lt;pre&gt;
I see the value in doing this completely on the client-side, but let
me take a bit of a turn here, and ask folks how we can polyfill some
of the mockup stuff into Plone 4?  A lot of folks doing JS development
outside the core are doing so for *NOW* projects, and would be more
likely to contribute to future if some of what they contribute is
useful now.  I have two specific widget improvement areas I want to
contribute to mockup, much easier to justify my time spent if I can
have a story for re-purposing at least in-part for Plone 4.3 deployed
add-ons.

Sean

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
&lt;/pre&gt;</description>
    <dc:creator>Sean Upton</dc:creator>
    <dc:date>2013-06-18T12:40:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32704">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32704</link>
    <description>&lt;pre&gt;Quoting Elizabeth Leddy (2013-06-17 19:41:28)

oocss looks nice and hopefully becomes a standard soon. both sass and less are
capable of doing the same thing.

about sass. currently to setup mockup we install require developer to install
nodejs and ppl already have trouble doing it. requiring sass would mean that
developer needs to install ruby as well.

i know sass is more capable (in some areas) then less (which is written in
nodejs) but we really have to see if we gain that much with sass to complicate
developers setup. and also one thing is to install it and another thing is to
maintain it, i would really like to avoid having yet another language if we
dont need really _really_ need it.

on +1 to eliminate as much id as possible. would be nice that at least our
default theme doesn't depend on any id.

also it would be nice to develop plone related "oocss objects" using less/sass,
in similar manner that is being done here: http://axle.dalesande.com



--
Rok Garbas - http://www.garbas.si

----------------&lt;/pre&gt;</description>
    <dc:creator>Rok Garbas</dc:creator>
    <dc:date>2013-06-18T08:40:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32703">
    <title>Re: [Framework-Team] Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32703</link>
    <description>&lt;pre&gt;Hey, Eric so great !! I love the plan.

on the fly and some minor bugs solved and later 1.2 with a shared content
solution that feets on the plone way of life :) After that, we will start
working on the PLIP to propose what should be on plone by default and what
should be on a official add-on to have a OOB multilingual solution.

and there is also a thread on the Plone-UI list. I don't know who should
decide where we should go, but IMHO we should move to use more commonly
used (but maybe less cool, optimal, ... ) solutions that helps people
outside plone to come to plone. For example, deco.gs is great, bootstrap is
great, we can discuss during days about which is better, but bootstrap is
widely used, and people are happy with them ( and is maintained ). It's the
same discussion on less/sass , both are great, but we should decide to use
what is easier to maintain ( and we can always change on future ).

I know that on Plone-UI list, Oriol, Thijs, Nathan are talking about plone
5 theme and I like the idea behi&lt;/pre&gt;</description>
    <dc:creator>Ramon Navarro Bosch</dc:creator>
    <dc:date>2013-06-18T08:44:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32701">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32701</link>
    <description>&lt;pre&gt;

hey all, uploaded this cause it seems relevant -
https://github.com/collective/plonetheme.diazoboilerplate41

I am coding it with the goal to have a diazo theme I can hand to a CSS 
designer with the most common diazo rules implemented and to have a 
mockup which forces the CSS coder to cover all the Plone cases I need 
them to cover.

So it has three aspects:

- The boilerplate theme itself doesn't have content in it to theme, but 
the idea is that the theme when used in plone should produce HTML which 
can then be re-used as the mockup file. So the mockup should be able to 
do a round trip through plone and be used as a mockup again. (The only 
catch is that you need to remove the absolute part of resource URLs)

- The theme has an edited version of public.css (hence this theme is 
fixed to Plone 4.1). The edited version of public.css wrappes plone 
styles in a 'plonestyle' class. Allowing the diazo to style plone 
specific widgets.

- Lastly, the mockup is annotated with HTML comments giving an 
indicat&lt;/pre&gt;</description>
    <dc:creator>Adam Terrey</dc:creator>
    <dc:date>2013-06-18T03:35:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32700">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32700</link>
    <description>&lt;pre&gt;
I'm not 100% sold on the "no ids" concept but other than that OOCSS looks hot. There has been some talk in this arena that it's best when combined with SASS. Does anyone have strong opinions either way?  

Liz------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
&lt;/pre&gt;</description>
    <dc:creator>Elizabeth Leddy</dc:creator>
    <dc:date>2013-06-17T17:41:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32699">
    <title>Re: Workaround for download.zope.org</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32699</link>
    <description>&lt;pre&gt;Thank you!!!  

&lt;/pre&gt;</description>
    <dc:creator>Elizabeth Leddy</dc:creator>
    <dc:date>2013-06-17T16:10:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32698">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32698</link>
    <description>&lt;pre&gt;
+10

&lt;/pre&gt;</description>
    <dc:creator>Guido Stevens</dc:creator>
    <dc:date>2013-06-17T12:43:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32697">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32697</link>
    <description>&lt;pre&gt;
For a new theme it would be good to use OOCSS like practices. Order the
styles from generic to specific, make use of the well setup object oriented
plone classes, to create low specificity easily overridable selectors. No
more id's, no more !importants and short, efficient selectors.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
&lt;/pre&gt;</description>
    <dc:creator>Thijs Jonkman</dc:creator>
    <dc:date>2013-06-17T11:35:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32696">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32696</link>
    <description>&lt;pre&gt;On Sat, Jun 15, 2013 at 7:31 PM, Elizabeth Leddy
&amp;lt;elizabeth.leddy-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:


It is the right way if you see the sunburst theme as a css framework.
Depending on the difference between sunburst and what you are trying to
accomplish it could result in a lot of extra css on top of plone's already
big stack.
I tend to take the sunburst styles and convert them to sass and then part
change, part add at the end.

FYI, for Plone 5 you will not be required to switch to the new theme at

I have a lot of ideas on that :-) For how Sunburst looks it uses way to
much css. Also importants and even id styling should not be used, because
it's just not necessary. The best would be if the theme part of the new
theme is a very light layer on top of an existing light weight framework.


You shouldn't have to deal with deco at all, if you use it as prescribed. I
have a sass file that creates custom versions of deco for me (I tend to
just include the convenience classes from 1/2 to 1/6, I also &lt;/pre&gt;</description>
    <dc:creator>Thijs Jonkman</dc:creator>
    <dc:date>2013-06-17T11:25:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32695">
    <title>Re: JavaScript module loading</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32695</link>
    <description>&lt;pre&gt;
On Jun 17, 2013, at 12:54 , Johannes Raggam &amp;lt;raggam-nl-u+9JQtDlGM4&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


As one of the drivers of patternslib I see no risk there. We have ongoing customer projects that drive a lot of patterns development that have a longer lifetime, and several of us have been using patterns in other projects that will need to be maintained for a long time as well. I do agree that Patternslib should get a lot more marketing than we've been doing so far.

Wichert.


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
&lt;/pre&gt;</description>
    <dc:creator>Wichert Akkerman</dc:creator>
    <dc:date>2013-06-17T11:05:01</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.devel</link>
  </textinput>
</rdf:RDF>
