> On Sep 26, 2017, at 4:22 PM, mandy chung wrote:
>
>
>
> On 9/26/17 2:10 PM, Michael Hall wrote:
>>>
>>> The example below seems to be something that would be better
>>> off in java.nio.files and so would not have been appropriate for the
>>> desktop JEP and you may want to file an RFE again
On 9/26/17 2:10 PM, Michael Hall wrote:
The example below seems to be something that would be better
off in java.nio.files and so would not have been appropriate for the
desktop JEP and you may want to file an RFE against core-libs/java.nio
I would agree this might not be the best fit to AWT
> On Sep 26, 2017, at 12:20 PM, Phil Race wrote:
>
> I didn't do the work here so I am answering as best I can.
> FileManager is not directly exposed but is used in implementing
> a couple of APIs on the java.awt.Desktop class.
This will not help developers who used this in their applications.
I didn't do the work here so I am answering as best I can.
FileManager is not directly exposed but is used in implementing
a couple of APIs on the java.awt.Desktop class.
If you think some important use case that is appropriate there is
missed then you can file an RFE on that.
The example below
I know JEP 272 covered the com.apple.eawt API’s.
Is there nothing to cover the eio.FileManager?
I have code using it to try and determine platform specific location’s for files
public static Path getFolder(DataTypes option) {
File f = null;
try {
