[TYPO3-dev] New icons to the core or to t3skin?
Dmitry Dulepov
dmitry.dulepov+t3ml at gmail.com
Fri Jan 29 17:12:01 CET 2010
Hi!
On 2010-01-29 16:13:58 +0200, JoH asenau said:
> The goal is to get rid of any kind of "single icon" and switch to sprites
> completely.
> So you always get just ONE big sprite containing all the necessary Icons for
> the current combination of Skin(s) and Extensions. This can only be
> acchieved by generating this sprite and definitely not manually.
The goal sounds good as such. Now, do you imagine how complex CSS
calculations for that gigantic sprites will be if every extension can
add sprites to it? Do you know how many problems exists with overlaying
one image over another on different hosts? Who will make sure it works
everywhere?
While the idea is great, the approach reminds me a girl who decided to
lose weight by eating nothing: it is extreme approach, which causes a
lot of unnecessary complecations. As I described in another approach,
instead you should have a logical groups of sprites that are easy to
update and a simple API that can dynamically substitute an image from a
default sprite with an image from the other sprite. There is no harm in
loading two sprites. ut over cost of the implementation and maintanance
is much less.
Think about it. Simplicity is good. It even was advocated by Jens
Hoffman at one of developer's days. What happened to it? We go for
challenges or for user experience? :)
--
Dmitry Dulepov
TYPO3 expert / TYPO3 core team member / TYPO3 security team member
Read more @ http://dmitry-dulepov.com/
More information about the TYPO3-dev
mailing list