Jump to content

Brian Handscomb

Level 2
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

11 Neutral

About Brian Handscomb

Profile Information

  • Subscription
    PREMIUM

Recent Profile Visitors

374 profile views
  1. For the first two and a half months of 2020 the v8 Android app was probably the app I used second most (behind a v5 Mac app) using it every day and I found it perfectly fine... Web seemed fine too on the occasions I used it, which I admit wasn't often... Actually last I tried I found I can't use the new web app, just wouldn't load at all for me, so I have myself set to one of the TWO other web versions... just checked and I have it set to "classic" as opposed to either "previous" or "new"... Perfectly usable...
  2. There are a lot of official versions of the desktop clients you can download just by finding announcement posts on this forum... When I get back to working in my actual office I'll be happily "reverting" to using the installed v5.x Mac client for at least a while longer, and my personal Android phone has a v8.x client I think (thankfully can't run any v10)... These have been perfectly stable and usable for a very long time (Mac v5 a very very very ling time) and in terms of the Evernote service I would be VERY surprised if something broke them... But... I know v5 Mac breaks on Big Sur (crashes
  3. Nested notebooks IMHO don't "make sense" (a book inside a book) and very quickly raises complications, but I could imagine the scenario where you might have a group of books that you could "collapse" like a folder in a file system navigator and you could maybe put groups into groups if you really wanted, and from a tech point of view you'd add a piece of metadata to the notebook called "parent" which old clients could ignore, then make a new class of object for the groups. Providing clients ignore unknown metadata fields (or maybe the API has a way of telling whether or not to include that bit
  4. A few days ago saw Mac 7.14 (non Legacy) pop up a big message saying this version was no longer receiving updates and it was time to upgrade to a new version... Dismissed it and went to double check the update check option... still disabled... Seems like even pre "Legacy" they at some point implemented a sneaky "back door" update notification system... Might be time to investigate the "robert7" fork of NixNote2 which uses Qt... I already use it on Linux (alongside old official Mac, Windows and Android clients, not so much iOS now). From the About Qt blurb... "Qt provides single-sourc
  5. Part of me still hopes EN "does a Winamp"... A huge amount of time was spent totally rebuilding Winamp and when Winamp3 came out a lot of people found it was unstable and missing features (sounds familiar) and went back to version 2... The Winamp devs took stock of the situation and went back to the version 2 core code for a couple of minor revisions before releasing a version 5 based on version 2 with some new features of version 3 re-built to work with the version 2 code. I think maybe "less than single digit" percent chance of EN following that route as they've "admitted fault" but are pres
  6. Very nice and have looked at this before but I wish there was an option "not an Electron app". There are plenty of ways to do cross platform apps with "real code" rather than write a bunch of HTML, CSS and JavaScript... Qt, GTK, wxWidgets, Mono, IUP (I've at least tried most of these myself). The lure of writing a web app and magically creating a desktop app is too great for many people. Even Microsoft have gone down that dark path in recent years...
  7. IMHO they should "republish" the old mobile apps, under a different name if needed rather than fall back on "oh the application stores don't let us give you an old version of the existing app" excuses. I've managed to dig up a couple of old iPads and the older EN versions that were on them is wonderful in comparison and totally removed V10 apps from newer devices, not that I used mobile apps that much. My personal phone is running an older version of Android so is "safe" from getting V10 as far as I'm aware.
  8. Manual and controllable sync is also nice for network bandwidth control... For people that need such things...
  9. I saw someone note "Legacy" having features disabled? Sadly from "Legacy" it is considered a downgrade by the version check and you have to mess about with local files but it may be the last "real" versions may work better... I would not trust versions on other sites but Evernote GA announcements should be perfectly fine, last releases below... I don't think these will offer to upgrade to either the v10 or the newer "Legacy" versions when you use them but can always disable the auto update feature in the application settings. https://discussion.evernote.com/forums/topic/122340-evernote-fo
  10. IMHO v10 even in the current form was a mistake, compounded by "hiding" a hacked about "legacy" version on a support document - better would have been linking to the still available still working releases on the download page with a clear note about the different versions and the missing features of version 10... Saying there s no alternative but Legacy is untrue... As for EN saying the various app stores don't allow "downgrades" there is nothing stopping EN making another app version alongside the new version using a different name, maybe called "Evernote Classic", if they wanted to support t
  11. I would personally reverting to a "real" version... e.g. On Mac I was sticking with 5.6 or 5.7 depending on machine but one computer I had to install Big Sur and that killed the v5 clients... I tried v10.4.3 I think it was, regretted it after barely a few minutes then looked up older versions... Lots of people point to the "Legacy" versions but I don't trust they didn't do something nasty in the code we haven't discovered yet......
  12. Didn't say that... far from it... In terms of "live clients" I still have as far back as 4.6.2 Windows and 5.6.2 Mac and am not seeing any problem. In fact the only "problem" I have with 7.14 Mac is unlike my "beloved" 5.6/5.7 clients it seems 7.14 seems to want to insist that tables are wider than the notes forcing you to scroll and just like all the 6.x and v7.x clients there is no divider between the note title and the note body... The latter is a minor thing but to me is something I really liked (still like) with v5 Mac. IMHO when I saw 10.4.3 in November it struck me as something tha
  13. On Mac in the "bad old days" of the launch of version 6 (late 2014) and the IMHO bad UI changes that version brought I rolled back not to 5.7.x but to 5.6.x on my "work laptop" (I don't use "local" notebooks so it's not a big issue), though I left 5.7.x on another machine. For me this by now ancient version continued to work PERFECTLY until the day in November I needed to install "Big Sur" and the "ancient" version of Evernote crashed on launch... So I downloaded the then latest Evernote, seeing version "10" and thinking "wow I must have missed hearing about so many versions"... Nope, they ski
  14. Personally after briefly moving to 6.0 (or 6.0.1, can't remember) which had major backlash against the design, myself included, I went back to version 5.6.2 and disabled updates and have been happy ever since. I'm not sure if I have the same on my work Mac or whether I only went back to 5.7.x and just disabled as much as possible the new features 5.7 added. Only just today have I peeked back and three things have caught me attention... Firstly talk of people downgrading from 7.0.x to 6.x which sounds very familiar. Secondly I noted back in 6.1 EN reverted the sidebar to dark again. Finall
×
×
  • Create New...