Commits on Nov 19, 2010
  1. @ymendel
  2. @ymendel

    Merge branch 'aging'

    ymendel committed Nov 18, 2010
  3. @ymendel
  4. @ymendel
  5. @ymendel

    Allowing aging for partial project data

    Can pass a :before option to age, so only data before that is moved.
    Not accepting :after because that makes no sense.
    ymendel committed Nov 18, 2010
  6. @ymendel

    specs for age options

    ymendel committed Nov 18, 2010
  7. @ymendel

    Allowing aging from command line

    Pretty much just like deleting. It requires a project name, no options.
    ymendel committed Nov 18, 2010
  8. @ymendel

    Allowing aging for project instance

    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.
    ymendel committed Nov 18, 2010
Commits on Nov 18, 2010
  1. @ymendel

    Handling old versions of aged projects

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

    Starting project aging

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

    Summary code cleanup

    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.
    ymendel committed Nov 18, 2010
Commits on Sep 3, 2010
  1. @ymendel

    Fixing dates in the history.

    Apparently everything I did in 2009 was recorded as 2008. Woops!
    ymendel committed Sep 3, 2010
Commits on Aug 16, 2010
  1. @ymendel
  2. @ymendel

    A little clearer name for the option-fixing helper method.

    It's about the time *range*, and I don't want this to be confused
    with the `time_from_options` method
    ymendel committed Aug 16, 2010
  3. @ymendel

    Allowing date options for before/after.

    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.
    ymendel committed Aug 16, 2010
  4. @ymendel

    Fixing bad spec name

    ymendel committed Aug 15, 2010
  5. @ymendel

    Specs for --on option and other commands.

    list and summary
    ymendel committed Aug 15, 2010
  6. @ymendel

    Adding --on option from command line.

    To get the :on option to the commands, of course.
    ymendel committed Aug 15, 2010
  7. @ymendel

    Adding :on option for summary.

    Cheap and easy, just like the total. Yay for smartness.
    ymendel committed Aug 14, 2010
  8. @ymendel

    Adding :on option for totaling data.

    Since the total just uses list to get the data, this is FREE.
    I'm so happy when I do something close to right.
    ymendel committed Aug 14, 2010
  9. @ymendel

    Slight refactoring of time-option fixing.

    I knew I wrote timely for a reason.
    ymendel committed Aug 13, 2010
  10. @ymendel

    Adding :on option for listing data.

    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.
    ymendel committed Aug 13, 2010
Commits on Aug 26, 2009
  1. @ymendel
  2. @ymendel

    Updating command option help.

    The --message and --time options aren't only for punching in/out.
    ymendel committed Aug 26, 2009
  3. @ymendel

    Explicit spec for log behavior with argument and -m.

    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.
    ymendel committed Aug 26, 2009
  4. @ymendel

    Allowing command-line to log message with -m option.

    Basically, I'm sick of accidentally using -m when logging a message.
    This way, it'll actually work.
    ymendel committed Aug 26, 2009
  5. @ymendel

    Ensuring unknown command doesn't run summary.

    Left this out when adding summary.
    ymendel committed Aug 26, 2009
Commits on Aug 17, 2009
  1. @ymendel
  2. @ymendel

    Adding instance-level summary.

    ymendel committed Aug 17, 2009
  3. @ymendel

    Allowing summary from command line.

    Much like list with a smidge of total (for the formatting).
    ymendel committed Aug 17, 2009
  4. @ymendel
  5. @ymendel

    Adding nice formatting for summary times.

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

    Allowing bounds for summary.

    Like total and list, can use :before/:after options for summary.
    ymendel committed Aug 13, 2009
  7. @ymendel

    Using all project time data in summary.

    Y'know, instead of just the last time entry.
    ymendel committed Aug 13, 2009
  8. @ymendel

    Recording unspecified time in summary.

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