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. Version 1.1 will be out before the end of the year, with a Windows version to hopefully follow some time next year.
Aeon 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. This means Aeon Timeline needs a clean, easy, intuitive user interface.
Firstly, I want to thank everybody who responded to my last blog post: From Mac to Windows: Why is Microsoft making it so hard? There is always a risk that any post dealing with a Mac versus Windows topic could descend into a flame war, so I was very appreciative of the intelligent thoughts and suggestions offered by everyone who commented on the blog.
Secondly, I will apologise for taking so long posting this follow up blog post. I have been sitting on this blog post for a couple of months waiting for permission to include a few quotes from Chris Bernard, a Chief Experience Evangelist at Microsoft, but after not hearing back, I have decided to publish the post without them.
In that time, Microsoft has abandoned the Metro name, but I will continue to use it here in lieu of a non-Wordy alternative.
Now that Aeon Timeline has been shipped off to the Mac AppStore folk for review, I have a bit of dead time while I wait for their approval. Since I say on my website that I am considering a Windows version, and I am now getting several emails a day asking for one, I have spent the evening researching my options.
The results is not pretty: Microsoft has created a mess of half-finished technologies, with no clear path to move forward. If I am wrong in this, I would dearly love for a more experienced Windows developer to come along and point this out.
What follows will be somewhat more technical and developer-oriented than my usual blog posts. I have tried to keep it simple, but apologies if I lose any non-developers along the way. The implications, in turns of support for different operating systems, may still be relevant to you.