3 ms·
As a side note. I find it puzzling why Apple haven't included some sort of vector support natively. Seems like such a powerful thing to be able to use more fre
by ThomPete 15y ago
As a side note. I find it puzzling why Apple haven't included some sort of vector support natively.
Seems like such a powerful thing to be able to use more freely.
Anyone knows why that is? CPU, battery something else? (I am not a programmer)
- astine 15y agoI can only speculate but my thought would be implementation complexity. Bitmaps work fine for say 99% of interface elements and graphic elements and they are a lot simpler to implement. Vector graphics just aren't a high priority I suppose.I mean, they aren't even natively supported in most operating systems anyway. As per resource usage, vector graphics actually use less disk space. Rendering requires more CPU than bitmaps, but I doubt it's something Apple couldn't handle with a warning in the documentation.
- thought_alarm 15y agoPDF is the OS X and iOS native vector format (and before that, PostScript). It was one of the great design decisions made by the early NeXT OS engineers, even though few people understand what "Display PostScript" or "Display PDF" really means. Most of the toolbar icons you see in Mail, Preview, Finder, etc. are actually PDFs that scale to any size. The OP could have (and probably should have) used PDF for his vector-based graphics. And actually, by exporting raw CoreGraphics drawing functions from Illustrator he's essentially exporting a PDF document in a custom file format.