Handling updates to the JavaFX Caspian look
zonski at googlemail.com
Tue Mar 13 22:40:39 PDT 2012
I'm for - I hate things breaking, but this sounds like a good future proof
against exactly that, while still allowing for improvements. Take the pain
now while the impact is relatively controlled is my vote.
Separate discussion, but this relates back to auto-updates and having
control over when JFX upgrades itself. I'm still voting hard and loud for
developers having some control over this, even if it's just something we
have to manually configure (i.e. the default is to auto-update) and maybe
can only do for non-applets - therefore be it on our own heads if any
security holes hit us.
On Wed, Mar 14, 2012 at 3:14 PM, Gerrit Grunwald <han.solo at muenster.de>wrote:
> I could only agree, if it won't be changed now it will never be
> changed...I like
> Am 14.03.2012 um 02:21 schrieb Richard Bair <richard.bair at oracle.com>:
> > Thank you for bringing this up!
> >> I don't think anyone wants to end up in the same situation as Swing,
> where the default L&F is Metal, because moving the default to a more modern
> L&F would potentially break (or at least maim) many deployed Swing
> > I find this very compelling. We've been down this road before (not being
> able to fundamentally alter the default look) and it was UGLY! I like the
> idea that people can install a specific default stylesheet and remain
> compatible or get the latest and greatest automatically.
More information about the openjfx-dev