- This introduces a new option "template_backend" that will be set to indicate the backend template, defaults to 2k11.
- The "Engine: xxx" line in info.txt still works, but only for the frontend
- The frontend fallback chain defaults to the old "default" template to ensure that themes will work that have "old-style" HTML output
- The backend fallback chain only falls back to 2k11 and then "default"
- In the future, we will remove templates/default/admin once the mechanism is proven stable
To test this in all cases you can:
- Copy 2k11/ to 2k11-custom, edit info.txt, give it a distinct name. Edit the admin/index.tpl file to add some code to ensure that you will see that template in the backend if you pick it, or adjust the style.css or whatever.
- Copy idea/ to idea-custom, edit info.txt, add a "Engine: 2k11" line. Now you can test how a template would look like that fallsback on 2k11 instead of "default"
Those permutations can be checked and come to my mind:
- Backend: 2k11, Frontend: 2k11
- Backend: 2k11-custom, Frontend: 2k11
- Backend: 2k11, Frontend: 2k11-custom
- Backend: 2k11, Frontend: idea
- Backend: 2k11, Frontend: idea-custom
- Backend: 2k11-custom, Frontend: idea
- Backend: 2k11-custom, Frontend: idea-custom
They seem to work.
Currently the display of backend and frontend theme in templates.inc.tpl takes up some larger space. Maybe it could be prettified somehow, maybe put frontend and backend template next to each other, not beneath each other? Maybe @yellowled has some suggestions.
@onli and @ophian - please have a look at this, since you both also worked on the fallback chains. Please tell me if you have issues with this. We can easily revert, if you see this approach as not workable. This is more a "proof of concept" draft.
Partly. Plugins still need to use a different JS, fitting for the ckeditor. And plugins are bundled in the other-part of the toolbar instead of trying to follow the (xinha-)toolbar parameter
It makes it harder to spot "Draft", "Sticky" and "Scheduled", and
we don't have a good solution to distinguish those by color. Might
come in a 2.0.x, though.
The first will add a better width to plugin sequence_item(s), covering all screen resolutions, and sets auto margin to center on bigger screens, where sequence_container grows greater than inner 96%.
The seconds breaks sequence_item text in its own inline box on screens >= 768px.
This is well tested with plugins containing sequence_item movers eg entryproperties plugin.
This used to be two seperate processes for the category icon and
images selected in plugin/theme config. It has now been simplified
to use just one process, which also uses the same markup and JS.
This adds to the consistency of the UI/UX, but it also saves some
CSS and a lot of JS, most of the latter of the expensive kind that
modifies the DOM.
Some plugins on Spartacus have longer descriptions, making their
entires longer. Now, the description is collapsible using a details
element.
References #125
This build includes only the tests and shivs in Modernizr we do
actually use. If we add tests (in CSS or JS) or find some are
missing, this build needs to be renewed.
References #85
The equal heights boxes look weird on small screens, so we're not
firing the plugin there any longer.
This introduces a new variable for breakpoints for responsive JS.
Please *only* add more breakpoints if you actually use them.
References #100
Some plugins might want to hook into the non-WYSIWYG editor and
create buttons which do use different "tags" for open/close or
not create HTML markup at all. This makes it possible for them
to do so.
References #122
References #114
