Re: Apache Flex 4.10.0 release

2013-08-06 Thread Peter Ginneberge

FYI.
I haven't been following the release discussion closely, but just wanted to let 
you all know that AIR 3.8 is currently broken:

https://bugbase.adobe.com/index.cfm?event=bug&id=3603433
http://forums.adobe.com/message/5569366#5569366

Now I understand this doesn't affect the Flex SDK, however if the Flex installer installs AIR 3.8, I don't know if that's a good 
idea.


regards,
Peter



Re: Apache Flex 4.10.0 release

2013-08-06 Thread Nicholas Kwiatkowski
We can't.  you can only feed buildbot the svn commit number.  When we push
the full site, we can test it then.  Once the full site is been pushed, we
can make smaller changes that should go in near-realtime.


On Tue, Aug 6, 2013 at 9:03 AM, Justin Mclean wrote:

> Hi,
>
> With the CMS how you selectively publish a single file? I's like to
> publish the installer 3.0 config file to see if the changes I made work.
>
> Thanks,
> Justin


Re: Apache Flex 4.10.0 release

2013-08-06 Thread Justin Mclean
Hi,

With the CMS how you selectively publish a single file? I's like to publish the 
installer 3.0 config file to see if the changes I made work.

Thanks,
Justin

Re: Apache Flex 4.10.0 release

2013-08-06 Thread Justin Mclean
Hi,

> It's 5.30am here in the bay area.  I am still going in and out of sleep :-)
I'll give it a go - if you could double check it in a couple of hours that 
would be a great help.

It's almost 7am here, site goes live at 10am.

Justin

Re: Apache Flex 4.10.0 release

2013-08-06 Thread Nicholas Kwiatkowski
Om,

If you can take care of it sometime between 8am and 9am Pacific, that would
rock.  Statistically, we should have a great majority of the DISTs
populated with this release by then. I'll start running the update to the
website around 8:30 pacific (it will take about 30 minutes because it has
to recompile the template AND copy over the new asdocs).

-Nick


On Tue, Aug 6, 2013 at 8:46 AM, OmPrakash Muppirala wrote:

> It's 5.30am here in the bay area.  I am still going in and out of sleep :-)
>
> When exactly did you want me to make the updates to the config files?
>
> Thanks,
> Om
> On Aug 6, 2013 5:43 AM, "Justin Mclean"  wrote:
>
> > Hi,
> >
> > > Has the installer config 3.0 been updated to point to the actual
> released
> > > sdk urls?
> > >
> > > Also, config 2.0 needs to have the version and url of installer updated
> > so
> > > that auto update kicks in.
> >
> > No I don't believe so. Any chance you could do this as your more familiar
> > with how that works, correct locations of files etc etc?
> >
> > > Please take a few minutes to download the installer and run it through
> to
> > > the end before making the announcement.
> >
> > I'll do that (on OSX) and check the links before we go live, but if
> > someone else could double check as well that would be a help.
> >
> > Justin
>


Re: Apache Flex 4.10.0 release

2013-08-06 Thread OmPrakash Muppirala
It's 5.30am here in the bay area.  I am still going in and out of sleep :-)

When exactly did you want me to make the updates to the config files?

Thanks,
Om
On Aug 6, 2013 5:43 AM, "Justin Mclean"  wrote:

> Hi,
>
> > Has the installer config 3.0 been updated to point to the actual released
> > sdk urls?
> >
> > Also, config 2.0 needs to have the version and url of installer updated
> so
> > that auto update kicks in.
>
> No I don't believe so. Any chance you could do this as your more familiar
> with how that works, correct locations of files etc etc?
>
> > Please take a few minutes to download the installer and run it through to
> > the end before making the announcement.
>
> I'll do that (on OSX) and check the links before we go live, but if
> someone else could double check as well that would be a help.
>
> Justin


Re: Apache Flex 4.10.0 release

2013-08-06 Thread Justin Mclean
Hi,

> Has the installer config 3.0 been updated to point to the actual released
> sdk urls?
> 
> Also, config 2.0 needs to have the version and url of installer updated so
> that auto update kicks in.

No I don't believe so. Any chance you could do this as your more familiar with 
how that works, correct locations of files etc etc?

> Please take a few minutes to download the installer and run it through to
> the end before making the announcement.

I'll do that (on OSX) and check the links before we go live, but if someone 
else could double check as well that would be a help.

Justin

Re: Apache Flex 4.10.0 release

2013-08-06 Thread OmPrakash Muppirala
Has the installer config 3.0 been updated to point to the actual released
sdk urls?

Also, config 2.0 needs to have the version and url of installer updated so
that auto update kicks in.

Please take a few minutes to download the installer and run it through to
the end before making the announcement.

Thanks,
Om
On Aug 6, 2013 4:47 AM, "Nicholas Kwiatkowski"  wrote:

> Sounds good.  I'll re-adjust everything for noon EDT, 10AM Mountain (your
> local time).  The website will go live about 5 minutes before the blog
> post.
>
> -Nick
>
>
> On Tue, Aug 6, 2013 at 7:32 AM, Justin Mclean  >wrote:
>
> > Hi,
> >
> > > What time works best?
> > Midday works fro me, should generate a bit more buzz on twitter etc as
> > well. That way we can also fix any issues, respond to any tweets/blog
> > comments etc etc promptly as opposed if we released at midnight.
> >
> > > I hesitate to much earlier than noon... I'm still seeing about 1/4 of
> the
> > > dist sites missing files at 7am EDT.
> >
> > Should be good by then - look at the age histogram at the bottom of the
> > page here..
> > http://www.apache.org/mirrors/
> >
> > Thanks,
> > Justin
>


Re: Apache Flex 4.10.0 release

2013-08-06 Thread Nicholas Kwiatkowski
Sounds good.  I'll re-adjust everything for noon EDT, 10AM Mountain (your
local time).  The website will go live about 5 minutes before the blog post.

-Nick


On Tue, Aug 6, 2013 at 7:32 AM, Justin Mclean wrote:

> Hi,
>
> > What time works best?
> Midday works fro me, should generate a bit more buzz on twitter etc as
> well. That way we can also fix any issues, respond to any tweets/blog
> comments etc etc promptly as opposed if we released at midnight.
>
> > I hesitate to much earlier than noon... I'm still seeing about 1/4 of the
> > dist sites missing files at 7am EDT.
>
> Should be good by then - look at the age histogram at the bottom of the
> page here..
> http://www.apache.org/mirrors/
>
> Thanks,
> Justin


Re: Apache Flex 4.10.0 release

2013-08-06 Thread Justin Mclean
Hi,

> What time works best?
Midday works fro me, should generate a bit more buzz on twitter etc as well. 
That way we can also fix any issues, respond to any tweets/blog comments etc 
etc promptly as opposed if we released at midnight.

> I hesitate to much earlier than noon... I'm still seeing about 1/4 of the
> dist sites missing files at 7am EDT.

Should be good by then - look at the age histogram at the bottom of the page 
here..
http://www.apache.org/mirrors/

Thanks,
Justin

Re: Apache Flex 4.10.0 release

2013-08-06 Thread Nicholas Kwiatkowski
What time works best?  I have no issues coordinating it for John -- it's
been a while since he's been able to announce a Flex release at his show.
 I hesitate to much earlier than noon... I'm still seeing about 1/4 of the
dist sites missing files at 7am EDT.

-Nick


On Tue, Aug 6, 2013 at 1:13 AM, Justin Mclean wrote:

> Hi,
>
> > I've armed the blog and website to go live tomorrow night (8/7/2013) at
> > midnight EDT.  Unless I hear otherwise, things should be ready to go :)
>
> Any chance you could make it midday? I was going to get John to make an
> announcement about the release tomorrow morning at 360 stack.
>
> The web site changes can't go live until the blog post is up.
>
> Thanks,
> Justin


Re: Apache Flex 4.10.0 release

2013-08-05 Thread Justin Mclean
Hi,

> I've armed the blog and website to go live tomorrow night (8/7/2013) at
> midnight EDT.  Unless I hear otherwise, things should be ready to go :)

Any chance you could make it midday? I was going to get John to make an 
announcement about the release tomorrow morning at 360 stack.

The web site changes can't go live until the blog post is up.

Thanks,
Justin

Re: Apache Flex 4.10.0 release

2013-08-05 Thread Nicholas Kwiatkowski
I've armed the blog and website to go live tomorrow night (8/7/2013) at
midnight EDT.  Unless I hear otherwise, things should be ready to go :)

Thanks for all the hard work team!

-Nick


On Mon, Aug 5, 2013 at 1:45 PM, Justin Mclean wrote:

> Hi,
>
> The 4.10 release has just been committed to SVN, once 24 hours have passed
> I send out the official email announcement.
>
> Do we want two announcements one for the installer and one for the SDK or
> do we just have have a combined one?
>
> Other than the installer config needing to be updated to point to the new
> release, and the new builds put up on the web site is there anything else
> we need to do?
>
> Thanks,
> Justin


Re: Apache Flex 4.10.0 release

2013-08-05 Thread OmPrakash Muppirala
On Mon, Aug 5, 2013 at 11:00 AM, aYo ~  wrote:

> One combined should suffice I believe.
>

Agreed.

Update: Installer badge now supports sdk-installer-config-3.0.xml and hence
Apache Flex 4.10.0.

I will upload the new installerBadge.swf file to this page once we are
ready to go live.

Thanks,
Om

[1] http://flex.apache.org/installer.html


>
> aYo
> www.ayobinitie.com
> mrbinitie.blogspot.com
> On 5 Aug 2013 18:46, "Justin Mclean"  wrote:
>
> > Hi,
> >
> > The 4.10 release has just been committed to SVN, once 24 hours have
> passed
> > I send out the official email announcement.
> >
> > Do we want two announcements one for the installer and one for the SDK or
> > do we just have have a combined one?
> >
> > Other than the installer config needing to be updated to point to the new
> > release, and the new builds put up on the web site is there anything else
> > we need to do?
> >
> > Thanks,
> > Justin
>


Re: Apache Flex 4.10.0 release

2013-08-05 Thread aYo ~
One combined should suffice I believe.

aYo
www.ayobinitie.com
mrbinitie.blogspot.com
On 5 Aug 2013 18:46, "Justin Mclean"  wrote:

> Hi,
>
> The 4.10 release has just been committed to SVN, once 24 hours have passed
> I send out the official email announcement.
>
> Do we want two announcements one for the installer and one for the SDK or
> do we just have have a combined one?
>
> Other than the installer config needing to be updated to point to the new
> release, and the new builds put up on the web site is there anything else
> we need to do?
>
> Thanks,
> Justin


Re: Apache Flex 4.10.0 release

2013-08-05 Thread OmPrakash Muppirala
On Mon, Aug 5, 2013 at 10:45 AM, Justin Mclean wrote:

> Hi,
>
> The 4.10 release has just been committed to SVN, once 24 hours have passed
> I send out the official email announcement.
>
> Do we want two announcements one for the installer and one for the SDK or
> do we just have have a combined one?
>

Lets do it in both.  Can we just use the PR statement that Scott had
prepared for the announcements and blog posts?  That has all the relevant
information.


>
> Other than the installer config needing to be updated to point to the new
> release, and the new builds put up on the web site is there anything else
> we need to do?
>
>
Copy pasting from the other thread I just started:

*Here is what needs to be done:*
1.  Upload SDK artifacts to release site


Apache Flex 4.10.0 release

2013-08-05 Thread Justin Mclean
Hi,

The 4.10 release has just been committed to SVN, once 24 hours have passed I 
send out the official email announcement. 

Do we want two announcements one for the installer and one for the SDK or do we 
just have have a combined one?

Other than the installer config needing to be updated to point to the new 
release, and the new builds put up on the web site is there anything else we 
need to do?

Thanks,
Justin

