Jump to content

sfeley

Level 1
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sfeley

  1. Which is exactly why I've been advocating using a third party Javascript editor component. There are dedicated projects that have spent man-years solving these sorts of problems across all major operating systems and browsers. The Evernote team shouldn't be writing code to make basic formatting work. They should implement a tool that solves that problem once, for all their client platforms, so that they can focus on the cool things that basic editors don't do. "You don't know their code, you don't know if this is hard or not" is not a compelling excuse. These components were written to integrate easily into other projects, and they're used widely in similar projects. From a functional standpoint, there's nothing stopping this. If Evernote made bad design decisions early on that prevent good changes now (the jargon term for this is "technical debt") then they have even more reasons for stepping back and reconsidering their architecture. This'll be my last post on this topic for a while. I've been staying in this thread hoping that someone from Evernote will eventually check their forums; but users arguing with other users is a waste of time, and this thread is degenerating quickly.
  2. But he's right. I suggested upthread that Evernote could be improved quickly and simply by using an established third-party editor control instead of rolling its own. No one from the development team has spoken up to suggest it would be hard. By building their own idiosyncratic editor on each platform they've reinvented the wheel a few times over -- but they've gotten the shape wrong in different ways each time. Using an mature open source Javascript editor would allow for a more consistent experience, eliminate these weird gaffes, and free them up to spend more time on the features that make Evernote different. It's those features that make "Build your own!" such an unhelpful battle cry. The editor would be easy, sure. But everything else -- the syncing, the text recognition, the mobile integration -- is much harder. That stuff is good. That stuff is unique, and it really does make Evernote special. That's why it's tragic that the editor sucks so much. The part that isn't hard or special is so broken that it keeps the hard, special, and good parts from being usable for many purposes.
  3. Good idea! Now just point us to the Evernote source code and one of us might be willing to give it a shot. I won't speak for TopRamen, but his post wasn't out of line. Evernote is a commercial product. Some of us did pay for it. (I did.) It's had a subpar interface for a long time now and the developers don't appear to be responding to these customer concerns. This isn't minor griping -- these are real functionality problems that keep customers of the product from using it as advertised. If it was open source, you might have a point about its users helping to improve it, but it isn't. We rely on the company to deliver value. Saying "Don't like it? Write your own!" is disingenuous. If I complained that my car was great except that it was missing window controls and the steering wheel only turned left, would you tell me to chill out and build my own car?
  4. It'd be an easy fix if the developers cared: just use a standard open source Javascript editor with minor customizations, and deploy it across all platforms, instead of trying to build their own in each client. That they haven't responded to that suggestion suggests to me that their priorities are about trying to capture new markets instead of focusing on their core product. In the meantime I've stopped using Evernote. (I'd forgotten that I was watching this thread until I got a notice that it had been updated.) Google Documents fulfills most of the same needs for me at this point, and Dropbox with its iPhone client fulfills the rest. They already have my yearly payment so they may not care for a while that they've lost me as a customer, but I won't be renewing.
  5. No answer? Is it simply impossible? That's saddening.
  6. I'm not going to go on a long tirade or try to insist that a feature request be pushed to the top of your stack. I just want to know: How can I delete a row from a table? I can't figure out any way to do it, in the Mac client nor the online Web access, and I need to do it today. Thanks very much for your help.
  7. Thoughts for the Powers That Be: If you're using Webkit and the underlying format of these notes is just a slightly enhanced HTML (which is what I'd already suspected) then you shouldn't need to develop and maintain your own editor. The Web is full of excellent, open source, highly extensible rich text editors for HTML. TinyMCE, CKEditor, WYMeditor, YUI2, et cetera. All of them would support the features that are being asked for here: more consistent paragraph formatting, proper table editing, better font and embedded media control, and so forth. Many of them have also put extensive work into the fiendish "Paste from Word" problem. For things that are Evernote-specific (the "To Do" checkbox, for instance) they have simple extension hooks as well. Why not just drop in one of those mature editors and let this functionality be someone else's problem? If the answer is "Because we offer a superior user experience and we want to keep control over that," I could see the logic, but... Well, to be blunt, you really don't.
×
×
  • Create New...