No description provided.
this is going to be on hold for a while, initially the idea was, not only the inline editing functionality but the integration with createJS (the semantic part), sadly the setup in order to make a tile "createjs friendly" was too hard and adds complexity, in most cases, correctly describe a content type with a rdfa schema was just to difficult. So we dropped that approach, next we tried to integrate just a lightweight html5 wyswyg editor, first with aloha, didn't work well because a nasty dependency (jqueryui 1.9rc), 1.9 has some conflicts with jquerytools, so the inclusion wasn't an option, and aloha didn't work with 1.8, the latest integration test was with hallo, this time, the dependency are fulfilled but the library has a very poor support for the native html5 edition features in ffx and after a few clicks you end with tons of errors logs.
there is a few more editor to test, the first one and more promising is "mercury" http://jejacks0n.github.com/mercury/ and "wysihtml5" http://xing.github.com/wysihtml5/
Hi, maintainer of Create.js here. It would be interesting to hear what you found difficult in RDFa, and whether we could help you to get VIE and Create integrated.
Here are some quick thoughts on Plone's inline editing story: http://bergie.iki.fi/blog/inline-editing-done-right/
The difficult in the RDFa mark process, was correctly describe an object using a vocab, talking with @bergie he pointed me, that the only required elements in order to get createjs working are: the backbone.sync server side handler, the property attribute in the editable html element (can match the tile schema names) and a URI.
so, @Quimera, can we face this challenge using create.js now?