Re: [RESULT] [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-04 Thread Erik de Bruin
Thank you, Justin, for your patience and perseverance!

EdB



On Sun, Aug 4, 2013 at 4:24 PM, Justin Mclean  wrote:
> Hi,
>
> Binding votes:
> +1 Erik de Bruin
> +1 Alex Harui
> +1 Justin Mclean
>
> Non binding votes:
> +1 Swen van Zanten
> +1 Mark Kessler
> +1 aYo
> +1 Carlos Rovira
>
> There were no +0 or -1 votes and a total of 7 +1 votes, 3 of which were 
> binding.
>
> So this will in now official 4.10 Apache Flex release!
>
> Thanks to everyone who tried out the release candidates and to those who 
> voted.
>
> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


[RESULT] [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-04 Thread Justin Mclean
Hi,

Binding votes:
+1 Erik de Bruin
+1 Alex Harui
+1 Justin Mclean

Non binding votes:
+1 Swen van Zanten
+1 Mark Kessler
+1 aYo
+1 Carlos Rovira

There were no +0 or -1 votes and a total of 7 +1 votes, 3 of which were binding.

So this will in now official 4.10 Apache Flex release!

Thanks to everyone who tried out the release candidates and to those who voted.

Justin

Re: [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-03 Thread Justin Mclean
Hi,

+1 (binding)

- Tested on OSX 10.7.5
- MD5 and signed package OK
- readme, release_notes, notice, license etc all fine
- Can compile from source package
- SDK can be used in Flash Builder (with know issue noted in release notes)
- Could use SDK in mobile, desktop and browser application

Thanks,
Justin


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-03 Thread Justin Mclean
Hi,

The 72 hours are almost up (12 or so hours to go), I'd like to see a few more 
+1 votes from the PMC in there.

Thanks,
Justin

Re: [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-03 Thread Carlos Rovira
+1 (not binding)

Mac OSX 10.8.4
Flex SDK 4.10
FP 11.1
IntelliJ 13 (Cardea EAP 130.1486)



2013/8/3 

> Will test on Linux Mint FDT5 later today
>
>
>
> aYo
> www.ayobinitie.com
> mrbinitie.blogspot.com
>
>
>
> From: Alex Harui
> Sent: Friday, 2 August 2013 18:25
> To: dev@flex.apache.org
>
> +1
> Src kit build passed.
> Signature match on src tar and zip kit
> Rat passed on src zip kit
> Mustella passed on Mac with 11.1 and Win7 with 11.7
> Notice files look fine
>
> Thanks Justin!
> -Alex
>
> On 8/1/13 3:57 PM, "Mark Kessler"  wrote:
>
> >+1
> >
> >OS: Win7 64bit
> >Flex SDK: 4.10
> >FP: 11.8
> >
> >Successfully built SDK.
> >Used SDK to built simple apps successfully.
> >
> >
> >-Mark
> >
> >
> >
> >On Thu, Aug 1, 2013 at 6:27 AM, Justin Mclean
> >wrote:
> >
> >> Hi,
> >>
> >> This is a  Apache Flex 4.10.0 release candidate 4. Please see the
> >> RELEASE_NOTES and the README.
> >>
> >> There are only a few minor differences from RC3, which are:
> >> - Fixed FLEX-32599 Stop RTE when scrolled horizontally + cleaned up
> >> spacing/readability.
> >> - Fixed FLEX-33632 Moved initialization of locale chain to after bundle
> >> modules are installed.
> >> - Revert addition of removeItem to IList.
> >> - Change 'Adobe Flex' to 'Apache Flex' in SWF metadata.
> >>
> >> There is a bug in Adobe Flash Builder 4.6 and 4.7  that causes a issue
> >> when creating new applications.
> >>
> >> While this this issue has a simple work around and a solution has been
> >> found it is currently unknown
> >> if Adobe will release a patch for either Flash Builder 4.7 or 4.6.
> >>
> >> The release candidate can be found here;
> >> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc4/
> >>
> >> Before voting please review the section,"What are the ASF requirements
> >>on
> >> approving a release?", at:
> >> http://www.apache.org/dev/release.html#approving-a-release
> >>
> >> When testing please check the md5 and asc files and make sure that the
> >> source can be compiled.
> >>
> >> Please vote to approve this release:
> >> +1 Approve the release
> >> -1 Veto the release (please provide specific comments to why)
> >>
> >> This vote will be open for 72 hours.
> >>
> >> The vote passes if there is:
> >> - At least 3 +1 votes from the PMC
> >> - More positive votes than negative votes
> >>
> >> If you find an issue with the release that's a "show stopper" please
> >>don't
> >> hold off voting -1. Existing voters can change their vote during the
> >>voting
> >> process,
> >> but once the 72 hours are up that's it, no excuses this time!
> >>
> >> People who are not in PMC or who are not an committer are also
> >>encouraged
> >> to test out the release and vote, although their votes will not be
> >>binding.
> >>
> >> When voting please indicate what OS, IDE, Flash Player version and AIR
> >> version you tested the SDK with.
> >>
> >> Please put all discussion about this release in the DISCUSSION thread
> >>not
> >> this VOTE thread.
> >>
> >> Thanks,
> >> Justin
>



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es


Re: [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-02 Thread ayo
+1

Win 8, AFSDK 4.10.0 

there is still the the Win 8 FB7 layout attribute issue. 



aYo
www.ayobinitie.com
mrbinitie.blogspot.com



From: Alex Harui
Sent: ‎Friday‎, ‎2‎ ‎August‎ ‎2013 ‎18‎:‎25
To: dev@flex.apache.org

+1
Src kit build passed.
Signature match on src tar and zip kit
Rat passed on src zip kit
Mustella passed on Mac with 11.1 and Win7 with 11.7
Notice files look fine

Thanks Justin!
-Alex

On 8/1/13 3:57 PM, "Mark Kessler"  wrote:

>+1
>
>OS: Win7 64bit
>Flex SDK: 4.10
>FP: 11.8
>
>Successfully built SDK.
>Used SDK to built simple apps successfully.
>
>
>-Mark
>
>
>
>On Thu, Aug 1, 2013 at 6:27 AM, Justin Mclean
>wrote:
>
>> Hi,
>>
>> This is a  Apache Flex 4.10.0 release candidate 4. Please see the
>> RELEASE_NOTES and the README.
>>
>> There are only a few minor differences from RC3, which are:
>> - Fixed FLEX-32599 Stop RTE when scrolled horizontally + cleaned up
>> spacing/readability.
>> - Fixed FLEX-33632 Moved initialization of locale chain to after bundle
>> modules are installed.
>> - Revert addition of removeItem to IList.
>> - Change 'Adobe Flex' to 'Apache Flex' in SWF metadata.
>>
>> There is a bug in Adobe Flash Builder 4.6 and 4.7  that causes a issue
>> when creating new applications.
>>
>> While this this issue has a simple work around and a solution has been
>> found it is currently unknown
>> if Adobe will release a patch for either Flash Builder 4.7 or 4.6.
>>
>> The release candidate can be found here;
>> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc4/
>>
>> Before voting please review the section,"What are the ASF requirements
>>on
>> approving a release?", at:
>> http://www.apache.org/dev/release.html#approving-a-release
>>
>> When testing please check the md5 and asc files and make sure that the
>> source can be compiled.
>>
>> Please vote to approve this release:
>> +1 Approve the release
>> -1 Veto the release (please provide specific comments to why)
>>
>> This vote will be open for 72 hours.
>>
>> The vote passes if there is:
>> - At least 3 +1 votes from the PMC
>> - More positive votes than negative votes
>>
>> If you find an issue with the release that's a "show stopper" please
>>don't
>> hold off voting -1. Existing voters can change their vote during the
>>voting
>> process,
>> but once the 72 hours are up that's it, no excuses this time!
>>
>> People who are not in PMC or who are not an committer are also
>>encouraged
>> to test out the release and vote, although their votes will not be
>>binding.
>>
>> When voting please indicate what OS, IDE, Flash Player version and AIR
>> version you tested the SDK with.
>>
>> Please put all discussion about this release in the DISCUSSION thread
>>not
>> this VOTE thread.
>>
>> Thanks,
>> Justin

Re: [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-02 Thread ayo
Will test on Linux Mint FDT5 later today



aYo
www.ayobinitie.com
mrbinitie.blogspot.com



From: Alex Harui
Sent: ‎Friday‎, ‎2‎ ‎August‎ ‎2013 ‎18‎:‎25
To: dev@flex.apache.org

+1
Src kit build passed.
Signature match on src tar and zip kit
Rat passed on src zip kit
Mustella passed on Mac with 11.1 and Win7 with 11.7
Notice files look fine

Thanks Justin!
-Alex

On 8/1/13 3:57 PM, "Mark Kessler"  wrote:

>+1
>
>OS: Win7 64bit
>Flex SDK: 4.10
>FP: 11.8
>
>Successfully built SDK.
>Used SDK to built simple apps successfully.
>
>
>-Mark
>
>
>
>On Thu, Aug 1, 2013 at 6:27 AM, Justin Mclean
>wrote:
>
>> Hi,
>>
>> This is a  Apache Flex 4.10.0 release candidate 4. Please see the
>> RELEASE_NOTES and the README.
>>
>> There are only a few minor differences from RC3, which are:
>> - Fixed FLEX-32599 Stop RTE when scrolled horizontally + cleaned up
>> spacing/readability.
>> - Fixed FLEX-33632 Moved initialization of locale chain to after bundle
>> modules are installed.
>> - Revert addition of removeItem to IList.
>> - Change 'Adobe Flex' to 'Apache Flex' in SWF metadata.
>>
>> There is a bug in Adobe Flash Builder 4.6 and 4.7  that causes a issue
>> when creating new applications.
>>
>> While this this issue has a simple work around and a solution has been
>> found it is currently unknown
>> if Adobe will release a patch for either Flash Builder 4.7 or 4.6.
>>
>> The release candidate can be found here;
>> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc4/
>>
>> Before voting please review the section,"What are the ASF requirements
>>on
>> approving a release?", at:
>> http://www.apache.org/dev/release.html#approving-a-release
>>
>> When testing please check the md5 and asc files and make sure that the
>> source can be compiled.
>>
>> Please vote to approve this release:
>> +1 Approve the release
>> -1 Veto the release (please provide specific comments to why)
>>
>> This vote will be open for 72 hours.
>>
>> The vote passes if there is:
>> - At least 3 +1 votes from the PMC
>> - More positive votes than negative votes
>>
>> If you find an issue with the release that's a "show stopper" please
>>don't
>> hold off voting -1. Existing voters can change their vote during the
>>voting
>> process,
>> but once the 72 hours are up that's it, no excuses this time!
>>
>> People who are not in PMC or who are not an committer are also
>>encouraged
>> to test out the release and vote, although their votes will not be
>>binding.
>>
>> When voting please indicate what OS, IDE, Flash Player version and AIR
>> version you tested the SDK with.
>>
>> Please put all discussion about this release in the DISCUSSION thread
>>not
>> this VOTE thread.
>>
>> Thanks,
>> Justin

Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-02 Thread Justin Mclean
Hi,

> If I recall correctly, it's version 10.1
Close the minimum is 10.2. This is in the README.

The 4.10 SDK wont compile with 10.1 but it may be possible to get it working on 
10.1 with a little work.

Thanks.
Justin

Re: [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-02 Thread Alex Harui
+1
Src kit build passed.
Signature match on src tar and zip kit
Rat passed on src zip kit
Mustella passed on Mac with 11.1 and Win7 with 11.7
Notice files look fine

Thanks Justin!
-Alex

On 8/1/13 3:57 PM, "Mark Kessler"  wrote:

>+1
>
>OS: Win7 64bit
>Flex SDK: 4.10
>FP: 11.8
>
>Successfully built SDK.
>Used SDK to built simple apps successfully.
>
>
>-Mark
>
>
>
>On Thu, Aug 1, 2013 at 6:27 AM, Justin Mclean
>wrote:
>
>> Hi,
>>
>> This is a  Apache Flex 4.10.0 release candidate 4. Please see the
>> RELEASE_NOTES and the README.
>>
>> There are only a few minor differences from RC3, which are:
>> - Fixed FLEX-32599 Stop RTE when scrolled horizontally + cleaned up
>> spacing/readability.
>> - Fixed FLEX-33632 Moved initialization of locale chain to after bundle
>> modules are installed.
>> - Revert addition of removeItem to IList.
>> - Change 'Adobe Flex' to 'Apache Flex' in SWF metadata.
>>
>> There is a bug in Adobe Flash Builder 4.6 and 4.7  that causes a issue
>> when creating new applications.
>>
>> While this this issue has a simple work around and a solution has been
>> found it is currently unknown
>> if Adobe will release a patch for either Flash Builder 4.7 or 4.6.
>>
>> The release candidate can be found here;
>> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc4/
>>
>> Before voting please review the section,"What are the ASF requirements
>>on
>> approving a release?", at:
>> http://www.apache.org/dev/release.html#approving-a-release
>>
>> When testing please check the md5 and asc files and make sure that the
>> source can be compiled.
>>
>> Please vote to approve this release:
>> +1 Approve the release
>> -1 Veto the release (please provide specific comments to why)
>>
>> This vote will be open for 72 hours.
>>
>> The vote passes if there is:
>> - At least 3 +1 votes from the PMC
>> - More positive votes than negative votes
>>
>> If you find an issue with the release that's a "show stopper" please
>>don't
>> hold off voting -1. Existing voters can change their vote during the
>>voting
>> process,
>> but once the 72 hours are up that's it, no excuses this time!
>>
>> People who are not in PMC or who are not an committer are also
>>encouraged
>> to test out the release and vote, although their votes will not be
>>binding.
>>
>> When voting please indicate what OS, IDE, Flash Player version and AIR
>> version you tested the SDK with.
>>
>> Please put all discussion about this release in the DISCUSSION thread
>>not
>> this VOTE thread.
>>
>> Thanks,
>> Justin



Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-02 Thread Erik de Bruin
If I recall correctly, it's version 10.1

EdB



On Fri, Aug 2, 2013 at 11:39 AM, Jagan Langa Sami Durai
 wrote:
> Hi,
>
> correct me if my understanding is wrong. Developer may prefer any latest
> flash player while compiling and releasing. But my question is. what is the
> minimum flash player version supported by 4.10.0 sdk?
>
> *
> Regards,
> S. Jagan  Langa* *|* *Team Lead*
> *Sybrant Technologies Pvt Ltd*
> *
> *
> Mobile: +91 98430 50897
> Skype: seesamjagan
> --
>
> In The Media:
> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
> **
>
> * *
>
> *About Sybrant:*
>
> *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
> India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
> recognized for working with our clients right from the product
> conceptualization till the execution stage offering end-to-end solutions
> that sets us apart from other firms in this space. Right from developing a
> learning management system for a French company to helping a Non-Profit
> with a Mobile application till developing UX for a IT firm, Sybrant is
> known for delighting Customers”*
>
> --
>
>
> 2013/8/2 OmPrakash Muppirala 
>
>> On Aug 2, 2013 2:24 AM, "Jagan Langa Sami Durai" 
>> wrote:
>> >
>> > hi
>> >
>> > I have installed the rc4 sdk with the latest sdk installer. I noticed
>> that,
>> > by default, min. player version is marked as 11.8 in the flex-config.xml.
>> > is it supposed to point 11.8 or its an error?
>> >
>> > 
>> > 
>> >11.8
>> >
>>
>> This would depend on what version of Flash Player you select in the first
>> screen on the Installer.  And 11.8 is selected by default.  So this is
>> expected behavior.
>>
>> Thanks,
>> Om
>>
>> >
>> >
>> >
>> > *
>> > Regards,
>> > S. Jagan  Langa* *|* *Team Lead*
>> > *Sybrant Technologies Pvt Ltd*
>> > *
>> > *
>> > Mobile: +91 98430 50897
>> > Skype: seesamjagan
>> >
>>
>> --
>> >
>> > In The Media:
>> >
>>
>> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
>> > **
>> >
>> > * *
>> >
>> > *About Sybrant:*
>> >
>> > *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
>> > India too, leverage Sybrant’s expertise for their Web & UIUX needs. We
>> are
>> > recognized for working with our clients right from the product
>> > conceptualization till the execution stage offering end-to-end solutions
>> > that sets us apart from other firms in this space. Right from developing
>> a
>> > learning management system for a French company to helping a Non-Profit
>> > with a Mobile application till developing UX for a IT firm, Sybrant is
>> > known for delighting Customers”*
>> >
>> >
>>
>> --
>> >
>> >
>> > 2013/8/1 Justin Mclean 
>> >
>> > > HI,
>> > >
>> > >
>> > > > > > > > default="4.10.0 RC3" />
>> > >
>> > > Sorry about that - just fixing.
>> > >
>> > > Justin
>> > >
>>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-02 Thread Jagan Langa Sami Durai
Hi,

correct me if my understanding is wrong. Developer may prefer any latest
flash player while compiling and releasing. But my question is. what is the
minimum flash player version supported by 4.10.0 sdk?

*
Regards,
S. Jagan  Langa* *|* *Team Lead*
*Sybrant Technologies Pvt Ltd*
*
*
Mobile: +91 98430 50897
Skype: seesamjagan
--

In The Media:
http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
**

* *

*About Sybrant:*

*“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
recognized for working with our clients right from the product
conceptualization till the execution stage offering end-to-end solutions
that sets us apart from other firms in this space. Right from developing a
learning management system for a French company to helping a Non-Profit
with a Mobile application till developing UX for a IT firm, Sybrant is
known for delighting Customers”*

--


2013/8/2 OmPrakash Muppirala 

> On Aug 2, 2013 2:24 AM, "Jagan Langa Sami Durai" 
> wrote:
> >
> > hi
> >
> > I have installed the rc4 sdk with the latest sdk installer. I noticed
> that,
> > by default, min. player version is marked as 11.8 in the flex-config.xml.
> > is it supposed to point 11.8 or its an error?
> >
> > 
> > 
> >11.8
> >
>
> This would depend on what version of Flash Player you select in the first
> screen on the Installer.  And 11.8 is selected by default.  So this is
> expected behavior.
>
> Thanks,
> Om
>
> >
> >
> >
> > *
> > Regards,
> > S. Jagan  Langa* *|* *Team Lead*
> > *Sybrant Technologies Pvt Ltd*
> > *
> > *
> > Mobile: +91 98430 50897
> > Skype: seesamjagan
> >
>
> --
> >
> > In The Media:
> >
>
> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
> > **
> >
> > * *
> >
> > *About Sybrant:*
> >
> > *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
> > India too, leverage Sybrant’s expertise for their Web & UIUX needs. We
> are
> > recognized for working with our clients right from the product
> > conceptualization till the execution stage offering end-to-end solutions
> > that sets us apart from other firms in this space. Right from developing
> a
> > learning management system for a French company to helping a Non-Profit
> > with a Mobile application till developing UX for a IT firm, Sybrant is
> > known for delighting Customers”*
> >
> >
>
> --
> >
> >
> > 2013/8/1 Justin Mclean 
> >
> > > HI,
> > >
> > >
> > > >  > > > default="4.10.0 RC3" />
> > >
> > > Sorry about that - just fixing.
> > >
> > > Justin
> > >
>


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-02 Thread OmPrakash Muppirala
On Aug 2, 2013 2:24 AM, "Jagan Langa Sami Durai" 
wrote:
>
> hi
>
> I have installed the rc4 sdk with the latest sdk installer. I noticed
that,
> by default, min. player version is marked as 11.8 in the flex-config.xml.
> is it supposed to point 11.8 or its an error?
>
> 
> 
>11.8
>

This would depend on what version of Flash Player you select in the first
screen on the Installer.  And 11.8 is selected by default.  So this is
expected behavior.

Thanks,
Om

>
>
>
> *
> Regards,
> S. Jagan  Langa* *|* *Team Lead*
> *Sybrant Technologies Pvt Ltd*
> *
> *
> Mobile: +91 98430 50897
> Skype: seesamjagan
>
--
>
> In The Media:
>
http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
> **
>
> * *
>
> *About Sybrant:*
>
> *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
> India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
> recognized for working with our clients right from the product
> conceptualization till the execution stage offering end-to-end solutions
> that sets us apart from other firms in this space. Right from developing a
> learning management system for a French company to helping a Non-Profit
> with a Mobile application till developing UX for a IT firm, Sybrant is
> known for delighting Customers”*
>
>
--
>
>
> 2013/8/1 Justin Mclean 
>
> > HI,
> >
> >
> > >  > > default="4.10.0 RC3" />
> >
> > Sorry about that - just fixing.
> >
> > Justin
> >


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-02 Thread Jagan Langa Sami Durai
hi

I have installed the rc4 sdk with the latest sdk installer. I noticed that,
by default, min. player version is marked as 11.8 in the flex-config.xml.
is it supposed to point 11.8 or its an error?



   11.8




*
Regards,
S. Jagan  Langa* *|* *Team Lead*
*Sybrant Technologies Pvt Ltd*
*
*
Mobile: +91 98430 50897
Skype: seesamjagan
--

In The Media:
http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
**

* *

*About Sybrant:*

*“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
recognized for working with our clients right from the product
conceptualization till the execution stage offering end-to-end solutions
that sets us apart from other firms in this space. Right from developing a
learning management system for a French company to helping a Non-Profit
with a Mobile application till developing UX for a IT firm, Sybrant is
known for delighting Customers”*

--


2013/8/1 Justin Mclean 

> HI,
>
>
> >  > default="4.10.0 RC3" />
>
> Sorry about that - just fixing.
>
> Justin
>


Re: [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-01 Thread Mark Kessler
+1

OS: Win7 64bit
Flex SDK: 4.10
FP: 11.8

Successfully built SDK.
Used SDK to built simple apps successfully.


-Mark



On Thu, Aug 1, 2013 at 6:27 AM, Justin Mclean wrote:

> Hi,
>
> This is a  Apache Flex 4.10.0 release candidate 4. Please see the
> RELEASE_NOTES and the README.
>
> There are only a few minor differences from RC3, which are:
> - Fixed FLEX-32599 Stop RTE when scrolled horizontally + cleaned up
> spacing/readability.
> - Fixed FLEX-33632 Moved initialization of locale chain to after bundle
> modules are installed.
> - Revert addition of removeItem to IList.
> - Change 'Adobe Flex' to 'Apache Flex' in SWF metadata.
>
> There is a bug in Adobe Flash Builder 4.6 and 4.7  that causes a issue
> when creating new applications.
>
> While this this issue has a simple work around and a solution has been
> found it is currently unknown
> if Adobe will release a patch for either Flash Builder 4.7 or 4.6.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc4/
>
> Before voting please review the section,"What are the ASF requirements on
> approving a release?", at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> When testing please check the md5 and asc files and make sure that the
> source can be compiled.
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Veto the release (please provide specific comments to why)
>
> This vote will be open for 72 hours.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> If you find an issue with the release that's a "show stopper" please don't
> hold off voting -1. Existing voters can change their vote during the voting
> process,
> but once the 72 hours are up that's it, no excuses this time!
>
> People who are not in PMC or who are not an committer are also encouraged
> to test out the release and vote, although their votes will not be binding.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested the SDK with.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Justin


Re: Apache Flex 4.10.0 Release

2013-08-01 Thread Paul Hastings

On 8/1/2013 2:47 AM, Nicholas Kwiatkowski wrote:

As time marches on, this method of "fixing" DV will become more and more


its looking more & more like 4.9.1 was the last SDK version where that "trick" 
worked. 4.10.0 RC3 shows black/grey screen instead of the DV no matter how many 
times i stand FB on its head. C'est la vie.








Re: [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-01 Thread Swen van Zanten
+1

Mac osx 10.8.4 FB air 3.8 fp 3.8
All works fine.

Regards,

SWEN VAN ZANTEN
Hoofdstraat 160
2171 BL, Sassenheim

Op 1 aug. 2013, om 13:13 heeft Erik de Bruin  het volgende 
geschreven:

> +1 (binding)
> 
> On my Mac:
> - hash and sig check out
> - SDK builds
> - checkintests pass
> - ant framework-rsls + IDE script run fine
> - resulting SDK imports ok in FB and compiles various projects fine
> 
> EdB
> 
> 
> 
> On Thu, Aug 1, 2013 at 12:27 PM, Justin Mclean  
> wrote:
>> Hi,
>> 
>> This is a  Apache Flex 4.10.0 release candidate 4. Please see the 
>> RELEASE_NOTES and the README.
>> 
>> There are only a few minor differences from RC3, which are:
>> - Fixed FLEX-32599 Stop RTE when scrolled horizontally + cleaned up 
>> spacing/readability.
>> - Fixed FLEX-33632 Moved initialization of locale chain to after bundle 
>> modules are installed.
>> - Revert addition of removeItem to IList.
>> - Change 'Adobe Flex' to 'Apache Flex' in SWF metadata.
>> 
>> There is a bug in Adobe Flash Builder 4.6 and 4.7  that causes a issue when 
>> creating new applications.
>> 
>> While this this issue has a simple work around and a solution has been found 
>> it is currently unknown
>> if Adobe will release a patch for either Flash Builder 4.7 or 4.6.
>> 
>> The release candidate can be found here;
>> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc4/
>> 
>> Before voting please review the section,"What are the ASF requirements on 
>> approving a release?", at:
>> http://www.apache.org/dev/release.html#approving-a-release
>> 
>> When testing please check the md5 and asc files and make sure that the 
>> source can be compiled.
>> 
>> Please vote to approve this release:
>> +1 Approve the release
>> -1 Veto the release (please provide specific comments to why)
>> 
>> This vote will be open for 72 hours.
>> 
>> The vote passes if there is:
>> - At least 3 +1 votes from the PMC
>> - More positive votes than negative votes
>> 
>> If you find an issue with the release that's a "show stopper" please don't 
>> hold off voting -1. Existing voters can change their vote during the voting 
>> process,
>> but once the 72 hours are up that's it, no excuses this time!
>> 
>> People who are not in PMC or who are not an committer are also encouraged to 
>> test out the release and vote, although their votes will not be binding.
>> 
>> When voting please indicate what OS, IDE, Flash Player version and AIR 
>> version you tested the SDK with.
>> 
>> Please put all discussion about this release in the DISCUSSION thread not 
>> this VOTE thread.
>> 
>> Thanks,
>> Justin
> 
> 
> 
> -- 
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl



Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread Justin Mclean
HI,


>  default="4.10.0 RC3" />

Sorry about that - just fixing.

Justin


Re: [VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-01 Thread Erik de Bruin
+1 (binding)

On my Mac:
- hash and sig check out
- SDK builds
- checkintests pass
- ant framework-rsls + IDE script run fine
- resulting SDK imports ok in FB and compiles various projects fine

EdB



On Thu, Aug 1, 2013 at 12:27 PM, Justin Mclean  wrote:
> Hi,
>
> This is a  Apache Flex 4.10.0 release candidate 4. Please see the 
> RELEASE_NOTES and the README.
>
> There are only a few minor differences from RC3, which are:
> - Fixed FLEX-32599 Stop RTE when scrolled horizontally + cleaned up 
> spacing/readability.
> - Fixed FLEX-33632 Moved initialization of locale chain to after bundle 
> modules are installed.
> - Revert addition of removeItem to IList.
> - Change 'Adobe Flex' to 'Apache Flex' in SWF metadata.
>
> There is a bug in Adobe Flash Builder 4.6 and 4.7  that causes a issue when 
> creating new applications.
>
> While this this issue has a simple work around and a solution has been found 
> it is currently unknown
> if Adobe will release a patch for either Flash Builder 4.7 or 4.6.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc4/
>
> Before voting please review the section,"What are the ASF requirements on 
> approving a release?", at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> When testing please check the md5 and asc files and make sure that the source 
> can be compiled.
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Veto the release (please provide specific comments to why)
>
> This vote will be open for 72 hours.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> If you find an issue with the release that's a "show stopper" please don't 
> hold off voting -1. Existing voters can change their vote during the voting 
> process,
> but once the 72 hours are up that's it, no excuses this time!
>
> People who are not in PMC or who are not an committer are also encouraged to 
> test out the release and vote, although their votes will not be binding.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR 
> version you tested the SDK with.
>
> Please put all discussion about this release in the DISCUSSION thread not 
> this VOTE thread.
>
> Thanks,
> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread Erik de Bruin
Ah, I see (some of) it:



Need to change the 'default' attribute as well...

EdB



On Thu, Aug 1, 2013 at 12:51 PM,   wrote:
> True, but there are no options for the choice of flashplayer, so the 
> installer cannot proceed
>
>
>
> aYo
> www.ayobinitie.com
> mrbinitie.blogspot.com
>
>
>
> From: Justin Mclean
> Sent: Thursday, 1 August 2013 11:46
> To: dev@flex.apache.org
>
>
> Hi,
>
>> Now RC4 is online, can you please point the Installer to it so people
>> have easy access?
>
> Done.
>
> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread ayo
True, but there are no options for the choice of flashplayer, so the installer 
cannot proceed



aYo
www.ayobinitie.com
mrbinitie.blogspot.com



From: Justin Mclean
Sent: ‎Thursday‎, ‎1‎ ‎August‎ ‎2013 ‎11‎:‎46
To: dev@flex.apache.org


Hi,

> Now RC4 is online, can you please point the Installer to it so people
> have easy access?

Done.

Justin

Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread Erik de Bruin
Same here... typo?

EdB



On Thu, Aug 1, 2013 at 12:51 PM, Swen van Zanten  wrote:
> It doesn't work the way it should anymore..
> flash player is not chooseable and the installer does not automatically fill 
> in the sdk.
>
> Regards,
>
> SWEN VAN ZANTEN
> Hoofdstraat 160
> 2171 BL, Sassenheim
>
> Op 1 aug. 2013, om 12:46 heeft Justin Mclean  het 
> volgende geschreven:
>
>> Hi,
>>
>>> Now RC4 is online, can you please point the Installer to it so people
>>> have easy access?
>>
>> Done.
>>
>> Justin
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread Erik de Bruin
Thank you, kind sir.

;-)

EdB



On Thu, Aug 1, 2013 at 12:46 PM, Justin Mclean  wrote:
> Hi,
>
>> Now RC4 is online, can you please point the Installer to it so people
>> have easy access?
>
> Done.
>
> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread Swen van Zanten
It doesn't work the way it should anymore.. 
flash player is not chooseable and the installer does not automatically fill in 
the sdk.

Regards,

SWEN VAN ZANTEN
Hoofdstraat 160
2171 BL, Sassenheim

Op 1 aug. 2013, om 12:46 heeft Justin Mclean  het 
volgende geschreven:

> Hi,
> 
>> Now RC4 is online, can you please point the Installer to it so people
>> have easy access?
> 
> Done.
> 
> Justin



Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread Justin Mclean
Hi,

> Now RC4 is online, can you please point the Installer to it so people
> have easy access?

Done.

Justin


Re: [DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread Erik de Bruin
Hi,

Now RC4 is online, can you please point the Installer to it so people
have easy access?

EdB



On Thu, Aug 1, 2013 at 11:38 AM, Justin Mclean  wrote:
> Hi,
>
> Place all discussion about Apache Flex 4.10.0 RC 4 here. Any questions you 
> have, issues you run into etc etc
>
> Thanks,
> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


[VOTE] Apache Flex 4.10.0 release candidate 4

2013-08-01 Thread Justin Mclean
Hi,

This is a  Apache Flex 4.10.0 release candidate 4. Please see the RELEASE_NOTES 
and the README.

There are only a few minor differences from RC3, which are:
- Fixed FLEX-32599 Stop RTE when scrolled horizontally + cleaned up 
spacing/readability.
- Fixed FLEX-33632 Moved initialization of locale chain to after bundle modules 
are installed.
- Revert addition of removeItem to IList. 
- Change 'Adobe Flex' to 'Apache Flex' in SWF metadata.

There is a bug in Adobe Flash Builder 4.6 and 4.7  that causes a issue when 
creating new applications.

While this this issue has a simple work around and a solution has been found it 
is currently unknown
if Adobe will release a patch for either Flash Builder 4.7 or 4.6.

The release candidate can be found here;
https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc4/

Before voting please review the section,"What are the ASF requirements on 
approving a release?", at:
http://www.apache.org/dev/release.html#approving-a-release

When testing please check the md5 and asc files and make sure that the source 
can be compiled.

Please vote to approve this release:
+1 Approve the release
-1 Veto the release (please provide specific comments to why)

This vote will be open for 72 hours.

The vote passes if there is:
- At least 3 +1 votes from the PMC
- More positive votes than negative votes

If you find an issue with the release that's a "show stopper" please don't hold 
off voting -1. Existing voters can change their vote during the voting process,
but once the 72 hours are up that's it, no excuses this time!

People who are not in PMC or who are not an committer are also encouraged to 
test out the release and vote, although their votes will not be binding.

When voting please indicate what OS, IDE, Flash Player version and AIR version 
you tested the SDK with. 

Please put all discussion about this release in the DISCUSSION thread not this 
VOTE thread.

Thanks,
Justin

[DISCUSSION] Apache Flex 4.10.0 Release Candidate 4 issues or problems here!

2013-08-01 Thread Justin Mclean
Hi,

Place all discussion about Apache Flex 4.10.0 RC 4 here. Any questions you 
have, issues you run into etc etc

Thanks,
Justin

Re: Apache Flex 4.10.0 Release

2013-07-31 Thread Chris Martin
Om,

No blog post.  A google plus user posted that tid bit on the Apache Flex
Community page (
https://plus.google.com/104408486838026884935/posts/17vGFEevkZM).  I don't
know of any side affects yet, as i haven't moved off of Flex 4.6 yet.  But
when i do (planning for this next dev cycle to move to Flex 4.10) i'll put
up some updates to the group, and maybe even write up a blog about it :)
Just don't have enough detail to warrant one now

Chris


On Wed, Jul 31, 2013 at 12:47 PM, Nicholas Kwiatkowski wrote:

> As time marches on, this method of "fixing" DV will become more and more
> broken.  FP version changes and SDK changes will not be realized and will
> cause issues -- from crashes to bad code.  I've already run across some
> major issues trying to use the new DataGrid with the hacked DV setup...
>  The time to start investigating your workflow is now...
>
>
> On Wed, Jul 31, 2013 at 12:59 PM, OmPrakash Muppirala
> wrote:
>
> > On Wed, Jul 31, 2013 at 9:27 AM, Chris Martin 
> wrote:
> >
> > > > It is really up to Adobe to figure out if they want to honor their
> > > >   user base's desire to continue using FB 4.6.  DV does not work with
> > > Apache
> > > >   Flex in any case.
> > >
> > > Om,
> > >
> > > Just a heads up, Design View does work with Apache Flex 4.9.1.  But you
> > > have to modify the sdk's flex-sdk-description.xml file by changing the
> > > value in the version tag to read 4.6.0.  Then design view will fire
> right
> > > up.
> > >
> > > Chris
> > >
> > >
> > Thanks for the note!  I learnt that nugget in this thread.  Is this
> > document somewhere on a blog post, etc.?  If not I will add a note about
> > this on our wiki.  Any known side effects of doing this?
> >
> > Thanks,
> > Om
> >
> >
> > >
> > > On Tue, Jul 30, 2013 at 5:14 PM, Alex Harui  wrote:
> > >
> > > >
> > > >
> > > > On 7/30/13 4:49 PM, "Justin Mclean" 
> wrote:
> > > >
> > > > >Hi,
> > > > >
> > > > >> It is still using bad code, but the change allows 4.10 to work.
> > > > >So 4*100+10*10 + 0 == 500 is going to be treated the same as 5.0.0
> > > (5*100
> > > > >+ 0 + 0 = 500), 4.10.1 (say we need to patch it) = 501 which will
> end
> > up
> > > > >with a higher version than than 5.0.0.
> > > > I didn't see any compares like that in the code I saw, but there
> could
> > be
> > > > elsewhere.
> > > >
> > > > >100% sure this is just not going to cause more issues down the
> track?
> > > > Nope, but it is relatively safe.  Basically the class I changed has 3
> > > > values, current, min and max.  I'm just changing the max value from 5
> > to
> > > > 100.  I don't think a max value would get used for version against
> > > version
> > > > compares.
> > > >
> > > > -Alex
> > > >
> > > >
> > >
> >
>


Re: Apache Flex 4.10.0 Release

2013-07-31 Thread Nicholas Kwiatkowski
As time marches on, this method of "fixing" DV will become more and more
broken.  FP version changes and SDK changes will not be realized and will
cause issues -- from crashes to bad code.  I've already run across some
major issues trying to use the new DataGrid with the hacked DV setup...
 The time to start investigating your workflow is now...


On Wed, Jul 31, 2013 at 12:59 PM, OmPrakash Muppirala
wrote:

> On Wed, Jul 31, 2013 at 9:27 AM, Chris Martin  wrote:
>
> > > It is really up to Adobe to figure out if they want to honor their
> > >   user base's desire to continue using FB 4.6.  DV does not work with
> > Apache
> > >   Flex in any case.
> >
> > Om,
> >
> > Just a heads up, Design View does work with Apache Flex 4.9.1.  But you
> > have to modify the sdk's flex-sdk-description.xml file by changing the
> > value in the version tag to read 4.6.0.  Then design view will fire right
> > up.
> >
> > Chris
> >
> >
> Thanks for the note!  I learnt that nugget in this thread.  Is this
> document somewhere on a blog post, etc.?  If not I will add a note about
> this on our wiki.  Any known side effects of doing this?
>
> Thanks,
> Om
>
>
> >
> > On Tue, Jul 30, 2013 at 5:14 PM, Alex Harui  wrote:
> >
> > >
> > >
> > > On 7/30/13 4:49 PM, "Justin Mclean"  wrote:
> > >
> > > >Hi,
> > > >
> > > >> It is still using bad code, but the change allows 4.10 to work.
> > > >So 4*100+10*10 + 0 == 500 is going to be treated the same as 5.0.0
> > (5*100
> > > >+ 0 + 0 = 500), 4.10.1 (say we need to patch it) = 501 which will end
> up
> > > >with a higher version than than 5.0.0.
> > > I didn't see any compares like that in the code I saw, but there could
> be
> > > elsewhere.
> > >
> > > >100% sure this is just not going to cause more issues down the track?
> > > Nope, but it is relatively safe.  Basically the class I changed has 3
> > > values, current, min and max.  I'm just changing the max value from 5
> to
> > > 100.  I don't think a max value would get used for version against
> > version
> > > compares.
> > >
> > > -Alex
> > >
> > >
> >
>


Re: Apache Flex 4.10.0 Release

2013-07-31 Thread Paul Hastings

On 7/31/2013 11:59 PM, OmPrakash Muppirala wrote:

On Wed, Jul 31, 2013 at 9:27 AM, Chris Martin  wrote:
Thanks for the note!  I learnt that nugget in this thread.  Is this
document somewhere on a blog post, etc.?  If not I will add a note about
this on our wiki.  Any known side effects of doing this?


there must be some magic sauce that i missed sprinkling on FB, as that trick 
doesn't work w/4.10.0 for me.




Re: Apache Flex 4.10.0 Release

2013-07-31 Thread OmPrakash Muppirala
On Wed, Jul 31, 2013 at 9:27 AM, Chris Martin  wrote:

> > It is really up to Adobe to figure out if they want to honor their
> >   user base's desire to continue using FB 4.6.  DV does not work with
> Apache
> >   Flex in any case.
>
> Om,
>
> Just a heads up, Design View does work with Apache Flex 4.9.1.  But you
> have to modify the sdk's flex-sdk-description.xml file by changing the
> value in the version tag to read 4.6.0.  Then design view will fire right
> up.
>
> Chris
>
>
Thanks for the note!  I learnt that nugget in this thread.  Is this
document somewhere on a blog post, etc.?  If not I will add a note about
this on our wiki.  Any known side effects of doing this?

Thanks,
Om


>
> On Tue, Jul 30, 2013 at 5:14 PM, Alex Harui  wrote:
>
> >
> >
> > On 7/30/13 4:49 PM, "Justin Mclean"  wrote:
> >
> > >Hi,
> > >
> > >> It is still using bad code, but the change allows 4.10 to work.
> > >So 4*100+10*10 + 0 == 500 is going to be treated the same as 5.0.0
> (5*100
> > >+ 0 + 0 = 500), 4.10.1 (say we need to patch it) = 501 which will end up
> > >with a higher version than than 5.0.0.
> > I didn't see any compares like that in the code I saw, but there could be
> > elsewhere.
> >
> > >100% sure this is just not going to cause more issues down the track?
> > Nope, but it is relatively safe.  Basically the class I changed has 3
> > values, current, min and max.  I'm just changing the max value from 5 to
> > 100.  I don't think a max value would get used for version against
> version
> > compares.
> >
> > -Alex
> >
> >
>


Re: Apache Flex 4.10.0 Release

2013-07-31 Thread Chris Martin
> It is really up to Adobe to figure out if they want to honor their
>   user base's desire to continue using FB 4.6.  DV does not work with
Apache
>   Flex in any case.

Om,

Just a heads up, Design View does work with Apache Flex 4.9.1.  But you
have to modify the sdk's flex-sdk-description.xml file by changing the
value in the version tag to read 4.6.0.  Then design view will fire right
up.

Chris


On Tue, Jul 30, 2013 at 5:14 PM, Alex Harui  wrote:

>
>
> On 7/30/13 4:49 PM, "Justin Mclean"  wrote:
>
> >Hi,
> >
> >> It is still using bad code, but the change allows 4.10 to work.
> >So 4*100+10*10 + 0 == 500 is going to be treated the same as 5.0.0 (5*100
> >+ 0 + 0 = 500), 4.10.1 (say we need to patch it) = 501 which will end up
> >with a higher version than than 5.0.0.
> I didn't see any compares like that in the code I saw, but there could be
> elsewhere.
>
> >100% sure this is just not going to cause more issues down the track?
> Nope, but it is relatively safe.  Basically the class I changed has 3
> values, current, min and max.  I'm just changing the max value from 5 to
> 100.  I don't think a max value would get used for version against version
> compares.
>
> -Alex
>
>


Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Alex Harui


On 7/30/13 4:49 PM, "Justin Mclean"  wrote:

>Hi,
>
>> It is still using bad code, but the change allows 4.10 to work.
>So 4*100+10*10 + 0 == 500 is going to be treated the same as 5.0.0 (5*100
>+ 0 + 0 = 500), 4.10.1 (say we need to patch it) = 501 which will end up
>with a higher version than than 5.0.0.
I didn't see any compares like that in the code I saw, but there could be
elsewhere.

>100% sure this is just not going to cause more issues down the track?
Nope, but it is relatively safe.  Basically the class I changed has 3
values, current, min and max.  I'm just changing the max value from 5 to
100.  I don't think a max value would get used for version against version
compares.

-Alex



Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Justin Mclean
Hi,

> It is still using bad code, but the change allows 4.10 to work.
So 4*100+10*10 + 0 == 500 is going to be treated the same as 5.0.0 (5*100 + 0 + 
0 = 500), 4.10.1 (say we need to patch it) = 501 which will end up with a 
higher version than than 5.0.0. 100% sure this is just not going to cause more 
issues down the track?

Justin

Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Alex Harui


On 7/30/13 4:23 PM, "Justin Mclean"  wrote:

>Hi,
>
>Also even with that patch to FB we would still have to change the RC
>version number form 4.10.0 to something else right for it to work in a
>patched version of FB? It sill using major*100+minor*10 to compare
>versions right?
It is still using bad code, but the change allows 4.10 to work.  I
basically upped the maximum version to 100 (from 5).  That's a lot of
releases from now and by that time we'll either have Adobe interested in
more FB release, created our own eclipse plug-ins and/or FB will be a
non-factor for various reasons.

I think we're ready to release as 4.10.0.  Do you still want to try for a
4.6 workaround?  I think that's going to be a hard thing to make happen.

-Alex



Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Justin Mclean
Hi,

Also even with that patch to FB we would still have to change the RC version 
number form 4.10.0 to something else right for it to work in a patched version 
of FB? It sill using major*100+minor*10 to compare versions right?

Justin

Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Justin Mclean
Hi,

> I don't think 4.6 is all that important. If we fix 4.7, the latest
> versions of the SDK and Flash Builder are good to go. 

Good we have a solution for 4.7 but given that this is really a perception 
issue (the actual problem has a very simple workaround ie edit and fix the 
generated code) and I'm reasonable sure the user base for 4.6 is still large we 
probably need a solution for both.

Do we have a time frame yet when we can consider the next RC? When do we 
consider this issue "solved"?

Justin

Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Alex Harui


On 7/30/13 12:09 PM, "OmPrakash Muppirala"  wrote:

>Thanks for digging into this issue and finding a solution.
>My thoughts/concerns on this:
>
>   - It is really up to Adobe to figure out if they want to honor their
>   user base's desire to continue using FB 4.6.  DV does not work with
>Apache
>   Flex in any case.
>   - Will the fix for FB 4.7 work with future releases of Apache Flex
>   (4.11, 5.0.0, 5.0.5, etc.) ?  Is this something we can easily test
>today?
I bumped the upper limit from 5 to 100.  I figure if we get to version 100
in Apache Flex we'll either be so popular that Adobe will be interested in
cranking out new releases of FB, or FB will have been left behind by the
community in favor of some other tool vendors.  In theory you can test by
editing flex-sdk-description.xml
>   - Any chance the fix be released as a patch to FB 4.7 instead of you
>   having to host the .jar file somewhere? Maintaining a tool for this
>would
>   be too cumbersome.
I'm waiting to find that out, but I'd say the odds are slim.  Naturally,
the less work we want it to be for our customers, the more work Adobe has
to do.  I think the options are things like:
1) Adobe creates new binaries for FB 4.7 and Adobe Auto Updater pushes the
fix
2) Adobe releases some tool that updates your FB 4.7 installation.
3) Adobe posts the patched JAR on some FB page on www.adobe.com with
instructions
4) Adobe gives me permission to post the JAR on my blog.

There are other factors like how much testing and support Adobe will
commit to.

I honestly don't know where we'll end up.

-Alex

>
>Thanks,
>Om
>
>
>On Tue, Jul 30, 2013 at 11:54 AM, Alex Harui  wrote:
>
>>
>>
>> On 7/30/13 11:35 AM, "Erik de Bruin"  wrote:
>>
>> >Can you give us odds on how likely that "if ever" is? If it's likely
>> >that Adobe will release this as a fix, I'd be willing to release the
>> >SDK in expectation of that event. If not, I'll keep pushing for a
>> >solution we can create and distribute ourselves.
>> I think either I or Adobe will publish something for Flash Builder 4.7.
>> I'm still waiting to find out how long that will take and how it will
>>get
>> published.  Now that the JAR has been tested and known to work, I've
>> removed it from my people.a.o folder since that isn't an allowed
>> deployment method.
>>
>> FlashBuilder 4.6 is another story.  Is this really critical?  It will
>>be a
>> pain for me to resurrect the source and propose the patch, and even more
>> painful to try to convince folks at Adobe that there is a business
>> justification for getting it published.  I know folks are still running
>> 4.6 to try to get Design View to work, but I was hoping they also had
>>4.7
>> installed and can create new projects in 4.7.  Remember, Adobe has
>>stated
>> that only FB 4.7 supports Apache Flex.
>>
>> So, my current position is that it is time to cut another RC and vote on
>> it.  All other issues have been addressed. I'm pretty sure FB 4.7 users
>> will be able to fix their installations sooner rather than later.  But
>>it
>> depends on how critical folks think a fix for FB 4.6 is.
>>
>> We also have to consider whether having folks replace a JAR is easy
>>enough
>> for the folks who are new to Flex and most likely to run into this
>>issue.
>> Should we be thinking about a utility that finds FB and updates it?
>>
>>
>> -Alex
>>
>>



Re: Apache Flex 4.10.0 Release

2013-07-30 Thread OmPrakash Muppirala
Thanks for digging into this issue and finding a solution.
My thoughts/concerns on this:

   - It is really up to Adobe to figure out if they want to honor their
   user base's desire to continue using FB 4.6.  DV does not work with Apache
   Flex in any case.
   - Will the fix for FB 4.7 work with future releases of Apache Flex
   (4.11, 5.0.0, 5.0.5, etc.) ?  Is this something we can easily test today?
   - Any chance the fix be released as a patch to FB 4.7 instead of you
   having to host the .jar file somewhere? Maintaining a tool for this would
   be too cumbersome.

Thanks,
Om


On Tue, Jul 30, 2013 at 11:54 AM, Alex Harui  wrote:

>
>
> On 7/30/13 11:35 AM, "Erik de Bruin"  wrote:
>
> >Can you give us odds on how likely that "if ever" is? If it's likely
> >that Adobe will release this as a fix, I'd be willing to release the
> >SDK in expectation of that event. If not, I'll keep pushing for a
> >solution we can create and distribute ourselves.
> I think either I or Adobe will publish something for Flash Builder 4.7.
> I'm still waiting to find out how long that will take and how it will get
> published.  Now that the JAR has been tested and known to work, I've
> removed it from my people.a.o folder since that isn't an allowed
> deployment method.
>
> FlashBuilder 4.6 is another story.  Is this really critical?  It will be a
> pain for me to resurrect the source and propose the patch, and even more
> painful to try to convince folks at Adobe that there is a business
> justification for getting it published.  I know folks are still running
> 4.6 to try to get Design View to work, but I was hoping they also had 4.7
> installed and can create new projects in 4.7.  Remember, Adobe has stated
> that only FB 4.7 supports Apache Flex.
>
> So, my current position is that it is time to cut another RC and vote on
> it.  All other issues have been addressed. I'm pretty sure FB 4.7 users
> will be able to fix their installations sooner rather than later.  But it
> depends on how critical folks think a fix for FB 4.6 is.
>
> We also have to consider whether having folks replace a JAR is easy enough
> for the folks who are new to Flex and most likely to run into this issue.
> Should we be thinking about a utility that finds FB and updates it?
>
>
> -Alex
>
>


Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Erik de Bruin
I don't think 4.6 is all that important. If we fix 4.7, the latest
versions of the SDK and Flash Builder are good to go. Everyone else
needs to update or live with the workaround.

EdB



On Tue, Jul 30, 2013 at 8:54 PM, Alex Harui  wrote:
>
>
> On 7/30/13 11:35 AM, "Erik de Bruin"  wrote:
>
>>Can you give us odds on how likely that "if ever" is? If it's likely
>>that Adobe will release this as a fix, I'd be willing to release the
>>SDK in expectation of that event. If not, I'll keep pushing for a
>>solution we can create and distribute ourselves.
> I think either I or Adobe will publish something for Flash Builder 4.7.
> I'm still waiting to find out how long that will take and how it will get
> published.  Now that the JAR has been tested and known to work, I've
> removed it from my people.a.o folder since that isn't an allowed
> deployment method.
>
> FlashBuilder 4.6 is another story.  Is this really critical?  It will be a
> pain for me to resurrect the source and propose the patch, and even more
> painful to try to convince folks at Adobe that there is a business
> justification for getting it published.  I know folks are still running
> 4.6 to try to get Design View to work, but I was hoping they also had 4.7
> installed and can create new projects in 4.7.  Remember, Adobe has stated
> that only FB 4.7 supports Apache Flex.
>
> So, my current position is that it is time to cut another RC and vote on
> it.  All other issues have been addressed. I'm pretty sure FB 4.7 users
> will be able to fix their installations sooner rather than later.  But it
> depends on how critical folks think a fix for FB 4.6 is.
>
> We also have to consider whether having folks replace a JAR is easy enough
> for the folks who are new to Flex and most likely to run into this issue.
> Should we be thinking about a utility that finds FB and updates it?
>
>
> -Alex
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Alex Harui


On 7/30/13 11:35 AM, "Erik de Bruin"  wrote:

>Can you give us odds on how likely that "if ever" is? If it's likely
>that Adobe will release this as a fix, I'd be willing to release the
>SDK in expectation of that event. If not, I'll keep pushing for a
>solution we can create and distribute ourselves.
I think either I or Adobe will publish something for Flash Builder 4.7.
I'm still waiting to find out how long that will take and how it will get
published.  Now that the JAR has been tested and known to work, I've
removed it from my people.a.o folder since that isn't an allowed
deployment method.

FlashBuilder 4.6 is another story.  Is this really critical?  It will be a
pain for me to resurrect the source and propose the patch, and even more
painful to try to convince folks at Adobe that there is a business
justification for getting it published.  I know folks are still running
4.6 to try to get Design View to work, but I was hoping they also had 4.7
installed and can create new projects in 4.7.  Remember, Adobe has stated
that only FB 4.7 supports Apache Flex.

So, my current position is that it is time to cut another RC and vote on
it.  All other issues have been addressed. I'm pretty sure FB 4.7 users
will be able to fix their installations sooner rather than later.  But it
depends on how critical folks think a fix for FB 4.6 is.

We also have to consider whether having folks replace a JAR is easy enough
for the folks who are new to Flex and most likely to run into this issue.
Should we be thinking about a utility that finds FB and updates it?


-Alex



Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Erik de Bruin
Can you give us odds on how likely that "if ever" is? If it's likely
that Adobe will release this as a fix, I'd be willing to release the
SDK in expectation of that event. If not, I'll keep pushing for a
solution we can create and distribute ourselves.

Thanks,

EdB



On Tue, Jul 30, 2013 at 7:14 PM, Alex Harui  wrote:
>
>
> On 7/29/13 11:48 PM, "Paul Hastings"  wrote:
>
>>
>>just in case you don't already know, this issue shows up in FB4.6 & SDK
>>4.10.0
>>as well.
> Yes, I'm aware, but it is a bundle of work to try to fix up 4.6 and I'm
> not sure how well that will go over with Adobe management since only 4.7
> "officially supports" Apache Flex.
>
> It may have to wait until after 360|Stack if ever.
>
> -Alex
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Swen van Zanten
Your right :)

Regards,

SWEN VAN ZANTEN
Hoofdstraat 160
2171 BL, Sassenheim

Op 30 jul. 2013, om 19:15 heeft Alex Harui  het volgende 
geschreven:

> 
> 
> On 7/30/13 1:48 AM, "Swen van Zanten"  wrote:
> 
>> It works great.
>> Project compiles without errors
>> 
>> mac osx 10.8.4
>> 
>> I'll will try FB 4.6 on my win7 later
> I'm pretty sure it won't work there.  Unfortunately the class I changed
> was refactored between 4.6 and 4.7.
> 
> -Alex
> 



Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Alex Harui


On 7/30/13 1:48 AM, "Swen van Zanten"  wrote:

>It works great.
>Project compiles without errors
>
>mac osx 10.8.4
>
>I'll will try FB 4.6 on my win7 later
I'm pretty sure it won't work there.  Unfortunately the class I changed
was refactored between 4.6 and 4.7.

-Alex



Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Alex Harui


On 7/29/13 11:48 PM, "Paul Hastings"  wrote:

>
>just in case you don't already know, this issue shows up in FB4.6 & SDK
>4.10.0 
>as well.
Yes, I'm aware, but it is a bundle of work to try to fix up 4.6 and I'm
not sure how well that will go over with Adobe management since only 4.7
"officially supports" Apache Flex.

It may have to wait until after 360|Stack if ever.

-Alex



Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Swen van Zanten
It works great.
Project compiles without errors

mac osx 10.8.4

I'll will try FB 4.6 on my win7 later

Regards,

SWEN VAN ZANTEN
Hoofdstraat 160
2171 BL, Sassenheim

Op 30 jul. 2013, om 08:57 heeft Erik de Bruin  het volgende 
geschreven:

> Same here:
> 
> Permission error on the download and the FB 4.7 location seems to be
> "eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722"
> 
> ???
> 
> EdB
> 
> 
> 
> On Tue, Jul 30, 2013 at 8:50 AM, OmPrakash Muppirala
>  wrote:
>> Same here.  Getting a "*Server Problem**Unknown server error.* Try again or
>> contact the server administrator."
>> 
>> Also, the folder in my FB installation
>> is eclipse\plugins\com.adobe.flexbuilder.codemodel_4.7.0.349722
>> 
>> This is on Windows 7, FB 4.7 64-bit
>> 
>> Thanks,
>> Om
>> 
>> On Mon, Jul 29, 2013 at 11:22 PM, Swen van Zanten  wrote:
>> 
>>> I have tried downloading the file.. but the browser says I have no
>>> permission..
>>> Also in your readme the folder that is pointed to is:
>>> eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
>>> But on my machine it is:
>>> eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722
>>> 
>>> Regards,
>>> 
>>> SWEN VAN ZANTEN
>>> Hoofdstraat 160
>>> 2171 BL, Sassenheim
>>> 
>>> Op 30 jul. 2013, om 08:04 heeft Alex Harui  het
>>> volgende geschreven:
>>> 
 Even later update on the "New Project" issue:
 
 I think I have successfully patched a jar in FlashBuilder to get around
 this problem.
 
 The patched jar and a readme is up on
 http://people.apache.org/~aharui/FlashBuilder/
 
 Can a few folks try it so we know it works?  I think it will only work
 with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do next.
 
 -Alex
 
 On 7/29/13 5:45 PM, "Alex Harui"  wrote:
 
> Latest update on the "New Project" issue:
> 
> I think I've found the offending code for real this time.  There is code
> for a version check that checks that the Flex version is less than 5.0.0
> by doing:
> 
> major * 100 + minor * 10 + micro
> 
> This means that we don't have the option to change to Apache Flex 5.0.0
>>> to
> get around this problem, and further means that someday when we really
> mean to do 5.0 we'll have this problem again.
> 
> There is a class called MXMLVersion2009.java that creates an instance of
> org.osgi.Framework.Version like this:
> 
>  init(..., ...,
>   new Version(4,5,0), new Version(5,0,0), new Version(4,0,0));
> 
> It looks like the expectation was that these versions would get updated
> when FB had synchronized releases with Adobe Flex SDKs.  We need to go
>>> in
> an change that 5 to something larger somehow.
> 
> 
> I am passing the same information on to the FB team at Adobe.
> 
> -Alex
> 
> On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:
> 
>>> I am hoping we're going to release something other than RC3 which
>>> means
>>> we have a few more days before we would release.  Here's my latest
>>> update on the 3 issues:
>>> 
>>> 1) ResourceModule via FlashVars:  Yes it affects a small population of
>>> the total Flex SWFs in the world, but at least two of folks who took
>>> the
>>> time to try the RC found it.  I have a fix ready to go.
>>> 2) This FB Issue.  I am trying to get a response from the FB team.
>>> And
>>> I'm looking through their source to try to find the actual cause.  If
>>> we
>>> cut another RC, we should at minimum update the release notes in the
 kits themselves to describe this issue and its workaround.  But maybe
 by the time we get the next RC ready we'll have more information.
>>> 3) The Ilist issue.  The bug author's workaround was to stop using
>>> DataList.  Not everyone has the luxury of doing that, so IMO, we
>>> really
>>> don't have a workaround.  And this will affect LCDS customers.  I
>>> think
>>> we >should revert the change to Ilist, but we don't have to revert the
>>> change to ListCollectionView.
>>> 
>>> So, I would prefer we cut another RC at least to address #1 and #3,
>>> and
>>> maybe we'll come up with a better plan for #2 during that time.
>>> 
>>> -Alex
>> 
>> To release or not to release - that is the question
>> +1 to Alex's approach. Strategically, it is better to release something
>> that provides developers with a good user experience. Releasing
>>> something
>> that requires deletion of files to work right or a patch to several of
>> the IDEs that are standard is a bad idea. Some of the goals we should
>> have when we test to determine if the RC should move forward: 1) Does
>>> the
>> SDK RC work smoothly on mac, windows, and Linux? 2) Does the AIR
>> installer work smoothly on mac, windows, and linux? 3) do the binary
>> distributions work smoothly on each of these platforms? 

Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Erik de Bruin
The file downloads fine.

