flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Rovira (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34149) Next features/bugs for spark MaskedTextInput experimental component
Date Sun, 16 Mar 2014 23:16:43 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937371#comment-13937371

Carlos Rovira commented on FLEX-34149:

Right now I'm evaluating to make points 1 and 2, since 1 will lead to some refactorings and
make 2 working in the new implementation. Make the reverse will be more complicated since
I'll need to work twice.

3 y 4 are logged in this ticket for referral, but I don't have plans at this time since there's
other work in SDK that I want to pursue.

> Next features/bugs for spark MaskedTextInput experimental component
> -------------------------------------------------------------------
>                 Key: FLEX-34149
>                 URL: https://issues.apache.org/jira/browse/FLEX-34149
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Spark Components
>    Affects Versions: Apache Flex 4.12.0
>            Reporter: Carlos Rovira
>            Assignee: Carlos Rovira
>            Priority: Minor
>              Labels: maskedtextinput
> After the release of Flex SDK 4.12 with the new MaskedTextInput component there's some
issues and improvements to take into account. This ticket is a placeholder to list all of
> 1) Mobile support. Right now the component is based on TextOperationEvent not supported
in mobile. So we need to remove this dependency and get it working for both mobile and desktop
> 2) In Actual version,  when different constraint patterns are applied (i.e: ### @@@),
when user remove chars this makes some chars occupy invalid positions. This only can be solved
maintaining the slots where chars exits and avoid "dragging" chars as user removes some of
them, so replacing with blanks.
> 3) Actually there's no support for direction LTR (left to right).
> 4) Support for regex complex patterns  (i.e: for dates, be able to express numbers restrictions
to avoid the user to enter numbers that could not be days, months, or years...)
> If there's more issues or features to take into account we can update this ticket to
log the needs.

This message was sent by Atlassian JIRA

View raw message