Agreed that things should just work. In case you're still looking for a fix for the dual monitor full screen issue. I had the same problem on Chrome. It was when they introduced built-in flash. You need to disable Chrome's built-in flash and everything is back to normal.
- Image uploading with automatic resize to fit the editing area
- Form Based Editor that uses a TEXTAREA. This completes our dual In-Place Editor and Form Based Editor goal.
- Improved link creation with separate interfaces for linking text and images
- Outline hover mode (outline when hovering over editable area)
- Tab/Shift-Tab to navigate tables
- Tab/Shift-Tab to indent/outdent lists
- Numerous bug fixes
Please check it out and let us know what you think.
I totally agree with this. I wouldn't say it's just about customer support but about customer relations. Whenever I walk by the Apple store, there are so many people in there that you can barely walk around. A lot of them are there for help/support. They know they can just walk into an Apple store and get face-to-face help. They can get their problem solved right there. This is a huge boon for non-tech savvy people. They trust that Apple will fix it for them in a timely fashion.
It shouldn't be too difficult. We have discussed creating plugins into things like MediaWiki, but that will be later on down the road. Lot's more to come.
Aloha is purely an in-place editor. However, there are times when you need an editor in a form. You either have to fudge it, or use two different editors. SnapEditor provides both, an in-place and form-based editor.
Aloha is currently sitting at over 1mb. I know that there are talks about cutting down the size, but SnapEditor is already small, coming in at around 180kb.
We have the utmost respect for the Aloha guys for making an open source editor, but it is still quite buggy. SnapEditor concentrates on providing a predictable experience with clean HTML. We built it from scratch to do this right.
SnapEditor is much smaller than Aloha. Aloha is over 1mb in size. SnapEditor sits at around 180kb. This will affect page loading times.
Aloha provides only in-place editing. SnapEditor provides both in-place and form-based editing.
We really respect the guys over at Aloha for producing an open source editor, but it is still quite buggy. SnapEditor concentrates on giving a predictable experience.
Online WYSIWYG editors have frustrated us for a long time. We were fed up so we decided to scratch our own itch and build one from the bottom up. We talked to over two dozen developers to weed out the top problems and then implemented a solution. The result is SnapEditor.
We’re still in beta but we believe we’re stable enough to release a version out into the wild. It’s better to release early and be embarrassed right? Please let us know what you think.
I started looking at Backbone.js over the last few days.
I started with reading the documentation[1]. It is very well documented and contains a wealth of information.
Then I took a look at the Todo example[2] referenced in the documentation. It is also very well documented and puts together all the basics of the documentation into one clean example.
At this point, I started branching out into other tutorials. Everything I read basically reiterated the documentation and example above. This was good in terms of drilling the ideas into my head more solidly, but I could have stopped after the Todo example.
There was one notable tutorial though that was very different. Backbone provides a framework, but does not specify a structured way to store or load files. I believe this is on purpose. Backbone concentrates on the framework and gets out of your way. This leaves some head scratching though. This tutorial[3] combines Backbone.js with Require.js and provides an intriguing solution.