The new jar does the trick, I get a nice, clean new project, no errors.

Thanks!

EdB



On Tue, Jul 30, 2013 at 10:00 AM, Alex Harui  wrote:
> OK, I think I've fixed the permissions.  Let me know if you have a problem
> using it.
>
> -Alex
>
> On 7/30/13 12:23 AM, "Alex Harui"  wrote:
>
>>OK, my bad on the folder name.  Updated the readme.
>>
>>Anybody know what permission I would have to change to allow the jar to be
>>downloaded?
>>
>>
>>On 7/29/13 11:57 PM, "Erik de Bruin"  wrote:
>>
>>>Same here:
>>>
>>>Permission error on the download and the FB 4.7 location seems to be
>>>"eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722"
>>>
>>>???
>>>
>>>EdB
>>>
>>>
>>>
>>>On Tue, Jul 30, 2013 at 8:50 AM, OmPrakash Muppirala
>>> wrote:
 Same here.  Getting a "*Server Problem**Unknown server error.* Try
again or
 contact the server administrator."

 Also, the folder in my FB installation
 is eclipse\plugins\com.adobe.flexbuilder.codemodel_4.7.0.349722

 This is on Windows 7, FB 4.7 64-bit

 Thanks,
 Om

 On Mon, Jul 29, 2013 at 11:22 PM, Swen van Zanten 
