This cropped up after builds@a.o came back online and needs attention:
BUILD FAILED
f:\hudson\hudson-slave\workspace\flex-sdk_release\build.xml:631: error
running fixcrlf on file
f:\hudson\hudson-slave\workspace\flex-sdk_release\temp\LICENSE
Any ideas?
EdB
On Wed, Jul 17, 2013 at 7:36 AM, Apa
Hi,
Think this was something you added the other week Alex? Any idea why this is
occurring?
swc-compile:
[echo] Compiling frameworks/libs/spark.swc
[compc] Loading configuration file
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/spark/compile-config.xml
[co
Forgot to put the view source link out for the example app [1]
[1] http://people.apache.org/~mkessler/examples/FLEX-33608/app.mxml.txt
On Tue, Jul 16, 2013 at 9:22 PM, Justin Mclean wrote:
> Hi,
>
> > I started using more getItemAt because not everything allows the
> brackets anymore.
> Only i
On Jul 16, 2013 5:14 PM, "Alex Harui" wrote:
>
>
>
> On 7/16/13 4:51 PM, "Carlos Rovira" wrote:
>
> >That would be right if huge applications where created in a consistent
and
> >homogeneous way during all "development life". If the app is tiny there's
> >more opportunities that experienced progr
Hi,
> I started using more getItemAt because not everything allows the brackets
> anymore.
Only in binding expressions I thought?
> Not sure how much of a speed difference there is.
Not sure, I'd getItemAt is probably faster but may be so little in it that it's
not really a concern.
Thanks,
J
Changing the flexsprite wasn't going to get everything. It was just low
hanging fruit for a test/example since it allowed me a wide range of
components to test with. If I could have changed the EventDispatcher it
would have been a better :P
I like the looping backwards idea for removing items...
Hi,
> https://github.com/KesslerConsulting/example/commit/30ee4b96911d301ea09516324241c4bc9d734f16
Very quick glance, but I think that removing items from a list when you're
looping to the number of original items in the list can get you into trouble.
for (nLoopingIndex = 0; nLoopingIndex < nLi
Hi,
> It would be better to just put a ticket into Adobe to have some methods /
> array's exposed (if they allow it).
It's been asked before (many times) but they decided for whatever reasons not
to implement it. Was one of the most requested features in Adobe's old bug base.
Does you code detec
Now with links... lol
[1] http://people.apache.org/~mkessler/examples/FLEX-33608/app.swf
[2]
https://github.com/KesslerConsulting/example/commit/30ee4b96911d301ea09516324241c4bc9d734f16
On Tue, Jul 16, 2013 at 8:16 PM, Mark Kessler
wrote:
> Well I had some old code laying around that did exact
Well I had some old code laying around that did exactly this. I've
stripped it out and created an example with it [1]. It overrides the
EventDispatcher methods. I do not plan on checking it into the sdk,
because it has to be duplicating the EventDispatcher's internal arrays. It
would be better
On 7/16/13 4:51 PM, "Carlos Rovira" wrote:
>That would be right if huge applications where created in a consistent and
>homogeneous way during all "development life". If the app is tiny there's
>more opportunities that experienced programers make a good work and code
>in
>the overall.
>
>When t
On 7/16/13 4:29 PM, "OmPrakash Muppirala" wrote:
>> About folks rewriting code...well, I certainly does not see people
>> migrating old applications from Flex 4.x to FlexJS, Since there will be
>> huge diferences that will make the task utopic. I expect flex developers
>> start working in FlexJ
That would be right if huge applications where created in a consistent and
homogeneous way during all "development life". If the app is tiny there's
more opportunities that experienced programers make a good work and code in
the overall.
When the app, the team, the code grows over years, more diff
> About folks rewriting code...well, I certainly does not see people
> migrating old applications from Flex 4.x to FlexJS, Since there will be
> huge diferences that will make the task utopic. I expect flex developers
> start working in FlexJS right from the first day for new projects due to
> lots
Ah, crap. My bad. I'm out of practice.
On 7/16/13 3:38 PM, "Justin Mclean" wrote:
>Hi,
>
>Please don't make changes in the develop branch that are needed for the
>release branch, especially when that file has already changed, merging is
>painful enough as it is.
>
>Justin
Hi Alex,
Migration is still an important factor, but backward compatibility isn't
> being guaranteed. What that means to me is that I'm not promising that
> every API in current Flex will be there in FlexJS, and we are going to try
> to find the best API for the future, but if given a choice of
Hi,
> I am making a bit of a change to the Installer (adding ability to switch
> Flex versions interactively). I will be ready to push it out in a few
> hours. Lets make a new build together after that.
Fine by me.
Justin
Justin,
I am making a bit of a change to the Installer (adding ability to switch
Flex versions interactively). I will be ready to push it out in a few
hours. Lets make a new build together after that.
Thanks,
Om
On Tue, Jul 16, 2013 at 3:56 PM, Justin Mclean wrote:
> Hi,
>
> I've stuck a OSX
Hi,
I've stuck a OSX compiled installer to help test out the 4.10 release here:
https://dist.apache.org/repos/dist/dev/flex/installer/2.6/rc1/binaries/
It uses the config file from here (which points at the Apache Flex 4.10.0 RC1
release)
http://flex.apache.org/installer/sdk-installer-config-3.
Hi,
Please don't make changes in the develop branch that are needed for the release
branch, especially when that file has already changed, merging is painful
enough as it is.
Justin
Hi,
>> 11.1 and 3.7 (legacy support)
>> 11.7 and 3.7 (long term support)
>> 11.8 and 3.8 (bleeding edge)
> Did you mean 11.1 and 3.1?
I'd keep it at 11.1 and 3.7 as that's a more likely combo, ie legacy FP support
but recent stable AIR version.
Justin
On Tue, Jul 16, 2013 at 11:14 AM, Paul Hastings wrote:
> On 7/16/2013 9:33 PM, OmPrakash Muppirala wrote:
>
>> I plan to put out an RC for the Installer soon.
>>
>
> i hate to say it but for someone like me having an installer to setup the
> SDK for testing would make it much easier. worked myself
Hi,
> I get that. I was wondering if having a regular build off the release
> branch would be a help during the RC period?
No need to we merge changes into develop which I think is simpler.
Justin
>>
>> The long answer: I was looking at how addToParent() is currently
>> implemented and found that I couldn't completely remember why I felt it
>> was a better strategy.
>
>I remember a conversation about trying to move away from the traditional
>display list approach so that we are not overly
On Jul 16, 2013 9:34 AM, "Alex Harui" wrote:
>
>
>
> >>
> >> Removed initModel and initSkin methods. The lifecycle is now much
> >simpler: instantiate, set properties and beads then add to the display
> >list. We're still using child.addToParent(parent), but I am going to
> >experiment next wit
On 7/16/13 1:57 PM, "flexcapaci...@gmail.com"
wrote:
>>A) wrapping addChild messed up a lot of low-level tools like display list
>> tree walkers used in Spy-like programs. I'm leaning against wrapping
>> addChild again.
>>
>
>What happened?
To walk the entire display list, you have to anticipa
Hi Carlos,
On 7/16/13 12:49 PM, "Carlos Rovira" wrote:
>Hi Alex,
>
>The short answer: to reduce migration pain. My internal customer showed
>> me a bunch of code with a lot of addElement() calls in it.
>>
>>
>I thought migration was not considered in FlexJS. IMHO, I think that
>should
>not be c
On Tue, Jul 16, 2013 at 11:33 AM, Alex Harui wrote:
>
>
> >>
> >> Removed initModel and initSkin methods. The lifecycle is now much
> >simpler: instantiate, set properties and beads then add to the display
> >list. We're still using child.addToParent(parent), but I am going to
> >experiment ne
Hi Alex,
The short answer: to reduce migration pain. My internal customer showed
> me a bunch of code with a lot of addElement() calls in it.
>
>
I thought migration was not considered in FlexJS. IMHO, I think that should
not be considered in the discussion of add to child vs add to parent.
>
On 7/16/2013 9:33 PM, OmPrakash Muppirala wrote:
I plan to put out an RC for the Installer soon.
i hate to say it but for someone like me having an installer to setup the SDK
for testing would make it much easier. worked myself into a tizzy trying to get
my dev environment squared away (JDK v
Thanks Fred, I have FDK in my local Nexus server, however I feel that this
process cost a lot of time, and it needs a lot of skills too, Flex users
really don't need to know it. -Gary
On Tue, Jul 16, 2013 at 1:01 PM, Frédéric THOMAS wrote:
> Do you think it's possible to add a feature to the SDK
No, I didn't mean that, but that makes sense.
EdB
On Tue, Jul 16, 2013 at 7:52 PM, OmPrakash Muppirala
wrote:
> On Tue, Jul 16, 2013 at 10:49 AM, Erik de Bruin wrote:
>
>> I'll set up the VM to cycle through the following 3 runs:
>>
>> 11.1 and 3.7 (legacy support)
>> 11.7 and 3.7 (long term
On Tue, Jul 16, 2013 at 10:49 AM, Erik de Bruin wrote:
> I'll set up the VM to cycle through the following 3 runs:
>
> 11.1 and 3.7 (legacy support)
> 11.7 and 3.7 (long term support)
> 11.8 and 3.8 (bleeding edge)
>
> Does that sound about right?
>
> EdB
>
>
Did you mean 11.1 and 3.1?
Om
>
>
I'll set up the VM to cycle through the following 3 runs:
11.1 and 3.7 (legacy support)
11.7 and 3.7 (long term support)
11.8 and 3.8 (bleeding edge)
Does that sound about right?
EdB
On Tue, Jul 16, 2013 at 7:30 PM, OmPrakash Muppirala
wrote:
> On Tue, Jul 16, 2013 at 9:35 AM, Alex Harui w
On Tue, Jul 16, 2013 at 9:35 AM, Alex Harui wrote:
> Interesting. The reports of "many" failures came from Mac users. Maybe
> Windows has been more stable.
>
> I'll try to set up local runs on both Mac and Win tonight. Do we want to
> use 11.7 or 11.8?
>
>
Lets try to do 11.8/3.8 for this rele
On Tue, Jul 16, 2013 at 10:01 AM, Frédéric THOMAS
wrote:
> Do you think it's possible to add a feature to the SDK Installer so that
>> it
>> can also deploy FDK into Sonatype Nexus server?
>>
>
> In order to do that, that's what is needed to be done on the Installer as
> I see it:
>
> - Check the
Do you think it's possible to add a feature to the SDK Installer so that
it
can also deploy FDK into Sonatype Nexus server?
In order to do that, that's what is needed to be done on the Installer as I
see it:
- Check the machine on which the SDK will be installed has Java and Maven
installed
Interesting. The reports of "many" failures came from Mac users. Maybe
Windows has been more stable.
I'll try to set up local runs on both Mac and Win tonight. Do we want to
use 11.7 or 11.8?
On 7/16/13 9:06 AM, "Erik de Bruin" wrote:
>Hi,
>
>As the title suggests, it looks like the 'jump'
>>
>> Removed initModel and initSkin methods. The lifecycle is now much
>simpler: instantiate, set properties and beads then add to the display
>list. We're still using child.addToParent(parent), but I am going to
>experiment next with changing over to parent.addElement(child).
>
>Any particul
Hi,
As the title suggests, it looks like the 'jump' to 11.7 doesn't cause
as much havoc as we expected :-)
These are the tests that failed:
gumbo/components/Image/styles/Image_styles_smoothingQuality
Image_Scale_stretch_smoothingQuality_high Failed
CompareBitmap(body:step 6) compare returned[ob
I get that. I was wondering if having a regular build off the release
branch would be a help during the RC period?
EdB
On Tue, Jul 16, 2013 at 5:28 PM, Nicholas Kwiatkowski wrote:
> Once 4.10 is out, wouldn't that branch be merged into the master and pretty
> much be out of commission? I'd im
Once 4.10 is out, wouldn't that branch be merged into the master and pretty
much be out of commission? I'd imagine that develop is where we want our
nightlys to come from anyway.
On Tue, Jul 16, 2013 at 11:11 AM, Erik de Bruin wrote:
> Mind that the build machine is offline, so the latest 'nig
Mind that the build machine is offline, so the latest 'nightly' is of
about 4 days ago and is from the 'develop' branch.
Does it make sense that when (if?) the build machine comes back online
I create an RC job that builds from the 'release4.10.0' branch -
nightly and/or when a commit happens?
Ed
On Jul 16, 2013 6:48 AM, "Alexander Doroshko" <
alexander.doros...@jetbrains.com> wrote:
>
> On 16.07.2013 17:27, Nicholas Kwiatkowski wrote:
>>
>> - IntelliJ is giving me an invalid namespace error for this build
>> (binaries). I'm trying to track that down to see what is causing it.
>
> I can
Pretty please?
EdB
On Mon, Jul 15, 2013 at 5:59 PM, Erik de Bruin wrote:
> Hi,
>
> The 'windows1' slave seems to be offline. We (Apache Flex) are nearing
> a release, so if you could expedite a solution, that would be awesome!
>
> Thanks,
>
> Erik de Bruin
>
>
>
> --
> Ix Multimedia Software
>
On 16.07.2013 17:27, Nicholas Kwiatkowski wrote:
- IntelliJ is giving me an invalid namespace error for this build
(binaries). I'm trying to track that down to see what is causing it.
I can take a look. Where can I get Installer for Flex SDK 4.10 release
candidate?
Do you think it's possible to add a feature to the SDK Installer so that it
can also deploy FDK into Sonatype Nexus server? Thanks. -Gary
On Tue, Jul 16, 2013 at 9:27 AM, Nicholas Kwiatkowski wrote:
> Justin,
>
> On Win7, x64, JDK 1.7
>
> Things you already know :
> - RAT runs fine
> - checkin
Hi,
> - IDE scripts are missing (I see you just committed those to the repo)
Yep fixed.
> - IDE scripts in the repo are not pointing to the correct URL for the AIR SDK
Adobe is taking its time in getting out AIR 3.8, it's normally released the
same time as Flash Player, 11.8 was released a week
Justin,
On Win7, x64, JDK 1.7
Things you already know :
- RAT runs fine
- checkin tests run fine
- Mustella runs fine
My tests :
- My mobile apps compile and test fine.
- A few spot-checks of previously known bugs are now corrected
- Desktop apps compile fine.
Failures :
- IDE scripts ar
Hi,
> I tried the utilities, it can not find playerglobal.swc, I guess it has the
> license problems too
Post the issue you encountered in detail in another thread and I'm sure someone
from the list can help.
> Is it possible to get around it or to make it easier?
I believe so but as I said I d
I tried the utilities, it can not find playerglobal.swc, I guess it has the
license problems too,
I would have to say this is the worst hit for Flex popularity, Is it
possible to get around it or to make it easier?
Thanks.
-Gary
On Tue, Jul 16, 2013 at 3:26 AM, Justin Mclean wrote:
> Hi,
>
>
On Jul 16, 2013 1:05 AM, "Alex Harui" wrote:
>
> OK, pushed a bunch of changes to hopefully make it more easy/clear when
creating components.
>
> I added IBeadView, IBeadController and IBeadLayout interfaces to go along
with the already existing IBeadModel. The CSS makes it more clear now as
to w
OK, pushed a bunch of changes to hopefully make it more easy/clear when
creating components.
I added IBeadView, IBeadController and IBeadLayout interfaces to go along with
the already existing IBeadModel. The CSS makes it more clear now as to what
parts make up the component.
I renamed view b
Hi,
> Is Apache Flex deployed in any maven repository? is there a sample POM
> using it?
The short answer is no, it's not in a publicly assessable repository due to
3rd party license restrictions.
However you can use the mavenizer tool to use it inhouse. For more info about
that read at the b
54 matches
Mail list logo
