There is no need to differentiate between site tools and the navigation
anymore. Instead now it's differentiated between the navigation tools
and the displayed content.
Now all toggling of the sidebar and the related menus is done through
the same click handler. HTML has been unified. All sidebar related
content is now in a single include file instead of several. Icons for
the site tools user tools and trace have been added.
The CSS for the whole sidebar still has to be refactored.
* master:
show license not copyright SPR-794
use proper translation mechanism for JS SPR-798
added type ints for other plugins
SPR-797 fix ID uniqueness
Now the SVGs are loaded via AJAX and are directly embedded into the
HTML. This allows for styling them via CSS and we can apply proper hover
styles.
The svg dispatcher was extended with an embed option (boolean parameter
'e') which will return an absolute minimum svg with absolutely no
styles.
I had a really hard time to understand the existing CSS which seemed
much too complicated for what it does.
Variable use was suboptimal. I couldn't figure out which variable
defines the proper size for the icon and the resulting margin.
This implements the JS logic as discussed in our meeting. A sidebar can
now contain virtually any wiki syntax. (currently hardcoded) H2 elements
will toggle all their following content which is wrapped in a wrapper
div.
This is currently implemented on top of the old JavaScript which should
be removed.
The toggle element should be made configurable.
We probably want to reuse some of the toggle logic for the user tools.
A SVG not found in the template or in the local media storage will now
be looked up in the Material Design Icon library (via a cached HTTP
request to the rawgit CDN).
* origin/svg-dispatch:
add caching and fix <g> wrapping
fixed content type header
fixed auth check
feat: add background-colors to SVG-dispatcher
first go at a dispatcher to dynamically recolor SVGs
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