wrote:

> I have tried downloading the file.. but the browser says I have no
> permission..
> Also in your readme the folder that is pointed to is:
> eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
> But on my machine it is:
> eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722
>
> Regards,
>
> SWEN VAN ZANTEN
> Hoofdstraat 160
> 2171 BL, Sassenheim
>
> Op 30 jul. 2013, om 08:04 heeft Alex Harui  het
> volgende geschreven:
>
> > Even later update on the "New Project" issue:
> >
> > I think I have successfully patched a jar in FlashBuilder to get
>around
> > this problem.
> >
> > The patched jar and a readme is up on
> > http://people.apache.org/~aharui/FlashBuilder/
> >
> > Can a few folks try it so we know it works?  I think it will only
>work
> > with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do
>next.
> >
> > -Alex
> >
> > On 7/29/13 5:45 PM, "Alex Harui"  wrote:
> >
> >> Latest update on the "New Project" issue:
> >>
> >> I think I've found the offending code for real this time.  There is
>code
> >> for a version check that checks that the Flex version is less than
>5.0.0
> >> by doing:
> >>
> >>  major * 100 + minor * 10 + micro
> >>
> >> This means that we don't have the option to change to Apache Flex
>5.0.0
> to
> >> get around this problem, and further means that someday when we
>really
> >> mean to do 5.0 we'll have this problem again.
> >>
> >> There is a class called MXMLVersion2009.java that creates an
>instance of
> >> org.osgi.Framework.Version like this:
> >>
> >>   init(..., ...,
> >>new Version(4,5,0), new Version(5,0,0), new
>Version(4,0,0));
> >>
> >> It looks like the expectation was that these versions would get
>updated
> >> when FB had synchronized releases with Adobe Flex SDKs.  We need to
>go
> in
> >> an change that 5 to something larger somehow.
> >>
> >>
> >> I am passing the same information on to the FB team at Adobe.
> >>
> >> -Alex
> >>
> >> On 7/29/13 7:46 AM, "Scott Guthmann" 
>wrote:
> >>
>  I am hoping we're going to release something other than RC3 which
> means
>  we have a few more days before we would release.  Here's my
>latest
>  update on the 3 issues:
> 
>  1) ResourceModule via FlashVars:  Yes it affects a small
>population of
>  the total Flex SWFs in the world, but at least two of folks who
>took
> the
>  time to try the RC found it.  I have a fix ready to go.
>  2) This FB Issue.  I am trying to get a response from the FB
>team.
>  And
>  I'm looking through their source to try to find the actual cause.
> If
> we
>  cut another RC, we should at minimum update the release notes in
>the
> > kits themselves to describe this issue and its workaround.  But
>maybe
> > by the time we get the next RC ready we'll have more
>information.
>  3) The Ilist issue.  The bug author's workaround was to stop
>using
>  DataList.  Not everyone has the luxury of doing that, so IMO, we
> really
>  don't have a workaround.  And this will affect LCDS customers.  I
> think
>  we >should revert the change to Ilist, but we don't have to
>revert the
>  change to ListCollectionView.
> 
>  So, I would prefer we cut another RC at least to address #1 and
>#3,
> and
>  maybe we'll come up with a better plan for #2 during that time.
> 
>  -Alex
> >>>
> >>> To 

Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Alex Harui
OK, I think I've fixed the permissions.  Let me know if you have a problem
using it.

-Alex

On 7/30/13 12:23 AM, "Alex Harui"  wrote:

>OK, my bad on the folder name.  Updated the readme.
>
>Anybody know what permission I would have to change to allow the jar to be
>downloaded?
>
>
>On 7/29/13 11:57 PM, "Erik de Bruin"  wrote:
>
>>Same here:
>>
>>Permission error on the download and the FB 4.7 location seems to be
>>"eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722"
>>
>>???
>>
>>EdB
>>
>>
>>
>>On Tue, Jul 30, 2013 at 8:50 AM, OmPrakash Muppirala
>> wrote:
>>> Same here.  Getting a "*Server Problem**Unknown server error.* Try
>>>again or
>>> contact the server administrator."
>>>
>>> Also, the folder in my FB installation
>>> is eclipse\plugins\com.adobe.flexbuilder.codemodel_4.7.0.349722
>>>
>>> This is on Windows 7, FB 4.7 64-bit
>>>
>>> Thanks,
>>> Om
>>>
>>> On Mon, Jul 29, 2013 at 11:22 PM, Swen van Zanten 
>>>wrote:
>>>
 I have tried downloading the file.. but the browser says I have no
 permission..
 Also in your readme the folder that is pointed to is:
 eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
 But on my machine it is:
 eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722

 Regards,

 SWEN VAN ZANTEN
 Hoofdstraat 160
 2171 BL, Sassenheim

 Op 30 jul. 2013, om 08:04 heeft Alex Harui  het
 volgende geschreven:

 > Even later update on the "New Project" issue:
 >
 > I think I have successfully patched a jar in FlashBuilder to get
around
 > this problem.
 >
 > The patched jar and a readme is up on
 > http://people.apache.org/~aharui/FlashBuilder/
 >
 > Can a few folks try it so we know it works?  I think it will only
work
 > with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do
next.
 >
 > -Alex
 >
 > On 7/29/13 5:45 PM, "Alex Harui"  wrote:
 >
 >> Latest update on the "New Project" issue:
 >>
 >> I think I've found the offending code for real this time.  There is
code
 >> for a version check that checks that the Flex version is less than
5.0.0
 >> by doing:
 >>
 >>  major * 100 + minor * 10 + micro
 >>
 >> This means that we don't have the option to change to Apache Flex
5.0.0
 to
 >> get around this problem, and further means that someday when we
really
 >> mean to do 5.0 we'll have this problem again.
 >>
 >> There is a class called MXMLVersion2009.java that creates an
instance of
 >> org.osgi.Framework.Version like this:
 >>
 >>   init(..., ...,
 >>new Version(4,5,0), new Version(5,0,0), new
Version(4,0,0));
 >>
 >> It looks like the expectation was that these versions would get
updated
 >> when FB had synchronized releases with Adobe Flex SDKs.  We need to
go
 in
 >> an change that 5 to something larger somehow.
 >>
 >>
 >> I am passing the same information on to the FB team at Adobe.
 >>
 >> -Alex
 >>
 >> On 7/29/13 7:46 AM, "Scott Guthmann" 
wrote:
 >>
  I am hoping we're going to release something other than RC3 which
 means
  we have a few more days before we would release.  Here's my
latest
  update on the 3 issues:
 
  1) ResourceModule via FlashVars:  Yes it affects a small
population of
  the total Flex SWFs in the world, but at least two of folks who
took
 the
  time to try the RC found it.  I have a fix ready to go.
  2) This FB Issue.  I am trying to get a response from the FB
team.
  And
  I'm looking through their source to try to find the actual cause.
 If
 we
  cut another RC, we should at minimum update the release notes in
the
 > kits themselves to describe this issue and its workaround.  But
maybe
 > by the time we get the next RC ready we'll have more
information.
  3) The Ilist issue.  The bug author's workaround was to stop
using
  DataList.  Not everyone has the luxury of doing that, so IMO, we
 really
  don't have a workaround.  And this will affect LCDS customers.  I
 think
  we >should revert the change to Ilist, but we don't have to
revert the
  change to ListCollectionView.
 
  So, I would prefer we cut another RC at least to address #1 and
#3,
 and
  maybe we'll come up with a better plan for #2 during that time.
 
  -Alex
 >>>
 >>> To release or not to release - that is the question
 >>> +1 to Alex's approach. Strategically, it is better to release
something
 >>> that provides developers with a good user experience. Releasing
 something
 >>> that requires deletion of files to work right or a patch to
several of
 >>> the IDEs tha

Re: Apache Flex 4.10.0 Release

2013-07-30 Thread João Fernandes
Eric could you try to clean the workspace cache[1] or eventually try a new
workspace?
I can't confirm if it would solve the problem because I'm moved to IntelliJ.


[1] {workspace}/.metadata/.plugins/com.adobe.flexbuilder.codemodel


On 30 July 2013 07:57, Erik de Bruin  wrote:

> Same here:
>
> Permission error on the download and the FB 4.7 location seems to be
> "eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722"
>
> ???
>
> EdB
>
>
>
> On Tue, Jul 30, 2013 at 8:50 AM, OmPrakash Muppirala
>  wrote:
> > Same here.  Getting a "*Server Problem**Unknown server error.* Try again
> or
> > contact the server administrator."
> >
> > Also, the folder in my FB installation
> > is eclipse\plugins\com.adobe.flexbuilder.codemodel_4.7.0.349722
> >
> > This is on Windows 7, FB 4.7 64-bit
> >
> > Thanks,
> > Om
> >
> > On Mon, Jul 29, 2013 at 11:22 PM, Swen van Zanten 
> wrote:
> >
> >> I have tried downloading the file.. but the browser says I have no
> >> permission..
> >> Also in your readme the folder that is pointed to is:
> >> eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
> >> But on my machine it is:
> >> eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722
> >>
> >> Regards,
> >>
> >> SWEN VAN ZANTEN
> >> Hoofdstraat 160
> >> 2171 BL, Sassenheim
> >>
> >> Op 30 jul. 2013, om 08:04 heeft Alex Harui  het
> >> volgende geschreven:
> >>
> >> > Even later update on the "New Project" issue:
> >> >
> >> > I think I have successfully patched a jar in FlashBuilder to get
> around
> >> > this problem.
> >> >
> >> > The patched jar and a readme is up on
> >> > http://people.apache.org/~aharui/FlashBuilder/
> >> >
> >> > Can a few folks try it so we know it works?  I think it will only work
> >> > with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do
> next.
> >> >
> >> > -Alex
> >> >
> >> > On 7/29/13 5:45 PM, "Alex Harui"  wrote:
> >> >
> >> >> Latest update on the "New Project" issue:
> >> >>
> >> >> I think I've found the offending code for real this time.  There is
> code
> >> >> for a version check that checks that the Flex version is less than
> 5.0.0
> >> >> by doing:
> >> >>
> >> >>  major * 100 + minor * 10 + micro
> >> >>
> >> >> This means that we don't have the option to change to Apache Flex
> 5.0.0
> >> to
> >> >> get around this problem, and further means that someday when we
> really
> >> >> mean to do 5.0 we'll have this problem again.
> >> >>
> >> >> There is a class called MXMLVersion2009.java that creates an
> instance of
> >> >> org.osgi.Framework.Version like this:
> >> >>
> >> >>   init(..., ...,
> >> >>new Version(4,5,0), new Version(5,0,0), new
> Version(4,0,0));
> >> >>
> >> >> It looks like the expectation was that these versions would get
> updated
> >> >> when FB had synchronized releases with Adobe Flex SDKs.  We need to
> go
> >> in
> >> >> an change that 5 to something larger somehow.
> >> >>
> >> >>
> >> >> I am passing the same information on to the FB team at Adobe.
> >> >>
> >> >> -Alex
> >> >>
> >> >> On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:
> >> >>
> >>  I am hoping we're going to release something other than RC3 which
> >> means
> >>  we have a few more days before we would release.  Here's my latest
> >>  update on the 3 issues:
> >> 
> >>  1) ResourceModule via FlashVars:  Yes it affects a small
> population of
> >>  the total Flex SWFs in the world, but at least two of folks who
> took
> >> the
> >>  time to try the RC found it.  I have a fix ready to go.
> >>  2) This FB Issue.  I am trying to get a response from the FB team.
> >>  And
> >>  I'm looking through their source to try to find the actual cause.
>  If
> >> we
> >>  cut another RC, we should at minimum update the release notes in
> the
> >> > kits themselves to describe this issue and its workaround.  But
> maybe
> >> > by the time we get the next RC ready we'll have more information.
> >>  3) The Ilist issue.  The bug author's workaround was to stop using
> >>  DataList.  Not everyone has the luxury of doing that, so IMO, we
> >> really
> >>  don't have a workaround.  And this will affect LCDS customers.  I
> >> think
> >>  we >should revert the change to Ilist, but we don't have to revert
> the
> >>  change to ListCollectionView.
> >> 
> >>  So, I would prefer we cut another RC at least to address #1 and #3,
> >> and
> >>  maybe we'll come up with a better plan for #2 during that time.
> >> 
> >>  -Alex
> >> >>>
> >> >>> To release or not to release - that is the question
> >> >>> +1 to Alex's approach. Strategically, it is better to release
> something
> >> >>> that provides developers with a good user experience. Releasing
> >> something
> >> >>> that requires deletion of files to work right or a patch to several
> of
> >> >>> the IDEs that are standard is a bad idea. Some of the goals we
> should
> >> >>> have when we test to determine if the RC should move fo

Re: Apache Flex 4.10.0 Release

2013-07-30 Thread Alex Harui
OK, my bad on the folder name.  Updated the readme.

Anybody know what permission I would have to change to allow the jar to be
downloaded?


On 7/29/13 11:57 PM, "Erik de Bruin"  wrote:

>Same here:
>
>Permission error on the download and the FB 4.7 location seems to be
>"eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722"
>
>???
>
>EdB
>
>
>
>On Tue, Jul 30, 2013 at 8:50 AM, OmPrakash Muppirala
> wrote:
>> Same here.  Getting a "*Server Problem**Unknown server error.* Try
>>again or
>> contact the server administrator."
>>
>> Also, the folder in my FB installation
>> is eclipse\plugins\com.adobe.flexbuilder.codemodel_4.7.0.349722
>>
>> This is on Windows 7, FB 4.7 64-bit
>>
>> Thanks,
>> Om
>>
>> On Mon, Jul 29, 2013 at 11:22 PM, Swen van Zanten 
>>wrote:
>>
>>> I have tried downloading the file.. but the browser says I have no
>>> permission..
>>> Also in your readme the folder that is pointed to is:
>>> eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
>>> But on my machine it is:
>>> eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722
>>>
>>> Regards,
>>>
>>> SWEN VAN ZANTEN
>>> Hoofdstraat 160
>>> 2171 BL, Sassenheim
>>>
>>> Op 30 jul. 2013, om 08:04 heeft Alex Harui  het
>>> volgende geschreven:
>>>
>>> > Even later update on the "New Project" issue:
>>> >
>>> > I think I have successfully patched a jar in FlashBuilder to get
>>>around
>>> > this problem.
>>> >
>>> > The patched jar and a readme is up on
>>> > http://people.apache.org/~aharui/FlashBuilder/
>>> >
>>> > Can a few folks try it so we know it works?  I think it will only
>>>work
>>> > with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do
>>>next.
>>> >
>>> > -Alex
>>> >
>>> > On 7/29/13 5:45 PM, "Alex Harui"  wrote:
>>> >
>>> >> Latest update on the "New Project" issue:
>>> >>
>>> >> I think I've found the offending code for real this time.  There is
>>>code
>>> >> for a version check that checks that the Flex version is less than
>>>5.0.0
>>> >> by doing:
>>> >>
>>> >>  major * 100 + minor * 10 + micro
>>> >>
>>> >> This means that we don't have the option to change to Apache Flex
>>>5.0.0
>>> to
>>> >> get around this problem, and further means that someday when we
>>>really
>>> >> mean to do 5.0 we'll have this problem again.
>>> >>
>>> >> There is a class called MXMLVersion2009.java that creates an
>>>instance of
>>> >> org.osgi.Framework.Version like this:
>>> >>
>>> >>   init(..., ...,
>>> >>new Version(4,5,0), new Version(5,0,0), new
>>>Version(4,0,0));
>>> >>
>>> >> It looks like the expectation was that these versions would get
>>>updated
>>> >> when FB had synchronized releases with Adobe Flex SDKs.  We need to
>>>go
>>> in
>>> >> an change that 5 to something larger somehow.
>>> >>
>>> >>
>>> >> I am passing the same information on to the FB team at Adobe.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:
>>> >>
>>>  I am hoping we're going to release something other than RC3 which
>>> means
>>>  we have a few more days before we would release.  Here's my latest
>>>  update on the 3 issues:
>>> 
>>>  1) ResourceModule via FlashVars:  Yes it affects a small
>>>population of
>>>  the total Flex SWFs in the world, but at least two of folks who
>>>took
>>> the
>>>  time to try the RC found it.  I have a fix ready to go.
>>>  2) This FB Issue.  I am trying to get a response from the FB team.
>>>  And
>>>  I'm looking through their source to try to find the actual cause.
>>> If
>>> we
>>>  cut another RC, we should at minimum update the release notes in
>>>the
>>> > kits themselves to describe this issue and its workaround.  But
>>>maybe
>>> > by the time we get the next RC ready we'll have more information.
>>>  3) The Ilist issue.  The bug author's workaround was to stop using
>>>  DataList.  Not everyone has the luxury of doing that, so IMO, we
>>> really
>>>  don't have a workaround.  And this will affect LCDS customers.  I
>>> think
>>>  we >should revert the change to Ilist, but we don't have to
>>>revert the
>>>  change to ListCollectionView.
>>> 
>>>  So, I would prefer we cut another RC at least to address #1 and
>>>#3,
>>> and
>>>  maybe we'll come up with a better plan for #2 during that time.
>>> 
>>>  -Alex
>>> >>>
>>> >>> To release or not to release - that is the question
>>> >>> +1 to Alex's approach. Strategically, it is better to release
>>>something
>>> >>> that provides developers with a good user experience. Releasing
>>> something
>>> >>> that requires deletion of files to work right or a patch to
>>>several of
>>> >>> the IDEs that are standard is a bad idea. Some of the goals we
>>>should
>>> >>> have when we test to determine if the RC should move forward: 1)
>>>Does
>>> the
>>> >>> SDK RC work smoothly on mac, windows, and Linux? 2) Does the AIR
>>> >>> installer work smoothly on mac, windows, and linux? 3) do the
>>>binary
>>> >>>

Re: Apache Flex 4.10.0 Release

2013-07-30 Thread João Fernandes
I'm with Erik here too, fix it in develop + branch both issues.


On 30 July 2013 07:57, Erik de Bruin  wrote:

> Same here:
>
> Permission error on the download and the FB 4.7 location seems to be
> "eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722"
>
> ???
>
> EdB
>
>
>
> On Tue, Jul 30, 2013 at 8:50 AM, OmPrakash Muppirala
>  wrote:
> > Same here.  Getting a "*Server Problem**Unknown server error.* Try again
> or
> > contact the server administrator."
> >
> > Also, the folder in my FB installation
> > is eclipse\plugins\com.adobe.flexbuilder.codemodel_4.7.0.349722
> >
> > This is on Windows 7, FB 4.7 64-bit
> >
> > Thanks,
> > Om
> >
> > On Mon, Jul 29, 2013 at 11:22 PM, Swen van Zanten 
> wrote:
> >
> >> I have tried downloading the file.. but the browser says I have no
> >> permission..
> >> Also in your readme the folder that is pointed to is:
> >> eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
> >> But on my machine it is:
> >> eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722
> >>
> >> Regards,
> >>
> >> SWEN VAN ZANTEN
> >> Hoofdstraat 160
> >> 2171 BL, Sassenheim
> >>
> >> Op 30 jul. 2013, om 08:04 heeft Alex Harui  het
> >> volgende geschreven:
> >>
> >> > Even later update on the "New Project" issue:
> >> >
> >> > I think I have successfully patched a jar in FlashBuilder to get
> around
> >> > this problem.
> >> >
> >> > The patched jar and a readme is up on
> >> > http://people.apache.org/~aharui/FlashBuilder/
> >> >
> >> > Can a few folks try it so we know it works?  I think it will only work
> >> > with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do
> next.
> >> >
> >> > -Alex
> >> >
> >> > On 7/29/13 5:45 PM, "Alex Harui"  wrote:
> >> >
> >> >> Latest update on the "New Project" issue:
> >> >>
> >> >> I think I've found the offending code for real this time.  There is
> code
> >> >> for a version check that checks that the Flex version is less than
> 5.0.0
> >> >> by doing:
> >> >>
> >> >>  major * 100 + minor * 10 + micro
> >> >>
> >> >> This means that we don't have the option to change to Apache Flex
> 5.0.0
> >> to
> >> >> get around this problem, and further means that someday when we
> really
> >> >> mean to do 5.0 we'll have this problem again.
> >> >>
> >> >> There is a class called MXMLVersion2009.java that creates an
> instance of
> >> >> org.osgi.Framework.Version like this:
> >> >>
> >> >>   init(..., ...,
> >> >>new Version(4,5,0), new Version(5,0,0), new
> Version(4,0,0));
> >> >>
> >> >> It looks like the expectation was that these versions would get
> updated
> >> >> when FB had synchronized releases with Adobe Flex SDKs.  We need to
> go
> >> in
> >> >> an change that 5 to something larger somehow.
> >> >>
> >> >>
> >> >> I am passing the same information on to the FB team at Adobe.
> >> >>
> >> >> -Alex
> >> >>
> >> >> On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:
> >> >>
> >>  I am hoping we're going to release something other than RC3 which
> >> means
> >>  we have a few more days before we would release.  Here's my latest
> >>  update on the 3 issues:
> >> 
> >>  1) ResourceModule via FlashVars:  Yes it affects a small
> population of
> >>  the total Flex SWFs in the world, but at least two of folks who
> took
> >> the
> >>  time to try the RC found it.  I have a fix ready to go.
> >>  2) This FB Issue.  I am trying to get a response from the FB team.
> >>  And
> >>  I'm looking through their source to try to find the actual cause.
>  If
> >> we
> >>  cut another RC, we should at minimum update the release notes in
> the
> >> > kits themselves to describe this issue and its workaround.  But
> maybe
> >> > by the time we get the next RC ready we'll have more information.
> >>  3) The Ilist issue.  The bug author's workaround was to stop using
> >>  DataList.  Not everyone has the luxury of doing that, so IMO, we
> >> really
> >>  don't have a workaround.  And this will affect LCDS customers.  I
> >> think
> >>  we >should revert the change to Ilist, but we don't have to revert
> the
> >>  change to ListCollectionView.
> >> 
> >>  So, I would prefer we cut another RC at least to address #1 and #3,
> >> and
> >>  maybe we'll come up with a better plan for #2 during that time.
> >> 
> >>  -Alex
> >> >>>
> >> >>> To release or not to release - that is the question
> >> >>> +1 to Alex's approach. Strategically, it is better to release
> something
> >> >>> that provides developers with a good user experience. Releasing
> >> something
> >> >>> that requires deletion of files to work right or a patch to several
> of
> >> >>> the IDEs that are standard is a bad idea. Some of the goals we
> should
> >> >>> have when we test to determine if the RC should move forward: 1)
> Does
> >> the
> >> >>> SDK RC work smoothly on mac, windows, and Linux? 2) Does the AIR
> >> >>> installer work smoothly on mac, windows, and linux? 3) do t

