<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Courier New";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New"">Michael:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New"">> </span>
<span style="font-size:11.0pt">2. Just-in-time validation for every significant interaction</span><span style="font-size:11.0pt;font-family:"Courier New""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New"">I'd think a loss of focus might be considered as a trigger for "significant interaction". Or perhaps you could give us an example of a use case in which it'll be insufficient?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New"">> </span>
<span style="font-size:11.0pt">when did a user significantly interact with the<br>
control?</span><span style="font-size:11.0pt;font-family:"Courier New""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New"">It depends on the application requirements. So, ultimately, the validation framework that the app developers are going to use must be flexible enough to handle all the cases.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New"">-andy<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Michael Strauß <michaelstrau2@gmail.com><br>
<b>Date: </b>Monday, March 27, 2023 at 10:19<br>
<b>To: </b>Andy Goryachev <andy.goryachev@oracle.com><br>
<b>Cc: </b>openjfx-dev <openjfx-dev@openjdk.org><br>
<b>Subject: </b>[External] : Re: Allow input controls to indicate significant user interaction<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Andy, thanks for your feedback.<br>
<br>
It's true that only an application knows which fields require feedback<br>
and which don't. That's why I don't propose to create a validation<br>
framework in the core platform.<br>
<br>
However, I don't think your solution addresses the point that I've raised.<br>
While using timers to trigger validation is certainly possible, it's<br>
not what I was describing; in fact, I would argue that this would be a<br>
very bad user experience in most cases.<br>
<br>
There are basically three kinds of validation semantics that are widely used:<br>
1. Eager validation for every value change<br>
2. Just-in-time validation for every significant interaction<br>
3. Delayed validation at the time of form submission<br>
<br>
The first and third options have easy solutions in JavaFX<br>
applications, but the second option has no good solution.<br>
Sure, I can add event listeners to applicable controls and try to find<br>
out whether any particular sequence of key strokes or mouse events<br>
corresponds to a significant interaction.<br>
But that requires me to also consider many different ways in which<br>
controls can be significantly interacted with. For example, while I<br>
can type text into a text field, I can also paste text using my mouse.<br>
It would be very hard for me to detect all these interactions, and<br>
there is certainly no well-defined solution, as most aspects of<br>
control behavior are delegated to black-box skins in any case.<br>
<br>
There simply is no reliable way to answer the question that I need to<br>
have answered: when did a user significantly interact with the<br>
control?<br>
<br>
<br>
On Mon, Mar 27, 2023 at 6:46 PM Andy Goryachev<br>
<andy.goryachev@oracle.com> wrote:<br>
><br>
> I think this functionality belongs to the application-level code, not in the platform. It's the application that knows which parts of a form need the visual feedback and which do not. In my opinion, there is no APIs that are missing in order to implement
a validation framework of any level of complexity.<br>
><br>
><br>
><br>
> Not responding to programmatic changes is easy: disable validation logic when setting values.<br>
><br>
><br>
><br>
> The validation and subsequent user feedback may happen at the time of form submission, or as a result of a short timer expiring. The timer should be restarted upon each update of the value properties being validated.<br>
><br>
><br>
><br>
> In any case, this problem has a well-defined solution and, in my opinion, does not require a change in the core platform.<br>
><br>
><br>
><br>
> Cheers,<br>
><br>
> -andy<o:p></o:p></span></p>
</div>
</div>
</body>
</html>