adam tang | 1 Nov 2011 15:26
Picon

Is Dexterity xml model schema support i18n translation?

Hi all,
I want to know if the following i18n directory is valid?
  1. <model>
  2. <schema>
  3.   <field name="title" type="zope.schema.TextLine">
  4.     <title i18n:translate="">Title</title>
  5.     <required>True</required>
  6.   </field>
  7.   <field name="body" type="zope.schema.Text">
  8.     <title i18n:translate="">Body text</title>
  9.     <required>False</required>
  10.   </field>
  11. </schema>
  12. </model>


--
三人行必有我师!
There are three men walking together.(collaboration,innovation and comity, THREE AS ONE.)
WebSite building Expert:http://315ok.org/
------------------------------------------------------------------------------
RSA&reg; Conference 2012
Save &#36;700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Plone-developers mailing list
Plone-developers@...
https://lists.sourceforge.net/lists/listinfo/plone-developers
Martin Aspeli | 2 Nov 2011 12:55
Picon
Gravatar

ZopeSkel 3.0a1

Argh! :)

Somewhere between yesterday afternoon and right now, ZopeSkel 3.0a1
disappeared off PyPI.

As I told my training course attendees, all 26 of which now have a
build with ZopeSkel = 3.0a1 pinned, removing packages from PyPI *ever*
is a terrible sin. I suggested the workaround if it ever happened was
to find out who did it and, well... ;-)

Can we please have it back? It's OK if it's hidden, but deleting it is very bad.

Martin

------------------------------------------------------------------------------
RSA&#174; Conference 2012
Save $700 by Nov 18
Register now&#33;
http://p.sf.net/sfu/rsa-sfdev2dev1
Tom Gross | 2 Nov 2011 14:34
Picon
Gravatar

Re: ZopeSkel 3.0a1

Hi Martin,

try this:

http://plone.org/products/zopeskel/releases/3.0a1/ZopeSkel-3.0a1.zip

Have fun on the conference :)

-Tom

Am 02.11.2011 12:55, schrieb Martin Aspeli:
> Argh! :)
>
> Somewhere between yesterday afternoon and right now, ZopeSkel 3.0a1
> disappeared off PyPI.
>
> As I told my training course attendees, all 26 of which now have a
> build with ZopeSkel = 3.0a1 pinned, removing packages from PyPI *ever*
> is a terrible sin. I suggested the workaround if it ever happened was
> to find out who did it and, well... ;-)
>
> Can we please have it back? It's OK if it's hidden, but deleting it is very bad.
>
> Martin
>
> ------------------------------------------------------------------------------
> RSA&#174; Conference 2012
> Save $700 by Nov 18
> Register now&#33;
> http://p.sf.net/sfu/rsa-sfdev2dev1

------------------------------------------------------------------------------
RSA&#174; Conference 2012
Save $700 by Nov 18
Register now&#33;
http://p.sf.net/sfu/rsa-sfdev2dev1
Kees Hink | 2 Nov 2011 17:41

new Dutch translations for roles

Maurits van Rees, Maarten Kling and i have been talking in on the plone-nl
mailinglist [1] about the current Dutch translations of roles: We're unhappy
with them.

A summary of two problems we have:

Editor is translated as "Schrijver", which means "author" or "writer" in Dutch.
The actual Editor role is more to do with editing content than starting it.

Contributor currently becomes "Medewerker", in Dutch this means "someone who is
co-operating", it is also being used as "employee" or colleague". This
translation doesn't give a clue about what the permissions of the role
(Contributor) are.

We propose these changes:

Reviewer (was Redacteur): Eindredacteur
Editor (was: Schrijver): Bewerker
Contributor (was: Medewerker): Bijdrager
We feel that these words (while still sounding a bit unnatural) describe more
adequately and intuitively what the role is for, and what permissions come with it.

We'd like to drop this suggestion here so everybody gets a chance too think
about it. Some add-on products might need to update their Dutch translations as
well. Probably it's a good idea to land the new translations in the next 4.x
release, so is 4.2 feasible?

Kees

[1] http://www.mail-archive.com/plone-plone-nl-G3yHMj00SlOLbbK5bonKug <at> public.gmane.org/msg00003.html
(Dutch)

------------------------------------------------------------------------------
RSA&#174; Conference 2012
Save $700 by Nov 18
Register now&#33;
http://p.sf.net/sfu/rsa-sfdev2dev1
AnthonyG | 2 Nov 2011 23:22
Picon

Latest thinking on serving css and javascript with plone.app.theming

Hi,

I'm wondering what the latest thinking is on serving css and javascript with
plone.app.theming.  For me adding support for Products.ResourceRegistries
like functionality to plone.app.theming would be a big win.  A theme will
most likely comprise of a collection of css and javascript files and it
would be great if these could be compressed, concatenated and cached in the
powerful way that resources for standard Plone pages are.

