Re: RFC: Proposal Dexterity API - two variants
Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
On 5 Nov 2014, at 11:49 pm, Martin Aspeli <[email protected]> wrote: > > > On 5 November 2014 22:43, David Glick (Plone) <david.glick-z4DKO/[email protected]> wrote: > > Well, we need a better way to do reusable fields then. > > This is a real use case: As an integrator, I want to install an add-on which provides some functionality I can enable for my types (for example a geolocation field), but I want to retain control over where it appears on my edit forms, and maybe change the label and help text. > > I agree with this. I'm just not sure you need to make it possible with zero code to say "it has to be exactly between the title and the description" if the cost of that flexibility is a lot of complexity in the UI. > > I do agree this part of the TTW story is somewhat under-explored though and probably you could give much more robust hints to the ordering algorithm (you know that beast all too well, David...) with better UI to manage it. I would say there needs to be a way to do field reordering TTW. I've had customers ask for it. But possibly it can be via a different mechanism since its not really changing the semantics or functionality of the type. It's more a presentation layer thing. I'd also like a way for site admin users to change field names, descriptions and perhaps validation rules such as making some fields compulsory, all without having to create a new content type. Diazo could be used to reorder them now and change descriptions but its not so pretty. A TTW translation tool could be used to change descriptions and titles (amoung other backend phrases). But overriding a field validation isn't so easy. Perhaps there is room for a contenttype fiddler plugin to allow these usecases? > > That's not the same as adding another API for accessing field values for all content objects though... > > Martin > ------------------------------------------------------------------------------ > _______________________________________________ > Plone-developers mailing list > Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/plone-developers ------------------------------------------------------------------------------