Jump to content

Stephen C

Level 1
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Stephen C

  1. In this case, I can tell you we are here. Seriously, we appreciate your support. If there is enough interest, we can get something up on the blog about the inner workings of this project. I'll just add that personally, it's been fascinating to watch develop. I'd love to hear more about the inner workings. As a software engineer myself, hearing about the technical changes would really reinforce my faith in the new system. Plus, I just really like to read about how different teams code up their solutions.
  2. I'm noticing some weird scrollbar bugs in the beta version of the web client in Google Chrome 39.0.2171.95 (64-bit, stable) on Ubuntu 14.04. I have overlay scrollbars turned on (which I understand is an experimental Chrome feature) and extra scrollbars are being rendered on top of other components in the UI. Examples: This issue isn't unique to Evernote Web and is mentioned in the Chromium bug tracker multiple times and hasn't been fixed in years. The solution is fairly simple however. The problem is that not every scrollable element is automatically assigned its own compositing layer in the layout engine, which causes the scrollbar to have some strange rendering issues when not on top -- notably the scrollbar "bleeds through" and sits on top of all other elements. An example of what I'm talking about can be seen in this jsFiddle http://jsfiddle.net/kvNFW/ and this screenshot: http://i.stack.imgur.com/V61dh.png The fix is to force Chrome to assign each part of the UI its own compositing layer using a CSS transform. The following line of CSS seems to work according to my tests and research: transform: translate3d(0, 0, 0);This will force an element into its own compositing layer in Chrome -- might do the same in WebKit browsers too. Technical: I took the liberty of using Chrome's developer tools to add the above CSS styling to the first child element of #gwt-debug-NoteContentView-root and to #gwt-debug-notebooksDrawerSlidingPanel to test the effect. Below are some screenshots of the results after adding the transforms: Note that I don't know if this will affect / break rendering in other browsers or not. Anyone else seeing this issue on Chrome?
  3. I can agree with this. I use the web interface pretty much exclusively and create lots of notes in it, but I still don't like the default screen to be a new note. It assumes what the user wants to do instead of allowing the user to decide what he/she wants to do.
  4. I for one like the new interface, especially the expanded view for note editing. I appreciate minimal interfaces that get out of the way of your work. Obviously this is just a beta, so half of the Evernote features are still missing (which means I'll have to use the old app for now), but I am looking forward to subsequent releases. Something that would help is quick keyboard shortcuts for searching, new note, etc.
×
×
  • Create New...