Re: How to edit dexterity types without needing to know about their behaviors
ajung <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
johannes raggam 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. > >> Consistency-is-king >> Andreas > > pragmatism is okay. > johannes I don't care about localized datetime values. Dates should always be stored and manipulated using UTC in the same way as any we should deal (in theory) with unicode strings internally. Localized datetime values and utf-8 encoded strings are value for presentation purposes, not for processing purposes. Pragmatism is not ok here - we are talk about elementary key functionality like getting and setting value and there can not be an exception doing things differently for whatever reason. Andreas -- View this message in context: http://plone.293351.n2.nabble.com/How-to-edit-dexterity-types-without-needing-to-know-about-their-behaviors-tp7570571p7570626.html Sent from the Core Developers mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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