-
Bug
-
Resolution: Fixed
-
P2
-
fx1.3
javafx-ui-controls\src\com\sun\javafx\scene\control\skin\caspian\caspian.css
begins like this
...
.scene {
/* The default font for all content, it in inherited by all nodes */
font: 12pt "Amble-Condensed";
....
unfortunately its not clear that Amble-Condensed is going to be always available, and
even if it were, that's the Postscript name, which works solely on Apple JDK - and
even there it shouldn't work. In other words it won't work on Windows, nor on the
PRISM stack on any platform. As well as not working it will incur a huge start up
penalty, particularly on the Java SE based stack as it tries to locate the font.
We should use names like "Dialog" in this file unless we know for sure the
fonts available.
Its possible we could use the 1.6 "registerFont" API to ensure its available
to the SE based runtime. This requires work to (a) make sure that API
works on Apple 1.6 (b) include the font into SOMA, (c) make the necessary
API calls.
Then we need to have some way in this file to support the different
platform scenarios.
begins like this
...
.scene {
/* The default font for all content, it in inherited by all nodes */
font: 12pt "Amble-Condensed";
....
unfortunately its not clear that Amble-Condensed is going to be always available, and
even if it were, that's the Postscript name, which works solely on Apple JDK - and
even there it shouldn't work. In other words it won't work on Windows, nor on the
PRISM stack on any platform. As well as not working it will incur a huge start up
penalty, particularly on the Java SE based stack as it tries to locate the font.
We should use names like "Dialog" in this file unless we know for sure the
fonts available.
Its possible we could use the 1.6 "registerFont" API to ensure its available
to the SE based runtime. This requires work to (a) make sure that API
works on Apple 1.6 (b) include the font into SOMA, (c) make the necessary
API calls.
Then we need to have some way in this file to support the different
platform scenarios.