Jump to content
Due to limited holiday staffing, chat will be unavailable from Thursday, July 2 at 5:30 PM (CDT) to Monday, July 13 at 8 AM (CDT). This will allow us to reply to your email requests as quickly as possible. Thank you for understanding. ×

eric scoles

Level 2
  • Content Count

  • Joined

  • Last visited

  • Days Won


eric scoles last won the day on February 5 2016

eric scoles had the most liked content!

Community Reputation

7 Neutral

About eric scoles

Profile Information

  • Subscription
  1. Updated to 6.15 from 6.11. Syncing no longer works. Have tried logging out/in. Currently trying to figure out how to revert to 6.11, as Evernote's pretty much useless without syncing.
  2. Changing to 'other browsers' is a major workflow impediment to a lot of us. As for 'other clippers', not sure what you mean. Do you mean 3rd party Evernote clippers? Or other clipping services? If the former, there's the opportunity cost of spending time researching & testing 3rd party clippers, then dealing with *their* flaws. & that's w/o considering the added risk of giving an unknown 3rd party access to your Evernote stack. If the latter, the field is pretty small: Evernote drove most competitors out of the field, & of the few that remain commercially viable AFAICS only OneNote approaches 80% of the feature set (& doesn't include features I use all the time).
  3. Clipper fails in Chrome on Windows 7 Pro. Using Chrome 39.0.2171.95 m on this workstation. What happens: I click on the clipper icon, and aside from the click-action nothing discernable happens. Here are typical relevant log entries for a failed attempt: 09:41:35 GMT-0400 (Eastern Daylight Time) (LOG) /background.html: browser action click handler at /js/main/Extension.js:2:625309:41:35 GMT-0400 (Eastern Daylight Time) (LOG) /background.html: null at /js/main/Extension.js:2:632909:41:35 GMT-0400 (Eastern Daylight Time) (WARN) /background.html: logged out while toggling coordinatorat chrome-extension://pioclpoplcdbaefihamjohnefbikjilc/js/main/Extension.js:2:6479at Array.<anonymous> (/js/main/Auth.js:2:6684)at i (/js/common/Bootstrap.js:2:1914)at g (/js/common/Bootstrap.js:2:1412)at e (/js/common/Bootstrap.js:2:1077)at Bootstrapper.j [as bootstrap] (/js/common/Bootstrap.js:2:2062)at Auth.m [as isAuthenticated] (/js/main/Auth.js:2:6156)at chrome-extension://pioclpoplcdbaefihamjohnefbikjilc/js/main/Extension.js:2:6294at EventImpl.dispatchToListener (extensions::event_bindings:395:22)What I've tried so far: Restarted Chrome. De/Reactivated the clipper. Turned off all ad and tracker blocking.
  4. The big advantage to using PDF is that it will capture some aspects of the page that HTML won't. For example, a Tweet embedded using Twitter's standard widget will NOT be captured if you clip the page it appears on. However, if you print the page to a PDF (using Chrome), it will be represented. The problem is with iframes and related elements: Evernote will not capture the content of iframes when it's clipping. This is not surprising and doesn't necessarily represent a defect -- for some very good technical reasons you would NOT want capturing the content of an iframe to be the default behavior -- though it is definitely a limitation, and a surmountable one. It should be theoretically possible* to use Google's PDF support to clip directly to PDF. However I think it's more likely you'll see some third party to that than see it in the Evernote clipper, at least right away. (Again, I don't blame them. To me, it's a pain, because I very often want to save Storifies or other pages that have embedded tweets, and if I do that in Evernote they've basically got a hole in them.) -- *anything is theoretically possible, if you're willing to spend enough $$ and throw enough RAM at the problem.
  5. There are some great features in the new clipper. It's just really poorly thought-through. This is a textbook example of a visual design team and a hatfull of product managers getting together to do what should be done by a UI design team.
  6. No, the new clipper is clearly inferior. It requires more steps and more mouse movement. That makes it bad. This is all essentially ergonomics 101. For reference: http://en.wikipedia.org/wiki/Fitts's_law Workflow to clip & tag with old clipper: Click icon expand/contract selection area as needed click tag link within the same small screen area enter tags click or tab to move into large comment area and enter comments as necessary click save button in same small screen area click save Note that throughout this process, your mouse pointer has probably moved a total of 200px, including back and forth. The targets are about the same size as they are in the workflow below, which in Fitts's Law terms means that they're functionally larger. Workflow to clip & tag with new clipper: click icon determine if simplified or regular article format is appropriate move mouse pointer to upper-middle of right edge of current window and click left-arrow to expand the clipping pane select other type as-necessary expand/contract clip area as needed click tag link add tags add comments as necessary (but note much smaller comment area) mouse to near bottom right corner of window to click 'save'. Note that on a normal size screen used the way most people use browser windows, your mouse pointer probably moved a minimum of 1500px mostly in long actions to acquire small targets. From a Fitts's Law optimization perspective, this is highly non-optimal. This is clearly an inferior workflow, from that perspective alone -- forget about the extra cognitive load imposed by the poor visual design.
  7. "Fixing" the UI in this case means abandoning it. They're not going to do that. Though I agree, it's borderline unusable in its current form. Very, very weird design decisions. Normally I don't like to remind people about Fitt's Law, but the UI designers at Evernote need some remedial education on it.
  • Create New...