<?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/32482"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32481"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32480"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32479"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32478"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32477"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32476"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32475"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32474"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32473"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32472"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32471"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32470"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32469"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32468"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32467"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32466"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32465"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32464"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32463"/>
      </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/32482">
    <title>Re: 4.2.6, 4.3.1</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32482</link>
    <description>&lt;pre&gt;Ah, that's my fault from a change in z3c.form; I'll fix it.
------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
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>David Glick (Plone</dc:creator>
    <dc:date>2013-05-24T00:24:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32481">
    <title>Re: 4.2.6, 4.3.1</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32481</link>
    <description>&lt;pre&gt;

Thank you. That last one is in plone.autoform: 


Look familiar to anyone? 

------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
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>Eric Steele</dc:creator>
    <dc:date>2013-05-24T00:21:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32480">
    <title>Re: 4.2.6, 4.3.1</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32480</link>
    <description>&lt;pre&gt;

If fixed 3 of 4 remaining failures
i can't identify the last failing test :
.view.txt&amp;lt;https://jenkins.plone.org/view/Core/job/plone-4.3-python-2.7/lastCompletedBuild/testReport/%28root%29//view_txt/&amp;gt;(?)
(
https://jenkins.plone.org/view/Core/job/plone-4.3-python-2.7/677/testReport/)






&lt;/pre&gt;</description>
    <dc:creator>thomas desvenain</dc:creator>
    <dc:date>2013-05-23T21:44:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32479">
    <title>Re: 4.2.6, 4.3.1</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32479</link>
    <description>&lt;pre&gt;Mainly time. I'll get off my ass and start making releases tonight. 

If someone could look into the current failures on 4.3 (https://jenkins.plone.org/view/Core/), I'd appreciate it.

Eric 


On Thursday, May 23, 2013 at 1:42 PM, Maarten Kling wrote:


------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
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>Eric Steele</dc:creator>
    <dc:date>2013-05-23T19:54:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32478">
    <title>Re: 4.2.6, 4.3.1</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32478</link>
    <description>&lt;pre&gt;Hi Eric,

Is there anything (except time) blocking the 4.3.1 release?
It would be nice to have a new release. If there are blocking issues 
please list them maybe i can help.

Thanks,
Kabz

&lt;/pre&gt;</description>
    <dc:creator>Maarten Kling</dc:creator>
    <dc:date>2013-05-23T17:42:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32477">
    <title>Re: enhanced collections views</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32477</link>
    <description>&lt;pre&gt;Hi,

On 23 May 2013 13:51, Dylan Jay &amp;lt;djay-n0pU0XVUApFWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


A (transient) tile is saved entirely as a URL, with query string
parameters for configuration. That's relatively easy to move around.


I agree with that philosophy.


There are some ways to make choices:

 - The 'display' menu
 - Tags/keywords
 - Content types (or 'categories' as Deco would call them)

These are all valid. Personally, I think perhaps the content type
option is most logical. You choose what type you want before you
insert the item, as we can use per-folder type restrictions to
constrain the site's information architecture.

The basic implementation of categories in Deco simply creates new
types in portal_types when a (super)user saves a new category of page.


I think there are three roles here:

 - Editors
 - Site admins
 - Themers

I think site admins are the ones who decide what content can go where.
A themer will make a theme that is as generic as necessary to support
what editors do within the c&lt;/pre&gt;</description>
    <dc:creator>Martin Aspeli</dc:creator>
    <dc:date>2013-05-23T13:31:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32476">
    <title>Re: enhanced collections views</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32476</link>
    <description>&lt;pre&gt;
 could be very powerful.

so in summary. if we 
- took listingviews (ie named set of fields to show for content + for each item in a list)
- put it into the themeeditor with a UI (with some corresponding file format) such as using tiles with attribute encoding like you suggest.
- had more help and nicer widgets, 
- included the querystring builder such that listingview can be a self contained view, or the query can be left out so that the list comes from folders or collections
- some way to hard code them into a theme or alternatively let them be used in deco tiles, portlets or dynamic views.
How does that sound?





------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf&lt;/pre&gt;</description>
    <dc:creator>Dylan Jay</dc:creator>
    <dc:date>2013-05-23T12:51:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32475">
    <title>Re: Tagging RF tests</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32475</link>
    <description>&lt;pre&gt;Brilliant, thanks!! That was what I was looking for :)

Cheers,
Gil


2013/5/22 &amp;lt;asko.soukka-X3B1VOXEql0&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may_______________________________________________
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>Gil Forcada Codinachs</dc:creator>
    <dc:date>2013-05-23T12:37:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32474">
    <title>Re: Plone 4.3 takes a lot of time to compose and compress javascripts?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32474</link>
    <description>&lt;pre&gt;It was something I was thinking about too, thanks Alessandro! The ZHW 
says it was taking time on the re.compile expression, maybe there's some 
relation between compression, big file and comession none?

I think the safe compression created just a too big line and re.compile 
has some performance problems on big lines, maybe? Putting the 
compression to none, it creates a file with the same content but 
splitted in more lines.

The longest lines are:

/* collective.js.jqueryui: jquery.ui.datepicker.min.js */

and

/* collective.js.jqueryui: jquery-ui-i18n.js */


I think this can be a problem for collective.js.jqueryui users and for 
future very long javascripts, I'm ccing the collective.js.jqueryui 
mantainer.


Il 22/05/2013 23:47, Alessandro Pisa ha scritto:


------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analyti&lt;/pre&gt;</description>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2013-05-23T08:42:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32473">
    <title>Re: Plone 4.3 takes a lot of time to compose and compress javascripts?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32473</link>
    <description>&lt;pre&gt;

Already bitten by this :)
If I rememeber well I solved:
 - going to portal_javascript
 - looking for collective.js.jqueryui.custom.min.js
 - setting the compression type to none

At the end the js is already minified :p

Ciao
&lt;/pre&gt;</description>
    <dc:creator>Alessandro Pisa</dc:creator>
    <dc:date>2013-05-22T21:47:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32472">
    <title>Re: Tagging RF tests</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32472</link>
    <description>&lt;pre&gt;Hi Gil,

passing non-critical test tags for zope.testrunner robotsuites was contributed recently and is available with the latest robotsuite release. See also the comments at:

https://github.com/collective/robotsuite/pull/1

Cheers,
Asko
 
 


Timo Stollenwerk kirjoitti 22.5.2013 19:18:

Am 22.05.2013 18:09, schrieb Gil Forcada Codinachs:


Do they always fail on Jenkins or just randomly? Our coredev robot tests 
used to fail on Jenkins every now and then because sometimes the 
selenium tests try to access a component that has not been fully loaded 
yet. You have to make sure the tests wait until the page has been fully 
loaded (with "Wait until page contains" and "Wait until keyword 
succeeds") before typing in data or testing for content. See for instance

https://github.com/plone/Products.CMFPlone/blob/4.3.x/Products/CMFPlone/tests/robot/test_overlays.robot


for examples.


Timo



------------------------------------------------------------------------------

Try New Relic Now &amp;amp; We'll Send You this Coo&lt;/pre&gt;</description>
    <dc:creator>asko.soukka-X3B1VOXEql0&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-22T16:56:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32471">
    <title>Re: Tagging RF tests</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32471</link>
    <description>&lt;pre&gt;Am 22.05.2013 18:09, schrieb Gil Forcada Codinachs:

Do they always fail on Jenkins or just randomly? Our coredev robot tests 
used to fail on Jenkins every now and then because sometimes the 
selenium tests try to access a component that has not been fully loaded 
yet. You have to make sure the tests wait until the page has been fully 
loaded (with "Wait until page contains" and "Wait until keyword 
succeeds") before typing in data or testing for content. See for instance

https://github.com/plone/Products.CMFPlone/blob/4.3.x/Products/CMFPlone/tests/robot/test_overlays.robot

for examples.

Timo



------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2&lt;/pre&gt;</description>
    <dc:creator>Timo Stollenwerk</dc:creator>
    <dc:date>2013-05-22T16:18:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32470">
    <title>Re: enhanced collections views</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32470</link>
    <description>&lt;pre&gt;

agreed.



yes, thats pretty much it. except with the addition you can include tal expressions if the catalog fields aren't enough for you.



ah ok I see where you are going now. 

I agree that there is no point to having listingviews in the control panel when they are so linked to the a diazo theme. 

In terms of using tile html representation, thats a clever idea esp since most of the work is already done to give us a UI to edit them. The one downside I see is that there isn't human editable data format so you can't use a code editor to cut and paste a listingview definition very easily. You have to rely on the forms.

However I don't think it's a good idea to move everything into the theme. There is always a connection between what is in the content area and the theme. 
I see the themer's job is to provide a set of tools the content editor can use to do their job. 

For example a "one place" solution for a blog would be hard coding the url /blog into your theme and making it do a query on all news item&lt;/pre&gt;</description>
    <dc:creator>Dylan Jay</dc:creator>
    <dc:date>2013-05-22T15:58:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32469">
    <title>Re: Plone 4.3 takes a lot of time to compose and compress javascripts?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32469</link>
    <description>&lt;pre&gt;
Forgot to add that this file is 234,84 kB (240481 byte). This seems 
quite big for a javascript...

------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
&lt;/pre&gt;</description>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2013-05-22T14:49:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32468">
    <title>Re: Plone 4.3 takes a lot of time to compose and compress javascripts?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32468</link>
    <description>&lt;pre&gt;In Products/ResourceRegistries/tools/packer.py, line 251 :

         for index, replacement in replacelist:
             # we use lambda in here, so the real string is used and no 
escaping
             # is done on it
             before = len(output)
             regexp = re.compile('\x00%i\x00' % (index+1))
             output = regexp.sub(lambda m:replacement, output)
         # done

isn't re.compile useless because of the loop? It is used once every time 
with a different index, but I'm a bad programmer so maybe I can't get it :-P




Il 22/05/2013 16:13, Yuri ha scritto:


------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, &amp;amp; servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
&lt;/pre&gt;</description>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2013-05-22T14:33:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32467">
    <title>Plone 4.3 takes a lot of time to compose andcompress javascripts?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32467</link>
    <description>&lt;pre&gt;Hi!

  tryng to debug while some pages took long to diplay, I've found that 
the problem was portal_javascripts js that take so long. This happen 
until the javascript is compiled/compressed by portal_javascript. I've 
installed ZopeHealth watch and was able to catch this behaviour. On the 
browser, requesting for example the url:

portal_javascripts/kss-bbb-cachekey-a4a4185a8da6b0ec16ca901b894e999a.js

it returns (until it has finished to compress/compile it) something like 
"internal server error", it can takes more than 15 seconds before giving 
the error.

It seems to happen mostly with this merged composition:

====================

/* Merged Plone Javascript file
  * This file is dynamically assembled from separate parts.
  * Some of these parts have 3rd party licenses or copyright information attached
  * Such information is valid for that section,
  * not for the entire composite file
  * originating files are separated by - filename.js -
  */

/* - kss-bbb.js - */

**omitted**

/* - inline_validatio&lt;/pre&gt;</description>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2013-05-22T14:13:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32466">
    <title>Supermodel, Dexterity Content types,named relations between content types</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32466</link>
    <description>&lt;pre&gt;Returning to Plone after a bit of hiatus...I have been playing with
the supermodel schema, and I think it is really cool. I have two
questions about the way Plone is moving forward with dexterity content
types, and how they work with each other.
First, I am trying to use the titles of instances of one Dexterity
content type (dctA) to fill the choice parameters for a field in
another content type (dctB).
I see that I can iterate over the instances of  dctA, register these
titles as a vocabulary, and then use the &amp;lt;vocabulary &amp;gt; tag within
supermodel..but the latter part seems to require filesystem level
access.  I would rather not give this access to my
students--preferring to have them focus on the generation of portable
xml models.  Am I missing another more straightforward way that allows
me to call dctA titles as choices for the field directly?  I do see
from supermodel's docs that  "...we can import a choice field with a
source, provided that source can be specified via an importable dotted
name..." But I &lt;/pre&gt;</description>
    <dc:creator>matthew lange</dc:creator>
    <dc:date>2013-05-21T22:36:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32465">
    <title>Re: enhanced collections views</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32465</link>
    <description>&lt;pre&gt;Hi,

(Small request: can we avoid giant images to a mimum, please? The
horizontal width of my Gmail has gone haywire ;-)


On 20 May 2013 16:22, Dylan Jay &amp;lt;djay-n0pU0XVUApFWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


I can buy that. It does mean the bar for usability and "future
proofing" is pretty high, though. Once something goes into core, it's
hard to take out.



So, to check that I understand: without this, it provides
UI-configurable views for folders, content items, portlets or
collections where the administrator can choose what gets rendered
(from schema or catalogue fields) and how (e.g. pagination)


That's a good start, indeed.



I think that's quite powerful. It does, however, create a dependency
between a theme and things in content space (layout of folders, items,
collections; assignments of portlets; assignments of custom views).
This makes it somewhat harder to package and propagate themes (e.g.
from dev to test to production). It may be worth thinking about how we
solve this, probably by using t&lt;/pre&gt;</description>
    <dc:creator>Martin Aspeli</dc:creator>
    <dc:date>2013-05-20T18:51:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32464">
    <title>Re: enhanced collections views</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32464</link>
    <description>&lt;pre&gt;
On 20/05/2013, at 11:40 PM, Martin Aspeli &amp;lt;optilude+lists-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


because it's tightly linked to theming and collections. You can create much better themes with something like listingviews.
Although I think a way to create forms in the core to replace PFG (based on dexterity schema editor) would be a good idea I think PFG doesn't have that many interactions with other components. 


good question. The custom fields is meant to be an advanced option. listing views is still very useful without using them.
It could be improved with some inline documentation or common api and by having many of the commonly used expressions preset for use in listing views (which we've already started doing)


hence why I'm bringing it to this list.
I'm very open to how to improve it and know that anything in the core has very well thought out and easy to use and that isn't hard.


It's a themer tool. Since it requires daizo changes to make it look like you want it's tightly liked to your&lt;/pre&gt;</description>
    <dc:creator>Dylan Jay</dc:creator>
    <dc:date>2013-05-20T15:22:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32463">
    <title>Re: enhanced collections views</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32463</link>
    <description>&lt;pre&gt;Hi


On 20 May 2013 08:27, Dylan Jay &amp;lt;djay-n0pU0XVUApFWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


It would be useful to articulate "why", i.e. why is it better for this to
be in core than in an add-on? I wonder if c.listingviews is analogous to
PloneFormGen: perhaps a "must have" add-on for a lot of sites, but not
something necessarily appropriate for core (either because it is confusing
to a casual end user, as opposed to the type of power-user [but
non-developer] you describe, or because of concerns around maintainability
and technology choice, or simply to allow more rapid innovation). That's a
genuine question, though, not an attempted put-down.



One question: How do people not familiar with the internals of Plone figure
out what to put in the 'TAL expression' boxes?



I am a bit sceptical when people say things like "some more UI love" or
"all that remains is some UI" as if that was the easy part. I think for
this kind of thing to be part of making Plone more user friendly and not
less, the UI needs to be&lt;/pre&gt;</description>
    <dc:creator>Martin Aspeli</dc:creator>
    <dc:date>2013-05-20T13:40:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32462">
    <title>Re: Tagging RF tests</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/32462</link>
    <description>&lt;pre&gt;Hi Gil,

not sure if this is useful (since you can use tags if you want) but I 
use zope.testrunner's layers to group my robot tests:

https://pypi.python.org/pypi/zope.testrunner/4.3.3#test-grouping

I usually assign all my robot tests to level 2, so they are not run by 
default when calling "bin/test". I use robot tests only for acceptance 
testing and I usually end up with quite a few tests, so I don't want to 
run those tests locally (at least not all of them). Before I commit I 
don a "bin/test" to test everything except the robot tests and then run 
the robot acceptance test I'm currently working on with "bin/test -t 
1778 --all" (1778 in this example is the issue tracker number of the 
single acceptance test I want to run and part of the name of this test, 
e.g. test_acceptance_1778.robot).

This way works quite well for me, Jenkins makes sure all my 
(robot)-tests still pass (just run "bin/jenkins-test --all" on Jenkins) 
and I don't have to run them all locally.

Here is my testing.py to set the tes&lt;/pre&gt;</description>
    <dc:creator>Timo Stollenwerk</dc:creator>
    <dc:date>2013-05-20T08:32:14</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>
