Re: RFC: Proposal Dexterity API - two variants
Martin Aspeli <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAPN0AATPmvrGThM4e=8PhRXr=XmfE_JKqN2zHG8hHrtMizE-jg@mail.gmail.com> |
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. 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