You are right about this - it is situational. However, if one is concerned with
performance and processor load, vectors fail at any mild level of complexity
compared to bitmaps.
An image with irregular detail can still, most always (unless every pixel is
different) be compressed down to a small
Agreed.
By converting from vectored to rastered art for some of our complex
components we tripled the frame rate in Flash.
At the same time, we converted our character from 6MB to 42KB by converting
it from a sprite sheet into animated components in Flash, but it took the
artist quite a while! (s
Paul Andrews skriver:
> Adobe has said for years that mobile platforms should use bitmaps to
> conserve processor utilisation. The other real problem with flash is
> that some developers use inefficient processing loops that eat up
> processing power - I can often see it on my laptop when the fan s
On 17/09/2012 22:10, Jon Bradley wrote:
Just look up the storage and memory needs of a vector point (plus it's
animation) and compare that to an RGB triplet.
It's pretty easy to find what you are looking for.
I don't think it's easy at all. A complex image with a lot of irregular
detail may
Just look up the storage and memory needs of a vector point (plus it's
animation) and compare that to an RGB triplet.
It's pretty easy to find what you are looking for.
-j
On Sep 17, 2012, at 4:57 PM, Henrik Andersson wrote:
> Ross P. Sclafani skriver:
>> http://www.adobe.com/devnet/flash/art
Ross P. Sclafani skriver:
> http://www.adobe.com/devnet/flash/articles/optimizing-mobile-performance.html
>
That discusses runtime performance, not how big the data is. And it does
not provide any concrete research results. Just unscientific individual
observations.
I want concrete numbers that
It's just the mathematics of how vectors are managed and calculated (on CPU).
There really is no comparison - vector graphics are convenient, not performant.
It's quite easy to look up online - or imagine watching your favorite movie on
the big screen and it being all vector (it would never even
http://www.adobe.com/devnet/flash/articles/optimizing-mobile-performance.html
On Sep 17, 2012, at 4:35 PM, Henrik Andersson wrote:
> Jon Bradley skriver:
>> Of static art and of limiting complexity. The moment complex vectors are
>> used, the data requirements balloon and once motion is taken i
Jon Bradley skriver:
> Of static art and of limiting complexity. The moment complex vectors are
> used, the data requirements balloon and once motion is taken into
> consideration (data for per-control point manipulation) the argument is far
> out the window.
>
> Either way, it's a moot argumen
i think battery life is paramount to data consumption in mobile, and the bits
saved by vector formats
have a very high cost in cpu cycles.
this is why AIR for iOS tends towards starling / spritesheet methodologies.
On Sep 17, 2012, at 4:13 PM, Henrik Andersson wrote:
> John McCormack skriver:
Of static art and of limiting complexity. The moment complex vectors are used,
the data requirements balloon and once motion is taken into consideration (data
for per-control point manipulation) the argument is far out the window.
Either way, it's a moot argument.
-j
On Sep 17, 2012, at 4:13 P
>From an eLearning perspective, anyone dealing with a browser-based LMS
will need to start planning for HTML5/JS/CSS unless something new comes
out that that is not currently on the radar.
gregb
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun
John McCormack skriver:
> One thing that Apple issue seemed to miss was that any significant
> download of pixels, no matter what the delivery language, is going to
> use a similar amount of battery life. So it really had little to do with
> Flash. More to do with control of the market.
I beg to d
That article is very interesting Kevin. I will chew on it a bit more
tomorrow, after work.
One thing that Apple issue seemed to miss was that any significant
download of pixels, no matter what the delivery language, is going to
use a similar amount of battery life. So it really had little to d
HTML5 is finally on the downslide of the gartner hype cycle's peak of
inflated expectations. So it makes sense that people are starting to
pronounce it's death. Mark Zuckerberg has caught on with his comments
about native apps vs. HTML5 from last week too.
HTML always had a place, and probably
Hopefully, Flash will live on in AIR...
http://labs.visual-analytics.net/?p=543
"Internet 2 is the Internet of (mostly mobile) Applications. So IOS ist
the next Internet “Browser”. As Flash was blasted as being the problem
the reality that HTML is the technology of the old WWW was overseen.
H
16 matches
Mail list logo
