The last release I built against 10.5 SDK and used the 10.4 minimum
version switch.
So the features of 10.5 are available but the check with
instancesRespondToSelector cares for 10.4 runtime environment.
The defines are to care for 10.4 build environments aka 10.4 SDK.
This I got from this and the next pages:
http://developer.apple.com/mac/library/documentation/DeveloperTools/Conceptual/cross_development/Configuring/configuring.html
Since I don't have Tiger myself I couldn't test it and asked on the
users list - no answer. Maybe we can drop Tiger support completely...
But if you use the 10.5 sdk, you cannot use 10.6 features, right? Are
you using 10.5 yourself?
The spellchecker finally decided to work for a reason I do not
understand :) I can indeed check that it becomes
very slow and Shqrk.qpp tells me that all the time is spent in
checkSpellingOfString ;(
What could we do from there?
The first solution is to make Paragraph send strings directly to the
spellchecker. This would
require to rework the spellcheck interface to allow to pass full
strings. I do not think
that aspell or enchant allow this, although I could not find a
documentation for enchant :(
The problem with this approach is that I am not even sure that it will
be enough. I am not sure
whether the time is spent in the setup of the function or in the word
checking itself.
If checking is slow (bad apple!), then we would have to rethink the on-
the-fly checking strategy.
Abdel, in case you are here: what were the other strategies, and which
ones were doable and would
incur less calls to the spellchecker?
Anyway, the fact is that I did the checks by pressing page down
repeatedly on a big manual, which
means that the number of words that got checked cannot be made smaller
than they are now :(
While typing this, I notice that Mail.app only does on the fly
checking at cursor position. I could add a
"isSlow()" method to the spell checking backends and revert to this
strategy for slow backends...
JMarc
