Re: How to edit dexterity types without needing to know about their behaviors
Sean Upton <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CANjV-2P7RE8RoG8VUjvGzrAFQkFBzAD3sEXsu4PMYHHYdfB1Jg@mail.gmail.com> |
On Fri, Mar 14, 2014 at 2:32 AM, Johannes Raggam <[email protected]> wrote: > i'll fix that, probably at the wine and beer sprint. but then you'll > still always get UTC datetime values instead of localized ones, if you > get the start/end attributes directly from the context. UTC should IMHO be the programmatic interface of dates/times always, inasmuch as that is possible. I always just assumed that in the best-case the behaviors could be used factory-less without requiring adaptation, but the whole (and only really substantial) justification for adaptation was to have one interface for dealing with both AT and DX types. If neither AT support nor non-UTC setting/getting is a requirement for Plone 5, what avenues exist to (mostly or completely?) avoid adaptation to the accessor interface? Sean ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech