What I'm referring to is data that is already available to the packager
that is not being used effectively. It's only applied to JNLP data or
something, when it can also apply to the resources in the launcher exe. I
think the two issues are distinct.
Scott
On Fri, Jan 10, 2014 at 5:23 PM, Mark
Comments in-line
>
> I just started experimenting with the javafxpackager and I noticed that the
> .exe that is created could, and probably should, have more things
> customized in the resources. If you get properties on the file in Windows
> and look at the Details tab, things like Product name
Comments inlineā¦
On Jan 10, 2014, at 12:11 PM, Danno Ferrin wrote:
> I came on board working on the packager stuff last month. Nearly all of the
> design decisions for this were made before I came on board, but I will do my
> best to explain it.
>
>
> I'm wondering why not make java.exe the
a.net
[mailto:openjfx-dev-boun...@openjdk.java.net] On Behalf Of Danno Ferrin
Sent: Friday, January 10, 2014 9:11 AM
To: Scott Palmer
Cc: openjfx-dev@openjdk.java.net
Subject: Re: javafxpackager and launcher
I came on board working on the packager stuff last month. Nearly all of the
design decisions for
>> An "application bundle mode" could probably be
>> triggered via the contents of a resource that is injected much like the
>> custom icon is injected into the fx launcher (I'm not sure if something
>> needs to be done for preloader support too. I think the embedded launcher
>> stub handles that
I came on board working on the packager stuff last month. Nearly all of
the design decisions for this were made before I came on board, but I will
do my best to explain it.
On Wed, Jan 8, 2014 at 8:20 PM, Scott Palmer wrote:
> The Java 8 java.exe launcher is now JavaFX aware in that it will la
The Java 8 java.exe launcher is now JavaFX aware in that it will launch
JavaFX Applications that don't have a main(String []) method.
The javafxpackager uses it's own launcher when creating a native package.
Are there plans to unify those launchers?
I noticed a comment under "future work" in WinLa