[TYPO3-t3skin] About myself & Tasks

Andreas Balzer typo3 at andreas-balzer.de
Mon May 28 19:46:12 CEST 2007


Jens Hoffmann schrieb:
> Guy come down .. is't just about GFX :)
Let me correct you. We don't only have a discussion about GFX here. We 
have a discussion about TYPO3.

> 1. PNG is not a good Vektor format.
Sorry.. but to make sure.. isn't it called "vector" in English? (just 
don't know)
>    Its a 24bit stored Pixel format with a 32bit alpha chanel. (Or 8bit.)
Yeah. But there's a tiny difference to a ps file. A png file has only 
vectors in Fireworks and Adobe Illustrator CS3 (or how it's called).. 
But a png file can be viewed without seeing those vectors on any 
computer out there. Firefox and IE support the format nativly.
However you can not view a ps file with them.

> 2. I would suggest SVG's. If needed ... I don't really see the needs. :)
I agree on your suggestion. SVG seems to be the best format. As an 
advantage: As it's based on XML TYPO3 could be enabled to draw those 
icons via TYPOScript if needed.


>    But if the new Skin gives a sensfull need for big Icons, we need at 
> least 2 ver.
>    1. Vektor for +32px Icons and 2. one Pixel ver. for -24px.
I would use three ones.. One for small icons (e.g. icons of a pagetree), 
middle sized icons for any menu or other navigation elements and a large 
sized version for every situation where something has to be shown in 
detail. e.g. let's show an element icon in detail views.. (like Windows 
Vista in Explorer)

> 5. I WORK IN PS, that's what I wrote. Not: I store only Pixel!
We know this. Yes.

> 6. It a lot quicker to create a bunch of Mogups in PS than in AI.
>    And on the end, in the web, you need a Pixel Layout and this is PiTa 
> in AI.
What about reusing them? If you have to draw everything twice then it's 
getting like "do I really have to do that again.... :-/".


I think it's a lot easier with vector images.

Andreas
BTW: Do you have those mockups you created as graphic files or do I 
really have to use the pdf's to recreate them?


More information about the TYPO3-team-t3skin mailing list