Hello Michiel!
If this means that we will use different APIs when running from Java Web
Start and when running directly from the jar, then I am not that
enthusiastic. It risks to complicate the testing and trouble shooting.
Otherwise i.e. if there is a way to use the JWSFileChooser also in the
non-Java Web Start environment, my only objection is that I assume the file
chooser stuff is also provided from the Eclipse RCP and we should not spend
too much work on things that will "soon" be taken care of by that
infrastructure.
/Linus
2008/8/29, Michiel van der Wulp <[EMAIL PROTECTED]>:
>
> Hi *,
>
> On the Java tutorial website at [1], there is the following text about the
> JFileChooser we use everywhere:
>
>
> «Note: If you intend to distribute your program as an unsigned JavaT Web
> Start application, then instead of using the JFileChooser API you should use
> the file services provided by the JNLP API. These services - FileOpenService
> and FileSaveService - not only provide support for choosing files in a
> restricted environment, but also take care of actually opening and saving
> them. An example of using these services is in JWSFileChooserDemo.
> Documentation for using the JNLP API can be found in the Java Web Start
> lesson. »
>
>
> If you run the demo at [2] (on Windows), then you see one big benefit: you
> get the native file chooser from the Windows, instead of the limited generic
> Java implementation.
>
> Now my question: Should we adapt?
> If so, I can start by creating an issue for this...
>
> [1]
> http://java.sun.com/docs/books/tutorial/uiswing/components/filechooser.html
> [2]
> http://java.sun.com/docs/books/tutorialJWS/uiswing/components/ex6/JWSFileChooserDemo.jnlp
>
>
> Regards,
> Michiel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
