onKeyPress for restricting numerical input only

fs(ops-users) wrote

hi ilango,

wouldn't it be much easier to restrict the input using a binding
constraint (either using a regex or a xs:type and maximum length)?
Additionally, you could use the xxforms:maxlength attribute if your
control is a xforms:input field.

HTH
florian




--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

fs(ops-users) wrote

And how can I also restrict the entry of characters like abc.Right now it lets me type in anything I want.

thanks
ilango
hi ilango,

wouldn't it be much easier to restrict the input using a binding
constraint (either using a regex or a xs:type and maximum length)?
Additionally, you could use the xxforms:maxlength attribute if your
control is a xforms:input field.

HTH
florian




--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Alessandro Vernet wrote

On Thu, May 15, 2008 at 7:03 AM, ilango_g <ilangocal@yahoo.com> wrote:
> For example, if I type in 123 in the first input field box and then I type
> in 4 (and there is this second input field box beside the first one with the
> appropriate - betweeen them ), the 4 should automatically be typed in the
> second box.

You could:

* Add incremental="true" on the field.
* On xforms-value-changed, check if the length of the next in the
field is 3; if this is the case, set the focus on the next field.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws


-----
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/

ilango_g wrote

Actually I did get the functionality working in FormsPlayer. It seems to me that the "xforms-valid" event that I use for setting a setfocus does not fire for some reason.
And in my original example, I do have an incremental="true". I have a simple example here, that can be tested in the sandbox. This shows the problems I have been having.

        And this is what I already had in my code:

                                   <xforms:action ev:event="xforms-value-changed">
                                                        <xforms:setvalue ref="instance('taskoutput')/fe:SSN/fe:part1_final" value="substring(instance('taskoutput')/fe:SSN/fe:part1,4,1)"/>                       
                                                </xforms:action>
                                                <xforms:setfocus ev:event="xforms-value-changed" control="secondTwoDigitPart"
                        if="string-length(.) eq 3 and . &gt; 0"/>
                                                <xforms:label>Arrestee SSN: </xforms:label>

Should I enclose the setfocus inside the value-changed-event action body?

view.xhtml


ilango

Alessandro Vernet wrote

On Thu, May 15, 2008 at 7:03 AM, ilango_g <ilangocal@yahoo.com> wrote:
> For example, if I type in 123 in the first input field box and then I type
> in 4 (and there is this second input field box beside the first one with the
> appropriate - betweeen them ), the 4 should automatically be typed in the
> second box.

You could:

* Add incremental="true" on the field.
* On xforms-value-changed, check if the length of the next in the
field is 3; if this is the case, set the focus on the next field.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws


-----
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/

fs(ops-users) wrote

hi ilan,

> http://www.nabble.com/file/p17293727/view.xhtml view.xhtml

your example file works fine in the online sandbox when changing the
bind constraint in line 56 from (string-length(.) = 4) to
(string-length(.) = 3) and the if condition in line 88 from
string-length(.) eq 2 to string-length(.) eq 3


HTH
florian



--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

fs(ops-users) wrote

hi ilan,

> Now if I shorten the field length to just accommodate the SSN fields, will
> the timelag go away.

i fear it won't - i think this is due to the client-server/AJAX architecture.

i see two possible solutions:

- accept the lag - the user will have to wait a little, and because of the
validation, he is forced to do so.

- use only one input field for the complete SSN and split the value entered
using the substring funtion - this could be done incrementally. You could add
three output fields, one for each SSN part that are updated with every keystroke.

HTH
florian



--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

fs(ops-users) wrote

hi ilan,

> - use only one input field for the complete SSN and split the value entered
> using the substring funtion - this could be done incrementally. You could
> add
> three output fields, one for each SSN part that are updated with every
> keystroke.

> Could you elaborate on this further?
> Does this mean that the user types in all the 9 digits of the SSN
> continuously.

yes, that's possible. I've attached a simple example (had to modify the
regex a little because negative look behind seems not to be supported).
There's only one input field for the complete SSN. Beneath, there are
three xforms:output fields that will display the parts separated by the
SSN separator.

The model contains a setvalue to initialize the SSN from taskinput. The
SSN parts in taskoutput are calculated from the complete SSN by a
substring function.

There's still a little lag between the keystrokes when entering the SSN
and the output of its parts, by the user can type continuously, and no
keystrokes are "lost".

Of course, the example could be amended, for example to apply the
substring function only if there's enough data entered to split.


HTH
florian


 

--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

fs(ops-users) wrote

ilango_g schrieb:

> My ideas are:
> 1) Insert an image over the single input field that appears to the user as
> three separate field. This would be another input image field sitting in
> place of the existing input control with the exception that there are 2 thin
> dividers. Or have an image with the spaces in it.
> 2) Alternatively, automatically have the system type in an "-" after he/she
> types in the first three characters of the SSN and another "-" after the
> next two characters.
>
> I know these are embellishments, but I would like to try one of these.
> What do you think is a preferred approach for that desired user experience?

I think the second one is preferable (IMHO). Using a overlay image would be
possible, too - some people modified / replaced the slider control with one
showing values / numbers. But in your case, the numbers entered would have to
fit exactly in the space left by the overlay, and that's quite tricky, i think.
That solution depends on certain layout preferences which may vary from user to
user and from browser to browser. So, i think the second alternative is the only
one that could work.

For the second alternative: When modifying the field value while the user enters
the SSN, we may run again into the problem regarding the little lag. It would
require to check the actual value and to issue a setvalue to insert the divider.
If the user continues to enter numbers, they may get lost during that process.
So, i fear a secure solution would be to wait until the user has entered the
complete SSN, or even the field has lost the focus. But this may not be the
desired user experience.

Another alternative may be to use a completely different approach: how about
creating a little java applet that would allow to enter the SSN as you desire?
This is a quite costly way, of course...

florian


--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

fs(ops-users) wrote

hi ilango,

> 1)What do you feel are the advantages of a Java applet

It doesn't have to communicate with the server while the user enters the data,
so the risk of a network lag is smaller (not existent??).

> 2) Do you think the applet is costly because of the performance overhead
> involved?

This is one point - it involves additional technologies and adds complexity to
the whole system. Leaving the field of "pure XForms" may decrease portability.
I'm not sure whether it may cause new problems regarding different browser
environments.

> 3) Another alternative I came up with is as follows:
> Use the following Javascript code available at:
> http://www.htmlcodetutorial.com/forms/index_famsupp_162.html - inside my
> XForm.
> Again, I might be naive about this one. Do you think I might still have the
> timelag if I used the above Javascript and I reference the Javascript for my
> control inside the form?

I'm not sure - i suppose what matters is that if the focus is moved, the browser
will communicate with the server to update the model (i don't know about the
client-server communication en detail). So, it doesn't matter _how_ the focus is
moved, it matters _that_ the focus was moved. As long as there are multiple
xforms control and the user moves from one to another, the problem will stay, i
fear.

Maybe it works with simple form fields: you could try to nest a xhtml form into
the xforms page and use javascript to read out the values entered. I coulnd't
test this because the online xforms sandbox seems to filter out embedded Javascript.

florian



--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws