31–40 of 82 posts
WMF anyone? Windows MetaFile contain(ed) serialized GDI graphic calls to generate the picture in a resolution independent way, while still working as a vector file format that other application could parse. Generating static ObjC seems like a dumb idea except in very specific cases.
I love the execution of this app, but I disagree with the underlying idea for most cases. Drawing your UI is never ever going to be as cheap as loading a converted PNG (which Apple's modified pngcrush converts for you). I think a lot of devs have the draw/vector vs. precomposed bitmap tradeoff the wrong way round. Drawing all of your gradated UIButtons with CoreGraphics methods is a false economy compared to just loa…
Not sure I can agree with you. I think vector drawing can be better in both size and drawing speed. It depends a lot on the representation. Bitmap will not get a lot better than what we've got at the moment with JPeg or Gif. Vector representations can vary wildly in compactness and rendering speed. Eg. SVG bad, CSS gradients good. SVG bad, EPS/PDF good. Obviously drawing from CPU can be much quicker than reading from…
Blitting a cached PNG will always be faster than CPU based drawing code and I think the app size tradeoff is worth it.
Earlier quoted context omitted.
Not sure I can agree with you. I think vector drawing can be better in both size and drawing speed. It depends a lot on the representation. Bitmap will not get a lot better than what we've got at the moment with JPeg or Gif. Vector representations can vary wildly in compactness and rendering speed. Eg. SVG bad, CSS gradients good. SVG bad, EPS/PDF good. Obviously drawing from CPU can be much quicker than reading from…
I'm not talking about Webkit or streaming over HTTP. I'm talking within the context of true native apps. Blitting a cached PNG will always be faster than CPU based drawing code and I think the app size tradeoff is worth it.
Reading your PNG from the disk in the first place will be slower than reading a compact vector, rendering it and caching.
Re-rendering from CPU can often be faster than GPU bus access times on PCs.
Anyways, it depends on what you're optimising for. I was just illustrating how vector can be much better than bitmap in many situations.
WMF anyone? Windows MetaFile contain(ed) serialized GDI graphic calls to generate the picture in a resolution independent way, while still working as a vector file format that other application could parse. Generating static ObjC seems like a dumb idea except in very specific cases.
Well.... WMF was a great example of the difference between theory and practice. Not really resolution or even device independent.
I don't see how they're not resolution and/or device independent.
I hope this idea is not patented, because I am developing a similar app.
I hope this idea is not patented, because I am developing a similar app.
Sometimes ideas are just floating around, aren't they? I was thinking of very similar things lately as well. Obviously this application must be under development for quite a while already. One thing that I'm not totally sold on it that fact that it generates code though. It is not going to be the running application which you interactively tweak. Because that is what Bret was showing in his talk. And that is also wha…
Sometimes ideas are just floating around, aren't they? I think Opacity [1] was the first program with this feature (added in 2009 [2]). 1. http://likethought.com/opacity/ 2. http://daringfireball.net/linked/2009/09/22/opacity