WOW! Great news :) Looking forward to that. !
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-flex-asjs-git-commit-DisableBead-should-not-access-the-strand-until-it-s-added-tp62602p62606.html
Sent fr
I’m actually thinking of merging TLF back sometime over the next few weeks.
I’m at the point where TLF is working pretty well…
If there’s specific commits that someone wants before then, I’ll be happy to
help with cherry picking.
> On Jun 25, 2017, at 3:14 PM, piotrz wrote:
>
> Harbs,
>
> Yo
Harbs,
Your TLF branch will not be soon merged, can you more important fixes from
time to time make also to develop ?
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-flex-asjs-git-commit-Di
Sure.
The bug was that specifying the initial disabled value in MXML caused a runtime
error:
http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/99864a8c
>> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/99864a8c
>>
Hi,
I’m curious and certainly not a veto / asking you to revert this.
Is there any reason why this isn’t a BailoutDisableBead via PAYG concepts?
Thanks,
Justin
> On 25 Jun 2017, at 7:36 pm, ha...@apache.org wrote:
>
> Repository: flex-asjs
> Updated Branches:
> refs/heads/tlf 26b15e5a0 -> 9986
