Packaging Application Metadata
mark.howe at oracle.com
Tue Mar 26 11:26:35 PDT 2013
This is something we have been thinking about. I created a Jira item for this issue and added as a subtask for Define Architecture/Design for Packager.
We won't be using JNLP for this, we want to make sure we start clean and don't have information that isn't relevant to the packager.
This is the issue:
On Mar 25, 2013, at 1:42 PM, Richard Bair wrote:
>>> Having said that, I'd personally leave JNLP and Applet completely alone and
>>> only look at the newer deployment options for this sort of stuff. They are
>>> likely to be unusable options before too long as browsers stop plugins and
>>> OS's lock into app stores. The horrid legacy of JNLP and Applet hinder all
>>> the new options (app stores, native installers, mobile, etc) from evolving
>>> quickly. Some people will likely object to that though, just my opinion.
>> I think that is the right way to go. Start fresh and it should be possible to generate the legacy format information for JNLP or Applets from the new format.
>> It would be nice for icons to have the tool do the conversion from plain old image files (32-bit PNG). Supply various size and let the tool generate any missing sizes that might be needed so a reasonable .ico or .icns file is created for both Windows and Mac.
> That is my preference as well. If you can supply the right stuff specially, then we will use it, but to the extent reasonable we should just automatically handle a lot of these more annoying differences.
More information about the openjfx-dev