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 checked plone.app.contenttypes as example which uses plone.supermodel for the schemas: https://github.com/plone/plone.app.contenttypes/blob/master/plone/app/contenttypes/interfaces.py By doing this I got at least my folder type working - half working. The folder shows up with the standard dublin core fields but does not show the extra field defined in the schema. Here is the schema and the FTI https://gist.github.com/zopyx/5649084 'schema' and 'klass' are properly defined in the FTI but the schema is obviously not used here. It took me now already roughly ten hours to get something working. How long would it take for a Plone n00b? -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-tp7565313p7565323.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
