Sankar,
Yes I know, but I've started to investigate why you need to dispatch any
events from VO class in order to have workable Binding. - If someone can
shed some light on this - Is it how we should work with our classes which we
are writing ?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail
Actually the above scenario was always working in my tests also, previously,
when you binding a field to an UI component in single reference way, i.e.,
{anyClass.fieldName}*"/>
But, this never works if you the field name comes after multiple references,
i.e.,
{anyClass.anotherClass.fieldName}*"/>
Alex, Sankar,
I did some investigation. Here is where I'm now. I did simplification of
Sankar's code. Some things is no needed in my opinion and binding should
works.
Code:
VO -> https://paste.apache.org/UVh7
View -> https://paste.apache.org/GI5n
After compilation _bindings array look like that
Sorry View code should be this one -> https://paste.apache.org/bPbC
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58064.html
Sent from the
Alex Harui wrote
> What does the click handler do? When a BindableCSSStyles property
> changes, the watchedProperty should change. I'm thinking there is a
> problem with the binding code still.
Yes, for test purpose I'm trying to change the property inside
BindableCSSStyles through button click
PKumar wrote
> I checked the same scenario with minor changes. You need to use bit more
> code to achieve the binding in FlexjS. use following code to achieve
> correct binding behavior,
>
> [Bindable]
*
> public
*
> var anyClass:ClassA = new ClassA();
> protected function onTextInputChangeA(ev
flex-sdk_release-candidate - Build #197 - Successful
Changes since last build:
No changes
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/197/.
Oops. First time in awhile I forgot those. Will take care of it shortly.
Peter
On Jan 9, 2017, at 5:49 PM, OmPrakash Muppirala wrote:
>>
>> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
>> d1b6c5d2/frameworks/projects/Express/src/main/flex/org/
>> apache/flex/express/List.as
>> ---
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> d1b6c5d2/frameworks/projects/Express/src/main/flex/org/
> apache/flex/express/List.as
> --
> diff --git
> a/frameworks/projects/Express/src/main/flex/org/apache/flex/exp
Hi Alex,
first of all I think we Need to distinguish between unit-tests and
functional-tests.
For Unit-Tests I think FlexUnit should be the way to go. Ideally runnable in
both SWF and JS. Here writing Tests in Flex(JS) is a good Thing.
For Functional-Tests, pure frontend Tests are usually only
flex-sdk_release-candidate - Build #196 - Successful
Changes since last build:
[Alex Harui] don't run jar checks on Windows
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/196/.
The goal of Mustella was to write tests in a declarative language, in this
case, MXML. That way, the test could be "interpreted" instead of just
run, so the test harness could have control over timing and some other
things that are really tricky in Flash like script timeouts and needing to
allow t
On 1/8/17, 10:25 PM, "Justin Mclean" wrote:
>Hi,
>
>> The subject line says RC1. IMO, we should be testing the CI build, not
>>RC1.
>
>As I stated I wasn’t testing RC1 I was testing the 4.16 release branch.
Actually, you stated you tested the 'develop' branch. My point here is
that, maybe, i
@Sanker,
I checked the same scenario with minor changes. You need to use bit more
code to achieve the binding in FlexjS. use following code to achieve correct
binding behavior,
[Bindable] privatevar anyClass:ClassA = new ClassA();
protected function onTextInputChangeA(event:Event):void
{
I think it pass experimentation state, Once you get a chance please merge it
to develop.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Runtime-error-when-setting-a-property-to-a-constan
On 1/9/17, 8:55 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>Yes, this is inline with what I expected. Is there an example of a
>dynamic bead in one of our examples or components?
I think org.apache.flex.html.DisableBead.as is a good example of a dynamic
bead. It might e
Happy New Year everyone.
I eventually figured out this issue. Our code was outputting thousands of
images in situations where most of those images were not going to be
displayed based on actionscript logic. I have since re-factored the code to
do most of this work dynamically and the performance i
On Jan 9, 2017 8:38 AM, "Alex Harui" wrote:
In the PAYG philosophy, there are beads that are essentially write-once
(or non-dynamic), and beads that are dynamic. In many smaller
applications, you set something and never change it. So why carry all of
the code around for things that aren't neede
On 1/8/17, 12:31 AM, "Harbs" wrote:
>Interesting. This is new to me as well.
>
>What’s interesting to me is that it seems like FlexJS should (mostly) not
>have this problem.
>
>If I’m reading it correctly, it’s reading geometric properties from the
>DOM which cause the reflow. Since the vast ma
On Jan 9, 2017 8:25 AM, "piotrz" wrote:
Santanau,
I will be looking into this issue [1] and I will try to test also your case
with BindableCSSStyles on fontawesome branch where my fixes is and let you
whether you need raise separate jira.
Btw.
Om do you plan soon merge fontawesome to develop ?
What does the click handler do? When a BindableCSSStyles property
changes, the watchedProperty should change. I'm thinking there is a
problem with the binding code still.
-Alex
On 1/9/17, 3:17 AM, "sankar" wrote:
>I noticed this method never fires inside BindableCSSStyles class. Is it
>suppos
In the PAYG philosophy, there are beads that are essentially write-once
(or non-dynamic), and beads that are dynamic. In many smaller
applications, you set something and never change it. So why carry all of
the code around for things that aren't needed.
For a write-once bead, it should hold its
Santanau,
I will be looking into this issue [1] and I will try to test also your case
with BindableCSSStyles on fontawesome branch where my fixes is and let you
whether you need raise separate jira.
Btw.
Om do you plan soon merge fontawesome to develop ?
[1] https://issues.apache.org/jira/bro
I was reading through this mailing thread. Recently I've created a post
http://apache-flex-development.247.n4.nabble.com/FlexJS-Does-BindableCSSStyles-requires-any-particular-way-of-implementation-td58040.html
against BindableCSSStyles class problem, and I noticed that
LayoutChangeNotifier's /w
I noticed this method never fires inside BindableCSSStyles class. Is it
supposed to be?
public function set watchedProperty(value:Object):void
{
if (_value !== value)
{
_value = value;
if (_strand is IBeadView)
IBeadView(_strand).
I noticed there were some differences between the MDL and the basic version
regarding events. One difference is the name: 'change', the other is that
'change' is thrown on MOUSE_UP but not on MOUSE_MOVE.
Are these differences by design?
--
View this message in context:
http://apache-flex-deve
I tried by a pretty basic code, the BindableCSSStyle, but it didn't worked in
my tests. Does it needs any particular way to implement?
Following is the source:
> http://ns.adobe.com/mxml/2009";
>xmlns:js="library://ns.apache.org/flexjs/basic">
>
>
>
>
On Mon, Jan 9, 2017 at 1:33 AM, piotrz wrote:
> Ahh! Yes! :)
>
> I'm wondering whether we are assigning everywhere values in setter and in
> strand additionally. Need to review all beads.
>
For what it's worth, I just tried it after your initial comment, but it is
near impossible to access the h
Ahh! Yes! :)
I'm wondering whether we are assigning everywhere values in setter and in
strand additionally. Need to review all beads.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-fl
I just saw this note from you a while ago :-)
http://apache-flex-development.247.n4.nabble.com/Re-git-commit-flex-asjs-refs-heads-develop-Add-ContactChip-bead-not-working-Throw-error-if-deletabled-td56969.html#a56971
Thanks,
Om
On Mon, Jan 9, 2017 at 12:45 AM, OmPrakash Muppirala
wrote:
>
Components do this, but the beads dont seem to be doing this.
For example, mdl.beads.Tooltip [1] does not follow this pattern. i.e. all
properties are set once in the set strand() method. And the setters simply
set the variable values. This is probably best for performance. But as
you said, if
You mean pattern with adding these line with element.classList.toggle ? We
were using it quite often [1] line 155.
And you are right in case of binding invalidation/validation would be nice.
[1]
https://git1-us-west.apache.org/repos/asf?p=flex-asjs.git;a=blob;f=frameworks/projects/MaterialDesign
On Mon, Jan 9, 2017 at 12:21 AM, Piotr Zarzycki
wrote:
> Hi Om,
>
> If I change "pulse" in Animation class using binding I think it won't
> change element.classList.toggle('fa-pulse',_pulse);. Maybe it would be
> good to have this line inside set ?
>
Yes, I was wondering about this. I dint see
Hi Om,
If I change "pulse" in Animation class using binding I think it won't
change element.classList.toggle('fa-pulse',_pulse);. Maybe it would be good
to have this line inside set ?
Thanks,
Piotr
2017-01-09 9:14 GMT+01:00 :
> Repository: flex-asjs
> Updated Branches:
> refs/heads/feature/fo
34 matches
Mail list logo
