Re: Basic NSGraphicsContext question
Re: Basic NSGraphicsContext question
- Subject: Re: Basic NSGraphicsContext question
- From: Gerard Iglesias <email@hidden>
- Date: Sat, 5 Jul 2003 16:02:17 +0200
On Saturday, July 5, 2003, at 2:12 PM, Alastair J.Houghton wrote:
It's interesting that you say that; from what I've seen of the Core
Graphics APIs, it looks like NSBezierPath is just a simple wrapper
around them... I wouldn't expect it to be "costly". How much slower
is NSBezierPath than the equivalent CG calls?
The cost of the ObjC runtime system, not big with small drawing but can
be taken in account with heavy drawing.
Didn't test perf for long time, and at a certain point in the past the
caching system was not working.
There are a few reasons I can see that you might need to use Core
Graphics APIs (for example, you want to use the CGShading stuff, which
doesn't have an AppKit equivalent AFAIK [although if someone does know
of one and I'm missing it, please tell me]), but I would have thought
that it was generally better to stick to the AppKit in Cocoa programs.
There is no religion here, even with an old NeXT maniac like me ;)
And for drawing It is fun to be at low level :)
And a lot of CG stuff are not available in the AppKit context for now:
Regards
Gerard
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.