[Product-Developers] <pissed> Generating the Dexterity boilerplate for Plone 4.3</pissed>

T. Kim Nguyen nguyen at uwosh.edu
Sat May 25 13:26:24 UTC 2013


Can we help do some of the work at the Symposium sprints? Will need someone to lead it. 


Kim
—
Sent from Mailbox for iPhone

On Sat, May 25, 2013 at 8:24 AM, Nathan Van Gheem <vangheem at gmail.com>
wrote:

> Yes, this is embarrassing. Ideally this would be fixed before eric releases
> 4.3.1.
> Could we get some issues in the trackers?
> On Sat, May 25, 2013 at 8:04 AM, Mikko Ohtamaa <
> mikko+plone at redinnovation.com> wrote:
>> They don't.
>>
>>
>>
>>
>> On 25 May 2013 14:40, ajung <lists at zopyx.com> wrote:
>>
>>> Rant continuing....
>>>
>>> Even the Dexterity documentation is outdated for Plone 4.3
>>>
>>>
>>> http://dexterity-developer-manual.readthedocs.org/en/latest/schema-driven-types.html
>>>
>>> How should a n00b start with Plone 4.3 and Dexterity without outdated
>>> documentation?
>>>
>>> -aj
>>>
>>>
>>>
>>> ajung wrote
>>> > Hi there,
>>> >
>>> > I am slightly annoyed with Dexterity under Plone 4.3.
>>> >
>>> > In the old days of Archetypes and Plone 4.x I could
>>> > easily generate policy packages and the content-type
>>> > boilerplate code easily and in a reliable way  using
>>> > Paster + Zopeskel - perfect world.
>>> >
>>> > Now with Plone 4.3 and Dexterity everything feels
>>> > like a big mess - from the integrators prospective.
>>> >
>>> > The official way for generating the boilerplate code
>>> > seems(?!) to be https://pypi.python.org/pypi/templer.plone.
>>> >
>>> > First: this package generates code with grok dependencies
>>> > that do not work on Plone 4.3 (I wrote an earlier email
>>> > about this problem) - can be easily fixed.
>>> >
>>> > Second: generating a new content-type using templer
>>> > generated code that seems to be incompatible with Plone 4.3
>>> > (e.g.  an import to plone.directives which seems to
>>> > have been refactored into plone.directives.dexterity ...
>>> > and so on).
>>> >
>>> > Now I tried using the same with Plone 4.2 and the generated
>>> > code is also not working on Plone 4.2 So what is this
>>> > Templer stuff about? Causing trouble and frustration?
>>> >
>>> > Now tried it the hard-core way and tried to look up the Dexterity
>>> > documentation and checked
>>> >
>>> > https://pypi.python.org/pypi/plone.app.dexterity#documentation
>>> >
>>> > All three links inside the Dexterity documentation section on PyPI
>>> > lead to abandoned pages....great...I am pissed.
>>> >
>>> >
>>> > Once again: having elementary functionality for integrators
>>> > not working is bad for Plone. Yes, I can fix this all myself
>>> > if I had time and interest but here is the chicken-egg problem:
>>> > we have various other options available nowadays building
>>> > CMS and web application without Plone. And as an integrator
>>> > I do have some basic expectations to the framework. Basic
>>> > things must just work.
>>> >
>>> >
>>> > Andreas
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://plone.293351.n2.nabble.com/pissed-Generating-the-Dexterity-boilerplate-for-Plone-4-3-pissed-tp7565313p7565320.html
>>> Sent from the Product Developers mailing list archive at Nabble.com.
>>> _______________________________________________
>>> Product-Developers mailing list
>>> Product-Developers at lists.plone.org
>>> https://lists.plone.org/mailman/listinfo/plone-product-developers
>>>
>>
>>
>>
>> --
>> Mikko Ohtamaa
>> http://opensourcehacker.com
>> http://twitter.com/moo9000
>>
>> _______________________________________________
>> Product-Developers mailing list
>> Product-Developers at lists.plone.org
>> https://lists.plone.org/mailman/listinfo/plone-product-developers
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-product-developers/attachments/20130525/1ae40946/attachment-0001.html>


More information about the Product-Developers mailing list