search

samg / timetrap

Simple command line timetracker
http://rubygems.org/gems/timetrap
Other
1.49k stars 116 forks source link

list of all sheets, even unused ones #27

Closed jwhendy closed 12 years ago

jwhendy commented 13 years ago

I just installed this and was "setting up" but creating the sheets I know I'll use. I found it odd that 't list' only listed the most recently created sheet. For example:

t sheet proj1 t sheet proj2 t sheet proj3 t list

Seems to only produce 'proj3 00:00:00...'

How can I list all my sheets? I just clocked into two of them just to see if they'd show up, and now those two do, but the last one is still not shown on 't list.' Primarily, if someone wanted to set everything up on the front end... this makes them need to remember what, specifically, they named every project since there seems to be no built in way to query all sheets, even empty ones.

Great project -- thanks for your work!

samg commented 13 years ago

This does tend to be a point of confusion for people. The root of it is that sheets aren't first class objects in timetrap. They're just an attribute on the entry, so without an entry belonging to it a sheet doesn't exist, and can't be listed. The one exception is the 'current' sheet, which does get shown in the lists. This is really just a tag that tells timetrap which sheet to check into when you run t in.

Hans, has forked the project and added a sheets table (https://github.com/samg/timetrap) which may behave more like you'd expect. There's some talk of pulling these or similar changes into the main project, but I haven't had time to really dig into this and investigate the potential migration issues users would have if the schema was changed.

If you have more suggestions about how you'd expect timetrap to behave with regard to sheets I'd be happy to hear it (t kill sheet has a similar issue. It will delete all entries for the sheet but you'll still see the sheet in your list until you switch to another.) Also I'm sure Hans and I would both appreciate feedback on the approach used in his fork.

/pull/26) H

jwhendy commented 13 years ago

@samg: Very cool. Thanks for the comment and that's understandable. It's really not a big deal -- just knowing this fact is helpful as one can make sure to only create a sheet prior to clocking in at least one task on it :) From then on, it's cake to list them.

Thanks for your work on this; it's quite nice and simple. I found punch.py and then this and mainly prefer this due to the reporting system. It's very nice that you've included a csv format for post processing in something like Excel. With punch.py... it could surely be done, but would require just a little more tweaking to futz with since it just outputs a date "glob" rather than separated values. Thanks!