Create a custom theme
0
We had originally hoped that Chronicle 1.1 would be out by now. Unfortunately, as is the nature of the beast in Software Development, that hasn't happened quite the way we wanted.
Since the original plan, we've gone through concept after concept, in an attempt to make Chronicle friendlier, more suited to more people's business rules, and more stable. Here's a couple of screenshots of familiar screens from Chronicle.
First, the configuration screen. Note a couple of improvements, including the "Always post on task change or exit". This will cause Chronicle to post your currently running timer to the active connector when you change task or exit Chronicle - in the current version it will just lose it. You'll also notice "Theme" - this allows you to select a theme for the appearance of Chronicle. You can choose to just use the normal Windows theme too. The layout of the tab area has changed as well, to make it easier to find what you're looking for.
Also, the workspace itself. The first thing you'll notice is the new "This time is billable" checkbox. If your connector reports to Chronicle that it supports marking time as billable or not, Chronicle will send this flag with your time logs to your time management system. We will be updating the activeCollab, BaseCamp and GeeBiz connectors to support this out of the box. Chronicle Enterprise Server will support forcing this flag on or off by policy for individual clients/projects/what have you.
What you can't see on this image, is that Chronicle 1.1 will no longer require you to dig down to a task to start a timer. If your connector supports it, you'll be able to log time at the project level. Also, double clicking on the timer itself will allow you to manually edit the value. Minimizing Chronicle will now send it to the System Tray (by the clock) as well.
Please note that we expect Chronicle 1.1 to come out relatively soon as we need to support 37signals account tokens for Basecamp logins. If you are unable to log into Basecamp before v1.1 releases, please edit your settings, and enter your API token for the login, and "X" for the password.
Since the original plan, we've gone through concept after concept, in an attempt to make Chronicle friendlier, more suited to more people's business rules, and more stable. Here's a couple of screenshots of familiar screens from Chronicle.
First, the configuration screen. Note a couple of improvements, including the "Always post on task change or exit". This will cause Chronicle to post your currently running timer to the active connector when you change task or exit Chronicle - in the current version it will just lose it. You'll also notice "Theme" - this allows you to select a theme for the appearance of Chronicle. You can choose to just use the normal Windows theme too. The layout of the tab area has changed as well, to make it easier to find what you're looking for.
Also, the workspace itself. The first thing you'll notice is the new "This time is billable" checkbox. If your connector reports to Chronicle that it supports marking time as billable or not, Chronicle will send this flag with your time logs to your time management system. We will be updating the activeCollab, BaseCamp and GeeBiz connectors to support this out of the box. Chronicle Enterprise Server will support forcing this flag on or off by policy for individual clients/projects/what have you.
What you can't see on this image, is that Chronicle 1.1 will no longer require you to dig down to a task to start a timer. If your connector supports it, you'll be able to log time at the project level. Also, double clicking on the timer itself will allow you to manually edit the value. Minimizing Chronicle will now send it to the System Tray (by the clock) as well.
Please note that we expect Chronicle 1.1 to come out relatively soon as we need to support 37signals account tokens for Basecamp logins. If you are unable to log into Basecamp before v1.1 releases, please edit your settings, and enter your API token for the login, and "X" for the password.