Re: Apache Flex 4.10.0 Release

2013-07-29 Thread Erik de Bruin
Same here:

Permission error on the download and the FB 4.7 location seems to be
"eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722"

???

EdB



On Tue, Jul 30, 2013 at 8:50 AM, OmPrakash Muppirala
 wrote:
> Same here.  Getting a "*Server Problem**Unknown server error.* Try again or
> contact the server administrator."
>
> Also, the folder in my FB installation
> is eclipse\plugins\com.adobe.flexbuilder.codemodel_4.7.0.349722
>
> This is on Windows 7, FB 4.7 64-bit
>
> Thanks,
> Om
>
> On Mon, Jul 29, 2013 at 11:22 PM, Swen van Zanten  wrote:
>
>> I have tried downloading the file.. but the browser says I have no
>> permission..
>> Also in your readme the folder that is pointed to is:
>> eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
>> But on my machine it is:
>> eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722
>>
>> Regards,
>>
>> SWEN VAN ZANTEN
>> Hoofdstraat 160
>> 2171 BL, Sassenheim
>>
>> Op 30 jul. 2013, om 08:04 heeft Alex Harui  het
>> volgende geschreven:
>>
>> > Even later update on the "New Project" issue:
>> >
>> > I think I have successfully patched a jar in FlashBuilder to get around
>> > this problem.
>> >
>> > The patched jar and a readme is up on
>> > http://people.apache.org/~aharui/FlashBuilder/
>> >
>> > Can a few folks try it so we know it works?  I think it will only work
>> > with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do next.
>> >
>> > -Alex
>> >
>> > On 7/29/13 5:45 PM, "Alex Harui"  wrote:
>> >
>> >> Latest update on the "New Project" issue:
>> >>
>> >> I think I've found the offending code for real this time.  There is code
>> >> for a version check that checks that the Flex version is less than 5.0.0
>> >> by doing:
>> >>
>> >>  major * 100 + minor * 10 + micro
>> >>
>> >> This means that we don't have the option to change to Apache Flex 5.0.0
>> to
>> >> get around this problem, and further means that someday when we really
>> >> mean to do 5.0 we'll have this problem again.
>> >>
>> >> There is a class called MXMLVersion2009.java that creates an instance of
>> >> org.osgi.Framework.Version like this:
>> >>
>> >>   init(..., ...,
>> >>new Version(4,5,0), new Version(5,0,0), new Version(4,0,0));
>> >>
>> >> It looks like the expectation was that these versions would get updated
>> >> when FB had synchronized releases with Adobe Flex SDKs.  We need to go
>> in
>> >> an change that 5 to something larger somehow.
>> >>
>> >>
>> >> I am passing the same information on to the FB team at Adobe.
>> >>
>> >> -Alex
>> >>
>> >> On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:
>> >>
>>  I am hoping we're going to release something other than RC3 which
>> means
>>  we have a few more days before we would release.  Here's my latest
>>  update on the 3 issues:
>> 
>>  1) ResourceModule via FlashVars:  Yes it affects a small population of
>>  the total Flex SWFs in the world, but at least two of folks who took
>> the
>>  time to try the RC found it.  I have a fix ready to go.
>>  2) This FB Issue.  I am trying to get a response from the FB team.
>>  And
>>  I'm looking through their source to try to find the actual cause.  If
>> we
>>  cut another RC, we should at minimum update the release notes in the
>> > kits themselves to describe this issue and its workaround.  But maybe
>> > by the time we get the next RC ready we'll have more information.
>>  3) The Ilist issue.  The bug author's workaround was to stop using
>>  DataList.  Not everyone has the luxury of doing that, so IMO, we
>> really
>>  don't have a workaround.  And this will affect LCDS customers.  I
>> think
>>  we >should revert the change to Ilist, but we don't have to revert the
>>  change to ListCollectionView.
>> 
>>  So, I would prefer we cut another RC at least to address #1 and #3,
>> and
>>  maybe we'll come up with a better plan for #2 during that time.
>> 
>>  -Alex
>> >>>
>> >>> To release or not to release - that is the question
>> >>> +1 to Alex's approach. Strategically, it is better to release something
>> >>> that provides developers with a good user experience. Releasing
>> something
>> >>> that requires deletion of files to work right or a patch to several of
>> >>> the IDEs that are standard is a bad idea. Some of the goals we should
>> >>> have when we test to determine if the RC should move forward: 1) Does
>> the
>> >>> SDK RC work smoothly on mac, windows, and Linux? 2) Does the AIR
>> >>> installer work smoothly on mac, windows, and linux? 3) do the binary
>> >>> distributions work smoothly on each of these platforms? 4) Are the
>> manual
>> >>> builds of the SDK and the binary versions supported by the top IDEs:
>> >>> IntelliJ, Flash Builder, Flash Develop, and FDT?
>> >>>
>> >>> My opinion is that we are not adequately evaluating if the RC versions
>> >>> are meeting these developer user experience questions when voting on an
>> >>> them. The

Re: Apache Flex 4.10.0 Release

2013-07-29 Thread OmPrakash Muppirala
Same here.  Getting a "*Server Problem**Unknown server error.* Try again or
contact the server administrator."

Also, the folder in my FB installation
is eclipse\plugins\com.adobe.flexbuilder.codemodel_4.7.0.349722

This is on Windows 7, FB 4.7 64-bit

Thanks,
Om

On Mon, Jul 29, 2013 at 11:22 PM, Swen van Zanten  wrote:

> I have tried downloading the file.. but the browser says I have no
> permission..
> Also in your readme the folder that is pointed to is:
> eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
> But on my machine it is:
> eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722
>
> Regards,
>
> SWEN VAN ZANTEN
> Hoofdstraat 160
> 2171 BL, Sassenheim
>
> Op 30 jul. 2013, om 08:04 heeft Alex Harui  het
> volgende geschreven:
>
> > Even later update on the "New Project" issue:
> >
> > I think I have successfully patched a jar in FlashBuilder to get around
> > this problem.
> >
> > The patched jar and a readme is up on
> > http://people.apache.org/~aharui/FlashBuilder/
> >
> > Can a few folks try it so we know it works?  I think it will only work
> > with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do next.
> >
> > -Alex
> >
> > On 7/29/13 5:45 PM, "Alex Harui"  wrote:
> >
> >> Latest update on the "New Project" issue:
> >>
> >> I think I've found the offending code for real this time.  There is code
> >> for a version check that checks that the Flex version is less than 5.0.0
> >> by doing:
> >>
> >>  major * 100 + minor * 10 + micro
> >>
> >> This means that we don't have the option to change to Apache Flex 5.0.0
> to
> >> get around this problem, and further means that someday when we really
> >> mean to do 5.0 we'll have this problem again.
> >>
> >> There is a class called MXMLVersion2009.java that creates an instance of
> >> org.osgi.Framework.Version like this:
> >>
> >>   init(..., ...,
> >>new Version(4,5,0), new Version(5,0,0), new Version(4,0,0));
> >>
> >> It looks like the expectation was that these versions would get updated
> >> when FB had synchronized releases with Adobe Flex SDKs.  We need to go
> in
> >> an change that 5 to something larger somehow.
> >>
> >>
> >> I am passing the same information on to the FB team at Adobe.
> >>
> >> -Alex
> >>
> >> On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:
> >>
>  I am hoping we're going to release something other than RC3 which
> means
>  we have a few more days before we would release.  Here's my latest
>  update on the 3 issues:
> 
>  1) ResourceModule via FlashVars:  Yes it affects a small population of
>  the total Flex SWFs in the world, but at least two of folks who took
> the
>  time to try the RC found it.  I have a fix ready to go.
>  2) This FB Issue.  I am trying to get a response from the FB team.
>  And
>  I'm looking through their source to try to find the actual cause.  If
> we
>  cut another RC, we should at minimum update the release notes in the
> > kits themselves to describe this issue and its workaround.  But maybe
> > by the time we get the next RC ready we'll have more information.
>  3) The Ilist issue.  The bug author's workaround was to stop using
>  DataList.  Not everyone has the luxury of doing that, so IMO, we
> really
>  don't have a workaround.  And this will affect LCDS customers.  I
> think
>  we >should revert the change to Ilist, but we don't have to revert the
>  change to ListCollectionView.
> 
>  So, I would prefer we cut another RC at least to address #1 and #3,
> and
>  maybe we'll come up with a better plan for #2 during that time.
> 
>  -Alex
> >>>
> >>> To release or not to release - that is the question
> >>> +1 to Alex's approach. Strategically, it is better to release something
> >>> that provides developers with a good user experience. Releasing
> something
> >>> that requires deletion of files to work right or a patch to several of
> >>> the IDEs that are standard is a bad idea. Some of the goals we should
> >>> have when we test to determine if the RC should move forward: 1) Does
> the
> >>> SDK RC work smoothly on mac, windows, and Linux? 2) Does the AIR
> >>> installer work smoothly on mac, windows, and linux? 3) do the binary
> >>> distributions work smoothly on each of these platforms? 4) Are the
> manual
> >>> builds of the SDK and the binary versions supported by the top IDEs:
> >>> IntelliJ, Flash Builder, Flash Develop, and FDT?
> >>>
> >>> My opinion is that we are not adequately evaluating if the RC versions
> >>> are meeting these developer user experience questions when voting on an
> >>> them. The community millions of devs are not as capable of the
> patching &
> >>> work arounds as you guys are. The best marketing you can do is
> creating a
> >>> feature rich product that is easy to use for any skill level - make it
> >>> simple (which is difficult to do).
> >>
> >
>
>


Re: Apache Flex 4.10.0 Release

2013-07-29 Thread Paul Hastings

On 7/30/2013 1:04 PM, Alex Harui wrote:


Can a few folks try it so we know it works?  I think it will only work
with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do next.


just in case you don't already know, this issue shows up in FB4.6 & SDK 4.10.0 
as well.




Re: Apache Flex 4.10.0 Release

2013-07-29 Thread Swen van Zanten
I have tried downloading the file.. but the browser says I have no permission..
Also in your readme the folder that is pointed to is: 
eclipse/plugins/com.adobe.flash.codemodel_4.7.0.349722
But on my machine it is: 
eclipse/plugins/com.adobe.flexbuilder.codemodel_4.7.0.349722

Regards,

SWEN VAN ZANTEN
Hoofdstraat 160
2171 BL, Sassenheim

Op 30 jul. 2013, om 08:04 heeft Alex Harui  het volgende 
geschreven:

> Even later update on the "New Project" issue:
> 
> I think I have successfully patched a jar in FlashBuilder to get around
> this problem.
> 
> The patched jar and a readme is up on
> http://people.apache.org/~aharui/FlashBuilder/
> 
> Can a few folks try it so we know it works?  I think it will only work
> with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do next.
> 
> -Alex
> 
> On 7/29/13 5:45 PM, "Alex Harui"  wrote:
> 
>> Latest update on the "New Project" issue:
>> 
>> I think I've found the offending code for real this time.  There is code
>> for a version check that checks that the Flex version is less than 5.0.0
>> by doing:
>> 
>>  major * 100 + minor * 10 + micro
>> 
>> This means that we don't have the option to change to Apache Flex 5.0.0 to
>> get around this problem, and further means that someday when we really
>> mean to do 5.0 we'll have this problem again.
>> 
>> There is a class called MXMLVersion2009.java that creates an instance of
>> org.osgi.Framework.Version like this:
>> 
>>   init(..., ...,
>>new Version(4,5,0), new Version(5,0,0), new Version(4,0,0));
>> 
>> It looks like the expectation was that these versions would get updated
>> when FB had synchronized releases with Adobe Flex SDKs.  We need to go in
>> an change that 5 to something larger somehow.
>> 
>> 
>> I am passing the same information on to the FB team at Adobe.
>> 
>> -Alex
>> 
>> On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:
>> 
 I am hoping we're going to release something other than RC3 which means
 we have a few more days before we would release.  Here's my latest
 update on the 3 issues:
 
 1) ResourceModule via FlashVars:  Yes it affects a small population of
 the total Flex SWFs in the world, but at least two of folks who took the
 time to try the RC found it.  I have a fix ready to go.
 2) This FB Issue.  I am trying to get a response from the FB team.  And
 I'm looking through their source to try to find the actual cause.  If we
 cut another RC, we should at minimum update the release notes in the
> kits themselves to describe this issue and its workaround.  But maybe
> by the time we get the next RC ready we'll have more information.
 3) The Ilist issue.  The bug author's workaround was to stop using
 DataList.  Not everyone has the luxury of doing that, so IMO, we really
 don't have a workaround.  And this will affect LCDS customers.  I think
 we >should revert the change to Ilist, but we don't have to revert the
 change to ListCollectionView.
 
 So, I would prefer we cut another RC at least to address #1 and #3, and
 maybe we'll come up with a better plan for #2 during that time.
 
 -Alex
>>> 
>>> To release or not to release - that is the question
>>> +1 to Alex's approach. Strategically, it is better to release something
>>> that provides developers with a good user experience. Releasing something
>>> that requires deletion of files to work right or a patch to several of
>>> the IDEs that are standard is a bad idea. Some of the goals we should
>>> have when we test to determine if the RC should move forward: 1) Does the
>>> SDK RC work smoothly on mac, windows, and Linux? 2) Does the AIR
>>> installer work smoothly on mac, windows, and linux? 3) do the binary
>>> distributions work smoothly on each of these platforms? 4) Are the manual
>>> builds of the SDK and the binary versions supported by the top IDEs:
>>> IntelliJ, Flash Builder, Flash Develop, and FDT?
>>> 
>>> My opinion is that we are not adequately evaluating if the RC versions
>>> are meeting these developer user experience questions when voting on an
>>> them. The community millions of devs are not as capable of the patching &
>>> work arounds as you guys are. The best marketing you can do is creating a
>>> feature rich product that is easy to use for any skill level - make it
>>> simple (which is difficult to do).
>> 
> 



Re: Apache Flex 4.10.0 Release

2013-07-29 Thread Alex Harui
Even later update on the "New Project" issue:

I think I have successfully patched a jar in FlashBuilder to get around
this problem.

The patched jar and a readme is up on
http://people.apache.org/~aharui/FlashBuilder/

Can a few folks try it so we know it works?  I think it will only work
with FlashBuilder 4.7 (and not 4.6).  Then we'll discuss what to do next.

-Alex

On 7/29/13 5:45 PM, "Alex Harui"  wrote:

>Latest update on the "New Project" issue:
>
>I think I've found the offending code for real this time.  There is code
>for a version check that checks that the Flex version is less than 5.0.0
>by doing:
>
>   major * 100 + minor * 10 + micro
>
>This means that we don't have the option to change to Apache Flex 5.0.0 to
>get around this problem, and further means that someday when we really
>mean to do 5.0 we'll have this problem again.
>
>There is a class called MXMLVersion2009.java that creates an instance of
>org.osgi.Framework.Version like this:
>
>init(..., ...,
> new Version(4,5,0), new Version(5,0,0), new Version(4,0,0));
>
>It looks like the expectation was that these versions would get updated
>when FB had synchronized releases with Adobe Flex SDKs.  We need to go in
>an change that 5 to something larger somehow.
>
>
>I am passing the same information on to the FB team at Adobe.
>
>-Alex
>
>On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:
>
>>>I am hoping we're going to release something other than RC3 which means
>>>we have a few more days before we would release.  Here's my latest
>>>update on the 3 issues:
>>>
>>>1) ResourceModule via FlashVars:  Yes it affects a small population of
>>>the total Flex SWFs in the world, but at least two of folks who took the
>>>time to try the RC found it.  I have a fix ready to go.
>>>2) This FB Issue.  I am trying to get a response from the FB team.  And
>>>I'm looking through their source to try to find the actual cause.  If we
>>>cut another RC, we should at minimum update the release notes in the
kits themselves to describe this issue and its workaround.  But maybe
by the time we get the next RC ready we'll have more information.
>>>3) The Ilist issue.  The bug author's workaround was to stop using
>>>DataList.  Not everyone has the luxury of doing that, so IMO, we really
>>>don't have a workaround.  And this will affect LCDS customers.  I think
>>>we >should revert the change to Ilist, but we don't have to revert the
>>>change to ListCollectionView.
>>>
>>>So, I would prefer we cut another RC at least to address #1 and #3, and
>>>maybe we'll come up with a better plan for #2 during that time.
>>>
>>>-Alex
>>
>>To release or not to release - that is the question
>>+1 to Alex's approach. Strategically, it is better to release something
>>that provides developers with a good user experience. Releasing something
>>that requires deletion of files to work right or a patch to several of
>>the IDEs that are standard is a bad idea. Some of the goals we should
>>have when we test to determine if the RC should move forward: 1) Does the
>>SDK RC work smoothly on mac, windows, and Linux? 2) Does the AIR
>>installer work smoothly on mac, windows, and linux? 3) do the binary
>>distributions work smoothly on each of these platforms? 4) Are the manual
>>builds of the SDK and the binary versions supported by the top IDEs:
>>IntelliJ, Flash Builder, Flash Develop, and FDT?
>>
>>My opinion is that we are not adequately evaluating if the RC versions
>>are meeting these developer user experience questions when voting on an
>>them. The community millions of devs are not as capable of the patching &
>>work arounds as you guys are. The best marketing you can do is creating a
>>feature rich product that is easy to use for any skill level - make it
>>simple (which is difficult to do).
>



Re: Apache Flex 4.10.0 Release

2013-07-29 Thread Alex Harui
Latest update on the "New Project" issue:

I think I've found the offending code for real this time.  There is code
for a version check that checks that the Flex version is less than 5.0.0
by doing:

major * 100 + minor * 10 + micro

This means that we don't have the option to change to Apache Flex 5.0.0 to
get around this problem, and further means that someday when we really
mean to do 5.0 we'll have this problem again.

There is a class called MXMLVersion2009.java that creates an instance of
org.osgi.Framework.Version like this:

