Improve duration argument format about toggl-cli HOT 8 CLOSED

I agree that its not immediately clear - I did something similar when I first used it, however as you suggest it was solved after I a) did it wrong the first time and then b) read --help.

I think that having the command support duration and/or time as it currently stands is the way to go rather than have another full set of commands.

Showing an example is possibly a good idea, but it likely wouldn't change the learning curve of a) do it wrong then b) read the docs...

from toggl-cli.

Hi Stafford.

Here I can see couple of things which can be used:

• It already uses : and @ prefixes, so what about + prefix? I understand that it is just changing one with another, but it still will look easier to read and understand than current notation: 'd'DURATION. And format would look really nice toggl-cli add TASK @toggl-cli +25:00.
• Look how man date has the same complexity issues, but they are giving really nice tips there, like "output date and time in RFC 2822 format. Example: Mon, 07 Aug 2006 12:34:56 -0600" so you can just copy paste line and adjust. Or look into man find, they wrote "see section STANDARDS CONFORMANCE below" so it's normal to point user to different direction.

And yes, I agree about learning curve you said, but still for me this notation 'd'DURATION at first place is 'd'00:25:00 rather complex. After lot failed attempts I understand what format you are requesting here: char 'd' as prefix for time format.

from toggl-cli.

I'm not a big fan of how 'd'DURATION reads and I think your +DURATION suggestion definitely improves it. If a switch were to occur, the 'd' prefix could be left in (silently) to support backwards compatibility if required.

If examples were to be included, I would be a supporter of having them at the end --help, rather than per command. The current command listing seems concise and quickly communicated as it stands - I think adding examples at the line level would be detrimental to that, but others may disagree.

Another option would be to catch incorrect +DURATION when entered and echo the expected format.

from toggl-cli.

I think I can improve those, if you want (can make a pull request with changes)?

from toggl-cli.

@drobertadams ?

from toggl-cli.

Guys, what the hell is the format to use this? I've looked and have no idea what this means:

DURATION = [[Hours:]Minutes:]Seconds

I've tried everything and even looked at the function calls..

from toggl-cli.

Square brackets mean optional. If you just enter a number, it will be
considered as "seconds". If you enter "13:14" it will be 13 minutes, 14
seconds. If you enter 13:14:15, it means 13 hours, 14 minutes, 15 seconds.

On Thu, Apr 7, 2016 at 2:53 PM Devon Ash [email protected] wrote:

Guys, what the hell is the format to use this? I've looked and have no
idea what this means:

DURATION = [[Hours:]Minutes:]Seconds

I've tried everything and even looked at the function calls..

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#57 (comment)

Dr. Robert Adams
School of Computing and Information Systems
Grand Valley State University

from toggl-cli.

There is new duration format as part of the new version of Toggl CLI, see documentation.

from toggl-cli.