Closed kchiou closed 8 years ago
(Kenny now). I agree that the datetime info should be there for remarks. The format @difiore gave is reasonable under the hood, but I think the displayed format should be in a more human-readable format.
Agreed with Kenny, human-readable format would be better.
To me, YYYY-MM-DD HH:MM:SS _IS_ human readable :)
HH:MM:SS is perhaps better.
Date and time formatting maybe (down the road) could be a user-defined setting. The current date format (MM/DD/YY) is confusing for international users (many non US sites use DD/MM/YY).
On 4/10/16 11:33 AM, tigoe wrote:
Agreed with Kenny, human-readable format would be better.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/ethoinformatics/ethoinfo-project-app/issues/7#issuecomment-208012538
I would suggest something like this is most readable. Switching in settings is good for international users. I know we can all probably read YYYY-MM-DD HH:MM:SS timestamps without too much trouble, but not all users can.
"April 10, 2016 @ 11:50:25"
Or look at this issues thread itself. "kchiou commented a minute ago" is pretty useful to me as a UI user. If there are well-supported strategies for human-readable times, I think we should use them.
Date formatting is a solved problem in JS. We can use any one of many options, choose one:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date
On Apr 10, 2016, at 12:53 PM, Kenny Chiou notifications@github.com wrote:
Or look at this issues thread itself. "kchiou commented a minute ago" is pretty useful to me as a UI user. If there are well-supported strategies for human-readable times, I think we should use them.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/ethoinformatics/ethoinfo-project-app/issues/7#issuecomment-208015004
right, since easy options are available, it makes sense (at some point) to have the user specify what they would like. right now, "remarks" is just a text field, so if there are multiple timestamps in there, it won't be as straightforward to parse out). I may make sense (as some point?) to treat remarks as an array.
On 4/10/16 11:55 AM, tigoe wrote:
Date formatting is a solved problem in JS. We can use any one of many options, choose one:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date
On Apr 10, 2016, at 12:53 PM, Kenny Chiou notifications@github.com wrote:
Or look at this issues thread itself. "kchiou commented a minute ago" is pretty useful to me as a UI user. If there are well-supported strategies for human-readable times, I think we should use them.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/ethoinformatics/ethoinfo-project-app/issues/7#issuecomment-208015004
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/ethoinformatics/ethoinfo-project-app/issues/7#issuecomment-208015195
Posted for Tony:
The clock button at the bottom of Remarks nicely enters a timestamp in "HH:MM" format, but it would make sense to have this enter a complete datetime stamp "YYYY-MM-DD HH:MM:SS" and with some kind of tag around it (e.g., bracketed in some way "[...]" or "<...>"