init(..., ...,
 new Version(4,5,0), new Version(5,0,0), new Version(4,0,0));

It looks like the expectation was that these versions would get updated
when FB had synchronized releases with Adobe Flex SDKs.  We need to go in
an change that 5 to something larger somehow.


I am passing the same information on to the FB team at Adobe.

-Alex

On 7/29/13 7:46 AM, "Scott Guthmann"  wrote:

>>I am hoping we're going to release something other than RC3 which means
>>we have a few more days before we would release.  Here's my latest
>>update on the 3 issues:
>>
>>1) ResourceModule via FlashVars:  Yes it affects a small population of
>>the total Flex SWFs in the world, but at least two of folks who took the
>>time to try the RC found it.  I have a fix ready to go.
>>2) This FB Issue.  I am trying to get a response from the FB team.  And
>>I'm looking through their source to try to find the actual cause.  If we
>>cut another RC, we should at minimum update the release notes in the
>>>kits themselves to describe this issue and its workaround.  But maybe
>>>by the time we get the next RC ready we'll have more information.
>>3) The Ilist issue.  The bug author's workaround was to stop using
>>DataList.  Not everyone has the luxury of doing that, so IMO, we really
>>don't have a workaround.  And this will affect LCDS customers.  I think
>>we >should revert the change to Ilist, but we don't have to revert the
>>change to ListCollectionView.
>>
>>So, I would prefer we cut another RC at least to address #1 and #3, and
>>maybe we'll come up with a better plan for #2 during that time.
>>
>>-Alex
>
>To release or not to release - that is the question
>+1 to Alex's approach. Strategically, it is better to release something
>that provides developers with a good user experience. Releasing something
>that requires deletion of files to work right or a patch to several of
>the IDEs that are standard is a bad idea. Some of the goals we should
>have when we test to determine if the RC should move forward: 1) Does the
>SDK RC work smoothly on mac, windows, and Linux? 2) Does the AIR
>installer work smoothly on mac, windows, and linux? 3) do the binary
>distributions work smoothly on each of these platforms? 4) Are the manual
>builds of the SDK and the binary versions supported by the top IDEs:
>IntelliJ, Flash Builder, Flash Develop, and FDT?
>
>My opinion is that we are not adequately evaluating if the RC versions
>are meeting these developer user experience questions when voting on an
>them. The community millions of devs are not as capable of the patching &
>work arounds as you guys are. The best marketing you can do is creating a
>feature rich product that is easy to use for any skill level - make it
>simple (which is difficult to do).



RE: Apache Flex 4.10.0 Release

2013-07-29 Thread Scott Guthmann
>I am hoping we're going to release something other than RC3 which means we 
>have a few more days before we would release.  Here's my latest update on the 
>3 issues:
>
>1) ResourceModule via FlashVars:  Yes it affects a small population of the 
>total Flex SWFs in the world, but at least two of folks who took the time to 
>try the RC found it.  I have a fix ready to go.
>2) This FB Issue.  I am trying to get a response from the FB team.  And I'm 
>looking through their source to try to find the actual cause.  If we cut 
>another RC, we should at minimum update the release notes in the >kits 
>themselves to describe this issue and its workaround.  But maybe by the time 
>we get the next RC ready we'll have more information.
>3) The Ilist issue.  The bug author's workaround was to stop using DataList.  
>Not everyone has the luxury of doing that, so IMO, we really don't have a 
>workaround.  And this will affect LCDS customers.  I think we >should revert 
>the change to Ilist, but we don't have to revert the change to 
>ListCollectionView.
>
>So, I would prefer we cut another RC at least to address #1 and #3, and maybe 
>we'll come up with a better plan for #2 during that time.
>
>-Alex

To release or not to release - that is the question
+1 to Alex's approach. Strategically, it is better to release something that 
provides developers with a good user experience. Releasing something that 
requires deletion of files to work right or a patch to several of the IDEs that 
are standard is a bad idea. Some of the goals we should have when we test to 
determine if the RC should move forward: 1) Does the SDK RC work smoothly on 
mac, windows, and Linux? 2) Does the AIR installer work smoothly on mac, 
windows, and linux? 3) do the binary distributions work smoothly on each of 
these platforms? 4) Are the manual builds of the SDK and the binary versions 
supported by the top IDEs: IntelliJ, Flash Builder, Flash Develop, and FDT?

My opinion is that we are not adequately evaluating if the RC versions are 
meeting these developer user experience questions when voting on an them. The 
community millions of devs are not as capable of the patching & work arounds as 
you guys are. The best marketing you can do is creating a feature rich product 
that is easy to use for any skill level - make it simple (which is difficult to 
do).


Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Erik de Bruin
I'd say 'release' AND 'develop', that way the fixes will be run
through Mustella and the build machine as well as made part of the
release. The 'release' branch doesn't get automatically tested or
build.

EdB



On Mon, Jul 29, 2013 at 7:54 AM, Alex Harui  wrote:
>
>
> On 7/28/13 10:50 PM, "Justin Mclean"  wrote:
>>>If so, I will check them into the release4.10 branch sometime tomorrow
>>> after Europe has had a chance to weigh in on this thread.
>>Why not check in so people can review? That how the system works, commit
>>then review.
> I was hoping there would be consensus on which branch (develop or
> release).  Are you ok if I check into release4.10?
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Alex Harui


On 7/28/13 10:50 PM, "Justin Mclean"  wrote:
>>If so, I will check them into the release4.10 branch sometime tomorrow
>> after Europe has had a chance to weigh in on this thread.
>Why not check in so people can review? That how the system works, commit
>then review.
I was hoping there would be consensus on which branch (develop or
release).  Are you ok if I check into release4.10?



Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Erik de Bruin
+1 on the fix and reverting. Thank you Alex for figuring those out.

I think we should actively prevent the 'New Project' issue from
occurring. All we need to do is change the version number to something
with only single digits. That really couldn't be simpler, could it?
5.0 has my vote.

This is not something people will be able to overlook. It is not an
obscure RTE in a feature few use, will happen each time they create a
new project. Doing nothing but adding a note in the docs will leave a
bad impression and will taint this release and - more importantly -
the still fragile image of the project. People, especially the press
and bloggers, tend to look at the negatives, no matter how awesome the
rest is.

EdB



On Mon, Jul 29, 2013 at 7:07 AM, Alex Harui  wrote:
>
>
> On 7/28/13 9:44 PM, "Justin Mclean"  wrote:
>
>>Hi,
>>
>>> What day do you get in the airplane?
>>Thursday your time.
> OK, do we have consensus on taking both the resource module fix and
> reverting Ilist?
> If so, I will check them into the release4.10 branch sometime tomorrow
> after Europe has had a chance to weigh in on this thread.
>
> Then we have to work out wording for whatever to say about the "New
> Project" issue and put that in the release notes.  I'm thinking we should
> should put in something generic that points to our wiki for the "latest
> news".  That way if we get a patch from Adobe we can update just the wiki.
>
> Thoughts?
> -Alex
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Justin Mclean
Hi,

> OK, do we have consensus on taking both the resource module fix and
> reverting Ilist?
I'm not sure enough people have expressed an option on either issue for 
consensus to be reached.

> If so, I will check them into the release4.10 branch sometime tomorrow
> after Europe has had a chance to weigh in on this thread.
Why not check in so people can review? That how the system works, commit then 
review.

Justin

Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Alex Harui


On 7/28/13 9:44 PM, "Justin Mclean"  wrote:

>Hi,
>
>> What day do you get in the airplane?
>Thursday your time.
OK, do we have consensus on taking both the resource module fix and
reverting Ilist?
If so, I will check them into the release4.10 branch sometime tomorrow
after Europe has had a chance to weigh in on this thread.

Then we have to work out wording for whatever to say about the "New
Project" issue and put that in the release notes.  I'm thinking we should
should put in something generic that points to our wiki for the "latest
news".  That way if we get a patch from Adobe we can update just the wiki.

Thoughts?
-Alex



Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Justin Mclean
Hi,

> What day do you get in the airplane? 
Thursday your time.

Justin


Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Alex Harui


On 7/28/13 9:15 PM, "Justin Mclean"  wrote:

>Hi,
>
>> I am hoping we're going to release something other than RC3 which means
>>we
>> have a few more days before we would release.
>
>2 day + 3 days (to vote) = 5 day minimum when means a minimal of over a
>week since the vote passed. Do you really think we should delay that long?
Yes, folks on the mailing list are complaining of #1 and #3.  I think it
would be bad PR to release with these issues.
>
>Just we aware that will overlap travel plans and 360 stack so there may
>be a further delays.
What day do you get in the airplane?  We might have enough time to get
this out before 360|Stack starts.

-Alex



Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Justin Mclean
Hi,

> I am hoping we're going to release something other than RC3 which means we
> have a few more days before we would release.

2 day + 3 days (to vote) = 5 day minimum when means a minimal of over a week 
since the vote passed. Do you really think we should delay that long?

Just we aware that will overlap travel plans and 360 stack so there may be a 
further delays.

Justin

Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Alex Harui


On 7/28/13 7:57 PM, "OmPrakash Muppirala"  wrote:
>I really think that it is not fair for us to delay the release just
>because
>of this FB bug.
I am hoping we're going to release something other than RC3 which means we
have a few more days before we would release.  Here's my latest update on
the 3 issues:

1) ResourceModule via FlashVars:  Yes it affects a small population of the
total Flex SWFs in the world, but at least two of folks who took the time
to try the RC found it.  I have a fix ready to go.
2) This FB Issue.  I am trying to get a response from the FB team.  And
I'm looking through their source to try to find the actual cause.  If we
cut another RC, we should at minimum update the release notes in the kits
themselves to describe this issue and its workaround.  But maybe by the
time we get the next RC ready we'll have more information.
3) The Ilist issue.  The bug author's workaround was to stop using
DataList.  Not everyone has the luxury of doing that, so IMO, we really
don't have a workaround.  And this will affect LCDS customers.  I think we
should revert the change to Ilist, but we don't have to revert the change
to ListCollectionView.

So, I would prefer we cut another RC at least to address #1 and #3, and
maybe we'll come up with a better plan for #2 during that time.

-Alex



Re: Apache Flex 4.10.0 Release

2013-07-28 Thread OmPrakash Muppirala
On Jul 28, 2013 7:37 PM, "Justin Mclean"  wrote:
>
> Hi,
>
> > Hi Justin, what say Adobe about this?
> Been no official response from Adobe but I wouldn't really expect one, we
have to submit a bug in there bug base and it may or may not get fixed at
some time in the future. I can't see them fixing it and releasing a patch
in under a month. Pure speculation happy to be proven wrong there. When was
the last update/patch to Flash builder released by Adobe?
>
> Thanks,
> Justin

I vote for releasing as 4.10 and adding a big note in our README and
website about this issue.  So far, the workaround seems to be very simple -
just delete the offending attribute (layout='absolute') and get going.  We
can also add a technote instructing FB users to change the version in
flex-sdk-description.xml to get rid of this problem.

We can file a bug with Adobe and see when they would fix the issue.  There
is a reasonable chance that they would fix this issue sooner than later.

I really think that it is not fair for us to delay the release just because
of this FB bug.

Thanks,
Om


Re: Apache Flex 4.10.0 Release

2013-07-28 Thread Justin Mclean
Hi,

> Hi Justin, what say Adobe about this? 
Been no official response from Adobe but I wouldn't really expect one, we have 
to submit a bug in there bug base and it may or may not get fixed at some time 
in the future. I can't see them fixing it and releasing a patch in under a 
month. Pure speculation happy to be proven wrong there. When was the last 
update/patch to Flash builder released by Adobe?

Thanks,
Justin

RE: Apache Flex 4.10.0 Release

2013-07-28 Thread FRANKLIN GARZON
Hi Justin, what say Adobe about this? 


Franklin Garzón
 
Regional Development Manager

MCITP  Microsoft SQLServer

 
*Si el hombre dejara de aprender entonces dejaría de existir*
 
094496862
 
 

> From: jus...@classsoftware.com
> Subject: Apache Flex 4.10.0 Release
> Date: Mon, 29 Jul 2013 11:19:45 +1000
> To: dev@flex.apache.org
> 
> Hi,
> 
> So far the only consensus (from those who have been vocal) is not to release 
> the voted on RC3 but:
> - We don't seem to have a solution the the Flash Builder version issue other 
> than changing version number to single digits.
> - The code for the release module issues hasn't been checked in.
> 
> Are there any other issues outstanding? Someone mentioned a FDT issue but I'm 
> not 100% what can be done there either.
> 
> If we change the version (to 4.9.5 say), we'll need to change 
> READMEs/RELEASE_NOTES, JIRA tags, Version.as files, announcement/press 
> release and probably a few other things.
> 
> Thanks,
> Justin
  

Apache Flex 4.10.0 Release

2013-07-28 Thread Justin Mclean
Hi,

So far the only consensus (from those who have been vocal) is not to release 
the voted on RC3 but:
- We don't seem to have a solution the the Flash Builder version issue other 
than changing version number to single digits.
- The code for the release module issues hasn't been checked in.

Are there any other issues outstanding? Someone mentioned a FDT issue but I'm 
not 100% what can be done there either.

If we change the version (to 4.9.5 say), we'll need to change 
READMEs/RELEASE_NOTES, JIRA tags, Version.as files, announcement/press release 
and probably a few other things.

Thanks,
Justin

Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Erik de Bruin
Can you please add this information to the JIRA ticket?

Thanks,

EdB



On Thu, Jul 25, 2013 at 10:57 AM, Jagan Langa Sami Durai
 wrote:
> Hi,
>
> Following is the ANT script snippet used to build my app. I have marked the
> locale = "" because we tend to load them at run time. since our application
> support multi-language and the language is decided at the time user log's
> in. red color highlights might give you guys a clue to corner the issue.
>
>  file="${ROOT}/src/@{app}.mxml"
> output="@{dest}/@{app}.swf"
> allow-source-path-overlap="true"
> link-report="@{dest}/${LINK_REPORT_XML}"
> *static-rsls="false" *
> optimize="true"
> services="@{services}"
> incremental="false" fork="true">
>
>  And This is how we set the locale to the SWF in the html wrapper
>
>  flashvars.localeChain = "en_US";
>  flashvars.resourceModuleURLs = "locale/en_US/strings.swf";
>
> *
> Regards,
> S. Jagan  Langa* *|* *Team Lead*
> *Sybrant Technologies Pvt Ltd*
> *
> *
> Mobile: +91 98430 50897
> Skype: seesamjagan
> --
>
> In The Media:
> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
> **
>
> * *
>
> *About Sybrant:*
>
> *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
> India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
> recognized for working with our clients right from the product
> conceptualization till the execution stage offering end-to-end solutions
> that sets us apart from other firms in this space. Right from developing a
> learning management system for a French company to helping a Non-Profit
> with a Mobile application till developing UX for a IT firm, Sybrant is
> known for delighting Customers”*
>
> --
>
>
> 2013/7/25 Erik de Bruin 
>
>> Yes, Alex is looking into it... He left a comment on the JIRA ticket
>> asking for a test case and the compiler settings used. Can you provide
>> that, please?
>>
>> EdB
>>
>>
>>
>> On Thu, Jul 25, 2013 at 10:19 AM, Jagan Langa Sami Durai
>>  wrote:
>> > Hi
>> >
>> >
>> > Any plan to fix this issue [1] in this release?
>> >
>> >
>> > [1] https://issues.apache.org/jira/browse/FLEX-33632
>> >
>> >
>> >
>> >
>> > *
>> > Regards,
>> > S. Jagan  Langa* *|* *Team Lead*
>> > *Sybrant Technologies Pvt Ltd*
>> > *
>> > *
>> > Mobile: +91 98430 50897
>> > Skype: seesamjagan
>> >
>> --
>> >
>> > In The Media:
>> >
>> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
>> > **
>> >
>> > * *
>> >
>> > *About Sybrant:*
>> >
>> > *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
>> > India too, leverage Sybrant’s expertise for their Web & UIUX needs. We
>> are
>> > recognized for working with our clients right from the product
>> > conceptualization till the execution stage offering end-to-end solutions
>> > that sets us apart from other firms in this space. Right from developing
>> a
>> > learning management system for a French company to helping a Non-Profit
>> > with a Mobile application till developing UX for a IT firm, Sybrant is
>> > known for delighting Customers”*
>> >
>> >
>> --
>> >
>> >
>> > 2013/7/25 Erik de Bruin 
>> >
>> >> I don't see Alex's vote anywhere yet... In the discuss thread he
>> >> announced was going to check on FLEX-33632. I agree with him that if
>> >> it checks out that it is indeed an issue, it would be a regression
>> >> serious enough to warrant immediate fixing.
>> >>
>> >> Just to be sure, I'll hold the release by changing my vote to:
>> >>
>> >> -1 (binding)
>> >>
>> >> If Alex dismisses FLEX-33632, you may consider my vote changed back to
>> >> the original +1 (binding) - just in case my timezone is sleeping when
>> >> you want to cut the release. If he needs to fix it, we need another RC
>> >> and a new vote :-)
>> >>
>> >> Sorry about this and thanks for your patience,
>> >>
>> >> EdB
>> >>
>> >>
>> >>
>> >> On Thu, Jul 25, 2013 at 9:37 AM, Justin Mclean <
>> jus...@classsoftware.com>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > 72 hours are just about up - final chance for anyone have any
>> objections
>> >> for this becoming a release.
>> >> >
>> >> > Thanks,
>> >> > Justin
>> >>
>> >>
>> >>
>> >> --
>> >> Ix Multimedia Software
>> >>
>> >> Jan Luykenstraat 27
>> >> 3521 VB Utrecht
>> >>
>> >> T. 06-51952295
>> >> I. www.ixsoftware.nl
>> >>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Erik de Bruin
Ah, I see you just did that. Please ignore me ;-)

EdB



