Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Create.js makes too simplistic assumptions in some areas, forcing us to have more and uglier boilerplate code than necessary.
Proposed resolution
The problems have been discussed with the Create.js maintainer and will be fixed before a Create.js 1.0 release (they've been marked as blockers).
- https://github.com/bergie/create/issues/133
- https://github.com/bergie/create/issues/140
- https://github.com/bergie/create/issues/142
- https://github.com/bergie/create/issues/166
Remaining tasks
- Help get upstream issues fixed.
- Leverage the fixes to achieve cleaner code.
User interface changes
None.
API changes
None.
Comments
Comment #1
Wim LeersAs part of #1886566: Make WYSIWYG editors available for in-place editing, I worked on improving the naming of the different PropertyEditor widgets. Instead of:
this:
But then I ran into ridiculous problems because jQuery UI Widget works in ways that are completely beyond all common sense: http://stackoverflow.com/questions/7739525/jquery-ui-how-to-call-a-widge.... (namespaces aren't actually namespaces in jQuery UI Widgets.)
So I had to use "bridging" to be able to use namespaces:
jQuery.widget.bridge('DrupalEditEditor_direct', jQuery.DrupalEditEditor.direct);
Unfortunately, that breaks with Create.js: https://github.com/bergie/create/issues/166. Hence, that issue is now also listed in the issue summary.
Comment #2
Wim Leers#1979784: Factor Create.js and VIE.js out of the Edit module removed Create.js and VIE.js, so this was implicitly fixed there.
Comment #2.0
Wim LeersAdding https://github.com/bergie/create/issues/166.