I haven't tried StatesTest in a while. Can you work with DataBindingTest
instead? It should have everything StatesTest has and more.
-Alex
On 9/18/13 9:58 PM, "OmPrakash Muppirala" wrote:
>I picked this project up [1] after a while and when I run the app, I am
>getting this RTE:
>
>TypeError:
I picked this project up [1] after a while and when I run the app, I am
getting this RTE:
TypeError: Error #1009: Cannot access a property or method of a null object
reference.
at org.apache.flex.core::ViewBase/set
states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as\src\org\ap
On 9/18/13 4:43 PM, "OmPrakash Muppirala" wrote:
>On Sep 18, 2013 10:15 AM, "Alex Harui" wrote:
>>
>>
>>
>> On 9/18/13 10:09 AM, "OmPrakash Muppirala" wrote:
>> >
>> >Adding it as a source path instead, has an added advantage of being
>>able
>> >to
>> >make edits to the SDK and see it reflect
On Sep 18, 2013 10:15 AM, "Alex Harui" wrote:
>
>
>
> On 9/18/13 10:09 AM, "OmPrakash Muppirala" wrote:
> >
> >Adding it as a source path instead, has an added advantage of being able
> >to
> >make edits to the SDK and see it reflect in your app immediately.
> I actually use a separate Flex libra
Hi,
> Justin, please revert. I think it broke the build.
Sorry about that - reverted.
Justin
I didn't know there was a ticket already.
Thanks guys.
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mercredi 18 septembre 2013 22:03
À : dev@flex.apache.org
Objet : Re: MultiBitmapSource
Yes, but I think Justin opened one for you. I think it is:
htt
Yes, but I think Justin opened one for you. I think it is:
https://issues.apache.org/jira/browse/FLEX-33739
Please check and add yourself to the watch and vote.
-Alex
On 9/18/13 12:48 PM, "Maurice Amsellem"
wrote:
>Is raising a JIRA directly the right approach to proposing new features
>or b
On Sep 18, 2013 12:49 PM, "Maurice Amsellem"
wrote:
>
> Is raising a JIRA directly the right approach to proposing new features
or behavior change (such as the one below)?
>
Raising the ticket should be sufficient for most cases. If the expected
behavior is not very clear, you can start a discus
Is raising a JIRA directly the right approach to proposing new features or
behavior change (such as the one below)?
Thanks
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mardi 17 septembre 2013 20:26
À : dev@flex.apache.org
Objet : Mul
Hi Folks,
In response to your board report for September 2013, I had some
suggestions for dealing with the problem of getting less and less
VOTEs per RC you roll.
One thing you may want to do is suggest is for the RM to ask the PMC if
their
VOTEs may be "carried through", especially in the case
Added a FlexUnit component.
On 9/18/13 11:55 AM, "labri...@digitalprimates.net"
wrote:
>>Maybe an additional JIRA Component named FlexUnit would be helpful.
>
>I think that's the right idea. Else you are immediately tying things to a
>version and that's not the point of reporting a bug
>Maybe an additional JIRA Component named FlexUnit would be helpful.
I think that's the right idea. Else you are immediately tying things to a
version and that's not the point of reporting a bug
There is a JIRA version "Apache FlexUnit 4.2".
Maybe an additional JIRA Component named FlexUnit would be helpful.
Cyrill
On 18.09.2013, at 19:46, "Michael A. Labriola"
wrote:
>
> How should we specify bugs for things like FlexUnit when entering them in
> JIRA to keep things a bit separate.
How should we specify bugs for things like FlexUnit when entering them in JIRA
to keep things a bit separate.
Maybe there is something obvious I missed... if not, ideas?
Mike
On Sep 18, 2013 9:38 AM, "Alex Harui" wrote:
>
> Thanks for writing that up, but I think it should be simpler than that.
> Something like:
>
> 1. Follow the steps here [1] to set up FlexJS SDK and your FlexJS app
> 2. Select Project > Properties > Flex Build Path > Library Path
> 3. Expand the F
Your under the assumption he sleeps. He's really a machine :)
-Original Message-
It's 3 AM in Sydney, he should be up soon :-)
EdB
smime.p7s
Description: S/MIME cryptographic signature
Happy you finally got it working :-)
> It's not very clear if the input of the mavenizer is an IDE SDK, or a plain
> binary kit.
It waits for an IDE ready SDK, so, the steps 3 to 5 bellow are wrong IMO, you
should had 5, then 4 as IIRC, the ide script bring the FP version set in you
property f
On 9/18/13 10:09 AM, "OmPrakash Muppirala" wrote:
>
>Adding it as a source path instead, has an added advantage of being able
>to
>make edits to the SDK and see it reflect in your app immediately.
I actually use a separate Flex library project for FlexJSUI.swc and link
that project.
>>In theor
I think we should leave this for Justin. You break it, you buy it.
It's 3 AM in Sydney, he should be up soon :-)
EdB
On Wed, Sep 18, 2013 at 6:42 PM, Alex Harui wrote:
> I think it is nighttime for Justin. Should we wait for him to revert?
> I'd do the revert myself, but I have other pushabl
On 9/18/13 9:58 AM, "Kessler CTR Mark J" wrote:
>Your under the assumption he sleeps. He's really a machine :)
True, maybe he doesn't. It's been amazing to see him crank through the
bugs, but he is usually silent on the mailing list until 4pm my time.
Maybe he isn't sleeping and just refueli
It's not very clear if the input of the mavenizer is an IDE SDK, or a plain
binary kit.
Until now I was trying with the IDE SDK (since I wasn't producing a binary
kit from sources), this may be the main cause of my problems: I think that
the mavenizer got confused by the extra SWCs files put in th
I think it is nighttime for Justin. Should we wait for him to revert?
I'd do the revert myself, but I have other pushable commits pending and
nervous about following the steps to try to push just a revert.
-Alex
On 9/18/13 8:49 AM, "Erik de Bruin" wrote:
>Wow, that broke so hard, Google decide
Thanks for writing that up, but I think it should be simpler than that.
Something like:
1. Follow the steps here [1] to set up FlexJS SDK and your FlexJS app
2. Select Project > Properties > Flex Build Path > Library Path
3. Expand the FlexJS SDK
4. Expand the FlexJSUI.SWC
5. Set source attachme
Oops, my mistake. It works just fine. Issue resolved.
Thank you, guys!!!
On Sep 18, 2013 10:23 AM, "Oleg Konovalov" wrote:
> I still get the same exception from the same line if I do that.
> Any other ideas?
> On Sep 17, 2013 10:50 PM, "Justin Mclean"
> wrote:
>
>> Hi,
>>
>> > validator.source =
If you use a filter in GMail... there is a check box in the filter that says do
not mark as spam. My gmail used to mark some of your emails as spam Erik :P
-Mark
-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl]
Sent: Wednesday, September 18, 2013 11:50 AM
To: dev@flex
Wow, that broke so hard, Google decided the notification were spam.
They got filtered out, so I didn't notice anything until Alex emailed.
Sorry about that.
I have paused the builds until the commit is reverted.
EdB
On Wed, Sep 18, 2013 at 4:07 PM, Alex Harui wrote:
> Justin, please revert. I
I still get the same exception from the same line if I do that.
Any other ideas?
On Sep 17, 2013 10:50 PM, "Justin Mclean" wrote:
> Hi,
>
> > validator.source = "{field}"; <<< Error: source attribute "{field}"
> can
> > not be of Type String [from mx.validators::Validator/set]
>
> validator.s
Justin, please revert. I think it broke the build.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
jmcl...@apache.org wrote:
Updated Branches:
refs/heads/develop d2768bef3 -> 18ce3aa9f
FLEX-33740 made removedFromStageHandler protected so it could be overridden
Project: http:/
Hi Guys :)
Does it works for you mscharp ? ->
"
${flex.groupId}
framework
${flex.sdk.version}
pom
I guess, what I would do more or less is:
update-index --assume-unchanged flex-sdk-description.xml
run the ant targets you mentioned or even a release
change the build number in the flex-sdk-description.xml to 0
run the sdk/ide batch I need
run the Maven converter (because you set the build number
>
>
> > running checkin tests (and I think that my mustella is not set up
> properly, never tried running it yet),
> Running the checkin tests is separate from running mustella.
Thank for the tip, I'll try to run it later to see what happens (but I have
no modified sources currently).
p.s. the
Hi,
> running checkin tests (and I think that my mustella is not set up properly,
> never tried running it yet),
Running the checkin tests is separate from running mustella.
Justin
@Justin
Thank you for the README change.
@Frederic
Don't know, it looks like that the "binary-release noclean" would also do
unnecessary tasks such as creating docs, running checkin tests (and I think
that my mustella is not set up properly, never tried running it yet),
packaging binary files, ecc
[1] describes how to set up Flash Builder to work with the FlexJS SDK. It
is not very clear how to use Flash Builder to debug your FlexJS apps.
In case someone wants to debug FlexJS apps using FlashBuilder, here are the
steps:
1. Follow the steps here [1] to set up FlexJS SDK and your FlexJS ap
34 matches
Mail list logo
