Unfortunately the problem is pixels themselves. With higher res screens the 
desire for clean imagery is greater. So with pixels, they have to be set at 
there largest size at 72 DPI. So this means with zoomed material you have to 
have multiple images set at their largest size per device otherwise zooming 
gets pixelated (dividing one pixel into two). Thus to achieve a clean image, 
your one pixel increases exponentially in file size. With vector, it's a little 
more math to describe 1 size that then is scaleable. Now you can go the route 
of one middle sized image and allow some pixelation on larger screens and over 
processing on some smaller screens. But to truly get the cleanest fastest pixel 
based image on all devices and screen you have to have I'd say at least 3-5 
different files. Each a different size. Seems like a lot of overhead to me. 

Also, I always wondered why postscript wasn't utilized in HTML image and font 
rendering. Seems to me that postscript would fit nicely unless I am not 
understanding postscript. But now I am OT.

Guess to get back OT I'd just say I loved how Flash handled vector. I could 
design in Adobe Illustrator or fireworks, be able to scale what ever size I 
wanted and export to flash. It was soo easy on bandwidth as far as my 
experiences went with the projects I did. In a world of trying to fit a banner 
ad with all it's animations and graphics audio and possibly video under 100K I 
utilized vector 8 out of 10 times to reduce file sizes.


Sent from losPhone

On Sep 18, 2012, at 11:57 AM, John McCormack <j...@easypeasy.co.uk> wrote:

> Henrick
> I do agree with you that Flash's vector graphics would save a lot of 
> bandwidth. What I meant was that if you download a bitmap the effect on 
> battery life would be the same for Flash, HTML5 and JS, so the argument about 
> Flash didn't stand up.
> On this vector vs  bitmaps thing...
> For an image with just a single pixel (4 bytes + header) the demand on the 
> CPU would far less than if you used vector data. For an image in which 
> encoding is not used, a single 640x480 image has 307,200 pixels at 4 bytes 
> per pixel = 1MB plus but, of course, you couldn't describe it with vectors. 
> The effect on battery life of this is image dependent, not language dependent.
> As far as I can recall, with higher demand the CPU goes faster causing more 
> logical state changes per second and whenever a logical bit changes state the 
> transistors in the chips momentarily pass excess current and that's why the 
> CPU uses more power and gets hot. The same happens with overclocking.
> Of course vectors are great for scaled images and if JS and HTML5 don't do 
> those as well as Flash they won't be as good zoomed in.
> Anyway, its absolutely wonderful to hear you all again.
> John
> _______________________________________________
> Flashcoders mailing list
> Flashcoders@chattyfig.figleaf.com
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Flashcoders mailing list

Reply via email to