Jump to content

danrochman

Level 1
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

1 Neutral

1 Follower

About danrochman

  1. +1 / BUMP / Whatever. I happen to also be one of those nerds that proudly uses prefixes (usually an underscore, and sometimes an exclamation mark) to force things to the top of an "alphabetically" sorted list, such as Notes by Title. So I, too, am now seeing the sort order difference between the Mac and Win versions of EN. Please fix. In this day and age (I just love saying that, sorry), there really should never be an arbitrary/unexpected collation difference across product versions/platforms. If I'm being really nerdy, I'd seriously encourage you to have an *explicit* collation, at least in the online help somewhere, for each character set that you support. Users (like me) shouldn't have to drill down and try to suss out (by trial and error?) things like "Well, the Windows version is running on Windows 8, US English, with a SQLite back end, and this character set, so they're probably using blah blah blah collation, whereas the Mac version is also using SQLite, but the front-end library is sorting the results using the <xyz> collation, so...". I understand that internationalization is hard, but it's definitely worth doing - and doing right - in a product like this. According to this post, and this one (and many, many thanks to Owyn/Evernote Geek for doing the digging, and sharing his findings) Evernote seems to be using a custom collation called "NOCASEUTF8". At least in SQLite. Is that true? Is that only on Windows? Can we get any more info?? Specifically, what character sets and collations are supported in the back-end data store, and on each of the clients? It definitely won't hurt the casual users (nor power users, nor trunk developers, nor anyone for that matter) for the Evernote team to be really explicit about which characters are supported, and which collations are used. And ideally, the supported character sets and collations would be completely uniform across Mac/Win/Web/iOS/Android/Other. This topic has been out there (and the cross-platform inconsistencies have been an issue) for YEARS now, so it'd be great for an Evernote dev to take an hour or two next week and just clear this up once and for all... "An hour or two" he brazenly said, :-D -danrochman
  2. +1 I love the nested tag functionality in the desktop app & web, but need it most of all in the Android app, where drilling down into a tree would be much faster than any other way of finding my tagged notes. But while a treeview control in a left-hand pane would be consistent with the desktop and web apps, it's probably unwieldy on most non-tablet Android devices, even in portrait mode. As an alternative UI, I'd be pretty happy with tags acting like (nested) folders, rather than a split-pane treeview control UI. I picture it as follows: 1. Have a setting in the Android app to "Show all tags" (the current model) or "Show only root tags" (or some such - yes, that wording is bad), which would hide all nested tags from the initial "Tags" view. This setting could default to the current model, so that some users (like me) could opt in by changing just one setting, while everyone else wouldn't have to notice or deal with any change. 2. In the current Tags view, when showing only root tags (at the outset), modify the Note Count values for each tag so that they include the notes tagged with that tag AND ALSO any/all notes tagged with any tags that are nested below/within that tag. Relatively simple grouping/recursion, I hope. 3. When I tap on a tag, show me the "Notes tagged " section just as you do now, BUT ALSO have a "Child Tags of " section right below (or above?) it, listing each of the child tags immediately below the current tag, with each of those tags showing their own note counts, using the same code as was used at the root. Tapping on any of those tags takes me down one level, and so on indefinitely. This lets me quickly and intuitively drill down to any note/tag I want. Throw in a couple of small buttons at the top of each screen (below the root) for navigation: a "Home" button (back to the tag root), and an Up/Back button. Breadcrumb navigation would be nice, but not essential, and with deeply nested tags (and/or tags with long names), it probably wouldn't be that workable anyway... So, just my $0.02. I'm not much an Android/Java developer, but I've got the SDK installed, and know enough to be dangerous. If you give me access to the sources, I'd be happy to contribute. ps: I'm going premium the minute nested tags arrive on Android.
×
×
  • Create New...