Shared menus

[Richard Gaskin]

Chipp Walters wrote:
> Richard Gaskin wrote:
> 
>> I feel bad for their ROI: the API is considered "for Apple use and 
>> subject to change", which often translates to "your stuff will break 
>> with our next release."
> 
> 
> Heck, if they were ONLY THAT NICE at Apple! They routinely break stuff 
> with their next release with no warning at all-- hence the multiple 
> changes to altBrowser. In fact, most of the time, it's their stuff which 
> is broken.

Dude, don't get me started.

While I have apps written for Win95 that continue to run without 
difficulty in Microsoft's latest OS, on Mac we've had to port from 68k 
to PPC, and then from Classic to OS X, and even now stuff break between 
releases of OS X.

The latest of these affecting my work is:
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=3098>

Mark Waddingham is on top of that, in touch with Apple engineers to see 
when they'll fix that bug apparently introduced in QT 7.0, or if they 
have a workaround for it.  In the meantime we're in the process of 
redesigning our app to work around Apple's bug.

And then there was "GURLGURL", and Apple's requirement that all 
developers write their own custom filter proc to provide NavServices 
glue which could have been done once in the OS, and the issues you've 
encountered with their web rendering, and....

--
  Richard Gaskin
  Managing Editor, revJournal
  _______________________________________________________
  Rev tips, tutorials and more: http://www.revJournal.com