tomboy-notes / tomboy-ng

Next generation of Tomboy
MIT License
388 stars 38 forks source link

Insert Timestamp #108

Closed shtalinberg closed 4 years ago

shtalinberg commented 5 years ago

Insert Timestamp with shortcut - useful functionality in previous linux tomboy can you add to new version ?

davidbannon commented 5 years ago

Yes, should be easy. Ctrl-T ? What would you want stamped, that is what would you like the stamp to look like ? Davo

shtalinberg commented 5 years ago

Ctrl-D (Cmd-D for mac) better for compatibility with old tomboy you can try in previous linux tomboy version - looked good

davidbannon commented 5 years ago

I don't have Tomboy installed anymore, without Tomboy, I don't need the massive Mono libraries .... If you can give me a sample, or something like - [21 Aug, 2019 - 10:11] I'd rather avoid getting into an argument with other sabout the right way to printing dates, the ISO standard, 20190821 is correct but ugly. My American cousins like 082119, incorrect and ugly :-) What do you like ?

Davo

dajoker commented 4 years ago

I'll represent the Americans, since they'll just give bad ideas otherwise. How about this:

yyyy-MM-dd HH:mm:ss e.g. 2019-12-29 21:59:03

It's easy for somebody to reformat, and in the future the formatting could pull locale settings, or let the user set the format themselves, and for now we'd have something that is great.

davidbannon commented 4 years ago

That, sir, is the ansi standard ! My preferred way but everyone I speak to hates it. Its good in the most significant terms are always to the left and because the year is obviously at the start, we know its not one of the other ambiguous possibilities. And easily generated in code.

dajoker commented 4 years ago

Yes, I agree with everything you wrote, though most people I talk do don't hate it, they just have to look at it a second time to figure it out. Without it, though, we're stuck with the backwards europeans (day before month before year, so literally backwards) and the messed-up Americans (month-day-year), and that's before we get into a squabble about two-digit vs. four-digit years, or twelve-hour vs. twenty-four-hour clocks, or spelled out month names (argh no!), or "time" before "date", or the level of precision in the timestamp. ANSI gives a good default, and then as people chime in, or volunteer to help (or maybe from the start if you are up to it) a setting can be added for them to select common options, or specify their own.

In summary, as a default ANSI makes the most sense (to me) to complete the feature request, but by all means let people make it different (wrong) however they like if time permits, or if they want to code that feature themselves. ;-)

aguador commented 4 years ago

The ANSI standard is the only one that makes sense. Are you going to waste code, possible providing a sort on the underlying ANSI format while "translating" the visual into the other formats based on interface language or something else?

davidbannon commented 4 years ago

Done in V0.26