Posted by Wim Leers on January 4, 2013 at 12:12pm
This issue is about leveraging Create.js + VIE cleanly and properly instead of hackily like we have to do today due to Drupal limitations.
- In Edit, we weren't able to fully leverage Create.js+VIE's built-in discovery system (powered by RDFa) because Drupal's RDFa support is not good enough (not my words, but an objective observation by the Create.js/VIE developer). This implies properly leveraging VIE's type system, which also implies a cleaner way of determining which Create.js PropertyEditor widget should be used for a field (for that, also see #1874936-2: Pluggable in-place editors (allow modules to define new Create.js PropertyEditor widgets) and #1874936-3: Pluggable in-place editors (allow modules to define new Create.js PropertyEditor widgets)).
- Because at the time of development there was no REST API yet to retrieve and update content from Drupal, we had to implement a
Backbone.syncimplementation on top of forms as a transport layer. This clearly is ugly, fugly, doomed to have or cause problems, etc. We should be leveraging Drupal 8's new JSON-LD, but then that needs to have validation support first (we of course don't want to save invalid data).
This is blocked on: