Hi, At the moment we are concentrating on getting out the iOS version, however once this is done we will start looking at new features such as a calendar view. Jess
Thank you for clarification! I don't know how much trouble it would be, but if (as a stop-gap) you could add the ability to split/join time and date on import/export to CVS that would make my workaround a lot less work! 😉
You say your calendar program uses a single field for date/time and that you're having to concat time/date information from Aeon Timeline CSV exports. Are you perhaps using an old version of AT? When I do a CSV export from AT 2.2.6 the time/date is exported as a single field in a standard string format that looks like "01 October 2017 10:00:00AM". Even internally, AT2 stores date/time as a single value like "63642448800" which roughly speaking is the number of seconds since year 0 in the Gregorian calendar. Databases generally use the same method where date and time are calculated as an offset from a zero point such as the Unix epoch. iCal is another pretty common date/event interchange format where the date/time is in the form "20171001T100000". Even if you just type the 'date' command on your Mac terminal you'll get something like "Sun 1 Oct 2017 10:00:00 EDT". Date is just a coarser measurement of time and whether you find it difficult to visualize or not, barring some Quantum Leap discovery, it is quite linear and easily represented with a single inte ger if you can agree on the zero point. It's quite standard to not split the date and time information into separate fields for both internal representation or interchange. Generally, it's only split at the user interface level. I understand that you'd like to see a traditional calendar view in AT2. That might be a nice view to have indeed. So far as your intermediate workaround, I think you're already getting everything you should need/expect in the way of data export/import.
Sorry for the confusion-- I had it backwards! My calendar program uses two date/time fields, and Aeon uses one. I have figured out the easiest way possible to split or join the column for import/export, but I figured it couldn't hurt to see if I can make it a little easier! 😉