Must haves:
* a theme should be able to register the css and javascript it requires to
render pages.  I'd suggest the best way to achieve this would be to extend
Products.ResourceRegistries to have multiple css and javascript registries
(one per theme) and a standard place to put this configuration in a theme
zip
* this might reference both files from the theme and ones in the Plone core
* it should then provide a way in rules.xml to insert required <link> and
<script> tags referencing virtual resources (the compressed, concatenated
versions of the original set). Perhaps via an element in a new
plone.app.theming namespace that sends a subrequest to a styles / javascript
view of ResourceRegistries? e.g. <theme:css /> <theme:javascript />

Should haves:
* categorize resources as only relevant when certain conditions are met in
the theme.  This might be done via the existing condition field. e.g.
"theme.type = 'leaf'"
* provide a way of passing arguments to the registry from the theme. e.g.
<theme:css><theme.param name="type" value="leaf"/></theme:css>

The bulk of the work seems to me to be in enabling support for additional
registries in Products.ResourceRegistries.

I can also see a much less involved solution which just involves the
additional <theme:css> and <theme:javascript> elements to plone.app.theming. 
These would put an attribute on the subrequest that you can then check for
in the registry condition attributes.  You'd configure your resources using
generic set-up profiles in the normal way.

How does this match other peoples ideas in this area?  Is anyone working on
this right now? 

I might be able to persuade my client to allow me to spend a reasonable
amount of time contributing to this.

--
View this message in context: http://plone.293351.n2.nabble.com/Latest-thinking-on-serving-css-and-javascript-with-plone-app-theming-tp6957198p6957198.html
Sent from the Core Developers mailing list archive at Nabble.com.

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
Ross Patterson | 4 Nov 2011 01:45
Favicon
Gravatar

Re: Review process

Malthe Borch <mborch@...> writes:

> On 24 October 2011 08:43, Godefroid Chapelle
> <gotcha@...> wrote:
>> Reason why I think we should RECOMMEND to ask for reviews before merging
>> our pull requests.
>
> Pull requests also offer (and to some extent mandate) that you type in
> a good reason for someone (or ultimately, yourself) to merge a
> changeset into the master branch. It's a nice way to track and
> document big changes.
>
> Maybe if a mail was automatically sent to plone-dev every time a pull
> was requested, it would help "spreading the news" that an interesting
> changeset had been submitted.

I was just going to ask if this is possible.  It also allows for the
pull request mailing list post to become a thread for discussion when
discussion is warranted.

Ross

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
Malthe Borch | 4 Nov 2011 09:18
Picon
Gravatar

Re: Review process

On 4 November 2011 01:45, Ross Patterson <me <at> rpatterson.net> wrote:
> I was just going to ask if this is possible.  It also allows for the
> pull request mailing list post to become a thread for discussion when
> discussion is warranted.

From the docs on Github:

  "Everyone that can push to the base repository will receive an email
notification"

So I suppose if plone-dev <at> lists... was a user that could push, then it
would receive the notification and thus send it to the list – if the
Github e-mail daemon was allowed to post to plone-dev that is.

\malthe

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Plone-developers mailing list
Plone-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-developers
adam tang | 4 Nov 2011 09:38
Picon

Diazo theme 's control panel is invalid ?

I had installed optilux.policy and all of packages of professional plone4 develop book 's codes.
and also  enabled optilux.theme in Diazo theme control panel,but the cinema theme can not display ,instead of it is default plone theme.

I should how to do  for seeing the optilux theme?

Thanks.

--
三人行必有我师!
There are three men walking together.(collaboration,innovation and comity, THREE AS ONE.)
WebSite building Expert:http://315ok.org/

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Plone-developers mailing list
Plone-developers@...
https://lists.sourceforge.net/lists/listinfo/plone-developers
Maurits van Rees | 4 Nov 2011 10:48
Picon
Favicon
Gravatar

Re: Review process

Op 04-11-11 09:18, Malthe Borch schreef:
> On 4 November 2011 01:45, Ross Patterson<me <at> rpatterson.net>  wrote:
>> I was just going to ask if this is possible.  It also allows for the
>> pull request mailing list post to become a thread for discussion when
>> discussion is warranted.
>
>  From the docs on Github:
>
>    "Everyone that can push to the base repository will receive an email
> notification"
>
> So I suppose if plone-dev <at> lists... was a user that could push, then it
> would receive the notification and thus send it to the list – if the
> Github e-mail daemon was allowed to post to plone-dev that is.

The emails already show up on the plone-cvs list:

https://lists.sourceforge.net/lists/listinfo/plone-cvs

(Or gmane.comp.web.zope.plone.cvs for gmane users.)

--

-- 
Maurits van Rees   http://maurits.vanrees.org/
Web App Programmer at Zest Software: http://zestsoftware.nl
"Logical thinking shows conclusively that logical thinking
is inconclusive." - My summary of Gödel, Escher, Bach

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Plone-developers mailing list
Plone-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-developers
Malthe Borch | 4 Nov 2011 11:10
Picon
Gravatar

Re: Review process

On 4 November 2011 10:48, Maurits van Rees <m.van.rees@...> wrote:
> The emails already show up on the plone-cvs list:

As far as I can see, those are commits only, or mostly.

For plone-dev, it would be useful only to have pull requests I think,
i.e. changes that the author has asked for confirmation (hence
discussion) on.

\malthe

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1

Gmane