Support for Apple Extensions

[Artem Ananiev]

On 7/5/2013 1:20 PM, Kaydell Leavitt wrote:
> Hi Alan,
>
> I would say that I absolutely need the following things:
>
> 1. JFileChooser Save dialog  that is native for both files and for folders
> 2. JFileChooser Open dialog that is native for both files and folders.
> 3. Print Command that is native
> 4. A menu jar at the top of the screen -- not at the top of the window.  (Where a Mac user expects it to be.)
> 5. Preferences menu item where it is expected to be (in the application menu calling an ApplicationListener)
> 6. About menu item where it is expected to be (in the application menu calling an ApplicationListener)
> 7. The quit menu item working in where the user expects it (in the application menu calling an ApplicationListener).
> 8. The Services menu should just work.
>
> I think that would work for me.

All the above is UI related stuff (eAWT). It should work in JDK7/8 as it 
worked in Apple JDK6, since the code was contributed to OpenJDK by Apple 
with little or no modifications. Note, however, that it is not as 
supported as public APIs in java.* and javax.* namespace. We don't have 
any plans to drop support for eAWT, but all the issues in these classes 
will be of lower priority by default.

What about eIO? Is it used by anybody?

> So, the com.apple.Application class is in limbo?  What about the new Application class in JavaFX?  Where does that stand?

Application is in com.apple.eawt, it's still there as it was in JDK6. It 
is not related to JavaFX Application.

Thanks,

Artem

> -- Kaydell
> kaydell.leavitt at icloud.com
> http://learnbymac.com
>
>
>
>
> On Jul 5, 2013, at 3:04 AM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
>
>> On 05/07/2013 09:53, Paul Taylor wrote:
>>> This was discussed this in some detail last Autumn, and we were assured that support would be continued, and on a postive note from my own experience Ive found everything I need  does all work on the 1.7.0_40_ea-b291 release. Alan I would suggest you discuss this with the oracle developers who were looking at this back then. At the time I also requested it should be properly documented but the response on that was pretty divided.
>> I think the right thing is to understand which of these com.apple APIs are commonly used as it may may sense to add standard APIs for some of these cases. If you links to the discussion from "last Autumn" that would be useful.
>>
>> -Alan
>