TYPO3.Neos

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19474

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19474

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19474

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19474

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/21081

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/21081

1. We currently have two "sets" of icons: light and dark - will there be more? does everybody has to provide two icons?
2. What about different sizes? in different representations (e.g. node tree vs workspace module or for different screens) we might want to display icons in a different resolution

I think in the long run we should go for single colored vector icons throughout the Neos backend as this would solve both issues above and some more.

I'm wondering if we could go this path already now instead of introducing a (breaking?) change that is only an intermediate solution. What about including (configurable) icon fonts and some (dynamic) CSS? That would also simplify the markup from:

1<div class="neos-content-new-selecttype-button">
2  <a rel="typo3:TYPO3.Neos.NodeTypes:Headline" class="neos-content-new">
3    <script id="metamorph-86-start" type="text/x-placeholder"></script>
4      <img src="Images/Icons/White/text_letter_t_icon-16.png">
5    <script id="metamorph-86-end" type="text/x-placeholder"></script>
6    Headline
7  </a>
8 </div>

to just:

1<div class="neos-content-new-selecttype-button">
2  <a rel="typo3:TYPO3.Neos.NodeTypes:Headline" class="neos-content-new">
3    Headline
4  </a>
5 </div>