Jump to content

PeeJayTee

Employee Alumni
  • Posts

    103
  • Joined

  • Last visited

  • Days Won

    3

PeeJayTee last won the day on November 20 2015

PeeJayTee had the most liked content!

3 Followers

About PeeJayTee

Recent Profile Visitors

4,271 profile views

PeeJayTee's Achievements

99

Reputation

3

Community Answers

  1. Thanks, Eric. That's an interesting suggestion. Right now, the table shortcut is specifically looking for multiple [][] in a row so they don't collide with the checkbox shortcut... but now that you mention it, your examples are a logical extension of the syntax and not currently supported. I'll send this over to our devs to look at. Thanks for the feedback!
  2. Wow - this one is tough to read. As some of you may be aware, we've recently made some changes at Evernote - one of the biggest is a re-investment in our core experiences like note editing, searching and syncing. Here's a blog post with a little more detail: https://blog.evernote.com/blog/2015/09/22/the-future-of-writing-in-evernote/ TLDR; We're completely overhauling the editor in all of our Evernote clients. The baseline for Mac and Windows has been released, and Android is hopefully going to be in beta in the next 3 weeks. This includes the "tap to edit" behavior described in this thread. It also focuses on some long standing inconsistencies in the way notes are displayed - especially with images, tables, and lists. There will be a broader announcement when we're ready, but I wanted to reply here because, frankly, it's a little embarrassing to have let this go so long without a response. We really our sorry and are working to make it better. P.J.
  3. Thanks - this is absolutely on the roadmap, but not in this release. Thanks for the feedback and stay tuned. Hi guys. If it's not planned for next beta of the evernote editor, are you going to support just some of markdown? Why this question was ignored? I have the same interest. Will you support markdown? Sorry for missing this one... we had originally planned to support some "markdown-inspired" shortcuts in this version. For example, typing **Some Stuff** would result in Some Stuff. This was introduced in an early Mac beta last week, and it was clear that there are some shortcomings with this approach. Here are the details if you're interested... https://discussion.evernote.com/topic/88677-evernote-for-mac-62-beta-1-released/?p=380238
  4. Thanks - this is absolutely on the roadmap, but not in this release. Thanks for the feedback and stay tuned.
  5. Sorry for missing this one... the answer is not super easy to give. The UI will change gradually over time. I wouldn't stop your videos for this release - it's not going to look or feel fundamentally different at all - almost no UI changes. Lots of the changes in the next few versions will be to how the editor feels when you type and cleaning up some of the inconsistencies and quirks. If you have a lesson on "stuff that's weird and unexpected in Evernote", then I might hold off That said, progress and change go hand in hand, and we're promising to make meaningful progress so that necessitates some meaningful change. It's not going to happen in the next few weeks, but larger changes will likely come in a few months.
  6. Thanks for the suggestions and kind words, everyone. As we're rolling out to all of the clients, our focus is going to be spent on making some smaller improvements to the experience along the way. In the coming months, be looking for improvements to lists, tables, and copy/paste specifically. More/larger improvements are coming, but these areas are the ones that touch the most people and need the most help. We add features to the betas first, and the best way to have your feedback heard is to try out the betas and let us know what you think. With millions and millions of people using Evernote on a given day, it's really hard to make changes without breaking someone's workflow. We rely on the beta testers as our last line of defense to tell us if things are getting better. Also, we're always reading the forums... forum threads often turn into bug reports and then to fixes and features, but the loop hasn't been getting closed very well. We'll work on that. Thanks again, P.J.
  7. This is definitely on our radar - I don't believe that this is a limit of the technology, but rather, something we need to do differently.
  8. I'm glad it worked... Sorry again for the trouble.
  9. Oh, one thing I forgot... the visual progress. I'm happy to post some updates here, but I will warn you, most of the short term things are rather mundane (the way the return/delete keys works in lists, the copying and pasting of tables, basic formatting shortcuts)
  10. Wow. Thanks for all of the feedback. Regarding the technical details, I'll see if I can summarize here, but I think this might be better suited for a follow on blog post. Here are the particulars: In all of our clients, what you actually see, interact with, and edit is HTML. Originally, each of the clients consumed ENML and then translated that to HTML so that you can view and edit it. Those edits were translated back to ENML which was store locally and synced with the Evernote service. ENML is well defined, so there was no need to standardize the ENML -> HTML conversion. So long as each client produced and consumed valid ENML, things were fine. This worked well for a while, but as the codebases and clients features diverged, inconsistencies between the converters caused inconsistent HTML rendering across clients. Bugs started to show up on one client, then were fixed only to pop up on another. New editor features needed to be built by each team so a new feature meant 5-7 times the work of building it once... all of this leads us to where we are today. The "new" editor is a shared, common codebase that consumes and produces ENML, just like the old ones. The difference is that the technology we used to build the new editor (JavaScript) is cross platform, so we can build it once and share it everywhere. No more inconsistencies. Fewer bugs. Better editing for everyone. The complexity lies in the details. Each of the clients were not built thinking that we would just "drop in a new editor" so we needed to do some rearchitecting and refactoring. Hence "replacing the pipes". This work is completed on Mac and Windows, and is ongoing on the other clients. @JMichael, that's why I posted this message twice. I wanted to make sure the Mac and Windows users were aware. Be expecting more detail as things progress.
  11. I'm sorry that you feel this way, but I can tell you that we hear you and we do care... this is precisely why we're making it a priority to be more responsive. Beyond that, we will just have to earn your trust by following through.
  12. Hey everyone, This is P.J. from the Product Team at Evernote. I wanted to take a moment to tell you about a project that we've been working on for quite a while. As some of you may have noticed, the note editor changed in the Windows 5.9 release. Though it introduced a relatively small number of new features, it represents a larger body of work that will significantly improve note editing in Evernote. Years of writing the editors of our clients independently of one another has taken a toll on the the consistency and quality of Evernote’s editing experience. We recognize this and we’re fully committed to making it better. We’ve created a dedicated team focused on improving the note editor and we’re hoping you notice the difference. In the coming weeks and months, you’ll start to see the fruits of this labor appear in all of the things you do to create notes in Evernote—typing, bullets and lists, tables, images, copy and pasting are just a few of the things we’ll be working on to start. Bigger improvements will follow. For more on the thinking behind this project, check out this blog post. We can’t promise to get everything right the first time, but we can promise to listen to your feedback and work tirelessly to make every version of Evernote’s editor better than the last. If you have feedback on the editor, we’re here to listen. Feel free to comment on this thread or DM me. Thanks!
  13. Sorry for the problems - there is an issue in the latest version of Scannable that does make this process a little more cumbersome. Instead of choosing Send>>Share>>Gmail, try Send>>Share>>Open In...>>Gmail. That should send the file as a PDF. This is definitely NOT our intention, and we should have this issue resolved in the next version of Scannable. Thank you for your understanding! P.J.
  14. Thanks for the feedback - in the latest version of Scannable, if you choose Send>>Share>>Export, you should be able to save to Google drive.
  15. Ha. Sometimes, the truth is really boring
×
×
  • Create New...