On 10/27/16, 9:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi Alex,
>
>I like the Yishayw concept os adding beads in CSS. Don't know about the
>runtime cost of this, but it would allow users to configure if they want
>this or those beads for their use. If you add in the
Hi Alex,
I like the Yishayw concept os adding beads in CSS. Don't know about the
runtime cost of this, but it would allow users to configure if they want
this or those beads for their use. If you add in the component, all is done
there and people can't change it. Maybe you're the person to decide
On 10/27/16, 12:48 AM, "carlos.rov...@gmail.com on behalf of Carlos
Rovira" wrote:
>Thanks,
>
>I was not thinking this from that point of view. Maybe in MDL has sense to
>include majority of beads since it's a concrete implementation of visuals:
>Material Design Lite
>But don't know if we could
On 10/27/16, 4:39 AM, "yishayw" wrote:
>Regarding verboseness, maybe we could have a new css property such as
>'additionalBeads' which IStrand implementers look for and create?
>
>That keeps mxml compact with PAYG and flexibility.
Possible, but I'm not sure that is worth the instance initializ
yishayw wrote
> how do you re-enable a bead
should read
yishayw wrote
> how do you re-enable a strand
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-When-to-Bead-was-Re-FlexJS-enabled-property-tp56044p56073.html
Sent from the Apach
o-Bead-was-Re-FlexJS-enabled-property-tp56044p56072.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
en-to-Bead-was-Re-FlexJS-enabled-property-tp56044p56070.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
ableBead' and 'BlurBead'. Of course, baking it in in advance is
> the
> least verbose and could work for a non-basic component set.
>
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/FlexJS-When-to-Bead-was
bleBead' and 'BlurBead'. Of course, baking it in in advance is the
least verbose and could work for a non-basic component set.
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-When-to-Bead-was-Re-FlexJS-enabled-property-tp56044p56049.htm
Hi Carlos,
I just saw your tweet with the MDL example in front of the MXML for it.
There seemed like a lot of MXML in the example. I was wondering if you
considered baking in the Prompt and Disable beads into your example to
make it less verbose.
The reason the Basic components have TextPromptB
On 10/26/16, 2:18 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi,
>
>I implemented the Disabled bead, just notice that
>
>host.element is HTMLInputElement is not working, I had to comment lines as
>below to get it working.
>I don't understand @flexjsignorecoercion HTMLInput
t was very helpful
> to learn how you made it. Thanks!
>
> 2016-10-21 18:06 GMT+02:00 yishayw :
>
>> Oops, I guess you guys have already picked up on this. Saw the first post,
>> didn't see the rest...
>>
>>
>>
>> --
>> View this message in
GMT+02:00 yishayw :
> Oops, I guess you guys have already picked up on this. Saw the first post,
> didn't see the rest...
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/FlexJS-enabled-property-
> tp55853p55918.html
>
Hi Carlos,
We have a DisableBead in the html package of the sprite-refactor branch. You
might want to take a look and possibly merge to develop.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-enabled-property-tp55853p55916.html
Sent from the
Oops, I guess you guys have already picked up on this. Saw the first post,
didn't see the rest...
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-enabled-property-tp55853p55918.html
Sent from the Apache Flex Development mailing list archi
//apache-flex-users.246.n4.nabble.com/FlexJS-TextInput-Form-validation-td13577.html
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-enabled-property-tp55853p55883.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On 10/18/16, 8:42 AM, "Josh Tynjala" wrote:
>You should be able to set the disabled property on your HTMLButtonElement
>or HTMLInputElement (or any other type of element that can be disabled) to
>true. This should have the same effect as setting the disabled attribute
>on
>the HTML tag.
Yep, a
You should be able to set the disabled property on your HTMLButtonElement
or HTMLInputElement (or any other type of element that can be disabled) to
true. This should have the same effect as setting the disabled attribute on
the HTML tag.
- Josh
2016-10-18 8:37 GMT-07:00 Carlos Rovira :
> Hi Ale
Hi Alex,
in MDL the disabled is done simply adding "disabled" to the tag, either in
declaration or by code. the DisabledBead don't use that approach. I could
make my own DisabledBead, I only need to know how I can write "disabled" in
the code at runtime. Do you know the way to do this in FlexJS?
t
I responded about 3 weeks ago, but I don’t know where the response went. I just
resent it…
On Oct 18, 2016, at 6:11 PM, Alex Harui wrote:
> On 10/18/16, 5:06 AM, "Harbs" wrote:
>
>> The purpose is to remove all Flash APIs from Flex objects. The refactor
>> composes Flash objects rather than i
On 10/18/16, 4:28 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi,
>
>I tested DisableBead, but had to make some changes, since depends os
>changes in sprite branch. So removed the cherry pick in my branch. I'll
>left that behind for now.
FWIW, if MDL has a defined implemen
On 10/18/16, 5:06 AM, "Harbs" wrote:
>The purpose is to remove all Flash APIs from Flex objects. The refactor
>composes Flash objects rather than inherits them.
>
>I would like to merge it into develop now, but Alex has questioned
>whether we want to keep the refactor. It’s basically waiting for
On 10/18/16, 12:32 AM, "carlos.rov...@gmail.com on behalf of Carlos
Rovira" wrote:
>Hi,
>thanks Harbs, I cherry piclked the Yishay commit in my branch, and will
>play with it.
>
>btw, I think the visible property, although maybe could be only one
>implementation, seems to be the same philosophy
The purpose is to remove all Flash APIs from Flex objects. The refactor
composes Flash objects rather than inherits them.
I would like to merge it into develop now, but Alex has questioned whether we
want to keep the refactor. It’s basically waiting for someone to do some
profiling to see wheth
Hi,
I tested DisableBead, but had to make some changes, since depends os
changes in sprite branch. So removed the cherry pick in my branch. I'll
left that behind for now.
The Sprite refactor branch seems a huge one, what's the purpose behind? and
when is estimate to finish and merge?
Thanks
2
Hi,
thanks Harbs, I cherry piclked the Yishay commit in my branch, and will
play with it.
btw, I think the visible property, although maybe could be only one
implementation, seems to be the same philosophy right?
Not all buttons should be hidden, so following the criteria, seems a code
to aggregat
Yes. Yishay implemented a DisableBead.
On Oct 17, 2016, at 10:56 AM, Carlos Rovira wrote:
> Hi,
>
> I saw there's a "visible" property for components working in place.
> But another basic property in Flex was "enabled". I wonder if there's
> already something implemented, I didn't find it.
>
>
On 10/17/16, 12:56 AM, "carlos.rov...@gmail.com on behalf of Carlos
Rovira"
wrote:
>Hi,
>
>I saw there's a "visible" property for components working in place.
>But another basic property in Flex was "enabled". I wonder if there's
>already something implemented, I didn't find it.
Button enable/
Hi,
I saw there's a "visible" property for components working in place.
But another basic property in Flex was "enabled". I wonder if there's
already something implemented, I didn't find it.
--
Carlos Rovira
http://about.me/carlosrovira
29 matches
Mail list logo
