4 ms·
You could go with a traditional time selector (http://api.rubyonrails.org/classes/ActionView/Helpers/DateHelper.html#method-i-select_time http://api.rubyonrails
by aidanfeldman 15y ago
You could go with a traditional time selector (http://api.rubyonrails.org/classes/ActionView/Helpers/DateHelper.html#method-i-select_time http://api.rubyonrails.org/classes/ActionView/Helpers/DateHe...), but I like the single box for typing in the time. Might be able to parse more things with a library like Chronic (best name for a gem ever - http://chronic.rubyforge.org/ http://chronic.rubyforge.org/).
Congrats buddy!
- vnchr 15y agoThanks! I'll look into that. Improving the output formatting is my easiest next step. Then the input, so I'll check out that library. You're a pal.
- watmough 15y agoFor people that are just 'starting out' and also people that just want to keep their hand in, it's really a good idea to practice writing small pieces of intricate code like tokenizers, string processing etc., rather than just selecting the closest library to hand. Obviously, if you're writing code commercially, you may want either complete control over some code (write it), or you may want it now (use a lib), so writing all your own code may be an impossible luxury. Here's a small example snippet I just did. I've been doing software since 1988, but often just gluing (MFC) api's together, and not doing stuff that really benefits me as much as it might. Anyways, here's a gist that implements a 'good enough to use' version of an iOS 4.0-only api as a category on NSData, allowing string searching of arbitrary data: https://gist.github.com/1238869 https://gist.github.com/1238869