On Thu, Jul 25, 2013 at 10:59 AM, Erik de Bruin  wrote:
> Can you please add this information to the JIRA ticket?
>
> Thanks,
>
> EdB
>
>
>
> On Thu, Jul 25, 2013 at 10:57 AM, Jagan Langa Sami Durai
>  wrote:
>> Hi,
>>
>> Following is the ANT script snippet used to build my app. I have marked the
>> locale = "" because we tend to load them at run time. since our application
>> support multi-language and the language is decided at the time user log's
>> in. red color highlights might give you guys a clue to corner the issue.
>>
>> > file="${ROOT}/src/@{app}.mxml"
>> output="@{dest}/@{app}.swf"
>> allow-source-path-overlap="true"
>> link-report="@{dest}/${LINK_REPORT_XML}"
>> *static-rsls="false" *
>> optimize="true"
>> services="@{services}"
>> incremental="false" fork="true">
>>
>>  And This is how we set the locale to the SWF in the html wrapper
>>
>>  flashvars.localeChain = "en_US";
>>  flashvars.resourceModuleURLs = "locale/en_US/strings.swf";
>>
>> *
>> Regards,
>> S. Jagan  Langa* *|* *Team Lead*
>> *Sybrant Technologies Pvt Ltd*
>> *
>> *
>> Mobile: +91 98430 50897
>> Skype: seesamjagan
>> --
>>
>> In The Media:
>> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
>> **
>>
>> * *
>>
>> *About Sybrant:*
>>
>> *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
>> India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
>> recognized for working with our clients right from the product
>> conceptualization till the execution stage offering end-to-end solutions
>> that sets us apart from other firms in this space. Right from developing a
>> learning management system for a French company to helping a Non-Profit
>> with a Mobile application till developing UX for a IT firm, Sybrant is
>> known for delighting Customers”*
>>
>> --
>>
>>
>> 2013/7/25 Erik de Bruin 
>>
>>> Yes, Alex is looking into it... He left a comment on the JIRA ticket
>>> asking for a test case and the compiler settings used. Can you provide
>>> that, please?
>>>
>>> EdB
>>>
>>>
>>>
>>> On Thu, Jul 25, 2013 at 10:19 AM, Jagan Langa Sami Durai
>>>  wrote:
>>> > Hi
>>> >
>>> >
>>> > Any plan to fix this issue [1] in this release?
>>> >
>>> >
>>> > [1] https://issues.apache.org/jira/browse/FLEX-33632
>>> >
>>> >
>>> >
>>> >
>>> > *
>>> > Regards,
>>> > S. Jagan  Langa* *|* *Team Lead*
>>> > *Sybrant Technologies Pvt Ltd*
>>> > *
>>> > *
>>> > Mobile: +91 98430 50897
>>> > Skype: seesamjagan
>>> >
>>> --
>>> >
>>> > In The Media:
>>> >
>>> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
>>> > **
>>> >
>>> > * *
>>> >
>>> > *About Sybrant:*
>>> >
>>> > *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
>>> > India too, leverage Sybrant’s expertise for their Web & UIUX needs. We
>>> are
>>> > recognized for working with our clients right from the product
>>> > conceptualization till the execution stage offering end-to-end solutions
>>> > that sets us apart from other firms in this space. Right from developing
>>> a
>>> > learning management system for a French company to helping a Non-Profit
>>> > with a Mobile application till developing UX for a IT firm, Sybrant is
>>> > known for delighting Customers”*
>>> >
>>> >
>>> --
>>> >
>>> >
>>> > 2013/7/25 Erik de Bruin 
>>> >
>>> >> I don't see Alex's vote anywhere yet... In the discuss thread he
>>> >> announced was going to check on FLEX-33632. I agree with him that if
>>> >> it checks out that it is indeed an issue, it would be a regression
>>> >> serious enough to warrant immediate fixing.
>>> >>
>>> >> Just to be sure, I'll hold the release by changing my vote to:
>>> >>
>>> >> -1 (binding)
>>> >>
>>> >> If Alex dismisses FLEX-33632, you may consider my vote changed back to
>>> >> the original +1 (binding) - just in case my timezone is sleeping when
>>> >> you want to cut the release. If he needs to fix it, we need another RC
>>> >> and a new vote :-)
>>> >>
>>> >> Sorry about this and thanks for your patience,
>>> >>
>>> >> EdB
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Jul 25, 2013 at 9:37 AM, Justin Mclean <
>>> jus...@classsoftware.com>
>>> >> wrote:
>>> >> > Hi,
>>> >> >
>>> >> > 72 hours are just about up - final chance for anyone have any
>>> objections
>>> >> for this becoming a release.
>>> >> >
>>> >> > Thanks,
>>> >> > Justin
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Ix Multimedia Software
>>> >>
>>> >> Jan Luykenstraat 27
>>> >> 3521 VB Utrecht
>>> >>
>>> >> T. 0

Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Jagan Langa Sami Durai
Hi,

Following is the ANT script snippet used to build my app. I have marked the
locale = "" because we tend to load them at run time. since our application
support multi-language and the language is decided at the time user log's
in. red color highlights might give you guys a clue to corner the issue.



 And This is how we set the locale to the SWF in the html wrapper

 flashvars.localeChain = "en_US";
 flashvars.resourceModuleURLs = "locale/en_US/strings.swf";

*
Regards,
S. Jagan  Langa* *|* *Team Lead*
*Sybrant Technologies Pvt Ltd*
*
*
Mobile: +91 98430 50897
Skype: seesamjagan
--

In The Media:
http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
**

* *

*About Sybrant:*

*“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
recognized for working with our clients right from the product
conceptualization till the execution stage offering end-to-end solutions
that sets us apart from other firms in this space. Right from developing a
learning management system for a French company to helping a Non-Profit
with a Mobile application till developing UX for a IT firm, Sybrant is
known for delighting Customers”*

--


2013/7/25 Erik de Bruin 

> Yes, Alex is looking into it... He left a comment on the JIRA ticket
> asking for a test case and the compiler settings used. Can you provide
> that, please?
>
> EdB
>
>
>
> On Thu, Jul 25, 2013 at 10:19 AM, Jagan Langa Sami Durai
>  wrote:
> > Hi
> >
> >
> > Any plan to fix this issue [1] in this release?
> >
> >
> > [1] https://issues.apache.org/jira/browse/FLEX-33632
> >
> >
> >
> >
> > *
> > Regards,
> > S. Jagan  Langa* *|* *Team Lead*
> > *Sybrant Technologies Pvt Ltd*
> > *
> > *
> > Mobile: +91 98430 50897
> > Skype: seesamjagan
> >
> --
> >
> > In The Media:
> >
> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
> > **
> >
> > * *
> >
> > *About Sybrant:*
> >
> > *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
> > India too, leverage Sybrant’s expertise for their Web & UIUX needs. We
> are
> > recognized for working with our clients right from the product
> > conceptualization till the execution stage offering end-to-end solutions
> > that sets us apart from other firms in this space. Right from developing
> a
> > learning management system for a French company to helping a Non-Profit
> > with a Mobile application till developing UX for a IT firm, Sybrant is
> > known for delighting Customers”*
> >
> >
> --
> >
> >
> > 2013/7/25 Erik de Bruin 
> >
> >> I don't see Alex's vote anywhere yet... In the discuss thread he
> >> announced was going to check on FLEX-33632. I agree with him that if
> >> it checks out that it is indeed an issue, it would be a regression
> >> serious enough to warrant immediate fixing.
> >>
> >> Just to be sure, I'll hold the release by changing my vote to:
> >>
> >> -1 (binding)
> >>
> >> If Alex dismisses FLEX-33632, you may consider my vote changed back to
> >> the original +1 (binding) - just in case my timezone is sleeping when
> >> you want to cut the release. If he needs to fix it, we need another RC
> >> and a new vote :-)
> >>
> >> Sorry about this and thanks for your patience,
> >>
> >> EdB
> >>
> >>
> >>
> >> On Thu, Jul 25, 2013 at 9:37 AM, Justin Mclean <
> jus...@classsoftware.com>
> >> wrote:
> >> > Hi,
> >> >
> >> > 72 hours are just about up - final chance for anyone have any
> objections
> >> for this becoming a release.
> >> >
> >> > Thanks,
> >> > Justin
> >>
> >>
> >>
> >> --
> >> Ix Multimedia Software
> >>
> >> Jan Luykenstraat 27
> >> 3521 VB Utrecht
> >>
> >> T. 06-51952295
> >> I. www.ixsoftware.nl
> >>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>


Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Erik de Bruin
Yes, Alex is looking into it... He left a comment on the JIRA ticket
asking for a test case and the compiler settings used. Can you provide
that, please?

EdB



On Thu, Jul 25, 2013 at 10:19 AM, Jagan Langa Sami Durai
 wrote:
> Hi
>
>
> Any plan to fix this issue [1] in this release?
>
>
> [1] https://issues.apache.org/jira/browse/FLEX-33632
>
>
>
>
> *
> Regards,
> S. Jagan  Langa* *|* *Team Lead*
> *Sybrant Technologies Pvt Ltd*
> *
> *
> Mobile: +91 98430 50897
> Skype: seesamjagan
> --
>
> In The Media:
> http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
> **
>
> * *
>
> *About Sybrant:*
>
> *“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
> India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
> recognized for working with our clients right from the product
> conceptualization till the execution stage offering end-to-end solutions
> that sets us apart from other firms in this space. Right from developing a
> learning management system for a French company to helping a Non-Profit
> with a Mobile application till developing UX for a IT firm, Sybrant is
> known for delighting Customers”*
>
> --
>
>
> 2013/7/25 Erik de Bruin 
>
>> I don't see Alex's vote anywhere yet... In the discuss thread he
>> announced was going to check on FLEX-33632. I agree with him that if
>> it checks out that it is indeed an issue, it would be a regression
>> serious enough to warrant immediate fixing.
>>
>> Just to be sure, I'll hold the release by changing my vote to:
>>
>> -1 (binding)
>>
>> If Alex dismisses FLEX-33632, you may consider my vote changed back to
>> the original +1 (binding) - just in case my timezone is sleeping when
>> you want to cut the release. If he needs to fix it, we need another RC
>> and a new vote :-)
>>
>> Sorry about this and thanks for your patience,
>>
>> EdB
>>
>>
>>
>> On Thu, Jul 25, 2013 at 9:37 AM, Justin Mclean 
>> wrote:
>> > Hi,
>> >
>> > 72 hours are just about up - final chance for anyone have any objections
>> for this becoming a release.
>> >
>> > Thanks,
>> > Justin
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Jagan Langa Sami Durai
Hi


Any plan to fix this issue [1] in this release?


[1] https://issues.apache.org/jira/browse/FLEX-33632




*
Regards,
S. Jagan  Langa* *|* *Team Lead*
*Sybrant Technologies Pvt Ltd*
*
*
Mobile: +91 98430 50897
Skype: seesamjagan
--

In The Media:
http://www.pr-inside.com/motorola-solutions-showcases-sybrant-s-mobile-r3745747.htm
**

* *

*About Sybrant:*

*“Sybrant is a premier web/mobile/UIUX expert. Most admirable IT firms in
India too, leverage Sybrant’s expertise for their Web & UIUX needs. We are
recognized for working with our clients right from the product
conceptualization till the execution stage offering end-to-end solutions
that sets us apart from other firms in this space. Right from developing a
learning management system for a French company to helping a Non-Profit
with a Mobile application till developing UX for a IT firm, Sybrant is
known for delighting Customers”*

--


2013/7/25 Erik de Bruin 

> I don't see Alex's vote anywhere yet... In the discuss thread he
> announced was going to check on FLEX-33632. I agree with him that if
> it checks out that it is indeed an issue, it would be a regression
> serious enough to warrant immediate fixing.
>
> Just to be sure, I'll hold the release by changing my vote to:
>
> -1 (binding)
>
> If Alex dismisses FLEX-33632, you may consider my vote changed back to
> the original +1 (binding) - just in case my timezone is sleeping when
> you want to cut the release. If he needs to fix it, we need another RC
> and a new vote :-)
>
> Sorry about this and thanks for your patience,
>
> EdB
>
>
>
> On Thu, Jul 25, 2013 at 9:37 AM, Justin Mclean 
> wrote:
> > Hi,
> >
> > 72 hours are just about up - final chance for anyone have any objections
> for this becoming a release.
> >
> > Thanks,
> > Justin
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>


Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Erik de Bruin
And wow!

You called it a minute before my email. I guess officially we have a
release now. So a possible fix for the RSL thing goes into an point
update, if it checks out to be a regression?

EdB



On Thu, Jul 25, 2013 at 10:13 AM, Erik de Bruin  wrote:
> I don't see Alex's vote anywhere yet... In the discuss thread he
> announced was going to check on FLEX-33632. I agree with him that if
> it checks out that it is indeed an issue, it would be a regression
> serious enough to warrant immediate fixing.
>
> Just to be sure, I'll hold the release by changing my vote to:
>
> -1 (binding)
>
> If Alex dismisses FLEX-33632, you may consider my vote changed back to
> the original +1 (binding) - just in case my timezone is sleeping when
> you want to cut the release. If he needs to fix it, we need another RC
> and a new vote :-)
>
> Sorry about this and thanks for your patience,
>
> EdB
>
>
>
> On Thu, Jul 25, 2013 at 9:37 AM, Justin Mclean  
> wrote:
>> Hi,
>>
>> 72 hours are just about up - final chance for anyone have any objections for 
>> this becoming a release.
>>
>> Thanks,
>> Justin
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Erik de Bruin
I don't see Alex's vote anywhere yet... In the discuss thread he
announced was going to check on FLEX-33632. I agree with him that if
it checks out that it is indeed an issue, it would be a regression
serious enough to warrant immediate fixing.

Just to be sure, I'll hold the release by changing my vote to:

-1 (binding)

If Alex dismisses FLEX-33632, you may consider my vote changed back to
the original +1 (binding) - just in case my timezone is sleeping when
you want to cut the release. If he needs to fix it, we need another RC
and a new vote :-)

Sorry about this and thanks for your patience,

EdB



On Thu, Jul 25, 2013 at 9:37 AM, Justin Mclean  wrote:
> Hi,
>
> 72 hours are just about up - final chance for anyone have any objections for 
> this becoming a release.
>
> Thanks,
> Justin



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


[RESULT] [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Justin Mclean
Hi,

Binding votes:
+1 Erik de Bruin
+1 Justin Mclean
+1 Cyrill Zadra
+1 Nicholas Kwiatkowski

Non binding votes:
+1 Carlos Rovira
+1 Jose Barragan
+1 Swen van Zanten
+1 Mark Kessler

There were no +0 or -1 votes and a total of 8 +1 votes, 4 of which were binding.

So baring any major issues this will be the official 4.10 Apache Flex release.

Thanks to everyone who tried out the release candidates and to those who voted.

Justin

Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-25 Thread Justin Mclean
Hi,

72 hours are just about up - final chance for anyone have any objections for 
this becoming a release.

Thanks,
Justin

Re: [DISCUSSION] ** Apache Flex 4.10.0 Release Candidate 3

2013-07-24 Thread Alex Harui
My vote is pending the investigation of FLEX-33632.  Source kit built and
Mustella passed locally for the main suite, mobile and AIR on Windows with
11.7 and Mac with 11.1

Hopefully the bug author was not setting compiler arguments correctly and
we are simply catching that situation now.  But we don't have a mustella
test for resource modules loaded at RSL load time since that requires a
custom HTML template and a browser instead of standalone debugger player,
so we could have missed this scenario.

Enough folks use resource modules at RSL load time so it would be bad if
we broke it.

-Alex

On 7/23/13 12:51 AM, "OmPrakash Muppirala"  wrote:

>On Tue, Jul 23, 2013 at 12:45 AM, Justin Mclean
>wrote:
>
>> Hi,
>>
>> Any issues or questions about Apache Flex 4.10 RC3 please place in this
>> thread.
>>
>> Thanks,
>> Justin
>
>
>Please use the installers available here:
>https://dist.apache.org/repos/dist/dev/flex/installer/2.6/rc2/binaries/
>for
>testing the SDK.
>
>Thanks,
>Om



Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-24 Thread Mark Kessler
Doh I would have tried it with 3.8 instead of 3.7 for that last test of the
rc3 sdk... lol

-Mark


On Wed, Jul 24, 2013 at 12:00 PM, Dasa Paddock  wrote:

> AIR 3.8 is now available at:
> http://adobe.com/go/air_sdk/
>
> --Dasa
>
> On Jul 24, 2013, at 5:00 AM, Nicholas Kwiatkowski 
> wrote:
>
> > +1  (binding)
> >
> > Windows 7, x64,  JDK 1.7, FP 11.7
> >
> > MD5 and ASC check fine.
> > Compiles fine (from source)
> > Checkin-tests pass
> > Mustellella (full) tests pass
> > Simple mobile apps compile, check fine
> > Complex mobile apps compile, look good
> > Web apps compile as expected.
> >
> > WARNING:   makeApacheFlexForIDE.bat includes the 3.8 AIR SDK download
> > location, which is still throwing a 404.  This file had to be touched by
> > hand in order for the make script to work.
> >
> > Apps compile well with IntelliJ 11.3, 12.0 and 12.1.4
> > I didn't get a chance to review the README with a fine-tooth comb.  I
> hope
> > to do that this afternoon if I get out of work before 9pm, but if not
> I'll
> > assume it was reviewed by others.
> >
> >
> > -Nick
> >
> >
> >
> > On Tue, Jul 23, 2013 at 3:45 AM, Justin Mclean  >wrote:
> >
> >> Hi,
> >>
> >> This is a  Apache Flex 4.10.0 Release Candidate 3. Please see the
> >> RELEASE_NOTES and the README.
> >>
> >> There are only a few minor differences from RC2 including a minor change
> >> to the AIR config files (air home path) , minor changes to README and
> >> RELEASE_NOTES, and a couple of very minor build script changes. There
> have
> >> been no SDK code changes.
> >>
> >> The release candidate can be found here;
> >> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc3/
> >>
> >> Before voting please review the section,"What are the ASF requirements
> on
> >> approving a release?", at:
> >> http://www.apache.org/dev/release.html#approving-a-release
> >>
> >> When testing please check the md5 and asc files and make sure that the
> >> source can be compiled.
> >>
> >> Please vote to approve this release:
> >> +1 Approve the release
> >> -1 Veto the release (please provide specific comments to why)
> >>
> >> This vote will be open for at least 72 hours or as long as needed.
> >>
> >> The vote passes if there is:
> >> - At least 3 +1 votes from the PMC
> >> - More positive votes than negative votes
> >>
> >> People who are not in PMC or who are not an committer are also
> encouraged
> >> to test out the release and vote, although their votes will not be
> binding.
> >>
> >> When voting please indicate what OS, IDE, Flash Player version and AIR
> >> version you tested the SDK with.
> >>
> >> Please put all discussion about this release in the DISCUSSION thread
> not
> >> this VOTE thread.
> >>
> >> Thanks,
> >> Justin
>
>


Re: [VOTE] Apache Flex 4.10.0 Release Candidate 3

2013-07-24 Thread Mark Kessler
+1

OS: Windows 7
IDE: FlashDevelop (just to be different)
FP: 11.8
Air: 3.7

Successfully compiled sdk
successfully compiled test applications.

-Mark


On Tue, Jul 23, 2013 at 3:45 AM, Justin Mclean wrote:

> Hi,
>
> This is a  Apache Flex 4.10.0 Release Candidate 3. Please see the
> RELEASE_NOTES and the README.
>
> There are only a few minor differences from RC2 including a minor change
> to the AIR config files (air home path) , minor changes to README and
> RELEASE_NOTES, and a couple of very minor build script changes. There have
> been no SDK code changes.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/flex/sdk/4.10.0/rc3/
>
> Before voting please review the section,"What are the ASF requirements on
> approving a release?", at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> When testing please check the md5 and asc files and make sure that the
> source can be compiled.
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Veto the release (please provide specific comments to why)
>
> This vote will be open for at least 72 hours or as long as needed.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> People who are not in PMC or who are not an committer are also encouraged
> to test out the release and vote, although their votes will not be binding.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested the SDK with.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Justin


  1   2   3   >