Re: NSView and performance drawing again. A Result!
Re: NSView and performance drawing again. A Result!
- Subject: Re: NSView and performance drawing again. A Result!
- From: Paul Fox <email@hidden>
- Date: Thu, 11 Jul 2002 17:27:25 +0100
>
You may want to rethink things a little... the old QuickDraw routines
>
most likely do not support anti-aliasing (without extra work) and they
>
are not exactly multi-lingual friendly. Also QuickDraw is not being
>
maintained very much and will go away someday.
Well I am not that fussed. Anti-aliasing seems to work for text - havent
tried for line drawing. If necessary I will have an option for
Cocoa or Quickdraw in the app and people can choose (the 'go-faster' button
or the 'go-slower' button!)
Yes - it may go away - I'll worry about that when it happens - by
then Cocoa may be better optimised and we'll be on faster machines.
As for multi-lingual, well I am only an 8-bit app - not Unicode.
>
I suggest getting a technical support incident token and working with
>
folks at Apple to see what you and/or they may be doing that is causing
>
you performance problems. I see many applications that are Cocoa/Carbon
>
based (using ATSUI) that don't appear to have text performance problems
>
(when jumping around in text). It sounds like a little caching of text
>
views may speed your cross file swapping... but I am no expert in ATSUI
>
or Cocoa text.
I cannot cache anything in Cocoa; I tried in ATSUI but had problems at
the last hurdle (text upside down -- I know why and couldnt be bothered
to cure it since the Quickdraw worked so much better anyhow).
Try any of these well-performing apps with a huge file - I would
be interested to know what happens. (I must give it a go in TextEdit).
I have tried hard to be a conforming citizen but to no avail. No
one really cares about the internals - the customers will want performance,
not be concerned about the implementation.
>
Even if the solution ends up being close to what you have done at least
>
some folks at Apple will know about it and the may improve Cocoa/ATSUI
>
as a result.
I would be happy to talk it thru with people at Apple, but not if it
is going to cost. Its quite possible that no problem exists and its my
learning inability. I think not. I think it does what they expect.
I know that Cocoa is an issue - I just use Finder - scrolling a view
to give me an idea on performance issues.
>
Also get a hold of a jaguar seed to see if your text processing is still
>
slow, it may not be worth the QD if jaguar improves things enough for
>
you.
Yep - I am eager to see jaguar - but I am not going to install it
til it is a gold product. (I try not to work on beta products - too much
of a pain; I want to work on what customers actually use). I suspect
everyone will jump ship to jaguar and that will be great.
One of the issues about performance is that if it 'feels bad', then chances
are you (as a developer) are doing something wrong. I exhausted all
"Cocoa" mechanisms to get speed up. I have a simple test harness app
(now much more than simple!) to test ideas out to see where the bottlenecks
are, e.g. simple drawing texts without worrying about drawRects and other
application specific issues. This showed me that even if there
are no application inefficienes (such as double drawing, pointless
drawing, etc), that things would be too slow.
I hope to have an app that is as responsive as can be. Prior to
the QuickDraw code changes (and many many cocoa optimisations/workarounds),
it ran like molasses in liquid nitrogen. Some of these issues are
application architecture issues, but as I have repeatedly said on this
list, I am not gonna do things the 'Mac' way. Why should I?
If I do things the 'mac' way, then I should also be doing them the
'windows' way, or the 'Motif' way etc etc. Each platform thinks its better
than the others. I dont much care about that. I want a single app
running on three major platform architectures, not 3 copies of the
same app to maintain.
My way is not everybodies way, and some of the issues are an issue.
I hate to waste cpu cycles especially when they are my own. I hate it
even more if I end up wasting your cpu cycles!
>
-Shawn
>
>
p.s. I could forward you a
Yes - I would really like a
Can I have a pink one please? :-)
>
On Thursday, July 11, 2002, at 05:02 AM, Paul Fox wrote:
>
>
> After a lot of head bashing trying to see where the performance
>
...
+-------------------------------------------------------------------------+
| CRiSP - Flexible editor | CRiSP, syn. for BRIEF |#
| | Internet: email@hidden |#
| If you get no reply for | WWW: (mine)
http://www.crisp.demon.co.uk |#
| support, please check your | WWW:
http://www.crisp.com |#
| Reply-To: email address. | WWW:
http://www.pacemaker.co.uk |#
+-------------------------------------------------------------------------+#
###########################################################################
_______________________________________________
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.