JEP 253: UI control skins and input mapping discussion
jonathan.giles at oracle.com
Thu Aug 20 00:15:39 UTC 2015
I hope you'll agree that throughout our long discussion on JBS we both improved our implementations based on our discussion. To say that I haven't addressed your issues isn't fair - I worked with you to understand your issues and I addressed many of them as my InputMap implementation and API iterated. We have fundamentally different views on how to implement this, so I can't bend over and completely change my approach to your approach - or else we'd not be doing a proper job of exploring the domain. I'm not saying one approach is right and the other is wrong - I'm working on my idea of how to approach this, and as I said, I invite you to do the same.
In regard to 'closing doors' - I don't think anything I've done up to now has closed doors. I believe that WellBehavedFX will continue to be able to work in the current approach I have implemented (it just hooks into EventHandlers, right?) - it just won't make use of any of it! Nothing I'm creating is being forced down anyones throats - it is an implementation and API that is optional. As it stands, the sandbox repo I'm working in has all controls using it, but that doesn't mean controls such as your rich text editor are forced to use it, and I imagine that they will continue to work well with your WellBehavedFX API and implementation. Am I misunderstanding what you're saying?
More information about the openjfx-dev