> For Doug and Mike, was it really easier to do custom AMF and timezone math > vs just creating a custom DateWithoutTime class and transfer the Date > portion to/from the Date values in the components?
Note that my requirement was that we did indeed need the time element, we just always wanted it to be the same, regardless of the timezone on the server/DB vs the client. I think this is what you guys are referring to as a "floating" DateTime class. So we did have a custom class that actually used a normal Date class internally to store its state, but applied timezone adjustment logic during deserialization. If we needed to use the normal Flash Date object for something we had to access it like myFloatingData.date. Just for further background of our use case (apologies if this is repetitive, since our use case is similar to many others people have said). Our customers are uploading spreadsheets that sometimes contain dates, so a cell might have "1/1/2013 13:55". We store those as dates in the DB so we can do fun date things with them, like grouping by month, etc. And we wanted to have them as dates (as opposed to strings or something) in Flex because we wanted to be able to use the DateFormatter, the DateTimeAxis for charts, etc. That Jan 1 date at 1:55pm should always appear and be treated as 1:55pm. So I think that's just repeating a lot of what's already been said in this thread.
