Cc: Kevin Rushforth , openjfx-dev
Subject: Re: [External] : Re: [Request for Comments] Behavior / InputMap
Andy,
I should have been clearer on why I wrote this up. I think once you’ve
identified the minimum API surface that’s probably all you should implement.
More important to me is whether
; From: Martin Fox
> Date: Monday, October 30, 2023 at 17:24
> To: Andy Goryachev
> Cc: Kevin Rushforth , openjfx-dev
>
> Subject: [External] : Re: [Request for Comments] Behavior / InputMap
>
> I was looking over the InputMap proposal with an eye toward paring it down
Kevin Rushforth , openjfx-dev
Subject: [External] : Re: [Request for Comments] Behavior / InputMap
I was looking over the InputMap proposal with an eye toward paring it down to
the bare minimum.
>From the perspective of a user who wants to manipulate a control without
>subclassing it I thi
pment work and contribution from the
> community (ghm, #1014 :-)
>
> To summarize, what exactly is wrong with the proposal, and why? Please be
> specific.
>
> Thank you!
> -andy
>
>
>
> From: openjfx-dev <mailto:openjfx-dev-r...@openjdk.org>> on behalf
From: openjfx-dev on behalf of Michael Strauß
Date: Tuesday, October 17, 2023 at 15:56
To:
Cc: openjfx-dev@openjdk.org
Subject: Re: [External] : Re: [Request for Comments] Behavior / InputMap
Hi Andy,
I mean this in the most respectful way possible, but my feeling is that most of
the argume
Goryachev , openjfx-dev@openjdk.org
Subject: Re: [External] : Re: [Request for Comments] Behavior / InputMap
Hi Andy,
On 17/10/2023 20:07, Andy Goryachev wrote:
Dear John:
It looks like we have different views on the subject, so perhaps we should
invite other people to weigh in.
I would be
Hi Andy,
I mean this in the most respectful way possible, but my feeling is that
most of the arguments presented in favor of this enhancement seem to be
driven by an existing implementation, and not a "first-principles" analysis.
I've seen many proposals on this mailing list shot down with exactl
Hi Andy,
On 17/10/2023 20:07, Andy Goryachev wrote:
Dear John:
It looks like we have different views on the subject, so perhaps we
should invite other people to weigh in.
I would be interested to hear from others on this subject as well.
I feel however that I may need to make a more forma
Thank you!
We probably should extract the skinning discussion into a separate thread.
-andy
From: Pedro Duque Vieira
Date: Tuesday, October 17, 2023 at 05:57
To: Andy Goryachev
Cc: openjfx-dev@openjdk.org
Subject: Re: [External] : Re: [Request for Comments] Behavior / InputMap
Yes Input
inly not a call to a major
> redesign.
>
>
>
> Cheers,
>
> -andy
>
>
>
> *From: *Pedro Duque Vieira
> *Date: *Sunday, October 15, 2023 at 05:11
> *To: *Andy Goryachev
> *Cc: *openjfx-dev@openjdk.org
> *Subject: *[External] : Re: [Request for Comments
you
-andy
*From: *Martin Fox
*Date: *Saturday, October 14, 2023 at 14:48
*To: *John Hendrikx
*Cc: *Andy Goryachev ,
openjfx-dev@openjdk.org
*Subject: *Re: [External] : Re: [Request for Comments] Behavior / InputMap
I’ve been digging around in the code to get some context on the
existing mach
From: Martin Fox
Date: Monday, October 16, 2023 at 14:20
To: Andy Goryachev
Cc: John Hendrikx , openjfx-dev@openjdk.org
Subject: Re: [External] : Re: [Request for Comments] Behavior / InputMap
Andy,
John Hendrikx has given specific instances where this is breaking down already.
The JavaDoc
14:48
> To: John Hendrikx
> Cc: Andy Goryachev , openjfx-dev@openjdk.org
>
> Subject: Re: [External] : Re: [Request for Comments] Behavior / InputMap
>
> I’ve been digging around in the code to get some context on the existing
> machinery for ordering event handler execution. I
: Andy Goryachev , openjfx-dev@openjdk.org
Subject: Re: [External] : Re: [Request for Comments] Behavior / InputMap
I’ve been digging around in the code to get some context on the existing
machinery for ordering event handler execution. I haven’t had time to write up
test cases so all of this is
customization like your case of unregistering all key mappings from the
ScrollPane. It is certainly not a call to a major redesign.
Cheers,
-andy
From: Pedro Duque Vieira
Date: Sunday, October 15, 2023 at 05:11
To: Andy Goryachev
Cc: openjfx-dev@openjdk.org
Subject: [External] : Re: [Request for
uld be added to convert a regular event type
> to an internal one that is always processed after standard ones. It's
> possible such a method does not need to be public (but could be if users
> desire the old unpredictable behavior of mixing user and internal event
> handlers).
>
I fully agree with you here, Martin.
-andy
From: Martin Fox
Date: Thursday, October 12, 2023 at 09:31
To: Andy Goryachev
Cc: John Hendrikx , openjfx-dev@openjdk.org
Subject: Re: [External] : Re: [Request for Comments] Behavior / InputMap
Andy,
Speaking of the platform nuances – this
Andy,
> Speaking of the platform nuances – this might be relevant to the ongoing
> platform API discussion. Right now FX picks up nothing from the preferences
> set by the user within the OS. You are right, macOS allows the user to
> change key modifiers (for example, switch control and comma
(and got plenty, thanks!). Let’s see what else we could find.
Thank you
-andy
From: Martin Fox
Date: Wednesday, October 11, 2023 at 14:53
To: Andy Goryachev
Cc: John Hendrikx , openjfx-dev@openjdk.org
Subject: [External] : Re: [Request for Comments] Behavior / InputMap
Andy,
This might
Goryachev , openjfx-dev@openjdk.org
Subject: [External] : Re: [Request for Comments] Behavior / InputMap
On 09/10/2023 22:24, Andy Goryachev wrote:
Dear John:
Thank you for a very thoughtful analysis! I wanted to initiate a discussion,
with the goal of making FX better. Let me try to respond to
y, October 6, 2023 at 07:13
To: Andy Goryachev
Cc: openjfx-dev@openjdk.org
Subject: [External] : Re: [Request for Comments] Behavior / InputMap
Hi Andy,
I think the opaqueness of JavaFX controls is one of the greatest
shortcomings of the framework, so I welcome an enhancement.
Some thoughts:
1.
21 matches
Mail list logo
