Something to experiment with later... HTML5 editor image copy/paste

HTML5 when implemented is supposed to interact with the system's clipboard. I imagine the following scenario would work:

Until HTML5 copy/paste drag&drop is implemented, you'll have to rely on Flash or a (signed) Java applet to interact with the clipboard.

I would *love* to get this working with our editor. While I love skitch, it could be even easier to paste direct.

Though right now we do support pasting of image URLs (we download them properly to avoid hotlinking) -- and we're working on HTML5 drag and drop support too.

Mobile Safari and the iPad do not support contenteditable. So much for Rich Text Editing and TinyMCE

contenteditable is not supported in Safari on iPhone OS. If you're using contenteditable to enable text input within a styled element (for instance, <p contenteditable> or <div contentediable>), you can replace this styled element with a styled <textarea>. In Safari on iPad, iPhone, Mac OS X, and Windows, you can customize the appearance of <textarea> elements using CSS. If necessary, you can even disable any platform-specific, built-in styling on a <textarea> by specifying -webkit-appearance: none.

Surprising. You can't use rich text editors with your fancy iPad. So, SOL on that one. Seems like a glaring omission that I hope they rectify in iPhone OS 4.


MongoDB wasn't created in a lab

MongoDB wasn’t designed in a lab.  We built MongoDB from our own experiences building large scale, high availability, robust systems.  We didn’t start from scratch, we really tried to figure out what was broken, and tackle that.  So the way I think about MongoDB is that if you take MySql, and change the data model from relational to document based, you get a lot of great features: embedded docs for speed, manageability, agile development with schema-less databases, easier horizontal scalability because joins aren’t as important.  There are lots of things that work great in relational databases: indexes, dynamic queries and updates to name a few, and we haven’t changed much there.  For example, the way you design your indexes in MongoDB should be exactly the way you do it in MySql or Oracle, you just have the option of indexing an embedded field.

The MongoDB creator Eliot and his team are really on to something. Because it just so happens, after years of fighting MySQL, its pretty clear what they're creating is what we want.