[TYPO3-t3skin] About myself & Tasks

[Andreas Balzer]

Ingo Renner schrieb:
> Andreas Balzer wrote:
> 
>> They not only help in "development" but also help in the final 
>> product. Vecorized images can be scaled up/down with no problems. This 
>> means we can include features like several icon sizes without having 
>> to draw one icon several times. If you have a vector image/icon with 
>> the size of 100x100 you can easily scale it up to 900x900..
> 
> I've never seen icons 100x100 big.
So you never saw Windows Vista ;) They have included icons in 135x135 
(afaik.. the size is about 135x135.. but they can be bigger) so that you 
can scale them up in several conditions.

> If you'd use those icons in real 
> world icon size, say 32x32 or 16x16, they'll scale down without any loss 
> for sure. But the bad thing is that won't be able read any details 
> anymore or you have to guess what the icons meaning is.
Yes. I absolutly agree here. If we use vector images, we should have 2 
or 3 different sizes at the beginning. I for myself like the tango 
sizes. They use 16x16	22x22	32x32. I would propose to use 16x16, 32x32 
and 128x128 (numbers that can be devided by 2 while height=width)

> On the other hand -  what do we need 900x900 icons? We have a defined 
> icon size for the BE which is 18x16.
Sure we don't need 900x900 icons. But what about a situation where you 
should do something specific that is orientated on a graphics? Let's say 
you are viewing your todos and there's a nice and big image telling you 
this. (e.g. the extension icon is displayed in the middle and large..)

Or what about a popup that shows you a trashbin. It's easier to realize 
a popup that is noticed with big images rather then with small ones..

> GIF should be good for everybody unless he needs more colors, then it's 
> PNG.
Right. The resulting images a user sees will be gif images.

> To sum up: There's no need for vektors, we're not going to print icons 
> on uge banners or flags.
Just imagine about larger menus, popups with big illustrations (a 
trashbin to tell you something is going to be removed), or other 
secenarios where big images are just better..

You know until today people think that TYPO3 is way to complicated for 
them. They think the UI has to many things you have to remember and it 
doesn't really fit into their browser windows.

The hci team has thought about hiding all unnecessary information by 
default but letting you get those back onto the screen if you want..

This is a good example about our situation here.
We have to think about a _new_ UI. It's not about improving an old one. 
It's about creating _the_ UI of _the_ european CMS. We should't even 
think about "Oh.. We made that in TYPO3 4.X this way.. we should stick, 
because it was like that"... No.. We should think about "Hey. It's new, 
but this way it's a lot easier and better to understand".


So this is how I'm thinking about vector images..

Andreas