Permalink
Commits on Nov 19, 2010
  1. Merge branch 'aging'

    ymendel committed Nov 19, 2010
  2. Allowing aging for partial project data

    ymendel committed Nov 19, 2010
    Can pass a :before option to age, so only data before that is moved.
    Not accepting :after because that makes no sense.
  3. specs for age options

    ymendel committed Nov 18, 2010
  4. Allowing aging from command line

    ymendel committed Nov 18, 2010
    Pretty much just like deleting. It requires a project name, no options.
  5. Allowing aging for project instance

    ymendel committed Nov 18, 2010
    I was thinking of having this change the stored project so the instance
    moves along with the data instead of bring for the old project name
    (which is now empty). But that wouldn't communicate with other instances,
    so it might be confusing. Still considering.
Commits on Nov 18, 2010
  1. Handling old versions of aged projects

    ymendel committed Nov 18, 2010
    Aging should cascade down the line, not overwrite old versions.
  2. Starting project aging

    ymendel committed Nov 18, 2010
    For my own convenience, since sometimes I move a project's data out of the way
    (e.g. from project to project_old/1)
  3. Summary code cleanup

    ymendel committed Nov 18, 2010
    I can't believe I had an unless/else in this code, for serious.
    And what's the pointless format_time method in the spec all about?
    I'm a freaking moron.
    
    Also, a problem with OS X's strftime gives some problems with summary
    of a punch-in project during part of the year. Not sure what to do about that.
Commits on Sep 3, 2010
  1. Fixing dates in the history.

    ymendel committed Sep 3, 2010
    Apparently everything I did in 2009 was recorded as 2008. Woops!
Commits on Aug 16, 2010
  1. A little clearer name for the option-fixing helper method.

    ymendel committed Aug 16, 2010
    It's about the time *range*, and I don't want this to be confused
    with the `time_from_options` method
  2. Allowing date options for before/after.

    ymendel committed Aug 16, 2010
    A date can be provided from the command line thanks to Time.parse.
    Might as well allow dates for the actual methods and do something
    sensible with that input.
  3. Fixing bad spec name

    ymendel committed Aug 15, 2010
  4. Specs for --on option and other commands.

    ymendel committed Aug 15, 2010
    list and summary
  5. Adding --on option from command line.

    ymendel committed Aug 15, 2010
    To get the :on option to the commands, of course.
  6. Adding :on option for summary.

    ymendel committed Aug 14, 2010
    Cheap and easy, just like the total. Yay for smartness.
  7. Adding :on option for totaling data.

    ymendel committed Aug 14, 2010
    Since the total just uses list to get the data, this is FREE.
    I'm so happy when I do something close to right.
  8. Slight refactoring of time-option fixing.

    ymendel committed Aug 14, 2010
    I knew I wrote timely for a reason.
  9. Adding :on option for listing data.

    ymendel committed Aug 14, 2010
    Starting some sensible date-handling for Punch.
    I've long wanted the ability to simply ask about time spent on a particular day,
    and I'm finally sick of specifying before/after myself.
Commits on Aug 26, 2009
  1. Updating command option help.

    ymendel committed Aug 26, 2009
    The --message and --time options aren't only for punching in/out.
  2. Explicit spec for log behavior with argument and -m.

    ymendel committed Aug 26, 2009
    Not a huge fan of either message taking precedence over the other,
    but this way is easier and at least there's a spec now to say
    exactly what happens.
  3. Allowing command-line to log message with -m option.

    ymendel committed Aug 26, 2009
    Basically, I'm sick of accidentally using -m when logging a message.
    This way, it'll actually work.
  4. Ensuring unknown command doesn't run summary.

    ymendel committed Aug 26, 2009
    Left this out when adding summary.
Commits on Aug 17, 2009
  1. Adding instance-level summary.

    ymendel committed Aug 17, 2009
  2. Allowing summary from command line.

    ymendel committed Aug 17, 2009
    Much like list with a smidge of total (for the formatting).
  3. Adding nice formatting for summary times.

    ymendel committed Aug 13, 2009
    If you'd rather see a nice string than a number of seconds, go for it.
    Just like total, right?
  4. Allowing bounds for summary.

    ymendel committed Aug 13, 2009
    Like total and list, can use :before/:after options for summary.
  5. Using all project time data in summary.

    ymendel committed Aug 13, 2009
    Y'know, instead of just the last time entry.
  6. Recording unspecified time in summary.

    ymendel committed Aug 13, 2009
    "Unspecified" is anything after punch-in and before first message.
    (or if there are no messages)