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
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
@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
@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
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 think nothing more there
:)
2013/12/10 Maxime Cowez maxime.co...@gmail.com
in the
experimental library...
Hope you like it! :)
Carlos
2013/12/10 Maxime Cowez maxime.co...@gmail.com
@Carlos
It only *looks *clean and organized on the surface ;)
But it doesn't really respect the component lifecycle very well. Just
look
at the last line (the override
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
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
d'origine-
De : Maxime Cowez [mailto:maxime.co...@gmail.com]
Envoyé : lundi 14 octobre 2013 10:45
À : dev@flex.apache.org
Objet : Re: FLEX-33806 and spark Alert implementation
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
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 plug the
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 -
]
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
SkinnablePopupContainer ?
Maurice
-Message d'origine-
De : Maxime Cowez
modal=true
open={model.editDialogPM.showDialog} paren={someButton}
my:MyComponent id=createComponentDlg/
/parsley:PopUp
What do you think?
Maurice
-Message d'origine-
De : Maxime Cowez [mailto:maxime.co...@gmail.com]
Envoyé : vendredi 11 octobre 2013 12:23
À : dev
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
--
Jose
that mimics the functionality of the original Alert?
Chris
Von: Maxime Cowez [maxime.co...@gmail.com]
Gesendet: Montag, 10. Juni 2013 22:08
An: dev@flex.apache.org
Betreff: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts
and dialogs
addtional
properties)
Max
On Sun, Jun 16, 2013 at 10:09 PM, Maxime Cowez maxime.co...@gmail.comwrote:
@Carlos
Maybe we could update it to get the benefits in your implementation to
get best of both worlds.
I'll see what I can do from my end to integrate both approaches. I'll also
try
, something that
complements the SkinnablePopUpContainer counterpart.
You have plans to integrate with the rest of spark components?
Thanks
Carlos
2013/6/9 Maxime Cowez maxime.co...@gmail.com
Alex, the mxml for my test case looks like this with minimal
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 Cowez maxime.co...@gmail.comwrote:
@Carlos
very cool
/Commit/Yes button.
Max
On Mon, Jun 10, 2013 at 10:57 PM, Maxime Cowez maxime.co...@gmail.comwrote:
@alex
Interesting. Makes me wonder if Alert should be a container for a set of
buttons of your choosing.
As I've described in my response to Carlos: I believe you can get - almost
at 6:07 AM, Alex Harui aha...@adobe.com wrote:
Sounds interesting. If one of you can sketch out what the MXML would look
like, it would help clarify what you're thinking.
-Alex
On 6/8/13 12:13 PM, Maxime Cowez maxime.co...@gmail.com wrote:
@Carlos: Interesting idea. I had already created
@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
Flex 4; perhaps this can be solved another way
in FlexJS?
Max
On Sat, Jun 8, 2013 at 9:13 PM, Maxime Cowez maxime.co...@gmail.com wrote:
@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
@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
@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'.
s:states
s:State name=up stateGroups=upStates,normal/
s:State
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,
[
https://issues.apache.org/jira/browse/FLEX-33350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13613025#comment-13613025
]
Maxime Cowez commented on FLEX-33350:
-
No companies involved. You have my blessing
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-tabpanelfocusedCommentId=13581169#comment-13581169
]
Maxime Cowez commented on FLEX-33404:
-
When I compile your test case with 4.9
@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
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 maxime.co...@gmail.com 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
[
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
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:
[
https://issues.apache.org/jira/browse/FLEX-33248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559791#comment-13559791
]
Maxime Cowez commented on FLEX-33248:
-
[~cframpton] I tried the patched GridItemEditor
[
https://issues.apache.org/jira/browse/FLEX-33248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559820#comment-13559820
]
Maxime Cowez commented on FLEX-33248:
-
I have updated my original test application
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
37 matches
Mail list logo
