RFR: 8090456: Focus Management [v8]

[Andy Goryachev]

On Wed, 2 Oct 2024 17:33:15 GMT, Andy Goryachev <angorya at openjdk.org> wrote:

>> Public APIs for focus traversal and the focus traversal policy:
>> 
>> https://github.com/andy-goryachev-oracle/Test/blob/main/doc/FocusTraversal/FocusTraversal.md
>> 
>> This work is loosely based on the patch
>> https://cr.openjdk.org/~jgiles/8061673/
>
> Andy Goryachev has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 14 commits:
> 
>  - Merge remote-tracking branch 'origin/master' into 8090456.focus.traversal
>  - removed traversal event
>  - javadoc
>  - remove bounds
>  - whitespace
>  - Merge remote-tracking branch 'origin/master' into 8090456.focus.traversal
>  - Merge remote-tracking branch 'origin/master' into 8090456.focus.traversal
>  - review comments
>  - Merge remote-tracking branch 'origin/master' into 8090456.focus.traversal
>  - review comments part 1
>  - ... and 4 more: https://git.openjdk.org/jfx/compare/4d3c3661...9e1fa796

maybe the word to use is "convenient" instead of "resilient".

But ultimately, I wanted to separate already large Node class from the focus traversal and its convenience methods.  At some point, we are going to hit one of the class file limits... 
 Ultimately, there is no difference, as it all eventually goes through the same logic.

It might be a matter of _personal_ preference.  After all, we do have `SwingUtilities.invokeLater()` and `EventQueue.invokeLater()` in swing, and `Event.fireEvent()` in fx.

Is there a deep architectural reason you don't want FocusTraversal with its static methods?

-------------

PR Comment: https://git.openjdk.org/jfx/pull/1555#issuecomment-2402947532