Can now be used anywhere where a "real-time" filter is desirable.
As a usage example, it's implemented for the list of installable
plugins. Should work anywhere, though – needs an input element,
a list of target elements and an element within those target
elements to contain the search term.
Also made the function for the reset button for this reusable.
References #154
This time, I deleted ckeditor/ckeditor/.git and removed everytjing before. I hope that the line in .gitignore will prevent the linking the next time if someone forgets to delete the file
- 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.
documentworthy changes in our docs/NEWS file. This is important for me
when I write up blog entries about the new changes.
I tried to document every commit up until now.
Ian
Garvin Hicking
Matthias Mees
onli
Matthias Gutjahr