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.
Hi,
Thanks for letting us know! This sounds very promising. I'm getting a lot of issues with lag with the new release, and now that I understand you've switched to javascript, I'm worried if that would have a performance penalty which we can feel in larger notes?
The Evernote Editor
in Evernote for Windows Requests (Versions 6.25.1 and under)
Posted
Hi,
Thanks for letting us know! This sounds very promising. I'm getting a lot of issues with lag with the new release, and now that I understand you've switched to javascript, I'm worried if that would have a performance penalty which we can feel in larger notes?