Good news, I have fixed a few more annoying issues and now declare 1.3.4 as stable. This is now available on the new stable app cast and I will try to move existing users over to my updated version. I have also committed all outstanding changes into SVN so for the adventurous, you should be able to compile on your own. If not, let me know.
There has not really been any big new feature just a few minor updates (and sparkle updates should be working well now).
If you have 1.3.3 you should be able to get 1.3.4 automatically through sparkle. If it does not prompt you, click “Check for updates” and it should be available.
I have released the first beta after taking over the maintainership over TimeTracker. This version does not yet show up in the old users sparkle updater but it can be downloaded from the google site anyway.
As announced before, this version focuses on a new layout and more flexible filtering.
if you want to get further beta versions, go to the settings and select “Beta Releases” in the preferences.
This is just a quick note to let you know that I will be taking over the maintainership of the TimeTracker for mac since Aaron will not have enough time available to move the app forwards in the next year or so.
So thats quite exciting news. At the moment, I have most of the functionality that I want for the next release but there are still a few bugs here and there. Also I will need to work some more on backporting some of the features of the official TimeTracker (sparkle update for once) so that I can make new versions available to people via auto updates rather than needing to work with the website.
All my code is on the google code page and I intend to use this as a repository (I know that Aarons stuff is on GitHub but I am more used to SVN).
However, I encourage participation in the project as I neither have tons of time available nor am I the absolute uber-expert on Mac OS programming. So if you know some Sparkle details, feel free to contribute.
The upcoming version will mainly feature more flexible filtering, along with being able to combine queries such as show me all entries of last thursday, or all records happened on a monday in the past 6 weeks (you get the idea, otherwise look at the screenshot in the previous post).
I will NOT yet include customers as a new grouping hierarchy mainly because I want to get the current version stable and going before I move on.
Future versions will focus on the following features
ability to define and save custom filters (smart filters)
adding “customers” as a new grouping hierarchy
coredata support (could use some help there)
nicer and better export tools (Numbers, etc. – Long way out)
Regarding a release I need to figure out how to do it properly. As I said I want to eventually make it available through sparkle so that existing users will be notified about the update. I am fairly confident that the application is reasonably stable and I haven’t lost any data in years (not even during my migration from the older timetracker version which is required since the newer version adds support for comments, etc). However, I am not really comfortable with pushing the current version out just yet. So probably I will make a “beta” available here.
Once I have added sparkle support, will then push it into the Beta channel through sparkle. Then after some fixes, I will push the main version.
This is just a quick post so that you guys know what I am currently working on. As posted previously the main task is to make the filtering much smarter than it is today. I imagine this to work like smart playlists in itunes or smart albums in iphoto. See the screenshot for an example.
So the idea is to allow people to configure their own individual filters with elements such as
start date >= X days before today
If you have additional recommendations / wishes, let me know.
Some outlook for next versions: I have been toying around with the filtering concept which is currently not really nicely done. I think I will implement something like iTunes smart playlists where you can save your filters and have them easily accessible. Once this is done I will probably look at either merging the code with Aarons version or start implementing CoreData support (currently the whole database is loaded to RAM which will eventually accumulate lots of mem and affect startup/shutdown performance).
This is a minor bugfix release for time tracker. It fixes a problem where the app would start to behave weird when you have multiple projects with the same name or multiple tasks within a project with the same name.
Basically all I currently do is warn you when you try to choose a duplicate name. If you already have projects with the same name, then the app will change the project names (add a number after the duplicate name) so that the project name will be unique again.
In addition I have added a few more options to the configuration screen:
# of last tasks in menubar: lets you choose how many quickstart tasks are shown in the menu bar (you can quick start a task by clicking on the menubar icon and then selecting one of the most recent previous recorded tasks).
show time in menubar: if this is enabled then the duration of the current work period is shown in the menubar.
idle timeout (seconds): lets you configure the idle timeout in seconds. This basically defines how soon TimeTracker will prompt you whether you still want to keep on recording the time, default is 300s (i.e. 5 minutes).
Computer sleep detection: lets you define whether TimeTracker will attempt to recognize the computer going into sleep / standby. If turned on and TimeTracker notices a clock jump of > 60 seconds it will interpret this as standby mode and also trigger the idle warning. The default is on since at least on laptops that makes a lot of sense.
As always if you are new to my beta, be sure to read previous articles in my blog tagged with TimeTracker about data compability with public TimeTracker releases.
A new version of TimeTracker has been released. This now features the ability to start last recently used tasks from the statusbar (a feature that has been wanted quite badly). I haven’t done a lot of testing yet so your mileage may vary.
This is a bugfix release. It fixes potential crashes when using the settings screen. Also now the Filename box will always save its value even if you dont move the focus out of the field before closing the window.