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
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+pl...@redinnovation.com wrote:
They don't.
On 25 May 2013 14:40, ajung li...@zopyx.com wrote:
Rant
Bringing the discussion back to facts.
The documentation
http://dexterity-developer-manual.readthedocs.org/en/latest/schema-driven-types.html
uses form.schema (from plone.directives as base class) for the schema.
This is not working in Plone 4.3 - there is no plone.directives module.
So I
After reversing engineering: the problem here is in GenericSetup. The
configuration for
property name=schema.../property
is completely ignored. It is correctly exported through portal_setup after
setting it manually through the ZMI but the standard types tool import step
ignores this property.
https://dev.plone.org/ticket/13600
ajung wrote
After reversing engineering: the problem here is in GenericSetup. The
configuration for
property name=schema
...
/property
is completely ignored. It is correctly exported through portal_setup after
setting it manually through the ZMI but the
Working examples are often the best documentation.I agree that this is not
optimal.but have a look here:
Https://github.com/collective/collective.venue and it's dependencies and
Https://github.com/plone/plone.app.event
Both work on Plone 4.3 without grok.
--
Sent from my Nokia N9On 25.05.13
Templer is a work in progress. Until it is further along, ZopeSkel is the
stable solution. ZopeSkel works with 4.3, and zopeskel.dexterity has been
updated for 4.3.
On Fri, May 24, 2013 at 10:14 PM, ajung li...@zopyx.com wrote:
...
The official way for generating the boilerplate code
Work-in-progress here translates to broken-and-unusable.
Stuff like Templer or Zopeskel 3.X that actually never worked you have never
been published.
It wastes our time or causes lots of trouble and frustration - bad for
people *trying*
to use Plone. The developer experience right now is a
What is shipped with the installer and referenced in the docs? I assume
it's still zopeskel?
On Sat, May 25, 2013 at 10:44 AM, ajung li...@zopyx.com wrote:
Work-in-progress here translates to broken-and-unusable.
Stuff like Templer or Zopeskel 3.X that actually never worked you have
never
I am never using any installers. I build my buildout skels using Zopeskel
and added
https://pypi.python.org/pypi/templer.dexterity/1.0a1
as documented in the docs.
Andreas
Nathan Van Gheem wrote
What is shipped with the installer and referenced in the docs? I assume
it's still zopeskel?
The getstarted documentation warns about templer
http://developer.plone.org/getstarted/dexterity.html?highlight=templer
but not the official Dexterity reference manual.
The reference manual speaks about Zopeskel for generating the boilerplate
but does not warn about templer.
On Sat, May 25, 2013 at 6:48 AM, ajung li...@zopyx.com wrote:
Bringing the discussion back to facts.
The documentation
http://dexterity-developer-manual.readthedocs.org/en/latest/schema-driven-types.html
uses form.schema (from plone.directives as base class) for the schema.
This is not
On 5/25/13 6:55 AM, ajung wrote:
After reversing engineering: the problem here is in GenericSetup. The
configuration for
property name=schema.../property
is completely ignored. It is correctly exported through portal_setup after
setting it manually through the ZMI but the standard types tool
On 5/25/13 4:40 AM, ajung 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
Please use the copy of the manual at
14 matches
Mail list logo
