Hi Carlos,
I got this issue on my draft version of MaskedTextInput:
https://github.com/RIAstar/MaskedTextInputFx/issues/2
I redirected the poster to the Apache Flex experimental component, but I
think his issue might apply to your component as well.
Did you think of RTL text support?
Cheers,
Max
@Mark
> Is the regex requirement just for numbers or all input?
If you're working with a regex, you can configure any possible restriction
on the characters.
For instance: char at first position must be number between 4 and 8; char
at second position must be D, T or Z; char at third position must
Hi Carlos,
great work.
I found these little bugs:
1./
- take any input of your demo
- fill completely
- select all (with the mouse or ctrl+a, doesn't matter)
- type one character
> expected: one character at first position
> got: two identical characters at first and second position; second
b.com/carlosrovira/7895322
> Skin: https://gist.github.com/carlosrovira/7895395
> CSS: https://gist.github.com/carlosrovira/7895435
>
> As commented, this is the first draft, and it will hopefully evolved in the
> experimental library...
>
> Hope you like it!
and organized, I'll digg as I get some time :). can you upload a demo
> to some place where we can preview it?. Regarding the skin, It's very close
> to default spark TextInput skin, but I use the prompt to show the remaing
> mask, and I removed the incluedIn from prompt. I thi
@Carlos
I put my take at a MaskedTextInput in a Gist:
https://gist.github.com/RIAstar/7893328
I repeat: there's some rather dirty code in there, however there's also
some logic to handle multiple separators with a regex. Perhaps you can find
some inspiration there.
Apparently I also felt the need
Hey Carlos,
That's great. I'd written a very similar component a few years ago, which
worked pretty much the same as yours except the code was never
publication-worthy ;)
>From what I've seen, there are 2 minor differences:
- there was a list of possible separators (which could also be
configure
> I think both sentences lead to the same conclusion: making a new "Popup"
as easy as possible to implement (using your "PopupController").
> That way, it's not even needed to derive from anything.
> If you need a custom alert with let's say "Retry/Ignore/Abort" buttons,
build a custom Panel and
to use.
> If someone wants to implement a super-duper-extended Alert box, they can
> always subclass and change the skin.
>
> WDYT ?
>
> Maurice
>
> -Message d'origine-
> De : Maxime Cowez [mailto:maxime.co...@gmail.com]
> Envoyé : lundi 14 octobre 2013 10:45
&
> But on the other hand it needs to be displayed in a Panel Skin frame.
I don't totally agree on that one: one might very well imagine an Alert
that has no title, hence removing the need for a title bar. So Alert's skin
might have to react a bit differently than Panel's skin based on the value
of i
low).
> --
>
> PS: to say the truth, I am not using PopupAnchor but a variant of it,
> called "Popup" that is part of Cairngorm/Parsley, because it's IOC aware,
> but it's the same idea:
>
> open="{model.editDialogPM.showDialog}" paren="{someButton}&qu
msellem [mailto:maurice.amsel...@systar.com]
> Envoyé : vendredi 11 octobre 2013 11:31
> À : dev@flex.apache.org
> Objet : RE: FLEX-33806 and spark Alert implementation
>
> Hi Maxime,
>
> What's the difference between you new SkinnablePopup and the existing
> Skinnab
I've been working on a Spark implementation of Alert, which I've discussed
on this list before (see
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Alerts-and-dialogs-in-Flex-4-x-Spark-was-Alerts-and-dialogs-in-FlexJS-td27595.html).
Unlike the current experimental implementation - whic
nl_BE, nl_NL: "Verplicht" is more appropriate in the context of a form
field.
Max
On Sat, Aug 17, 2013 at 8:08 PM, Jose Barragan <
jose.barra...@codeoscopic.com> wrote:
> For es_ES, "Necesario" is correct, but we use "Requerido" for this context
> better.
>
> es_ES Requerido Required
>
s example) are
relative to the application.
See it in action at http://riastar.github.io/SkinnablePopUpFx/ (it can
be customized through custom item renderers and some addtional
properties)
Max
On Sun, Jun 16, 2013 at 10:09 PM, Maxime Cowez wrote:
> @Carlos
> > Maybe we coul
e, what
> >about implementing an abstract BaseAlert (or something similar that
> >contains a command-bar which can be filled with Buttons and a concrete
> >subclass Alert that mimics the functionality of the original Alert?
> >
> >Chris
> >
> >_
ault (not
'cancelable' or 'discardable'). This results in a simple message box with
an OK/Commit/Yes button.
Max
On Mon, Jun 10, 2013 at 10:57 PM, Maxime Cowez wrote:
> @alex
>
> > Interesting. Makes me wonder if Alert should be a container for a set of
> but
ues and added to the displayList.
So yes it is instantiated, but it's more lightweight than the UI component
itself. Or at least it was supposed to be: my conclusion from the
experiment was that it was not really worth the effort, unfortunately.
Max
On Mon, Jun 10, 2013 at 10:43 PM, Maxime
s my understanding that there already
is an implementation of Alert in the experimental components (that one is
more of a direct port to Spark of the old mx Alert though). I don't think
it would be wise to have two discrete implementations of the same concept.
Max
On Mon, Jun 10, 2013 at 10:08 PM,
As we were discussing some options in the thread "Alerts and dialogs in
FlexJS", we started to elaborate on dialog implementation in general. This
was carrying us away from the initial question so I started this new thread.
One of the initial topics was the possibility to declare Alerts/Dialogs as
t;>of
> > >> buttons of your choosing.
> > >>
> > >> FlexJS will have a minimum of two Alert classes: a simple one that is
> > >> essentially the JS alert() call, and then something that has a choice
> of
> > >> buttons more like mx:Al
e, it would help clarify what you're thinking.
>
> -Alex
>
> On 6/8/13 12:13 PM, "Maxime Cowez" wrote:
>
> >@Carlos: Interesting idea. I had already created a Flex 4 implementation
> >of
> >PopUp / Alert that can be used in a declarative way (s
ent)`...
Of course this is good old Flex 4; perhaps this can be solved another way
in FlexJS?
Max
On Sat, Jun 8, 2013 at 9:13 PM, Maxime Cowez wrote:
> @Carlos: Interesting idea. I had already created a Flex 4 implementation
> of PopUp / Alert that can be used in a declarative way (see
>
@Carlos: Interesting idea. I had already created a Flex 4 implementation of
PopUp / Alert that can be used in a declarative way (see
https://github.com/RIAstar/SkinnablePopUpFx). I'll see if I can tweak it to
leverage your idea; don't think it should be too hard.
Max
On Sat, Jun 8, 2013 at 4:30 P
@alex The polymer project has an interesting take on the conditionals
you're proposing.
Some examples:
https://github.com/Polymer/mdv/blob/master/examples/how_to/conditional_template.html
https://github.com/Polymer/mdv/blob/master/examples/how_to/conditional_attributes.html
On Fri, Jun 7, 2013 at
@Sebastian: I could not disagree more. In my opinion Flex *is* an MVC
framework. It doesn't need an additional layer that requires me to write a
whole lot of boilerplate, unnecessarily complicates project structure and
forces me to adhere to some rules I often find questionable. I believe Flex
has
I'd like to make this more concrete. Let's take Alex' Button example and
compare the 'stateGroups' way to the 'multidimensional states' way.
Here's what that Button's States might look like with 'stateGroups'.
When I find myself pondering such a situation, I usually come to the
conclusion it's time to split up my component into smaller ones: most of
the times it's a signal that there's too much going in one view and I'm
breaking "separation of concerns".
Of course that's not true for *every* situation, b
[
https://issues.apache.org/jira/browse/FLEX-33350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613025#comment-13613025
]
Maxime Cowez commented on FLEX-33350:
-
No companies involved. You have my bles
[
https://issues.apache.org/jira/browse/FLEX-33350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608794#comment-13608794
]
Maxime Cowez commented on FLEX-33350:
-
I'm the author of the early draft
I think it would be interesting if the DateField were combined with
"MaskedTextInput" component. By MaskedTextInput I mean a TextInput that has
a text mask (e.g. dd/mm/ for a date) in which the user can type his
values (numeric only in case of DateField) without using the mouse. In a
DateField
Maxime Cowez created FLEX-33413:
---
Summary: HTML wrapper ANT task fails to write
playerProductInstall.swf to disk
Key: FLEX-33413
URL: https://issues.apache.org/jira/browse/FLEX-33413
Project: Apache
[
https://issues.apache.org/jira/browse/FLEX-33404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581169#comment-13581169
]
Maxime Cowez commented on FLEX-33404:
-
When I compile your test case with 4.9
a workaround in a matter of minutes.
(sorry, hit the send button while typing the previous mail)
Max
On Fri, Feb 8, 2013 at 2:56 PM, Maxime Cowez wrote:
> @Avi It took me about a week to get my productiveness back to the level it
> was when I used FB. After that it only kept go
@Avi It took me about a week to get my productiveness back to the level it
was when I used FB. After that it only kept going up :)
Incidentally, one of the many advantages of IntelliJ is the help you can
get from people like Alexander (as he just proved).
As an example, I just recently filed this b
I was certain I had seen this somewhere before and after poking my brain
with a stick for a little while I remembered that someone had asked a
question about this exact issue on StackOverflow:
http://stackoverflow.com/questions/13847817/upgrading-from-flex-3-0-to-flex-3-6-custom-combobox-getting-ty
[
https://issues.apache.org/jira/browse/FLEX-33311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxime Cowez resolved FLEX-33311.
-
Resolution: Fixed
Fix Version/s: Apache Flex 4.9.0
Though no-one was assigned to this
[
https://issues.apache.org/jira/browse/FLEX-33248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559820#comment-13559820
]
Maxime Cowez commented on FLEX-33248:
-
I have updated my original test applicatio
[
https://issues.apache.org/jira/browse/FLEX-33248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559791#comment-13559791
]
Maxime Cowez commented on FLEX-33248:
-
[~cframpton] I tried the pat
[
https://issues.apache.org/jira/browse/FLEX-33354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556171#comment-13556171
]
Maxime Cowez commented on FLEX-33354:
-
It's in ButtonSkin
Maxime Cowez created FLEX-33352:
---
Summary: defaults.css from custom theme is no longer automatically
sourced
Key: FLEX-33352
URL: https://issues.apache.org/jira/browse/FLEX-33352
Project: Apache Flex
41 matches
Mail list logo
