Pressing ! and dealing with that datepicker is pretty tedious for someone who likes to schedule everything. Itād be amazing if I could just write natural language between the brackets after the ! and then Dynalist could parse it and insert the date it interprets.
Iād probably do the re-writing-after-parsing step as a history item so it can be undone with CMD+Z if itās incorrectly parsed ā that way, I can CMD+Z and just edit my string to try again.
And I do know about the arrow keys ā theyāre handy for sure, in other situations. One peeve, though, is that the time field always starts at 12:00am and thatās pretty much the least likely time Iād schedule anything Starting it at Date.now() ā right down to the time in minutes ā would be more intuitive, I think!
The reason for that is because often people want to add a āall dayā event. If itās defaulted to now, when synced to Google Calendar it will appear at the current time too.
12:00 am means āno timeā in this context, if that makes sense.
There are definitely solutions to this problem though. In fact, the appās kind of already solved for it, hasnāt it halfway. When I press ! it opens the calendar, then I can arrow-key around to the date I want, and press return whenever Iāve found the date. Itāll then inject !(2017-12-29) into the ticket. If, however, I press tab into the time field, it opens the list of times and, as you know, starts me at freakinā midnight so Iāve got to lean on the down arrow key until Iām at a reasonable time for scheduling things.
All Iām asking for is to have that time field default to the current time when I first tab to it. Otherwise, leave it blank.
Alternatively, break it up into multiple fields so I can just slam down the time and choose AM or PM afterwards.
In any case, the problem is that adding a time to due dates is super tedious. If thereās anything else I can do to help out with improving it, just let me know! Iām pretty close to writing my own greasemonkey script to fix it myself, but I think itās something everyone would appreciateā¦
Respectfully I disagree. I rarely want to schedule something for the exact moment Iām typing it in. And with the time field, well itās still a field. Rather than using arrow keys, If I want to start something at 15h30 then I just type 15 and the list jumps to that time period. I can then either use the arrow to go to 15h30 or just type in the exact time.
Typing two characters rather than hitting the down arrow to a maximum of 47 times is pretty straight forward and just as quick
I love all of Aaronās suggestions. Entering a calendar date using natural language is very common in lots of other apps (a few popular iOS - Fantastical, Todoist). Having DL parse and convert would be much faster than using the calendar dialog.
Tracy, Thatās cool to use TextExpander to insert the current date / time. However, the use cases I was thinking of is a variable time using natural language to type !in3d or !nextSaturday or !onJul1 and if as long as the format is consistent, the date would be converted. Can TextExpander handle this?
@Erica - Perhaps thereās existing natural language date parsing code you can leverage in DL ⦠check out Natty which in my testing does an awesome job: http://natty.joestelmach.com/try.jsp
Thanks for the suggestion for making the time same as current time when you tab into the time field.
One thing I donāt quite understand ā is it for time tracking/logging? Otherwise shouldnāt scheduled time be some other random time (like 3:30 pm tomorrow for a meeting)?
Itās not about time-tracking for me, itās just about having a sensible default. Regardless of what Iām scheduling, a default of āmidnightā is 100% never going to be useful to me. The current time is a smart default because it makes it simpler for me to do relative math, too. If itās in 2 hours, I can tab to hours and press DOWN twice. Bam.
I think the task of making time-entry super easy would be a fun UX challenge, and itād pay off pretty significantly for an app like DynaList.
I definitely agree. I just thought that having the time default to current time might be undesirable for some people, for example if they accidentally tabbed into the time field, now that they need to manually clean up the time part, if they want to clean date.
Iām thinking an option to change default time to current time would be best.
Not sure if thereās been a misunderstanding or not, but Iām really just asking for the select menu for time to auto-select the value thatās closest to the current time so I can more intuitively set ātwo hours from nowā by pressing Down three or four times, rather than like 14 times because it starts empty and pressing Down starts me at 12:00am.
The āpickerā is already two-staged, and I think itās pretty well done already: Typing ! opens the picker with the current date active (makes sense). I can Up / Down / Left / Right around to pick another date, and press Enter to accept just the date without any time. But if I Tab to the time field, this is where Iād just want it to automatically select the current time, but keep the select menu open so I can Up / Down to select other times, or just type a time myself ā the box is pre-populated, but Iām still in āPick a Timeā mode. If I press Enter without doing anything, Iāve set the current date and current time.
The only thing missing from the app today is the auto-population of the time field on focus ā not as soon as the date picker opens.
Aaronās suggestion of just changing the order of the elements in the time dropdown would be a good small improvement.
If you ever become interested in trying to do more natural language date entry, which I would love, I wanted to point out a library (chronic - https://github.com/mojombo/chronic). Iāve been using for years and has excellent dynamics based around the current date and time. ā2pmā ānext tuesdayā āmarch 1stā which may lay some good groundwork. I mention it only in concept because I have no idea what languages youāve implemented dynalist in.