![]() In the old version, the Inspector allowed you to set a start and end date only. Internally, this was stored as a duration in minutes, which meant you could shift the start date and the end date would follow. For users of the existing version 1.0.x, the reasons may be fairly apparent. One of the new features I am adding for version 1.1 is the ability to explicitly set event durations as an alternative to an explicit end date. Time will tell if I make the right decision. I don’t yet have a complete answer to the problem, but the shape of one is forming in my mind. This particular problem is subtle, but also difficult. What most users notice are the design decisions that have gone wrong.īelow is a sneak peek of a couple of new features coming to Aeon Timeline version 1.1. ![]() If the final decision goes unnoticed, it means the interface has done its job and got out of the way. It seems a shame to say it given the amount of time I have spent thinking about the problem I discuss below, but I hope this is destined to become one of those decisions. There are many decisions made in designing a user interface that take a long time to get right, but when done correctly, go completely unnoticed by the end user. This means Aeon Timeline needs a clean, easy, intuitive user interface. Version 1.1 will be out before the end of the year, with a Windows version to hopefully follow some time next year.Īeon Timeline is intended to aid creativity and data analysis, and to achieve this aim, it is important that users spend their time thinking about their content rather than the application they use to create it. As I have mentioned briefly, I am currently working on Aeon Timeline version 1.1 for Mac, which will bring Aeon Timeline up to the level I want it to reach before I write a feature-parity version for Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |