Question about time tracking and next versions

1, 2, 3, 4, 5
This topic is locked, no new messages can be posted
avatar viceroy321 Feb 20. 2007. 3:31 pm #11
if you had shortened your post only 10 characters (the last), it would have been much better.

-1 for advertising.
avatar Feb 20. 2007. 4:48 pm #12
Advertising, yes. But not bad advertising. We're contributing our code changes back to activeCollab. Plus, a percentage of the money we make is donated back to activeCollab. The more sign-ups we get, the more money AC gets.
avatar Feb 21. 2007. 5:27 am #13
Tyler, you think it is possible to add a Javascript (or whatever means) stopwatch to the tracker? I suck at keeping an eye on the time and have to guess later on. I could use a separate timer that counts my work time, but that kind of defeats the purpose, don't you think?
avatar Feb 22. 2007. 1:06 pm #14
Hey, Alex. The other developers and I made a conscious decision not to implement a javascript timer when we built the time tracking module. I've always thought a feature like that would be better suited as a small desktop app, an OS X widget maybe. That said, if you can make a good case for adding it to activeCollab I'm happy to reconsider the possibility.
avatar Feb 22. 2007. 1:24 pm #15
Hehe, interesting that you mention OS X widgets Tyler. I use The Daily Grind as time tracker. It is the best application I found for this purpose so far and I can fully live with it.

I just more or less thought it would be a good idea to keep together what belongs together. And a time tracker and a time counter seems like the perfect match for that philosophy, don't you think?

What were your reasons for not including it in the first place? Just curious.
avatar Feb 27. 2007. 11:36 pm #16
>> What were your reasons for not including it in the first place? Just curious.

Most of us at Sitening have had to use or tried to use an "active" timer in the past - one where you actively stop and start it to track your hours on each task. We all found that it was too much trouble. Too many things get in the way. For instance, I may be working on a specific client's project, but I'm also checking email, answering the phone, and talking with people in the office. Stopping and starting the time for each one of those interruptions isn't feasible (for us anyway). Long story short, the timer method just doesn't work for us as well as it does for some people, so we didn't have much motivation to add it as a feature.
avatar Feb 28. 2007. 1:01 am #17
I see. Thanks for the insight. I am happy with my OS X widget for now anyway.
avatar Ryan Cross Feb 28. 2007. 5:36 pm #18
Hey Tyler,

I just recently tried to install the code from your branch. I got it work, but there is a small problem. You are missing the initial /config/config.php with <?php return false; ?> inside it so that it functions properly with the init.php during installation. Otherwise, looks good.

avatar Feb 28. 2007. 9:59 pm #19
Doh. Thanks for pointing that out, Ryan.
avatar sajseven Mar 1. 2007. 11:22 am #20
Oh no! I tried this and got this error:

Fatal error: Call to undefined method Project::getTimes() in z:\activecollab\application\controllers\TimeController.class.php on line 36

What do I do?
activeCollab Team Member (NOT)

Topic is locked

If you have something important to say about the issues discussed in this post please write at hi@a51dev.com.

or Go To Next Page