Dear John: Thank you for providing these proposals!
Do I understand correctly that the idea of translating input events into control-specific events and bubbling them up is now gone? In “Goals” - * Allow changing the skin of a control without having to recreate behavior As we discussed before, some behaviors cannot be decoupled from the skin. This alone should disqualify the proposal from the start. Perhaps choosing a more complex control rather than a Button for a proof of concept would have been a better starting point? Right now I don’t know what to do - do you want me to repeat the same arguments and explanations? Please advise. Thank you -andy From: openjfx-dev <openjfx-dev-r...@openjdk.org> on behalf of John Hendrikx <john.hendr...@gmail.com> Date: Sunday, November 5, 2023 at 18:05 To: openjfx-dev@openjdk.org <openjfx-dev@openjdk.org> Subject: Public Behavior API proposal As promised, a public Behavior API proposal. Summary: Introduce a new Behavior interface that can be set on a control to replace its current behavior. The new behavior can be fully custom or composed (or later subclassed) from a default behavior. Some default behaviors will be provided as part of this proposal, but not all. See here: https://gist.github.com/hjohn/293f3b0ec98562547d49832a2ce56fe7 --John
