Transitioning from Apple extensions

[Scott Palmer]

On 2012-06-01, at 8:05 AM, Mario Torre wrote:

> The Apple LAF is being worked on, and I think is pretty good already.
> 
> I don't know if the system properties that were used to alter the LAF
> will be supported, I guess this would be ok, but someone more close to
> the Mac development is more qualified than me to answer that question.

There are certain things that would just be unreasonable to drop.  Like the screen menu bar.
Support for Apple events, like opening a document or responding to Quit, are rather essential as well. It's simply part of the look and feel… so to suggest that it is a "proprietary extension" in my opinion is rather silly.  That the Java look and feel model isn't robust enough to properly support it is a whole other issue that needs to be addressed on a higher level.

Scott


> 2012/6/1 Scott Palmer <swpalmer at gmail.com>:
>> On 2012-06-01, at 4:07 AM, Mario Torre <neugens.limasoftware at gmail.com> wrote:
>> 
>>> 2012/6/1 Chris Harshman <harshman+javadev at gmail.com>:
>>>> On Wed, May 30, 2012 at 4:29 AM, Artem Ananiev <artem.ananiev at oracle.com>wrote:
>>>> 
>>>>> We at Oracle do our best to support all Java apps on Mac OS X that were
>>>>> written for Apple's JDK6 and relied on Apple's extensions (system
>>>>> properties, command line args, com.apple classes, etc.), but we don't
>>>>> provide any official support for anything except public APIs.
>>>>> 
>>>> 
>>>> Is there any sort of guide (official or otherwise) mapping Apple's
>>>> extensions to public API replacement/equivalent/work-arounds? (I.e., is
>>>> there a way current developers can hedge their bets, coding to the 'rich'
>>>> Apple JDK6 experience but also degrading as gracefully as possible for
>>>> OpenJDK 7+?)
>>> 
>>> That's the bet that people lose when use proprietary extensions.
>>> 
>>> What are the specific "features" you're missing? Perhaps the most
>>> popular ones will be reintroduced, but I doubt that Apple specific
>>> functionality will end in the main JDK, that's not the place for it.
>> 
>> It is in cases where it is the JREs job to provide a reasonable user experience. Such as supporting the native platform's look and feel.  Let's face it, that's all the Apple "extensions" we're doing.
>> 
>> Scott
>> 
> 
> 
> 
> -- 
> pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
> Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF
> 
> IcedRobot: www.icedrobot.org
> Proud GNU Classpath developer: http://www.classpath.org/
> Read About us at: http://planet.classpath.org
> OpenJDK: http://openjdk.java.net/projects/caciocavallo/
> 
> Please, support open standards:
> http://endsoftpatents.org/