Re: svn commit: r1428687 - /incubator/flex/utilities/trunk/installer/RELEASE_GUIDE
That's a line ending issue. Run dos2unix on it. On 1/4/13 2:24 PM, "Om" wrote: > BTW, this script does not work for me on windows (cygwin) This is what I > get: > > $ ./sign_and_hash.sh > ./sign_and_hash.sh: line 48: $'\r': command not found > ./sign_and_hash.sh: line 49: $'\r': command not found > ./sign_and_hash.sh: line 50: syntax error near unexpected token `$'do\r'' > '/sign_and_hash.sh: line 50: `for file in *; do > > On Fri, Jan 4, 2013 at 2:13 PM, Om wrote: > >> So, should I just make a copy under utilities/trunk/installer? >> >> >> On Fri, Jan 4, 2013 at 2:11 PM, Justin Mclean >> wrote: >> >>> I'd leave it where it is each imo you should be able to build each >>> project from its own trunk and not have to check out multiple trunks >>> >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] taking Apache Flex to the next level
On 1/4/13 9:37 AM, "Michael Schmalle" wrote: >> Anything we say about the future right now is likely to be met with >> suspicion anyway. I think this is a critical year for Flex. We have to >> build a track record of releases that show that we are making progress. > > And here in sits the outside view. Since anything that is in > whiteboards or not included with releases in the next years will fall > on deaf ears... Unless the blog is updated regularly, the website has > layman terms explanations of current projects (maybe more conducive to > actually clicking links and "discovering what we are about"), right > now it looks like a developers site, not a users site. Why would a > user venture past the "download" link if it resembles a "how to build > the sdk or checkout code. True, but would be far better to show examples/tutorials instead of just words. I haven't tried to update the site, but it seems like there is no easy way to put up webservices that Flex examples typically use. This is another thing either Spoon needs to do or I need to do with my own "company". > > I'm not a web designer nor have the time for it but that is a HUGE > weak link right there and the blog. Plus it's all free advertising > that we are not totally taking advantage of. > Sure, a better site would help, but IMO, a site is helpful when people are looking for something, and a blog additionally helps those who have already found you. That's all good, but nothing like going viral. So far, we have not released anything so new or important that it will create the kind of buzz that is loud enough to make folks start looking for us especially in the face of the headwinds from the past year. If the JS stuff actually becomes something, then that has the chance of being that thing that is buzz-worthy. I'd love to know what else we could do that would make that kind of noise. The Maven stuff maybe? I'm not sure a better DataGrid would do it. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] taking Apache Flex to the next level
On 1/4/13 8:38 AM, "Erik de Bruin" wrote: > Alex, I see where you're coming from, and I don't necessarily disagree > on principle, but your statement does not compute: > > Success is meeting or exceeding expectations, but this project can't > have expectations because of the way it's set up... Does this mean you > don't see any way for this project to be successful? The further into the future you try to set expectations, the more error you are likely to have when you have volunteer workforces, and therefore there is a greater chance that you won't meet those expectations. But good marketing of the present sets expectations properly and folks can immediately find out that it not only works as expected, but works better than expected. That's how I think we can be successful as a project. By cranking out releases that solve problems for people and showing people that they can solve their problems today. Anything we say about the future right now is likely to be met with suspicion anyway. I think this is a critical year for Flex. We have to build a track record of releases that show that we are making progress. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] taking Apache Flex to the next level
On 1/4/13 8:02 AM, "Erik de Bruin" wrote: > I'm not talking Roadmap here, Alex, but even Open Source projects done > the Apache way can have a direction and maybe even actual goals. > > One definition might be: "maintaining the project status quo by > preventing any discussion about common goals" > > Another might be: "bringing the power of the Flex framework to > multiple, vendor independent platforms" > > Or even: "one framework to rule them all" ;-) > > I'm not saying we need any kind of fixed target or anything else that > might somehow be in conflict with the strict definition of the Apache > Way, what I'm looking for is giving people willing to help out > evangelising Apache Flex some kind of handle, something to start > building an effective campaign upon. > > EdB Erik, I just think that meeting or exceeding expectations is a key to success. With volunteer work forces and no hierarchical organizational constraints it is dangerous to set expectations. One can certainly infer direction based on past actions and current actions. There is actual code being written to try to get Flex to run without Flash. There are discussions going on about JS output and framework rewrites. A good marketing person can create excitement about what is happening now without having to promise too far into the future. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] taking Apache Flex to the next level
On 1/4/13 7:10 AM, "Erik de Bruin" wrote: > Hi all, > > A discussion on the PMC list brought up an interesting point, which I > think this list can contribute to: > > Can we give a clear definition of this project's future? IMO, no. But even if we can't, that doesn't mean we can't use better marketing about what we have done or are doing. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer Button Truncation
The screen with the install button should have a list of checkboxes on the left for each of the components you want to install. Until you've checked the required components it won't enable the install button. Is the screen blank except for the install button? On 1/3/13 10:02 PM, "jude" wrote: > The install button is disabled for me. This is on the screen right after > the choose the download location screen. I think there is supposed to be a > Accept License agreement checkbox which I don't see. > > On Thu, Jan 3, 2013 at 6:52 PM, Justin Mclean wrote: > >> Hi, >> >>> Justin, are you ready to cut an RC2? >> Done. >> >> http://people.apache.org/~jmclean/Apache%20Flex%20Installer%20RC2/ >> >> Justin >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 - RC2
FWIW, I'm seeing some action from Infra on getting the TLP tasks completed. On 1/3/13 5:48 PM, "Alex Harui" wrote: > Om, I would recommend just starting a vote thread. This time around you > know that several folks have seen RC1 and at least three of us probably > built from trunk today. The most significant code path change since RC1 was > probably the button sizing. > > -Alex > > On 1/3/13 5:11 PM, "Om" wrote: > >> The source and binary kits for both Mac and Windows are available here: >> >> http://people.apache.org/~bigosmallm/installapacheflex_2.0_RC2/ >> * >> >> Issues fixed in RC2: >> * >> >> 1. Fixed issue where changing languages caused selections to be cleared >> 2. While changing languages, buttons will automatically enlarge to fit all >> the text >> 3. More translations made possible by Roland and Nick >> 4. Fixed README, RELEASE_NOTES, RELEASE_GUIDE and build.properties files >> for more accuracy. >> >> Issues fixed in RC1: >> 1. UI of the components selection and license screen has been fixed to use >> just checkboxes for selection >> 2. All the various locales have been enabled. >> 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player >> 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other >> supported combination, you save a copy of the config file found at: >> http://incubator.apache.org/flex/sdk-installer-config-2.0.xml, modify the >> download urls to point to the required versions. Then run the app from >> command line mode with the optional command line parameter: -config=> to config file> >> >> Thanks, >> Om & Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 - RC2
Om, I would recommend just starting a vote thread. This time around you know that several folks have seen RC1 and at least three of us probably built from trunk today. The most significant code path change since RC1 was probably the button sizing. -Alex On 1/3/13 5:11 PM, "Om" wrote: > The source and binary kits for both Mac and Windows are available here: > > http://people.apache.org/~bigosmallm/installapacheflex_2.0_RC2/ > * > > Issues fixed in RC2: > * > > 1. Fixed issue where changing languages caused selections to be cleared > 2. While changing languages, buttons will automatically enlarge to fit all > the text > 3. More translations made possible by Roland and Nick > 4. Fixed README, RELEASE_NOTES, RELEASE_GUIDE and build.properties files > for more accuracy. > > Issues fixed in RC1: > 1. UI of the components selection and license screen has been fixed to use > just checkboxes for selection > 2. All the various locales have been enabled. > 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player > 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other > supported combination, you save a copy of the config file found at: > http://incubator.apache.org/flex/sdk-installer-config-2.0.xml, modify the > download urls to point to the required versions. Then run the app from > command line mode with the optional command line parameter: -config= to config file> > > Thanks, > Om & Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer Button Truncation
OK, it's in. Rev 1428672. On 1/3/13 3:36 PM, "Om" wrote: > Yes please :-) > > Om > > On Thu, Jan 3, 2013 at 3:34 PM, Alex Harui wrote: > >> Hey Om, >> >> After looking at Nick¹s greek translations, I got motivated enough to code >> up a way to get the buttons to grow in a nice way (at least to my eyes). I >> just finished it and can check it in. Do you want it for RC2? >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Installer Button Truncation
Hey Om, After looking at Nick¹s greek translations, I got motivated enough to code up a way to get the buttons to grow in a nice way (at least to my eyes). I just finished it and can check it in. Do you want it for RC2? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[jira] [Resolved] (FLEX-33338) Incomplete translation and formatting when using Greek locale with the installer.
[ https://issues.apache.org/jira/browse/FLEX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Harui resolved FLEX-8. --- Resolution: Fixed submitted in SVN 1428469. Thanks Nick. > Incomplete translation and formatting when using Greek locale with the > installer. > - > > Key: FLEX-8 > URL: https://issues.apache.org/jira/browse/FLEX-8 > Project: Apache Flex > Issue Type: Bug >Reporter: Nick Tsitlakidis > Assignee: Alex Harui >Priority: Minor > > The following list contains the changes that must be done to have a more > consistent translation. > The changes target visual controls that might have incorrect capitalization > or didn't include translated text at all. > 1st screen > Select Language -> Επιλέξτε Γλώσσα > ISTALL LOG -> ΑΡΧΕΙΟ ΚΑΤΑΓΡΑΦΗΣ ΕΓΚΑΤΑΣΤΑΣΗΣ > NEXT -> ΕΠΟΜΕΝΟ > BROWSE -> ΑΝΑΖΗΤΗΣΗ > Select installation directory -> Επιλέξτε τον κατάλογο εγκατάστασης > The selected directory is not empty -> Ο κατάλογος που επιλέξατε δεν είναι > άδειος > 2nd screen > CLOSE -> ΕΞΟΔΟΣ > INSTALL -> ΕΓΚΑΤΑΣΤΑΣΗ > 3d screen > Installing... -> Εγκατάσταση... > OPEN APACHE FLEX FOLDER -> ΑΝΟΙΓΜΑ ΦΑΚΕΛΟΥ APACHE FLEX -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FLEX-33338) Incomplete translation and formatting when using Greek locale with the installer.
[ https://issues.apache.org/jira/browse/FLEX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Harui reassigned FLEX-8: - Assignee: Alex Harui > Incomplete translation and formatting when using Greek locale with the > installer. > - > > Key: FLEX-8 > URL: https://issues.apache.org/jira/browse/FLEX-8 > Project: Apache Flex > Issue Type: Bug >Reporter: Nick Tsitlakidis > Assignee: Alex Harui >Priority: Minor > > The following list contains the changes that must be done to have a more > consistent translation. > The changes target visual controls that might have incorrect capitalization > or didn't include translated text at all. > 1st screen > Select Language -> Επιλέξτε Γλώσσα > ISTALL LOG -> ΑΡΧΕΙΟ ΚΑΤΑΓΡΑΦΗΣ ΕΓΚΑΤΑΣΤΑΣΗΣ > NEXT -> ΕΠΟΜΕΝΟ > BROWSE -> ΑΝΑΖΗΤΗΣΗ > Select installation directory -> Επιλέξτε τον κατάλογο εγκατάστασης > The selected directory is not empty -> Ο κατάλογος που επιλέξατε δεν είναι > άδειος > 2nd screen > CLOSE -> ΕΞΟΔΟΣ > INSTALL -> ΕΓΚΑΤΑΣΤΑΣΗ > 3d screen > Installing... -> Εγκατάσταση... > OPEN APACHE FLEX FOLDER -> ΑΝΟΙΓΜΑ ΦΑΚΕΛΟΥ APACHE FLEX -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/3/13 2:27 PM, "Nick Tsitlakidis" wrote: > Hello Alex, > I've just checked out the source for the installer. I'll spend some time > trying to build and check if all is right. > After a quick look in the class responsible for the locale settings, I see > some more changes that can happen so as soon as I figure out how the > process works I'll submit a patch with the new changes. > > Regarding the JIRA issue, what do you want me to include in there? The list of strings you wanted us to change. Someday we may want to go back and find out what you've contributed. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: AW: NumericInput component?
On 1/3/13 1:42 PM, "christofer.d...@c-ware.de" wrote: > I wasn't suggesting to put it into core immediately. > I just wanted to send the code without actually committing it, as I don't have > an idea where to put it ;-) > I would recommend creating a whiteboard folder and putting in there. Then folks can try putting it in their projects if they wish. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
Hi Nick, I checked in your suggested changes. If you have time, please build it and test it yourself. At minimum, check it when you see RC2 announced. Also, please open a JIRA issue and copy your email into it. I tend to use JIRA to track who we've accepted contributions from. Om, I've checked the rat report and ran the installer in english last night. Everything seems to be ok, so I'm ready for RC2. Thanks, -Alex On 1/3/13 8:19 AM, "Alex Harui" wrote: > > > > On 1/3/13 5:57 AM, "Nick Tsitlakidis" wrote: > >> More than happy to do it but I would like to have some guidance for this. >> I'm a total noob with patches since it's the first time I'm actively >> contributing something. I'm a member of the list since last year but never >> had the time to work on something until now. >> >> Are there any guidelines or a page I can check to learn how to do this? > There is some information on the Apache Flex web site. You have to check out > the source, figure out how to build the installer, modify the files and > generate the patch from the modified files. The way you generate the patch > depends on what kind of SVN client you are using. > > But for now, I will try to see if I can just copy/paste your changes. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/3/13 5:57 AM, "Nick Tsitlakidis" wrote: > More than happy to do it but I would like to have some guidance for this. > I'm a total noob with patches since it's the first time I'm actively > contributing something. I'm a member of the list since last year but never > had the time to work on something until now. > > Are there any guidelines or a page I can check to learn how to do this? There is some information on the Apache Flex web site. You have to check out the source, figure out how to build the installer, modify the files and generate the patch from the modified files. The way you generate the patch depends on what kind of SVN client you are using. But for now, I will try to see if I can just copy/paste your changes. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [LAZY] Planning to commit Installer Locale Editor to SVN
On 1/3/13 2:33 AM, "Roland Zwaga" wrote: > I'm ok with this, if it doesn't get officially released but only lives in > the SVN repo, > does this mean I don't have to sign an ICLA? > Hi Roland, please submit an ICLA (and update a CCLA if appropriate). No matter who checks in the code, you are still the author. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Continuing discussion on Installer 2.0 RC1
Om, Made the change to build.properties and fixed some typo's in the release notes. I think RELEASE_NOTES typically also have lists of bugs fixed or improvements made. Can you add that to the release notes? Thanks, -Alex On 1/2/13 1:31 PM, "Alex Harui" wrote: > > > > On 1/2/13 1:04 PM, "Om" wrote: > >> On Wed, Jan 2, 2013 at 12:53 PM, Alex Harui wrote: >> >>> >>> >>> >>> On 1/2/13 12:18 PM, "Om" wrote: >>> >>>> Thanks Greg. >>>> >>>> Alex, I think it is pretty clear from Greg's response on how we want to >>>> proceed. Do you have any more clarifications, or can we go ahead with >>> the >>>> [VOTE] for RC1? >>>> >>> Yes, it is good to learn that publishing on the site is not considered a >>> release and you can publish the xml file on the site without a vote. >>> >>> You can start a vote for RC1 if you want, but I think we should fix up a >>> few >>> of the issues folks have brought up so far. The ones I saw are: >>> >>> 1) the name of the default value for FLEX_HOME_MAC folder. >>> >> >> Can you or Carol fix this and check it in? > I'll do it. Carol is out rest of today I think. >> >> >>> 2) Greek locale capitalization (I think we'll probably have to live with >>> truncation issues in this version like prior versions) >>> >> >> Truncated labels automatically show tooltips. So we are not a lot of >> functionality. But I do agree it doesnt look too good. I am loathe to >> changing the size of buttons. Maybe someone can make the text's font size >> to scale down automatically based on content? >> Bonus: This would be a very nice feature addition to the Flex SDK :-) > Scaling font size would make it unreadable in many cases. I think the SDK > feature you are supposed to use is constraint columns. I think the visual > designers are probably ok having buttons grow to fit the text, but they want > two buttons on top of each other to grow to the size of the larger button. > > But I just want us to get the capitalization right in this release. Let's > see if we can get someone to tell us what to change. > >>> I wish we could get our >>> final URLs before sending out this release. >>> >>> >> I am okay with waiting if we know that the timeframe is in the order of >> days and not weeks/months. > I guess the best plan is to make an RC2 soon with the non-final URLs and be > prepared to cancel the vote if we get our final URLs on Monday next week. I > think the issue is that the board secretaries are still out on holiday and > don't have final minutes for infra to use to build out the TLP stuff. >> >> Thanks, >> Om -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
Hi Nick, The truncation issues might have to wait, but can you tell use where the incorrect capitalization is so we can try to fix it? Thanks, -Alex On 1/2/13 7:32 AM, "Nick Tsitlakidis" wrote: > Following Carol's comments, using the Greek locale also has some > inconsistencies. For example incorrect capitalization and problems with > truncation as well. > > Other than that, using the installer in a clean system (no other version of > the installer existing) worked great. > > > On Wed, Jan 2, 2013 at 5:03 PM, Carol Frampton wrote: > >> Just gave this a try. Here are my comments regarding the installation and >> use: >> >> 1. When I tried to install it I got that "there is something wrong" AIR >> error which is really unhelpful but I knew it meant I had to uninstall the >> old installer first. Why can't the old installer and the new installer >> co-exist since they are each installing a different version of Flex? >> >> 2. As Justin said, the DISCLAIMER needs to be removed. >> >> 3. Depending on the locale, the text in some of the buttons is truncated >> which looks bad. For example, try French. >> >> 4. When I switch the language in the middle of checking all the license >> agreements, whatever I've already checked is cleared. >> >> Carol >> >> On 1/1/13 1 :23AM, "Om" wrote: >> >>> This is version 2.0 of Apache Flex SDK Installer. This version lets users >>> download the Apache Flex SDK 4.9 and its required dependencies. >>> >>> https://people.apache.org/~bigosmallm/installapacheflex_2.0_RC1/ >>> >>> Significant improvements over previous version: >>> >>> 1. UI of the components selection and license screen has been fixed to >>> use >>> just checkboxes for selection >>> 2. All the various locales have been enabled. >>> 3. By default, Apache Flex SDK Installer 2.0 downloads Adobe Flash Player >>> 11.1 and Adobe AIR SDK 3.4. If you want to change it to any other >>> supported combination, you save a copy of the config file found at: >>> http://incubator.apache.org/flex/sdk-installer-config-2.0.xml, modify the >>> download urls to point to the required versions. Then run the app from >>> command line mode with the optional command line parameter: -config=>> to config file> >>> >>> Please take it for a spin and let us know your feedback. We would like to >>> put up a vote asap and release this right away! >>> >>> Thanks, >>> Om >> >> > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Continuing discussion on Installer 2.0 RC1
On 1/2/13 1:04 PM, "Om" wrote: > On Wed, Jan 2, 2013 at 12:53 PM, Alex Harui wrote: > >> >> >> >> On 1/2/13 12:18 PM, "Om" wrote: >> >>> Thanks Greg. >>> >>> Alex, I think it is pretty clear from Greg's response on how we want to >>> proceed. Do you have any more clarifications, or can we go ahead with >> the >>> [VOTE] for RC1? >>> >> Yes, it is good to learn that publishing on the site is not considered a >> release and you can publish the xml file on the site without a vote. >> >> You can start a vote for RC1 if you want, but I think we should fix up a >> few >> of the issues folks have brought up so far. The ones I saw are: >> >> 1) the name of the default value for FLEX_HOME_MAC folder. >> > > Can you or Carol fix this and check it in? I'll do it. Carol is out rest of today I think. > > >> 2) Greek locale capitalization (I think we'll probably have to live with >> truncation issues in this version like prior versions) >> > > Truncated labels automatically show tooltips. So we are not a lot of > functionality. But I do agree it doesnt look too good. I am loathe to > changing the size of buttons. Maybe someone can make the text's font size > to scale down automatically based on content? > Bonus: This would be a very nice feature addition to the Flex SDK :-) Scaling font size would make it unreadable in many cases. I think the SDK feature you are supposed to use is constraint columns. I think the visual designers are probably ok having buttons grow to fit the text, but they want two buttons on top of each other to grow to the size of the larger button. But I just want us to get the capitalization right in this release. Let's see if we can get someone to tell us what to change. >> I wish we could get our >> final URLs before sending out this release. >> >> > I am okay with waiting if we know that the timeframe is in the order of > days and not weeks/months. I guess the best plan is to make an RC2 soon with the non-final URLs and be prepared to cancel the vote if we get our final URLs on Monday next week. I think the issue is that the board secretaries are still out on holiday and don't have final minutes for infra to use to build out the TLP stuff. > > Thanks, > Om -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [MENTORS] Release Policy
On 1/2/13 12:18 PM, "Om" wrote: > Thanks Greg. > > Alex, I think it is pretty clear from Greg's response on how we want to > proceed. Do you have any more clarifications, or can we go ahead with the > [VOTE] for RC1? > Yes, it is good to learn that publishing on the site is not considered a release and you can publish the xml file on the site without a vote. You can start a vote for RC1 if you want, but I think we should fix up a few of the issues folks have brought up so far. The ones I saw are: 1) the name of the default value for FLEX_HOME_MAC folder. 2) Greek locale capitalization (I think we'll probably have to live with truncation issues in this version like prior versions) 3) remove DISCLAIMER file 4) Examine the checkbox issue Carol brought up about changing locales after checking some of the boxes. If it will be risky/painful, it can probably be deferred. I actually haven't looked at RC1 myself. I will do that next. Also, I still don't like the fact that someone running the installer sometime in the future can potentially have a different version installed, and I still don't like having the incubator URLs. I wish we could get our final URLs before sending out this release. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/2/13 6:09 AM, "Erik de Bruin" wrote: > I'm sorry I'm late to this discussion, but all I can say is: Wow! and: > Really? Yeah, sorry. I tend to be conservative about legal/policy stuff. I know some others have the "ask for forgiveness" philosophy, but that tends not to work too well in "corporate veil" situations. > > The whole website is in SVN. It is source (mdtext), consumed by a compiler > (the buildbot), spit out as HTML and released outside the project on the > WWW. How is that different from our other sources? Do you suggest we have a > vote on every update of the site? I think the line is about human readable, passive content, but I posed this in the mentor thread I just sent out. > > One rule to rule them all, if we insist on the letter, instead of the > spirit, of the rules. Mind you, I think you're killing a nice tool in the > process, one of the more successful tools in keeping the SDK 'alive and > kicking' in the real world. I'm not trying to kill the tool. In fact I have suggested ways to implement the desired goals that I think conform to the Apache policy. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[MENTORS] Release Policy
Hi Mentors, As you may have seen, there is a long thread going on about the installer and its deployment of a .xml file on the Apache Flex website. The main question is: Is this .xml file considered “source material” and therefore does it require a vote before being pushed to the Apache Flex website? The follow-up questions are: 1) Can such a file even be pushed to the Apache Flex website or can it only live in the dist folder? 2) Why does website content not require a vote before publishing (or is it supposed to)? 3) If not, what is the “line” that defines what requires a vote? Is it that it is human-readable content? Thanks for your thoughts on this matter. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Editing SDK within Flash Builder
Honestly, I don't know for sure, I don't use FB for SDK development. Other engineers did, but they were always complaining about FB breaking. One of the reasons for that was that Adobe was always developing FB and the SDK in parallel. That isn't the case now, so it might be more manageable, but I have my non-FB workflow that I'm happy with. That said, I believe those engineers would create a new workspace and import the entire frameworks/projects folder. HTH, -Alex On 1/2/13 7:16 AM, "Matt Hughes" wrote: > I did add the variable in the compiler options. That got things compiling, > but then I was missing assets. I added the source file for the *binary* > distribution (for some reason, they aren't in the source distribution). > That got me past that hurdle. But then when I ran, the CSS files were > missing... > > There has to be some defined way of doing thisŠ I can't believe every > Apache and Adobe contributor just muddles their way through this. Isn't > their some Ant task or some script that just sets up your Flash Builder > project to use the source of a particular Flex SDK? This is critical to > having community participation. > > > > > On Mon, Dec 31, 2012 at 11:51 AM, Alex Harui wrote: > >> >> >> >> On 12/31/12 7:38 AM, "Matt Hughes" wrote: >> >>> Is there some guide for editing SDK classes within Flash Builder? >>> >>> I have installed Flex 4.9 and have also downloaded the source. I tried >>> just removing the mx.swc and framework.swc from the Build Path Libraries >>> and then adding the respective src folders. That seems to get me closer, >>> but now I have lots of errors because I don't have the config variable: >>> >>> CONFIG::performanceInstrumentation >>> >>> >>> defined. I'm trying to investigate a possible bug in the SDK while >> running >>> a small test project. I'd like to make changes to some SDK classes and >> see >>> if that resolves my problem. I couldn't find any guides on the main Flex >>> page or on the Apache Flex wiki on getting this set up. >> I don't know if there is one correct way of setting this up. Each swc >> folder should have FlashBuilder project files in it so you can import each >> folder as a project and set up your test app as dependent on those >> projects. >> >> As a shortcut for your current setup, I think you can just define that >> variable in the compiler options (and set it to false). >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 11:16 PM, "Justin Mclean" wrote: > Hi, > >> -From [1], a release is "anything that is published beyond the group that >> owns it.". Putting the config.xml on the site to be consumed by one of our >> binaries makes it part of a release and requires a vote before it happens. > It published on the Flex web site by Flex committers give access by the ASF > I'd read that as not being "beyond the group". Or are you saying we need to > vote every time we make a change to the web site or wiki? I mentioned in another reply that there seems to be different rules for web-site content. But this is a file consumed by code. > >> -Also from [1], " All releases are in the form of the source materials >> needed to make changes to the software being released." > Everything is contained in the source and anyone can download and build the > installer so that is covered as well. > > I would agree there would the issue if any file was owned or hosted by a 3rd > party. This is not the case, Right, but the config.xml is part of this kit isn't it? If not it should be and then IMO, posting it on the site could be construed to be a "release". > >> -From [2], "The role of the PMC from a Foundation perspective is oversight. >> The main role of the PMC is not code and not coding - but to ensure that all >> legal issues are addressed, that procedure is followed, and that each and >> every release is the product of the community as a whole. > This installer is the product of the community I don't see how anyone could > claim otherwise so again I don't believe there is an issue here either. Because I think we have released a source material file (the config.xml) without a vote. I looked: it is there on incubator/flex now. > >> As much as we want to get this release out the door, the fact is it is more >> important to make sure we are following policy. > > We are following policy the installer will be put up for a vote and released > in the normal way. > > If you really think that the above is the case then I can't see how we will > ever be able to release the installer or even make the 4.9 release > announcement and having a 2 or 3 vote process is just too much to ask of most > committers limited time. I see the only options are, unles syou have a better > idea, is to remove the installer out of Apache or abandon it and insist that > users compile the SDK from scratch. I think longer term Dave Fisher had some good ideas. The list of dependencies should be in the SDK. The list of SDKs and their URLs should be in a file relative to the installer. Or could we get the list by hitting the dist folder and archive folder via HTTP and parsing the result to see what is in it? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 11:30 PM, "Om" wrote: > On Tue, Jan 1, 2013 at 11:23 PM, Alex Harui wrote: > >> >> >> >> On 1/1/13 11:09 PM, "Om" wrote: >> >>> On Jan 1, 2013 10:42 PM, "Alex Harui" wrote: >>>> >>>> Ok, here is my logic: >>>> >>>> -From [1], a release is "anything that is published beyond the group >> that >>>> owns it.". Putting the config.xml on the site to be consumed by one of >>> our >>>> binaries makes it part of a release and requires a vote before it >> happens. >>> >>> I still don't agree with this logic. The config xml is placed on our >>> website which is completely under our control. Which means that we don't >>> really 'release' it. >> We are taking something from SVN and consuming it in a binary distribution >> that we've deployed to our site and telling the world to use it. >> > > We consume a lot of resources from the website - the flex sdk, the md5, the > mirror url cgi script (which IS code). We dont release any of those in the > source kit for the Installer. How is the config xml any different? > > We also consume a host of external dependencies like flash player, air sdk, > etc. According to your logic, we cannot do this because we cannot > 'release' those files. It is in our SVN with the rest of our code and dictates what the code does. None of the other things you listed do both. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 11:13 PM, "Justin Mclean" wrote: > Hi, > >> I'm not sure Apache Flex is allowed to use Github as a end-run around Apache >> policy. > > The installer would not belong to Apache but be a separate project that is > worked on by people who want to give users of the Flex SDK an easy way to > install it. All it does it take the binary kit from Apache and download some > 3rd party software and combine them into a usable SDK. None of that is against > Apache polity. Users may have less trust in software that comes form outside > Apache but that is their choice to make. Well, that group would need approval from Apache to use Flex anywhere in the name of the installer, but yeah, an independent group of folks can certainly go off and create their own installer. I think there is some way to create an installer within Apache Flex that takes one vote and makes everyone happy. I'm not sure this is the right design, but I haven't spent much time thinking about a better way. > >> While I don't like the downloading of the config.xml from the site because I >> think it will pose the issues I listed in another reply, if we want to go >> that way, I believe the process is that we have to vote to approve the >> deployment of the config.xml to the website, then test the installer against >> it and then vote on the installer. We could try to do it as one, but my >> main objection to that is that we won't have tested the installer's code >> path that downloads the config.xml from the site. So I think it has to be >> two votes. > > So you really want to impose this process on future release managers, the > harder the process it the less likely people will want to take it on. It's > already much more complex than some other Apache projects. Correct me if I > wrong but I think your saying that every release of the installer woudl > require 2 votes and every release of the SDK require 2 or 3 votes? No, I don't. I think this is symptomatic of not having the right design. I am hopeful we can put our heads together and come up with a better design "later". For now though, my five minute of thinking says I would rather go back and not have the installer download from the site. The badge installer would find the config using a relative path just like the standalone installers. Then one vote and we're done! Unless I'm missing something. > >> The main delay is caused by the delay in getting the final dist folder. > > Really? Until that is set up we can use /incubator/flex. IMO, yes. The config.xml file should look up 4.9 via dist, not incubator. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 11:09 PM, "Om" wrote: > On Jan 1, 2013 10:42 PM, "Alex Harui" wrote: >> >> Ok, here is my logic: >> >> -From [1], a release is "anything that is published beyond the group that >> owns it.". Putting the config.xml on the site to be consumed by one of > our >> binaries makes it part of a release and requires a vote before it happens. > > I still don't agree with this logic. The config xml is placed on our > website which is completely under our control. Which means that we don't > really 'release' it. We are taking something from SVN and consuming it in a binary distribution that we've deployed to our site and telling the world to use it. Believe me, I've puzzled over why other web-site changes aren't also considered 'releases' and need voting. I think it is because there is no code involved. But in this case, there is code involved, whether it is the installer launched from our web-page or by the user downloading the installer. But I would love to be overruled by the mentors or board. I am taking the most conservative read of the policy because I see that as the safest play for now. I know it is delaying things, but all of us PMC members have a priority to make sure we are following Apache policy. > > We don't 'release' the installer badge, but it consumes the same exact > config xml. Are you saying that we need to release the source for the > badge as well? IMO, absolutely. Did we not do this in the prior version? Then we really messed up that release. I thought the same source created the badge installer, but it got packaged differently before posting on the site. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 10:37 PM, "Justin Mclean" wrote: > Hi, > >> Are you suggesting that the workflow is to use the -config switch for >> testing? Then we are not testing the final configuration. > > The same XML file would be uploaded so we would be testing the final config. > > Again this is a program to help users download the binaries to use in their > IDE of choice, it's provided to help them and is not really part of the SDK > itself. If you don't agree with how the installer is currently working please > come up with a suggestion to fix it so it complies with what you think the > legal issue is - which I have to say I'm still unsure actually exists. If then > we can't come up with a way around that then I suggest we host the installer > exe/dmg files externally and move the code out of Apache SVN to github. I'm not sure Apache Flex is allowed to use Github as a end-run around Apache policy. While I don't like the downloading of the config.xml from the site because I think it will pose the issues I listed in another reply, if we want to go that way, I believe the process is that we have to vote to approve the deployment of the config.xml to the website, then test the installer against it and then vote on the installer. We could try to do it as one, but my main objection to that is that we won't have tested the installer's code path that downloads the config.xml from the site. So I think it has to be two votes. FWIW, I am hopeful this is not the last release of the installer. I hope we continue to get rid of dependencies and need to change the installer again. > > This is just delaying the official 4.9 release announcement and stoping users > from installing the SDK. The main delay is caused by the delay in getting the final dist folder. >From reading board and infra emails, it appears that they are trying to finalize a script that creates all of the TLP infra but that is driven by having "final board minutes" which apparently have been delayed by the holiday season, although I see plenty of mods being made to the script. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 10:10 PM, "Om" wrote: > On Jan 1, 2013 9:49 PM, "Alex Harui" wrote: >> >> >> >> >> On 1/1/13 2:18 PM, "Nicholas Kwiatkowski" wrote: >> >>> Wouldn't we want to keep the config file on our website / SVN? It > seems to >>> me that placing the config file on any of the DISTS would be > disasterious, >>> as this contains the MD5 checksum that the app verifies to make sure the >>> release wasn't tampered by the dist... >> Interesting point. Anybody know wny we don't fetch the MD5 from the >> apache.org DIST (sans Mirror as recommended by Apache). >> > > The app is hardcoded to look at the apache site for the MD5 file. We don't > get it from any mirrors. Hmm. Then what is Nick's concern here? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
Ok, here is my logic: -From [1], a release is "anything that is published beyond the group that owns it.". Putting the config.xml on the site to be consumed by one of our binaries makes it part of a release and requires a vote before it happens. -Also from [1], " All releases are in the form of the source materials needed to make changes to the software being released.". The config file gets changed with each release and therefore IMO it is considered source materials even though it is not source code. -From [2], "The role of the PMC from a Foundation perspective is oversight. The main role of the PMC is not code and not coding - but to ensure that all legal issues are addressed, that procedure is followed, and that each and every release is the product of the community as a whole. That is key to our litigation protection mechanisms." and later "However those on the PMC are kept to a higher standard. As the PMC, and the chair in particular, are eyes and ears of the ASF Board, it is you that we rely on and need to trust to provide legal oversight. The board has the faculty to terminate a PMC at any time by resolution." As much as we want to get this release out the door, the fact is it is more important to make sure we are following policy. It is unfortunate that various logistical issues have prevented us from getting our final dist folder. But here we are and we have to work with Apache policy. [1] http://www.apache.org/dev/release#what [2] http://www.apache.org/foundation/how-it-works.html#pmc On 1/1/13 1:44 PM, "Justin Mclean" wrote: > Hi, > >>> Would you consider the disclaimer page to be part of the source? >> The DISCLAIMER file is in the source kit for incubating releases. > I was referring to the disclaimer link in the application not the DISCLAIMER > file. I don't think it is an issue if we pull up existing web pages, but IMO it is an issue to be publishing source materials on the site without a vote. > >> Source kits are (potentially filtered) dumps of what is in SVN. > And that correct with the installer, there's a source kit which someone can > take and compile the application. > >> I'm pretty sure Apache regulations would override any vote. > What "regulation" exactly? Can you point to me page that state that you can't > load XML files outside of it's SVN trunk? > >> This is potentially a legal issue > What is the legal issue here? The installer will be voted on and distributed > in the normal Apache Way (apache.org/dist). The XML file is also in SVN at > svn.apage.org that only Apache committers can access and change. The installer > will only download official Apache releases that have been voted on and placed > in apache.org/dist. > > I guess worse case a committer could modify the file XML file in SVN to > download another Apache binary kit but I think we would notice that and fix. > > Thanks, > Justin > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 2:00 PM, "Justin Mclean" wrote: > Hi, > >> 2) Is this a correct implementation? I'm wondering how would we test the >> next release. As soon as you replace/update that .xml file so we can test >> the next installer we are forcing everyone to suddenly start taking the next >> version. I understand you are saying we don't need to "test" the installer >> ever again, but I think we'd need to at least run it ourselves. > > When we make the next release of the SDK we can make teh change to the XML > (locally) and test the installer at the same time, once the vote has passed we > distrubite the new SDK and then update the XML file. Are you suggesting that the workflow is to use the -config switch for testing? Then we are not testing the final configuration. > >> 3) Is it reasonable to suddenly have the .xml file cause a different version >> to install to the customer's computer? > > The new version will only be be downloaded and installed if after the XML fie > is update the user runs the installers is again. It doesn't happen > suddenly/automatically. Right. If we are successful as a TLP, then somewhere in the world at any given time some developer will be installing some older version of Apache Flex on a computer. Many Flex shops are stuck on older versions because it takes a while to approve new versions for use. So they have to install those old versions again from time to time. And it would be an impediment if they suddenly got a newer versions instead. Now maybe the app can remember the last version installed and offer that one as the default and hint that there is a newer one available like updaters often do, but I don't think we should surprise them in a scenario like this. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 2:18 PM, "Nicholas Kwiatkowski" wrote: > Wouldn't we want to keep the config file on our website / SVN? It seems to > me that placing the config file on any of the DISTS would be disasterious, > as this contains the MD5 checksum that the app verifies to make sure the > release wasn't tampered by the dist... Interesting point. Anybody know wny we don't fetch the MD5 from the apache.org DIST (sans Mirror as recommended by Apache). -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 3:15 PM, "Nicholas Kwiatkowski" wrote: > I don't see why our binary distributions would be a problem to host > anywhere... The added stuff the installer downloads -- we can't host > those, but the binary stuff should be ok. > > I know that the people at Spoon have offered to host them. Want me to ping > them if it becomes a problem? > I would like to see Spoon decide whether they want to be this external entity that fills the gaps with Apache. One concern I have is that the name Spoon isn't all that meaningful anymore. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 3:09 PM, "Justin Mclean" wrote: > > Some other Apache projects have people who maintain binary distributions for > convenience and host them outside of Apache. Although in our case it could > probably only be hosted at Adobe due to the 3rd party licensing? Anyone know > if this would be possible? Actually, in theory, any entity can become an Adobe distributor. You fill out a form and various business folks at Adobe decide to approve you or not. I have not tried to make Apache such a distributor as I think it would be complicated to get Apache to execute a distributor's agreement since Adobe licensing is not Apache compatible. If I were to start my own "company" I would seek such a distributors agreement. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
OK, so this looks like a recent change. It seems to me the issues are: 1) Is it ok to take a .xml file from SVN and publish it on the web without a vote? Especially since it does not contribute to the content of our web site. 2) Is this a correct implementation? I'm wondering how would we test the next release. As soon as you replace/update that .xml file so we can test the next installer we are forcing everyone to suddenly start taking the next version. I understand you are saying we don't need to "test" the installer ever again, but I think we'd need to at least run it ourselves. 3) Is it reasonable to suddenly have the .xml file cause a different version to install to the customer's computer? I think the answer is "no" to all 3. Or did I miss a thread and the mentors approved #1? -Alex On 1/1/13 9:43 AM, "Om" wrote: > On Jan 1, 2013 8:22 AM, "Alex Harui" wrote: >> >> >> >> >> On 1/1/13 1:29 AM, "Om" wrote: >> >>> The config is not part of the source. There is only a reference to its > url >>> in the installer app. The installer was designed with this scenario in >>> mind. >>> >>> A copy is included as a convenience to the developer who uses it. In > that >>> sense it is more like a .properties file. >>> >>> We need to be able to change the sdk version without having to push an >>> update to the installer. Bundling the config xml with the source or > binary >>> will cause issues . >>> >> First, let me start off with saying that this kind of issue is a pain > point >> for me as well. Unfortunately, Apache doesn't release just binaries. I >> have definitely considered launching my own "company" to handle the stuff >> that Apache doesn't do very well, like binary distributions. >> >> AFAIK, the app cannot run without this file. We author it, it lives in our >> SVN, etc., so it is source. The definition for binary distro is a > compiled >> version of the source kit. I don't think you can remove files from the >> source distro in making it. >> > > The app will compile and run just fine even without the config xml being > present in the source or binary distro. It is NOT source. Like the Flex > SDK, .md5 file, the config xml is just another set of bytes that get > loaded during runtime to be processed. > > The config xml does not get compiled into the binary distro. > >> BTW, I'm not very familiar with .htaccess redirects, but I know we have to >> clear our builds from the incubator's dist folder when we get our final > dist >> folder. Would redirects still work for fetching the old incubator > release? >> > > If we just change the url for the flex sdk in the config xml that lives on > our website, there is no need for redirects. > >> How does the UI handle choosing which version to download? Justin went to >> all of this work to allow different player versions. We don't want to > lock >> folks down to the latest Flex version. >> > > You can pass a config xml with any combination of FP and AIR sdk via the > command line, using the -config option. > > Thanks, > Om -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 1:29 AM, "Om" wrote: > The config is not part of the source. There is only a reference to its url > in the installer app. The installer was designed with this scenario in > mind. > > A copy is included as a convenience to the developer who uses it. In that > sense it is more like a .properties file. > > We need to be able to change the sdk version without having to push an > update to the installer. Bundling the config xml with the source or binary > will cause issues . > First, let me start off with saying that this kind of issue is a pain point for me as well. Unfortunately, Apache doesn't release just binaries. I have definitely considered launching my own "company" to handle the stuff that Apache doesn't do very well, like binary distributions. AFAIK, the app cannot run without this file. We author it, it lives in our SVN, etc., so it is source. The definition for binary distro is a compiled version of the source kit. I don't think you can remove files from the source distro in making it. BTW, I'm not very familiar with .htaccess redirects, but I know we have to clear our builds from the incubator's dist folder when we get our final dist folder. Would redirects still work for fetching the old incubator release? How does the UI handle choosing which version to download? Justin went to all of this work to allow different player versions. We don't want to lock folks down to the latest Flex version. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 1/1/13 12:05 AM, "Justin Mclean" wrote: > Hi, > >> Apache only officially releases (and we are voting on) a source distribution >> for the installer. > Would a run time loaded config file be really considered part of that source? > Basically it's the same as the build.properties for the Flex SDK. While the > build.properties is part of the source release kit you generally need to edit > and change the values in it. Build.properties is compile-time. > > The XML file is not compiled into the source it can also be changed/edited by > the user to install other versions of the SDK or AIR. A "typical" version of > it is included in the source (just like build.properties) see > "sdk-insaller-config-2.0.xml" in the root src directory. > > Would you consider the disclaimer page to be part of the source? The DISCLAIMER file is in the source kit for incubating releases. > It's on the > wiki and linked to by the application. Or the cgi scipt it uses to get the > mirror? Where exactly do you draw the line? Source kits are (potentially filtered) dumps of what is in SVN. > > Either way when a vote is called for it only requires three more +1 than -1 > votes and I don't see this as a reason for voting -1. I'm pretty sure Apache regulations would override any vote. This is potentially a legal issue, so we have to get this right. I will do more research on the definitions of what is source. Hopefully our mentors will provide guidance as well. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 12/31/12 10:42 PM, "Justin Mclean" wrote: > HI, > >> Can we actually release this source if we don't have it pointing to the >> final dist folder for 4.9? > I think we can and that's not an issue. > > Only the XML file would need to change which in not in the installer > directory. > http://incubator.apache.org/flex/sdk-installer-config-2.0.xml Isn't that file in the source kit? > > The installer would not need to be recompiled so no vote would be required > IMO. Apache only officially releases (and we are voting on) a source distribution for the installer. IMO, the .xml file should be in the source kit and if we don't have a final version then we aren't ready to vote. The binary kit should probably have the .xml file as well since it is supposed to be a compiled version of the source distribution? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
On 12/31/12 10:23 PM, "Om" wrote: > Please take it for a spin and let us know your feedback. We would like to > put up a vote asap and release this right away! > Can we actually release this source if we don't have it pointing to the final dist folder for 4.9? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Editing SDK within Flash Builder
On 12/31/12 7:38 AM, "Matt Hughes" wrote: > Is there some guide for editing SDK classes within Flash Builder? > > I have installed Flex 4.9 and have also downloaded the source. I tried > just removing the mx.swc and framework.swc from the Build Path Libraries > and then adding the respective src folders. That seems to get me closer, > but now I have lots of errors because I don't have the config variable: > > CONFIG::performanceInstrumentation > > > defined. I'm trying to investigate a possible bug in the SDK while running > a small test project. I'd like to make changes to some SDK classes and see > if that resolves my problem. I couldn't find any guides on the main Flex > page or on the Apache Flex wiki on getting this set up. I don't know if there is one correct way of setting this up. Each swc folder should have FlashBuilder project files in it so you can import each folder as a project and set up your test app as dependent on those projects. As a shortcut for your current setup, I think you can just define that variable in the compiler options (and set it to false). -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Prepping for Installer 2.0 RC1
Not sure. Any chance you are pointing at AIR SDK 3.1 somehow? On 12/30/12 4:37 PM, "Om" wrote: > BTW, the app compiles and runs fine with Apache Flex 4.9/AIR 3.4 when I run > it from Flash Builder 4.6. > > On Sun, Dec 30, 2012 at 4:34 PM, Om wrote: > >> This is the error I am getting when I run ant release. Error in *bold* >> >> I googled this issue, it looks like quite a few folks have this issue with >> AIR 3.4. I have not been able to find out what is happening. Any ideas? >> >> C:\p\flex_os\workspace\flexroot\utilities\trunk\installer>ant release >> Buildfile: >> C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build.xml >> >> clean: >>[delete] Deleting directory >> C:\p\flex_os\workspace\flexroot\utilities\trunk\i >> nstaller\build >>[delete] Deleting directory >> C:\p\flex_os\workspace\flexroot\utilities\trunk\i >> nstaller\libs >>[delete] Deleting directory >> C:\p\flex_os\workspace\flexroot\utilities\trunk\i >> nstaller\release >> >> createDirs: >> [echo] >> [echo] >> >> >> [echo] Execute the update-version target once, and only once, >> when >> you modifiy this app. >> [echo] This will increment the version number to allow the >> app to b >> e updated by the AIR installer. >> [echo] >> >> >> [echo] >> [mkdir] Created dir: >> C:\p\flex_os\workspace\flexroot\utilities\trunk\install >> er\build >> [mkdir] Created dir: >> C:\p\flex_os\workspace\flexroot\utilities\trunk\install >> er\release >> >> update-version-in-xml-files: >> [echo] version in InstallApacheFlex-app.xml will be 2.0.0 >> >> init: >> >> certificate: >> >> check-as3commons.swc: >> >> get-as3commons.swc: >> [mkdir] Created dir: >> C:\p\flex_os\workspace\flexroot\utilities\trunk\install >> er\libs >> [get] Getting: >> http://projects.yoolab.org/maven/content/repositories/relea >> >> ses/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1. >> swc >> >> [get] To: >> C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\libs\a >> s3commons-zip-1.0.0-alpha.1.swc >> [get] ... >> [get] Getting: >> http://projects.yoolab.org/maven/content/repositories/relea >> >> ses/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1. >> swc >> .md5 >> [get] To: >> C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\libs\a >> s3commons-zip-1.0.0-alpha.1.swc.md5 >> [get] . >>[delete] Deleting: >> C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\ >> libs\as3commons-zip-1.0.0-alpha.1.swc.md5 >> >> compile: >> [mxmlc] Loading configuration file C:\Program Files (x86)\Adobe\Adobe >> Flash >> Builder 4.6\sdks\ApacheFlex4.9.0\frameworks\air-config.xml >> [mxmlc] >> C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build\Inst >> allApacheFlex.swf (1511233 bytes) >> >> abortBuild: >> >> *packageair:* >> * [java] >> C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\src\Instal* >> *lApacheFlex-app.xml: error 102: Invalid namespace >> http://ns.adobe.com/air/applic* >> *ation/3.4* >> >> BUILD FAILED >> C:\p\flex_os\workspace\flexroot\utilities\trunk\installer\build.xml:291: >> Java re >> turned: 12 >> >> Total time: 11 seconds >> >> On Sun, Dec 30, 2012 at 3:39 PM, Om wrote: >> >>> On Sun, Dec 30, 2012 at 3:36 PM, Justin Mclean >>> wrote: >>> >>>> Hi, >>>> >>>>> I am using Apache Flex 4.8 to build the installer. Which means AIR >>>> 3.1, >>>>> right? >>>> >>>> I think we should be using AF 4.9/AIR 3.4 - be nice if the SDK and >>>> installer were in sync. >>>> >>>> Justin >>>> >>>> >>> Makes sense. i will get on it now. Mind posting what errors you are >>> seeing? >>> >>> Om >>> >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Prepping for Installer 2.0 RC1
Any chance you are pointing to a Windows AIR SDK and not the Mac SDK for AIR? On 12/30/12 5:09 PM, "Justin Mclean" wrote: > Hi, > > I'm getting a different error: > > packagenative: > [java] SDK is missing file > /Users/justinmclean/Documents/air/mac/AdobeAIRSDK/lib/nai/bin/naip > > BUILD FAILED > /Users/justinmclean/Documents/Adobe Flash Builder 4.6/Apache Flex > Utilities/installer/build.xml:203: Java returned: 5 > > Looking at that directory I have 2 exe files - which can't run on OSX. > > ls /Users/justinmclean/Documents/air/mac/AdobeAIRSDK/lib/nai/bin/ > naip.exe nais.exe > > Thanks, > Justin > > > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [MENTOR] wiki access
I added you to the individual users and gave you permission. I couldn't figure out how to add you to a group. Maybe I don't have privileges for that yet. Let me know if it works or not. On 12/30/12 2:44 PM, "Cyrill Zadra" wrote: > Hi > > I'd like to request wiki write access. My wiki account: > cyrill.za...@gmail.com - Cyrill Zadra. > > thanks > cyrill -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Writable AST and Code generation for Falcon was: [Re: [jira] [Commented] (FLEX-33330) ... )
On 12/30/12 4:57 AM, "Michael Schmalle" wrote: > > Quoting Alex Harui : > >> >> >> >> On 12/29/12 8:52 AM, "Michael Schmalle" wrote: >> >>> I know when I wrote ASDoc, I was able to resolve everything but I used >>> the MXML compiler as a base. I just need to really understand what is >>> going on now. I takled the multithreading in FalconJx, but when I >>> debug, the multithreading is over after; >>> >>> >>> final File outputFolder = new File(outputFile.getParent()); >>> List reachableCompilationUnits = project >>> >>> .getReachableCompilationUnitsInSWFOrder(ImmutableSet >>> .of(mainCU)); >>> >>> Once this returns I swear it's synced back on 1 thread. After that >>> call I loop through all reachable units and produce .js files for each. >> Interesting. I agree by the time you get here we're back on one thread. >> But I'm pretty sure the reducers and emitters have been called at least for >> some threads by then. >> >> I hadn't noticed that was when you were starting your tree walk for >> FalconJx. I thought you were walking in response to the abcbytes request, >> but I'm pretty sure when I'm debugging FalconJS, that happens while many >> threads are spinning. > > Yes, this is true. I spent 2 hours on this now and have figured it out. > > Really, I think there are multiple ways you can implement things here. > With the current FalconJS they utilized the existing production > framework. > > Honestly, the way I first did it, I don't see a real problem with it > other than not using the multiple threads to create the actual > javascript source code (String) like I am doing. Yes, I agree you will get correct output by waiting until the threads are done, but then are you going to create degenerate reducers/emitters so you don't spend time creating ABC instruction lists which is what the threads seem to be doing? Otherwise, you will be inefficient by whatever time is spent generating ABC. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Writable AST and Code generation for Falcon was: [Re: [jira] [Commented] (FLEX-33330) ... )
On 12/29/12 8:58 AM, "Michael Schmalle" wrote: > And one other thing; > > I thought this compiler was written for FlashBuilder, this means Adobe > has a huge API for saying files have changed, updating scopes ect. Probably true. > > In the IWorkspace API you can see evidence of this. Which means in a > code editor, you are updating source files all the time and > reconnecting definitions in the global symbol table which is the > workspace which holds projects which hold their compilation units. I > see the projects ass the ponds holding the compilation unit boats and > the workspace as the earth holding all the ponds, excuse the cheesy > analogy. > > I might be looking at this naively but I think my assumptions have some value. Could be. I haven't run into any need to know about the workspace. And I believe in the way I'm running FalconJS right now, only one ICompilerProject exists, but I don't know if that is supposed to map to FB projects or not. So far I haven't needed to know that either. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Writable AST and Code generation for Falcon was: [Re: [jira] [Commented] (FLEX-33330) ... )
On 12/29/12 8:52 AM, "Michael Schmalle" wrote: > I know when I wrote ASDoc, I was able to resolve everything but I used > the MXML compiler as a base. I just need to really understand what is > going on now. I takled the multithreading in FalconJx, but when I > debug, the multithreading is over after; > > > final File outputFolder = new File(outputFile.getParent()); > List reachableCompilationUnits = project > .getReachableCompilationUnitsInSWFOrder(ImmutableSet > .of(mainCU)); > > Once this returns I swear it's synced back on 1 thread. After that > call I loop through all reachable units and produce .js files for each. Interesting. I agree by the time you get here we're back on one thread. But I'm pretty sure the reducers and emitters have been called at least for some threads by then. I hadn't noticed that was when you were starting your tree walk for FalconJx. I thought you were walking in response to the abcbytes request, but I'm pretty sure when I'm debugging FalconJS, that happens while many threads are spinning. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Writable AST and Code generation for Falcon was: [Re: [jira] [Commented] (FLEX-33330) ... )
On 12/29/12 8:26 AM, "Michael Schmalle" wrote: >> FWIW, my understanding of Falcon is that each class source file is a >> compilation unit and compilation units are parsed in separate threads. >> Therefore there is no actual point where all ASTs are sitting around. I can >> see a callback when the ASTs for a individual compilation unit is ready to >> be reduced, but I don't know if you can or want to synchronize all AST >> generation across all compilation units. > > I think you're half correct. If you look at it from a parsing point > your correct, but if you look at it from a definition compilation > point it's incorrect. > > To create a SWF file, Falcon uses the Workspace and a step to > reconnect all scopes which is syncornized after all compilation units > have been parsed. I hadn't noticed that. I will look for it next time I'm wading through the compiler. What I thought I saw was that a unit would request abc from another unit, which would result not only in its parsing but in its reduction to byte code which I would think you would want to avoid if you are trying to sync everything up. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Writable AST and Code generation for Falcon was: [Re: [jira] [Commented] (FLEX-33330) ... )
On 12/29/12 5:02 AM, "Roland Zwaga" wrote: > Well, I think the fastest communication protocol would actually be AMF. I > see no reason why an ANE couldn't send AMF back and forth. And all of the > serialization logic already exists for that, so implementing it should, > theoratically, be quite straightforward... Probably, but those are tied to Flash/AIR. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Writable AST and Code generation for Falcon was: [Re: [jira] [Commented] (FLEX-33330) ... )
On 12/29/12 5:19 AM, "Roland Zwaga" wrote: > Hm, sounds pretty sweet. If its not too much work to create a small > experiment to proof your theory than this could be a worthy approach :) > Generating extra classes etc shouldn't be a problem I suppose? > What the AOP bits would do, in a nutshell, would basically be renaming an > existing class, creating a new class with the old name of this class (and > making it a subclass of the original) and then creating overridden methods > in the new class. Questions: why isn't this more like injecting an include file into a class's source code? Why rename the base class and add more classes to the mix? > Come to think of, with this approach we wouldn't even need to inject > subtrees into existing AST's... All I need to do is rename certain classes, > I'm guessing that that wouldn't be too much of a hassle, right? FWIW, my understanding of Falcon is that each class source file is a compilation unit and compilation units are parsed in separate threads. Therefore there is no actual point where all ASTs are sitting around. I can see a callback when the ASTs for a individual compilation unit is ready to be reduced, but I don't know if you can or want to synchronize all AST generation across all compilation units. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Any issues with binary compile instructions?
On 12/28/12 9:26 PM, "Justin Mclean" wrote: > Hi, > > Seen a couple of complaints on twitter with people having issue > installing/compiling. Great to know folks are using. Please point them to the flex-users list for assistance. > > Are the instructions on this page for the binary release correct? Should it > mention makeFlexSDKForFlashBuilder.sh? > http://incubator.apache.org/flex/download.html Is the issue getting it to work in FB or other IDE? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Issue with merging release with trunk
On 12/28/12 9:09 PM, "Justin Mclean" wrote: > Hi, > >> Did you revert the trunk checkins that shouldn't have been checked in? > > No just overrode anything in conflict with the release version, everything > should of been in develop/release anyway. (ie same changes checked in twice) Well, it leaves the history a bit off because it might fool someone else into committing into trunk and it will only get checked in once, I think. Those files that were already changed probably aren't in the commit for the merge since there were no diffs. But I guess it will be ok. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Issue with merging release with trunk
On 12/28/12 6:14 PM, "Justin Mclean" wrote: > Hi, > >> I did a full checkout of trunk, and merge no longer gave that error but it >> took so long it timed out. > Looks like if you check out on people.a.o it works, I'll do a merge, check in > and tag. Anything that in conflict I'll take the the release version (there a > few things). Excellent. I'm pulling down trunk to run mustella. Did you revert the trunk checkins that shouldn't have been checked in? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Issue with merging release with trunk
I did a full checkout of trunk, and merge no longer gave that error but it took so long it timed out. There were tons of mustella updates because we did all of the mustella test fixing in develop branch. I think the right thing to do is for me to try to merge in the mustella folder (maybe in chunks if it can't handle it) then see what else is missing. Somebody should revert the unintended checkins to trunk. I can do it if nobody else wants to. -Alex On 12/26/12 10:06 PM, "Alex Harui" wrote: > I've gotten timeouts on vcc/default during updates and checkouts. I think > that is a different issue and a known bug in svn. > > This error seems different, so not sure what the issue is. > > > On 12/26/12 10:00 PM, "Justin Mclean" wrote: > >> Hi, >> >>> I got the same error trying to do an svn update. >> >> I was about to do a full check out of both trunk and develop with no issues >> over a slow link, but the merge dry run gave that error. I've not seen the >> issue before. >> >> It seem to happen at random times, ie some times it would get further than >> others with the merge. Perhaps we should raise an infra JIRA bug? >> >> Thanks, >> Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [wiki] created flex-contributors group
On 12/28/12 8:29 AM, "Bertrand Delacretaz" wrote: > On Fri, Dec 28, 2012 at 5:14 PM, Alex Harui wrote: >> ...One question though: do we need ICLAs from folks who want write >> access to the wiki?... > > I'd say it's good to have, but a contribution on the wiki is > definitely voluntary, it cannot happen by mistake - so even without an > iCLA it's IMO clear that said contribution belongs to the ASF. OK, I get that it is voluntary, but it would seem to me we would want a paper trail that shows that the contributions are authorized by copyright owner (which in this case would be Frank's employer)? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [wiki] created flex-contributors group
On 12/28/12 7:27 AM, "Dave Fisher" wrote: > > On Dec 28, 2012, at 7:07 AM, Bertrand Delacretaz wrote: > >> Hi, >> >> FYI flex-administrators, I have created a flex-contributors group, >> with the same rights as flex-committers for now, and added Frank >> Wienberg to it as per his request. It's probably more convenient to >> handle contributors permissions in this way, but I'm not sure what >> level of confluence permissions you need to be able to change that. >> >> Anyway, I have also added Alex and Justin to the flex-administrators >> group, so that they can grant access to others as needed. > > I like this solution. I'm around to help as well. Bertrand beat me to this > request by 30 minutes :-) > Thanks. One question though: do we need ICLAs from folks who want write access to the wiki? Frank, in particular, works for a company that has already delivered a product in the topic area, and even though the company's source code is open and lots of Frank's thoughts are on his blog, do we need to be extra careful about his contributions to Apache wikis? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [FalconJx] Package down to Expression production; JSGoogEmiter prototype
On 12/27/12 5:33 AM, "Erik de Bruin" wrote: > > I'm not sure how your solution provides for this? Mine doesn't either, > mind you, but I gave up perfection for simplicity very early in this > thread ;-) > +1 on simplicity vs perfection. IMO, If you take on full AS to JS cross-compilation, it is a very difficult task full of these edge cases. But I want to (at least at first) only cross-compile a subset of AS to JS. I am hopeful there is a subset that is straight forward to cross-compile that is sufficient enough for folks to build enterprise class apps. We would add warnings/errors to the compiler to catch the edge cases like untyped or (* typed) optional params. I think I recall that for..in iteration of classes is also an issue. Seems like we could live without that or require that you provide a filter function for the cases where you need it. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[jira] [Commented] (FLEX-33330) An easier way of managing the locales for the InstallApache application
[ https://issues.apache.org/jira/browse/FLEX-0?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539984#comment-13539984 ] Alex Harui commented on FLEX-0: --- Thanks. But does anybody know why the installer doesn't use .properties files and the ResourceManager? > An easier way of managing the locales for the InstallApache application > --- > > Key: FLEX-0 > URL: https://issues.apache.org/jira/browse/FLEX-0 > Project: Apache Flex > Issue Type: Improvement > Components: InstallApacheFlex >Reporter: Roland Zwaga >Priority: Minor > Labels: InstallApacheFlex, utility > Fix For: InstallApacheFlex 1.1 > > Attachments: ApacheFlexInstallerLocaleEditor.zip > > > Right now updating the translation for an existing locale, or creating a new > locale for the InstallApache application involves quite a bit of > copy/pasting. While the list of locales grows this problem will grow with it, > IMHO. > To try and combat this complexity I've created a small AIR application which > is capable of loading, parsing and editing the RuntimeLocale.as (which > contains all of the locale data) file of the InstallApache project. > I'll attach both an FXP export of the FlashBuilder project as well as an AIR > installer for the application. > Should folks find the app useful I'll be happy to donate the code to Apache > Flex. > A huge credit goes out to Michael Schmalle who created the asblocks library > (https://github.com/teotigraphix/as3-commons-asblocks) which takes care of > the parsing and editing of actionscript source files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Apache Flex 4.9 release on web site
The xml file for the installer will need to be changed then we will need a separate vote on its release. I think we need to hold off on its release until we get our TLP dist folder. We could release twice (sooner for the incubator URL) and again when we get our dist folder, but I'm hoping that we get our dist folder soon. On 12/27/12 6:29 AM, "Erik de Bruin" wrote: > Yes, I believe there was. But to my knowledge the 'interface' in the > XML file hasn't been altered, so the change I indicated will need to > implemented anyway. > > EdB > > > > On Thu, Dec 27, 2012 at 3:26 PM, Nicholas Kwiatkowski > wrote: >> ok. Was there a new version of the installer that was being produced? I >> thought I remember one being worked on (although, I'd admit I wasn't paying >> very good attention to it). >> >> -Nick >> >> On Thu, Dec 27, 2012 at 8:46 AM, Erik de Bruin wrote: >> >>> In sdk-installer-config.xml the line: >>> >>> >> path="incubator/flex/4.8.0-incubating/binaries/" >>> file="apache-flex-sdk-4.8.0-incubating-bin.zip" /> >>> >>> Needs to be updated to point to the latest SDK. That should be enough >>> to update both the Installer and InstallerBadge functionality. >>> >>> EdB >>> >>> >>> >>> On Thu, Dec 27, 2012 at 2:41 PM, Nicholas Kwiatkowski >>> wrote: >>>> But otherwise -- it looks good to me. I made a few quick changes on the >>>> index to add the date of the release. >>>> >>>> I'm showing that about 90% of the dists have the images now. From >>>> experience, it took the full 24 hours for all of them to get it. We >>> should >>>> publish the pages then. >>>> >>>> Do you know if the SDK installer is good to go as well? Is there >>> anything >>>> we need to do to get that page on the website updated? >>>> >>>> -Nick >>>> >>>> On Thu, Dec 27, 2012 at 8:34 AM, Nicholas Kwiatkowski >>> wrote: >>>> >>>>> Did you push those changes in the CMS? I don't see them on the staging >>>>> server yet. I do see them in SVN, though. I can take care of that for >>>>> you, if you wish. >>>>> >>>>> -Nick >>>>> >>>>> >>>>> On Thu, Dec 27, 2012 at 1:32 AM, Justin Mclean < >>> jus...@classsoftware.com>wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I've added some information to the web site for the 4.9 release, if >>>>>> someone could review and make it live I'd appreciate it. >>>>>> >>>>>> Paged edited include index, download and timeline. >>>>>> >>>>>> Thanks, >>>>>> Justin >>>>> >>>>> >>>>> >>> >>> >>> >>> -- >>> Ix Multimedia Software >>> >>> Jan Luykenstraat 27 >>> 3521 VB Utrecht >>> >>> T. 06-51952295 >>> I. www.ixsoftware.nl >>> > > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 dist and 4.8 archive
On 12/26/12 11:38 PM, "Justin Mclean" wrote: > Hi, > >> Crap. While waiting for the upload I saw this on [2]. So I guess this >> isn't going to work out. > > That's OK for now. > > 4.9.0 is currently in the incubator directory (which I assume will be > mirrored) and we can use that until we sort out the exact process. OK, I hope we don't get in trouble for that (non-incubating artifacts in the incubator folder), but hopefully this will all get sorted out shortly. I'm done for tonight. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 dist and 4.8 archive
Crap. While waiting for the upload I saw this on [2]. So I guess this isn't going to work out. Note: Infra will require projects to transition to this method of managing their dist/ dir. For this transition infra needs: to setup svnpubsub for the dist directory, and know what mailing list commit mails should go to. [2] http://www.apache.org/dev/release.html On 12/26/12 10:51 PM, "Alex Harui" wrote: > I am working from here [1] where it says: > > www.apache.org > Each Apache TLP has a release/TLP-name directory in the distribution > Subversion repository at https://dist.apache.org/repos/dist/. Once a release > vote passes, the release manager should svn add the artifacts (plus > signature and hash files) into this location. Each project is responsible > for the structure of its directory. The contents of these directories are > pushed to http://www.apache.org/dist/ by svnpubsub. Note that only the most > recent release of each supported release line should be contained here; see > here. > > Maven Distribution > See the Publishing Maven Releases guide. > > I've Just Published A Release: Why Isn't It Available From XYZ? > Apache uses mirroring both internally and externally. This process runs to a > schedule. First the files on people.apache.org are mirrored to > www.apache.org , and then the external mirrors pick up the files from > www.apache.org. It may take up to 24 hours or more for a newly published > release to be sync'd to all mirrors. Mirrors have their own schedules. > Mirrors are required to check at least once a day, but most will check for > updates 2 to 4 times per day. > > > [1] http://www.apache.org/dev/release-publishing.html > > I will try to upload your artifacts via SVN. I'll email again when done. > > > On 12/26/12 10:44 PM, "Justin Mclean" wrote: > >> Hi, >> >>> Maybe I have enough karma as PMC Chair. I made a release/flex directory and >>> it seemed to work. See if you can svn add to it. >> >> Not sure I have SVN access. My understanding was you just copied the files >> across to the dist directory and it got mirrored after 24 hours or so. >> >> If I do this: >> ls -las /www/www.apache.org/dist/flex >> >> I get: >> ls: /www/www.apache.org/dist/flex: No such file or directory >> >>> Archives are here: http://archive.apache.org/ >>> I looked and it appears that 4.8 and the installer are there. >> So once 4.9.0 has appeared in all the mirrors I'll delete it and update the >> release notes. >> >> Thanks, >> Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 dist and 4.8 archive
I am working from here [1] where it says: www.apache.org Each Apache TLP has a release/TLP-name directory in the distribution Subversion repository at https://dist.apache.org/repos/dist/. Once a release vote passes, the release manager should svn add the artifacts (plus signature and hash files) into this location. Each project is responsible for the structure of its directory. The contents of these directories are pushed to http://www.apache.org/dist/ by svnpubsub. Note that only the most recent release of each supported release line should be contained here; see here. Maven Distribution See the Publishing Maven Releases guide. I've Just Published A Release: Why Isn't It Available From XYZ? Apache uses mirroring both internally and externally. This process runs to a schedule. First the files on people.apache.org are mirrored to www.apache.org , and then the external mirrors pick up the files from www.apache.org. It may take up to 24 hours or more for a newly published release to be sync'd to all mirrors. Mirrors have their own schedules. Mirrors are required to check at least once a day, but most will check for updates 2 to 4 times per day. [1] http://www.apache.org/dev/release-publishing.html I will try to upload your artifacts via SVN. I'll email again when done. On 12/26/12 10:44 PM, "Justin Mclean" wrote: > Hi, > >> Maybe I have enough karma as PMC Chair. I made a release/flex directory and >> it seemed to work. See if you can svn add to it. > > Not sure I have SVN access. My understanding was you just copied the files > across to the dist directory and it got mirrored after 24 hours or so. > > If I do this: > ls -las /www/www.apache.org/dist/flex > > I get: > ls: /www/www.apache.org/dist/flex: No such file or directory > >> Archives are here: http://archive.apache.org/ >> I looked and it appears that 4.8 and the installer are there. > So once 4.9.0 has appeared in all the mirrors I'll delete it and update the > release notes. > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 dist and 4.8 archive
On 12/26/12 10:14 PM, "Justin Mclean" wrote: > Hi, > >> AFAICT, they haven't serviced the main TLP JIRA so I'm not surprised. I >> assume you tried to make the directory? > Yep - permission denied :-) Maybe I have enough karma as PMC Chair. I made a release/flex directory and it seemed to work. See if you can svn add to it. > >> I've seen some emails indicating that dist is automatically archived. Is it >> not already in the archive? > To be honest I don't even know were the archive is. > Archives are here: http://archive.apache.org/ I looked and it appears that 4.8 and the installer are there. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Issue with merging release with trunk
I've gotten timeouts on vcc/default during updates and checkouts. I think that is a different issue and a known bug in svn. This error seems different, so not sure what the issue is. On 12/26/12 10:00 PM, "Justin Mclean" wrote: > Hi, > >> I got the same error trying to do an svn update. > > I was about to do a full check out of both trunk and develop with no issues > over a slow link, but the merge dry run gave that error. I've not seen the > issue before. > > It seem to happen at random times, ie some times it would get further than > others with the merge. Perhaps we should raise an infra JIRA bug? > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 dist and 4.8 archive
On 12/26/12 9:57 PM, "Justin Mclean" wrote: > Hi, > > Currently there no top level flex directory in www.apache.org/dist. I've > raised a JIRA issue for this: > https://issues.apache.org/jira/browse/INFRA-5706 AFAICT, they haven't serviced the main TLP JIRA so I'm not surprised. I assume you tried to make the directory? > > Until that's resolve I've placed the 4.9 release here: > http://www.apache.org/dist/incubator/flex/4.9.0/ > > Does anyone know where the 4.8.0 release directory need to be moved so that > it's archived? This will need to be added to the release steps. I've seen some emails indicating that dist is automatically archived. Is it not already in the archive? And then I think you simply delete it from dist. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Issue with merging release with trunk
I got the same error trying to do an svn update. I am checking out trunk now which seems to be working. Then I'll try merge again, but it may not finish before I stop for the night. On 12/26/12 9:50 PM, "Nicholas Kwiatkowski" wrote: > I'm getting the same error at the moment. It is possible that something is > screwed up at Apache's SVN again. I get this error every few weeks for a > few hours. > > -Nick > > On Wed, Dec 26, 2012 at 4:48 PM, Justin Mclean > wrote: > >> Hi, >> >> Can someone be kind enough to run this from the base of a clean checked >> out trunk and mail the output to the list. >> >> svn --dry-run merge >> https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/release4.9 >> >> This is a dry run so no changes will occur it will just tell you what >> changes will occur. >> >> I've run it several times but I keep getting this error: >> SSL handshake failed: Broken pipe (https://svn.apache.org) >> >> I'd assume it's my current slow connection that causing an issue. >> >> Thanks, >> Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Merging release into develop issue?
lines/datagrid_heigh > t_30.png > Cmustella/tests/components/AdvancedDataGrid/Properties/Baselines/phone.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_inser > tcolumn_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_hiera > rch_data_colgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_enabl > ed2.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_y_50. > png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_verti > calscrollposition.png > Cmustella/tests/components/AdvancedDataGrid/Properties/Baselines/date.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_horiz > ontalscrollpolicy_off.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_inser > tcolumngroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_x_min > us10.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_y_min > us10.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_colum > nspanning_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/groupview.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_group > edview_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/zipcode.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_tree_ > displayitemsexpanded.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_multi > cellselection.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_custo > mheaderrenderer_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/property_layou > tDirection_rtl.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/property_layou > tDirection_ltr.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_verti > calscrollpolicy_on.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_focus > enabledfalse.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_tree_ > singlecellselection.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/property_layou > tDirection_application.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_heade > rrenderer_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_rowco > unt_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_x_50. > png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_tree_ > multicellselection.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_group > editable_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/columnspan.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_iteme > ditable_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_width > _30.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/style1.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/style2.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_horiz > ontalscrollpolicy_on.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/style3.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_visib > le_withcolgroups.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_singl > ecellselection.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/property_layou > tDirection_application_ltr.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_heigh > t_200.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/number.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_treev > iew.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_heigh > t_120.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_dragg > ablecolumns_state1.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_focus > enabledtrue.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/currency.png > C > mustella/tests/components/AdvancedDataGrid/Properties/Baselines/datagrid_dragg > ablecolumns_state2.png > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: undated built release notes
On 12/25/12 8:26 PM, "Justin Mclean" wrote: > Hi, > > I've updated; > https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK > > In particular to take into account the develop and release branches. > > This a slight issue with tagging the release as the release is built from the > release branch, but I assume we would want to tag the trunk after the release > branch has been merged with it. In theory there should be no changes in the > trunk, but it seems there been a few occasions when people have checked stuff > into the trunk accidentally or otherwise so we're likely to get a conflict or > two so what end up getting tagged by not actually be what was released. The > whole point of having seperate release, develop and trunk branch was that > trunk is the last good know release. > > Any suggestions of how to improve this process? Well, we should be vetoing any checkins to trunk. But I think folks aren't quite sure how to revert (it is sort of a pain in SVN) and some things didn't get reverted. I know there's sort of a rule about not reverting someone else's changes, but I think it is ok in this case. If you can, verify that the change that went into trunk did actually end up in develop, then revert it out of trunk. > > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [VOTE] Apache Flex 4.9 RC7
+1 (binding) PGP key matches for tar.gz and zip for both src and bin kits MD5 matches for tar.gz for src kit (didn't check src zip). MD5 matches for tar.gz and zip for bin kits Src kits built on both Mac and Win with FP11.1 Mustella passes on src kits on both Mac and Win with FP11.1 Installer installed bin kits on both Mac and Win. FB accepted results as a valid Flex SDK (4.6 on Mac, 4.7 on Win) Test apps compiled and ran in FB in both Mac and Win. Rat-check passed. README, LICENSE, NOTICE, and RELEASE_NOTES seem ok. Good work Justin! I think we keep an eye out for any negative votes then after 72 hours the packages can be moved out to dist. I can probably do it if your internet is too slow. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] [VOTE] Apache Flex 4.9 RC7
Nick, Please vote in the [VOTE] thread (not the [DISCUSS] thread). Thanks, -Alex On 12/24/12 7:32 AM, "Nicholas Kwiatkowski" wrote: > +1 > > Was able to build from source with no issues on Win7 + Java7. No issues > with the ANT script. Output created my AIR projects as expected. > Was able to use the binaries with no issues on Win7. No issues with the > outputs. > > Non-blocking -- Noticed that the URL in the samples\themes\README.txt still > points to opensouce.adobe.com, for a discussion about submitting updated > themes. Don't know if it supposed to or not. > > Thanks for the hard work Justin! > > -Nick > > On Mon, Dec 24, 2012 at 4:34 AM, Om wrote: > >> Justin, I dont see your PGP key here [1] >> According to this page [2], the release manager's public key should be >> present on that page for users to verify the artifacts. >> >> Thanks, >> Om >> >> >> [1] http://www.apache.org/dist/incubator/flex/KEYS >> [2] http://incubator.apache.org/flex/download.html >> >> >> -- Forwarded message -- >> From: Justin Mclean >> Date: Sun, Dec 23, 2012 at 9:15 PM >> Subject: [VOTE] Apache Flex 4.9 RC7 >> To: flex-dev@incubator.apache.org >> >> >> Hi, >> >> This is a Apache Flex 4.9.0 release candidate 7. Please see the >> RELEASE_NOTES and the README. >> >> Fixed in this release candidate: >> - Fix minor issue with 2 files failing rat license test >> - Minor changes to README >> >> The release candidate can be found here; >> >> http://people.apache.org/~jmclean/Apache%20Flex%204.9.0%20Release%20Candidate >> %207/ >> >> 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 >> >> 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 given >> it's the holidays. >> >> The vote passes if there is: >> - At least 3 +1 votes from the PMC >> - More positive votes than negative votes >> >> When voting please indicate what platform and IDE you compiled and tested >> the SDK with. >> >> Please put all discussion about this release in a DISCUSSION thread not >> this VOTE thread. >> >> Thanks, >> Justin >> >> PS Brought to you over a satellite link and made with solar power :-) >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS] [VOTE] Apache Flex 4.9 RC7
Justin's key is in the release branch's KEYS file. We'll put it up on dist when everything else goes up there (and presumably, not in the incubator folder). On 12/24/12 1:34 AM, "Om" wrote: > Justin, I dont see your PGP key here [1] > According to this page [2], the release manager's public key should be > present on that page for users to verify the artifacts. > > Thanks, > Om > > > [1] http://www.apache.org/dist/incubator/flex/KEYS > [2] http://incubator.apache.org/flex/download.html > > > -- Forwarded message -- > From: Justin Mclean > Date: Sun, Dec 23, 2012 at 9:15 PM > Subject: [VOTE] Apache Flex 4.9 RC7 > To: flex-dev@incubator.apache.org > > > Hi, > > This is a Apache Flex 4.9.0 release candidate 7. Please see the > RELEASE_NOTES and the README. > > Fixed in this release candidate: > - Fix minor issue with 2 files failing rat license test > - Minor changes to README > > The release candidate can be found here; > http://people.apache.org/~jmclean/Apache%20Flex%204.9.0%20Release%20Candidate% > 207/ > > 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 > > 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 given > it's the holidays. > > The vote passes if there is: > - At least 3 +1 votes from the PMC > - More positive votes than negative votes > > When voting please indicate what platform and IDE you compiled and tested > the SDK with. > > Please put all discussion about this release in a DISCUSSION thread not > this VOTE thread. > > Thanks, > Justin > > PS Brought to you over a satellite link and made with solar power :-) -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS][VOTE] APACHE FLEX 4.9 RC6
I saw your checkin. I agree that is the right thing to do. I ran ant main release and rat is clean. I'm ready for the next RC. Let me know if you need help. On 12/23/12 1:01 PM, "Justin Mclean" wrote: > I take a look at this today -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS][VOTE] APACHE FLEX 4.9 RC6
Some packages.dita files appear to be checked into SVN. So not all seem to be generated. And the ones not generated need headers. That's is a pretty clear rule from Apache. So, at some point today, one of needs to figure out: 1) Are they all generated and thus none should be in SVN? 2) If generated, then clean before RAT or exclude from RAT 3) If not generated, add headers or exclude from RAT. Basically, we need to tweak something so that RAT is clean. And that tweak will likely force a new RC. And I'm still pondering why it didn't show up on the first run. I think I ran release twice without running main in between so maybe that didn't clean something? What do you get when you run RAT? If it is a bug because I ran it twice, then maybe we can ignore, but the missing header in ErrorArray.as that I fixed last night forces an RC7, unfortunately. On 12/23/12 1:53 AM, "Om" wrote: > On Dec 23, 2012 1:12 AM, "Justin Mclean" wrote: >> >> Hi, >> >>> Rat-check failed with two issues. I'm fixing that now and running rat > again >>> (takes about an hour). I also fixed a minor issue in the README since > we're >>> going to have to re-kit again. >> >> It does look like it related to as_docs, at a guess the en_US locale is > hard coded in the clean and that may be causing an issue. You didn't happen > to compile for another locale did you? I think in that case these file > would be left about if you compiled for en_US then another locale. >> >> Do you really think this is an issue that should stop a release? They are > 2 generated XML files, they are not in source control regenerating the > asdocs will create them. > > Generated files can be excluded from the rat report. > > But if we are going to sign the asdoc package, then any changes to the > package has to be signed again which works need a new RC. > > Thanks, > Om > >> >> Thanks, >> Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS][VOTE] APACHE FLEX 4.9 RC6
OK, checked in a build.xml that excludes a batik icon. Strangely, on this run, RAT caught packages.dita files in rpc and textlayout. It is too late at night for me to figure out why there were not in the first rat report. Maybe you have a better knowledge of what these files are for. Hopefully you can figure it out. If not, I may not get to look until my Sunday evening. On 12/22/12 10:55 PM, "Alex Harui" wrote: > Justin, > > Rat-check failed with two issues. I'm fixing that now and running rat again > (takes about an hour). I also fixed a minor issue in the README since we're > going to have to re-kit again. > > I'll email again with the all clear when rat is clean and I check in > build.xml. > > While waiting for rat I read the README, LICENSE, NOTICE and RELEASE NOTES. > They all look good, but I did notice the RELEASE_NOTES say that asdoc > doesn't contain TLF. Do you know if that's true? Is the RM supposed to > generate an asdoc package as well? > > I think I have finally covered all criteria I would use to vote. Mustella > passes on 11.1 on Win and Mac. Binaries work. All the text files in the > root look ok to me. Signatures and MD5's matched. > > I think if we fix up RAT we should be good to go. Did your RAT report show > one binary and one unapproved license? > > -Alex > > > On 12/22/12 9:02 PM, "Justin Mclean" wrote: > >> Hi, >> >> This is a Apache Flex 4.9.0 release candidate 6. Please see the >> RELEASE_NOTES >> and the README. >> >> Fixed in this release candidate: >> - Fix so that the release build compiles the experimental projects (issue >> with >> empty.properties being removed from binary package) >> >> The release candidate can be found here; >> http://people.apache.org/~jmclean/Apache%20Flex%204.9.0%20Release%20Candidate>> % >> 206/ >> >> 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 >> >> 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 given it >> holidays. >> >> The vote passes if there is: >> - At least 3 +1 votes from the PMC >> - More positive votes than negative votes >> >> When voting please indicate what platform and IDE you compiled and tested >> the >> SDK with. >> >> Please put all discussion about this release in a DISCUSSION thread not this >> VOTE thread. >> >> Thanks, >> Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [DISCUSS][VOTE] APACHE FLEX 4.9 RC6
Justin, Rat-check failed with two issues. I'm fixing that now and running rat again (takes about an hour). I also fixed a minor issue in the README since we're going to have to re-kit again. I'll email again with the all clear when rat is clean and I check in build.xml. While waiting for rat I read the README, LICENSE, NOTICE and RELEASE NOTES. They all look good, but I did notice the RELEASE_NOTES say that asdoc doesn't contain TLF. Do you know if that's true? Is the RM supposed to generate an asdoc package as well? I think I have finally covered all criteria I would use to vote. Mustella passes on 11.1 on Win and Mac. Binaries work. All the text files in the root look ok to me. Signatures and MD5's matched. I think if we fix up RAT we should be good to go. Did your RAT report show one binary and one unapproved license? -Alex On 12/22/12 9:02 PM, "Justin Mclean" wrote: > Hi, > > This is a Apache Flex 4.9.0 release candidate 6. Please see the RELEASE_NOTES > and the README. > > Fixed in this release candidate: > - Fix so that the release build compiles the experimental projects (issue with > empty.properties being removed from binary package) > > The release candidate can be found here; > http://people.apache.org/~jmclean/Apache%20Flex%204.9.0%20Release%20Candidate% > 206/ > > 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 > > 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 given it > holidays. > > The vote passes if there is: > - At least 3 +1 votes from the PMC > - More positive votes than negative votes > > When voting please indicate what platform and IDE you compiled and tested the > SDK with. > > Please put all discussion about this release in a DISCUSSION thread not this > VOTE thread. > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 Release Candidate 3
Interesting. Does the console output give the full path to where it wrote the bad.png files? Are you sure you're in the right source branch (release4.9 vs develop). Anyway, I've seen those same failures so I think we just ignore them for now. On 12/22/12 8:18 AM, "Frédéric THOMAS" wrote: > There are no bad images in tests\spark\core\fxg\properties\baselines or > \tests\components\Charts\Bubble\Properties\Baselines that's why I can't get > how I can have Failed CompareBitmap > > - Fred > > -Message d'origine- > From: Alex Harui > Sent: Saturday, December 22, 2012 5:11 PM > To: flex-dev@incubator.apache.org > Subject: Re: Apache Flex 4.9 Release Candidate 3 > > Maybe I don't understand. If you use imageDiffAIR it can't find any bad > images? Are you looking in the right folders? > > > On 12/22/12 7:48 AM, "Frédéric THOMAS" wrote: > >> Hi Alex, >> >>> Player is choosing different pixel values. >> Use a grey background color in ImageDiffAIR >> >> As I said before, the problem is I haven't got any bad image to compare >> them >> with, I wonder how it can be possible to have Failed CompareBitmap without >> bad images, you know why ? >> >> - Fred >> >> -Message d'origine- >> From: Alex Harui >> Sent: Saturday, December 22, 2012 4:32 PM >> To: flex-dev@incubator.apache.org >> Subject: Re: Apache Flex 4.9 Release Candidate 3 >> >> Those will have to wait until we get the display list compare feature >> checked in after the release. Player is choosing different pixel values. >> Use a grey background color in ImageDiffAIR. >> >> Justin can you start a vote thread on RC6? >> >> Thanks, >> -Alex >> >> On 12/22/12 4:45 AM, "Frédéric THOMAS" wrote: >> >>> Hi, >>> >>> Running Mustella Tests against FP11.4/AIR3.4/en_US, I've still got these >>> failed tests : >>> >>> = >>> Failed: >>> = >>> components/Charts/Bubble/Properties/BubbleProperties >>> BubbleSeries_multipleAxes_disabledDays Failed CompareBitmap(body:step 1) >>> compare returned[object BitmapData] >>> gumbo/components/Image/styles/Image_styles_smoothingQuality >>> Image_Scale_stretch_smoothingQuality_high Failed CompareBitmap(body:step >>> 6) >>> compare returned[object BitmapData] >>> spark/core/fxg/properties/fxgtemplate_tester filters_filters_blend Failed >>> CompareBitmap(body:step 1) compare returned[object BitmapData] >>> spark/core/fxg/properties/fxgtemplate_tester scale9_bitmapgraphic_scale9 >>> Failed CompareBitmap(body:step 1) compare returned[object BitmapData] >>> spark/core/fxg/properties/fxgtemplate_tester >>> scale9_shape_bmpgraphic_scalegridgroup Failed CompareBitmap(body:step 1) >>> compare returned[object BitmapData] >>> >>> I've got no clue in how to fix them. >>> >>> Execpt for Bubble, what is weird is that I haven't got any bad images and >>> the tests failed comparing images, how that's possible ? >>> >>> >>> - Fred >>> >>> -Message d'origine- >>> From: Frédéric THOMAS >>> Sent: Saturday, December 22, 2012 2:34 AM >>> To: flex-dev@incubator.apache.org >>> Subject: Re: Apache Flex 4.9 Release Candidate 3 >>> >>> closed >>> >>> -Message d'origine- >>> From: Alex Harui >>> Sent: Friday, December 21, 2012 7:53 PM >>> To: flex-dev@incubator.apache.org >>> Subject: Re: Apache Flex 4.9 Release Candidate 3 >>> >>> It passed on my Mac, so I think it is ok to close. >>> >>> >>> On 12/21/12 2:17 AM, "Frédéric THOMAS" wrote: >>> >>>> Hi Alex, >>>> >>>> I committed my fix, see this tickect [1], I didn't close it, you can >>>> append >>>> it if you need to make other changes or revert my fix. >>>> >>>> [1] https://issues.apache.org/jira/browse/FLEX-33323 >>>> >>>> Thanks, >>>> Fred >>>> >>>> -Original Message- >>>> From: Alex Harui [mailto:aha...@adobe.com] >>>> Sent: Friday, December 21, 2012 8:09 AM >>>> To: flex-dev@incubator.apache.org >>>> Subject: Re: Apache Flex 4.9 Release Candidate 3 >>>> >>>> >>>> >>>> >>>> On 12/20/12 11:01 PM, "Frédéric THOMAS" wrote: >>>> >>>>> Hi, >>>>> >>>>>> If you switch back to 11.1 and regenerate the baseline, you should be >>>>>> ok. >>>>> >>>>> OK >>>>> >>>>>> If it turns out that it causes failures for others then just revert >>>>>> and we'll investigate why. >>>>> >>>>> What did you reverted exactly ? >>>> I haven't reverted anything yet. We'll see if your new 11.1 baseline >>>> causes >>>> any issues. >>>> >>>> -- >>>> Alex Harui >>>> Flex SDK Team >>>> Adobe Systems, Inc. >>>> http://blogs.adobe.com/aharui >>>> >>>> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 Release Candidate 3
Maybe I don't understand. If you use imageDiffAIR it can't find any bad images? Are you looking in the right folders? On 12/22/12 7:48 AM, "Frédéric THOMAS" wrote: > Hi Alex, > >> Player is choosing different pixel values. > Use a grey background color in ImageDiffAIR > > As I said before, the problem is I haven't got any bad image to compare them > with, I wonder how it can be possible to have Failed CompareBitmap without > bad images, you know why ? > > - Fred > > -Message d'origine- > From: Alex Harui > Sent: Saturday, December 22, 2012 4:32 PM > To: flex-dev@incubator.apache.org > Subject: Re: Apache Flex 4.9 Release Candidate 3 > > Those will have to wait until we get the display list compare feature > checked in after the release. Player is choosing different pixel values. > Use a grey background color in ImageDiffAIR. > > Justin can you start a vote thread on RC6? > > Thanks, > -Alex > > On 12/22/12 4:45 AM, "Frédéric THOMAS" wrote: > >> Hi, >> >> Running Mustella Tests against FP11.4/AIR3.4/en_US, I've still got these >> failed tests : >> >> = >> Failed: >> = >> components/Charts/Bubble/Properties/BubbleProperties >> BubbleSeries_multipleAxes_disabledDays Failed CompareBitmap(body:step 1) >> compare returned[object BitmapData] >> gumbo/components/Image/styles/Image_styles_smoothingQuality >> Image_Scale_stretch_smoothingQuality_high Failed CompareBitmap(body:step >> 6) >> compare returned[object BitmapData] >> spark/core/fxg/properties/fxgtemplate_tester filters_filters_blend Failed >> CompareBitmap(body:step 1) compare returned[object BitmapData] >> spark/core/fxg/properties/fxgtemplate_tester scale9_bitmapgraphic_scale9 >> Failed CompareBitmap(body:step 1) compare returned[object BitmapData] >> spark/core/fxg/properties/fxgtemplate_tester >> scale9_shape_bmpgraphic_scalegridgroup Failed CompareBitmap(body:step 1) >> compare returned[object BitmapData] >> >> I've got no clue in how to fix them. >> >> Execpt for Bubble, what is weird is that I haven't got any bad images and >> the tests failed comparing images, how that's possible ? >> >> >> - Fred >> >> -Message d'origine- >> From: Frédéric THOMAS >> Sent: Saturday, December 22, 2012 2:34 AM >> To: flex-dev@incubator.apache.org >> Subject: Re: Apache Flex 4.9 Release Candidate 3 >> >> closed >> >> -Message d'origine- >> From: Alex Harui >> Sent: Friday, December 21, 2012 7:53 PM >> To: flex-dev@incubator.apache.org >> Subject: Re: Apache Flex 4.9 Release Candidate 3 >> >> It passed on my Mac, so I think it is ok to close. >> >> >> On 12/21/12 2:17 AM, "Frédéric THOMAS" wrote: >> >>> Hi Alex, >>> >>> I committed my fix, see this tickect [1], I didn't close it, you can >>> append >>> it if you need to make other changes or revert my fix. >>> >>> [1] https://issues.apache.org/jira/browse/FLEX-33323 >>> >>> Thanks, >>> Fred >>> >>> -Original Message- >>> From: Alex Harui [mailto:aha...@adobe.com] >>> Sent: Friday, December 21, 2012 8:09 AM >>> To: flex-dev@incubator.apache.org >>> Subject: Re: Apache Flex 4.9 Release Candidate 3 >>> >>> >>> >>> >>> On 12/20/12 11:01 PM, "Frédéric THOMAS" wrote: >>> >>>> Hi, >>>> >>>>> If you switch back to 11.1 and regenerate the baseline, you should be >>>>> ok. >>>> >>>> OK >>>> >>>>> If it turns out that it causes failures for others then just revert >>>>> and we'll investigate why. >>>> >>>> What did you reverted exactly ? >>> I haven't reverted anything yet. We'll see if your new 11.1 baseline >>> causes >>> any issues. >>> >>> -- >>> Alex Harui >>> Flex SDK Team >>> Adobe Systems, Inc. >>> http://blogs.adobe.com/aharui >>> >>> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 Release Candidate 3
Those will have to wait until we get the display list compare feature checked in after the release. Player is choosing different pixel values. Use a grey background color in ImageDiffAIR. Justin can you start a vote thread on RC6? Thanks, -Alex On 12/22/12 4:45 AM, "Frédéric THOMAS" wrote: > Hi, > > Running Mustella Tests against FP11.4/AIR3.4/en_US, I've still got these > failed tests : > > = > Failed: > = > components/Charts/Bubble/Properties/BubbleProperties > BubbleSeries_multipleAxes_disabledDays Failed CompareBitmap(body:step 1) > compare returned[object BitmapData] > gumbo/components/Image/styles/Image_styles_smoothingQuality > Image_Scale_stretch_smoothingQuality_high Failed CompareBitmap(body:step 6) > compare returned[object BitmapData] > spark/core/fxg/properties/fxgtemplate_tester filters_filters_blend Failed > CompareBitmap(body:step 1) compare returned[object BitmapData] > spark/core/fxg/properties/fxgtemplate_tester scale9_bitmapgraphic_scale9 > Failed CompareBitmap(body:step 1) compare returned[object BitmapData] > spark/core/fxg/properties/fxgtemplate_tester > scale9_shape_bmpgraphic_scalegridgroup Failed CompareBitmap(body:step 1) > compare returned[object BitmapData] > > I've got no clue in how to fix them. > > Execpt for Bubble, what is weird is that I haven't got any bad images and > the tests failed comparing images, how that's possible ? > > > - Fred > > -Message d'origine- > From: Frédéric THOMAS > Sent: Saturday, December 22, 2012 2:34 AM > To: flex-dev@incubator.apache.org > Subject: Re: Apache Flex 4.9 Release Candidate 3 > > closed > > -Message d'origine- > From: Alex Harui > Sent: Friday, December 21, 2012 7:53 PM > To: flex-dev@incubator.apache.org > Subject: Re: Apache Flex 4.9 Release Candidate 3 > > It passed on my Mac, so I think it is ok to close. > > > On 12/21/12 2:17 AM, "Frédéric THOMAS" wrote: > >> Hi Alex, >> >> I committed my fix, see this tickect [1], I didn't close it, you can >> append >> it if you need to make other changes or revert my fix. >> >> [1] https://issues.apache.org/jira/browse/FLEX-33323 >> >> Thanks, >> Fred >> >> -Original Message- >> From: Alex Harui [mailto:aha...@adobe.com] >> Sent: Friday, December 21, 2012 8:09 AM >> To: flex-dev@incubator.apache.org >> Subject: Re: Apache Flex 4.9 Release Candidate 3 >> >> >> >> >> On 12/20/12 11:01 PM, "Frédéric THOMAS" wrote: >> >>> Hi, >>> >>>> If you switch back to 11.1 and regenerate the baseline, you should be >>>> ok. >>> >>> OK >>> >>>> If it turns out that it causes failures for others then just revert >>>> and we'll investigate why. >>> >>> What did you reverted exactly ? >> I haven't reverted anything yet. We'll see if your new 11.1 baseline >> causes >> any issues. >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: svn commit: r1425250 - in /incubator/flex/sdk/branches/release4.9: ./ frameworks/projects/apache/ mustella/tests/components/ mustella/tests/gumbo/components/TextInput/Properties/ mustella/tests/gu
Yeah, I didn't do a status beforehand so I was surprised they got committed. They were not in the two merges I was syncing. Not sure what is up with that. I did a content diff and nothing changed in those two files. On 12/21/12 10:47 PM, "Justin Mclean" wrote: > Hi, > >>incubator/flex/sdk/branches/release4.9/README (props changed) >> >> incubator/flex/sdk/branches/release4.9/frameworks/projects/apache/compile-con >> fig.xml (props changed) > Assume nothing changed in the above 2 files? > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [VOTE] Apache Flex 4.9 Release Candidate 4
We'll try to make RC6 work. I am downloading it now. On 12/21/12 7:39 PM, "Justin Mclean" wrote: > Hi, > >> What's your last day before you take off? > > Satellite internet connection up and running, it's slow but working (0.3 Mbps > down/0.1 Mbps up and 1 second ping time) so as long as I don't have to upload > too many new RCs should be OK. > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer language selection issue
Om, I was testing out the installer today. I noticed there is a backdoor for local files that copies instead of downloading to speed up testing, but that means there are different code paths. Do you have any objections if I re-arrange that to require the use of file:// URLs to speed up testing? Then we'll always be using the same code paths. I will also use file:// to skip the mirror lookup. BTW, I guess we have to finalize the vote and post the SDK to its final home before making the final RC for the installer so its sources can point to the right place? On 12/20/12 2:55 PM, "Om" wrote: > On Thu, Dec 20, 2012 at 2:44 PM, Chema Balsas wrote: > >> Hi, >> >> I've been digging around the installer, and I think I've found the issue >> with the languages... I'm not very comfortable with the code, so I want to >> ask before breaking anything ;) >> >> The problem seems to come from ViewResourceConstants.as, line 191 >> >> if(n>1) >> messageStringsContentLocalized = ... >> >> This never happens, as the localeChain is initialized inside >> selectDefaultLanguage() as resourceManager.localeChain = [ userLocale ]; >> >> It's also worth noting that if all the strings are not in the locale, an >> error is thrown. Shouldn't we have a base locale to inherit from? Urls for >> instance don't usually need translation, so they could default in general >> to the root locale. >> >> A possible fix is to append the root locale "en_US" when initializing >> localeChain, like >> >> resourceManager.localeChain = [ userLocale, "en_US" ]; >> >> This seems to fix all problems and I can see the existing "es_ES" strings >> and the default "en_US" strings for the missing ones. >> >> It's been a while since I've worked around these, so maybe this is not the >> solution at all... let me know what you think and how should this be >> addressed. >> Cheers, >> Chema >> >> >> > I think your analysis makes sense. Please go ahead and make the changes as > you mentioned. I can help test your changes. > > Thanks, > Om > > > >> 2012/12/20 Chema Balsas >> >>> Hi, >>> >>> I checked the submitted patch, and it does fix the issue of the license >>> agreements box to appear empty. However, I also can't see the labels for >>> the "Browse", "Next" and "Install Log". Was this known before? >>> >>> If you change the locale back and forth in the dropdown, then all texts >>> are shown correctly. >>> >>> >>> 2012/12/20 Alex Harui >>> >>>> I will try to get to it tonight. It would be nice if you could add a >> hook >>>> at startup (maybe command-line option or reading from the .xml file) >> that >>>> overrides the language/locale default it picks up from the player/os. >>>> That >>>> would enable us to simulate what folks in different countries will >>>> experience. That would enable to you verify that the patch worked >>>> yourself. >>>> Last time we went through this, I had to stop in the debugger and zap >> the >>>> variable by hand. It would make it easier to test if we could override >> in >>>> some way. >>>> >>>> >>>> On 12/20/12 1:04 PM, "Om" wrote: >>>> >>>>> Bump... >>>>> >>>>> The more people who can help test the Installer with other languages, >>>> the >>>>> better it would be for us to make a confident release. Please take a >>>> look >>>>> when you get a chance. >>>>> Source code is available here: >>>>> https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk >>>>> >>>>> Thanks, >>>>> Om >>>>> >>>>> On Thu, Dec 20, 2012 at 12:46 AM, Om wrote: >>>>> >>>>>> Commit 1424368 (hopefully) fixes this issue. >>>>>> >>>>>> Stefan Horochovec had provided this patch a while ago and attached it >>>> to >>>>>> the JIRA bug: https://issues.apache.org/jira/browse/FLEX-33223 >>>>>> >>>>>> Can you please test it and see if the issue is gone? >>>>>> >>>>>> Thanks, >>>>>> Om >>>>>> >>>>>> On Wed, Dec
Re: [VOTE] Apache Flex 4.9 RC5
You might already be gone, but I don't think you updated the signature files? They are not matching so the installer is failing. If I don't hear from you by tonight my time, I'll try to cut an RC6. On 12/20/12 2:59 PM, "Justin Mclean" wrote: > Hi, > >> In the binary kit, frameworks/build.xml does not build cleanly. > I've fixed, tested and checked in changes that fix this issue (rename > blank.properties to experimental.properties). > > I don't think this is a major enough issue to stop the current vote so I've > just replaced the binary packages in RC5. > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 Release Candidate 3
It passed on my Mac, so I think it is ok to close. On 12/21/12 2:17 AM, "Frédéric THOMAS" wrote: > Hi Alex, > > I committed my fix, see this tickect [1], I didn't close it, you can append > it if you need to make other changes or revert my fix. > > [1] https://issues.apache.org/jira/browse/FLEX-33323 > > Thanks, > Fred > > -Original Message- > From: Alex Harui [mailto:aha...@adobe.com] > Sent: Friday, December 21, 2012 8:09 AM > To: flex-dev@incubator.apache.org > Subject: Re: Apache Flex 4.9 Release Candidate 3 > > > > > On 12/20/12 11:01 PM, "Frédéric THOMAS" wrote: > >> Hi, >> >>> If you switch back to 11.1 and regenerate the baseline, you should be ok. >> >> OK >> >>> If it turns out that it causes failures for others then just revert >>> and we'll investigate why. >> >> What did you reverted exactly ? > I haven't reverted anything yet. We'll see if your new 11.1 baseline causes > any issues. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [FalconJx] New JavaScript runtime format prototype
Startup Time must meet a certain threshold of acceptability before enough folks will use your app and worry about runtime performance. IMO, startup time has several metrics: -First visual indicator: a progress bar or splash screen, enough to tell you that something is running -first screen: enough to tell what is running -first interaction: when you can start using the app -first goal: when you feel like you've accomplished some task with the app. Small apps collapse all of these into one, but the framework needs to support them being separate in really large apps. Also, IMO, standards are a double-edged sword. It is nice to have the consistency in your targets, but they can also be heavy and slow. It isn't clear we should just automatically use any standard. We chose the DOM event model in Flash/Flex because Macromedia was all about standards at the time, and I'm not clear it was the right decision. More efficient notification schemes were certainly possible, especially outside the actual display list. I saw a brief overview of Require and it seemed way more difficult than goog.require, but I could be wrong about that. There's some adage about premature optimization. These conversations are starting to feel like that. Let's get more code running, try to get people to use it, then figure out where we need to optimize. One of the good/bad things about JS it that it seems infinitely malleable. On 12/21/12 8:43 AM, "Kevin Newman" wrote: > My personal preference is to prioritize runtime performance over startup > times, though keeping in mind that startup time can be an issue, > especially for mobile. We don't want this thing to start up horrendously > slowly (I don't think that'll be the case here though). The best way to > measure will be to actually measure. Maybe a jsperf comparison of the > linked JS file, and a closure method is worth exploring (both startup > and runtime). > > BTW, what do you mean by startup times - do you mean the actual parsing, > loading and setting up of the classes (I think this)? Or is there an > speed issue with class instantiation as well (it seems like no)? I'm not > actually familiar enough with require.js just yet to know how that works. > > For those on the list that may not be aware, AMD/require.js modules are > [likely] coming to JS as they are currently in the ES-harmony spec: > http://wiki.ecmascript.org/doku.php?id=harmony:modules > > So are classes for that matter: > http://wiki.ecmascript.org/doku.php?id=harmony:classes > > These are the patterns that TypeScript is currently targeting > (AMD/require), and they are also increasingly popular by JS programmers > (being spec backed to a degree helps), so Flex would be in good company > if we choose to go the require.js/modules route, as Frank has done with > his vanilla.js with require.js prototype. > > Kevin N. > > P.S. It sounds like a bad idea, but I wonder if anyone has ever tried to > to use IE's Element as the base class for everything (instead of > Object), to gain access to getter/setter in IE lt 9. Does an Element > have to be on the DOM tree for get/set to work? I guess that would blow > up memory use, and maybe slow down all property access, so it's maybe > not useful for serious work (unless some jsperf charts shows it is), but > I'm still curious if it could work. > > > On 12/21/12 5:56 AM, Frank Wienberg wrote: >> We could also move all the AS3 helper functions (as, is, bind, cast, etc.) >> into one module (maybe even the same module), but that would actually >> introduce one more property dereferencing when using these functions at >> application run time (in contrast to start-up time, at which classes and >> interfaces are defined, where ultimate performance is not so much of an >> issue). >> >> What do you think? > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Component] Spacer
Don't you still need a class to have the name Spacer in ActionScript? I
think the manifest trick only works in MXML.
On 12/21/12 9:05 AM, "Carol Frampton" wrote:
> I'm not commenting on whether or not there should be a s:Spacer but you
> don't need a new class - you just need a new manifest entry to do the
> mapping. If you look in frameworks/spark-manifest.com you will see others
> there.
>
> Carol
>
> On 12/21/12 9 :44AM, "Kessler CTR Mark J"
> wrote:
>
>> Just curious if we could add a simple component that used to exist in
>> MX but not in Spark. The spacer component was just a simple UI
>> extension. We can do the exact same thing now with the s:Rect
>> (primitive), but it doesn't have an intuitive name. I think it would be
>> nice to add the spacer back in.
>>
>>
>>
>>
>>
>> --Same as--
>>
>>
>>
>>
>> Class:
>>
>> //Declare package.
>> package spark.components
>> {
>> //Create child class of the Rect class.
>> public class Spacer extends Rect
>> {
>> //----
>> // Constructor
>> //
>>
>> public function Spacer()
>> {
>> super();
>> }
>>
>> }
>>
>> }
>>
>>
>>
>> -Mark
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [OT] Adobe Flex Blog
Yeah, I'll try to get to that soon. I spent a few minutes on Wednesday trying to find out if what I blog has to be approved by Apache first but couldn't find any restrictions then got distracted by release stuff. We had to get clearance to write about the 4.8 release but I don't think that's true for announcing graduation. On 12/20/12 10:26 PM, "Justin Mclean" wrote: > Hi, > > Any chance we can get something about the graduation up on the Flex blog? > > http://blogs.adobe.com/flex/ > > Even if it's after the holiday period and by then it could have info about the > new 4.9 release as well. > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Apache Flex 4.9 Release Candidate 3
On 12/20/12 11:01 PM, "Frédéric THOMAS" wrote: > Hi, > >> If you switch back to 11.1 and regenerate the baseline, you should be ok. > > OK > >> If it turns out that it causes failures for others then just revert and >> we'll investigate why. > > What did you reverted exactly ? I haven't reverted anything yet. We'll see if your new 11.1 baseline causes any issues. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer language selection issue
I just checked in the ability to specify -language=xx_YY on the command-line for the installer that override the default language. I was able to reproduce the missing strings problem without your changes and it appears to be fixed with your changes. On 12/20/12 4:09 PM, "Chema Balsas" wrote: > I've committed the changes (r1424769). I've also added a rough (though > complete) first translation to spanish. I've built the installer and it > picks up fine my locale (es_ES) and all the strings. > > Please, verify that it is also working for other locales. > > Cheers, > Chema > > 2012/12/20 Om > >> On Thu, Dec 20, 2012 at 2:44 PM, Chema Balsas wrote: >> >>> Hi, >>> >>> I've been digging around the installer, and I think I've found the issue >>> with the languages... I'm not very comfortable with the code, so I want >> to >>> ask before breaking anything ;) >>> >>> The problem seems to come from ViewResourceConstants.as, line 191 >>> >>> if(n>1) >>> messageStringsContentLocalized = ... >>> >>> This never happens, as the localeChain is initialized inside >>> selectDefaultLanguage() as resourceManager.localeChain = [ userLocale ]; >>> >>> It's also worth noting that if all the strings are not in the locale, an >>> error is thrown. Shouldn't we have a base locale to inherit from? Urls >> for >>> instance don't usually need translation, so they could default in general >>> to the root locale. >>> >>> A possible fix is to append the root locale "en_US" when initializing >>> localeChain, like >>> >>> resourceManager.localeChain = [ userLocale, "en_US" ]; >>> >>> This seems to fix all problems and I can see the existing "es_ES" strings >>> and the default "en_US" strings for the missing ones. >>> >>> It's been a while since I've worked around these, so maybe this is not >> the >>> solution at all... let me know what you think and how should this be >>> addressed. >>> Cheers, >>> Chema >>> >>> >>> >> I think your analysis makes sense. Please go ahead and make the changes as >> you mentioned. I can help test your changes. >> >> Thanks, >> Om >> >> >> >>> 2012/12/20 Chema Balsas >>> >>>> Hi, >>>> >>>> I checked the submitted patch, and it does fix the issue of the license >>>> agreements box to appear empty. However, I also can't see the labels >> for >>>> the "Browse", "Next" and "Install Log". Was this known before? >>>> >>>> If you change the locale back and forth in the dropdown, then all texts >>>> are shown correctly. >>>> >>>> >>>> 2012/12/20 Alex Harui >>>> >>>>> I will try to get to it tonight. It would be nice if you could add a >>> hook >>>>> at startup (maybe command-line option or reading from the .xml file) >>> that >>>>> overrides the language/locale default it picks up from the player/os. >>>>> That >>>>> would enable us to simulate what folks in different countries will >>>>> experience. That would enable to you verify that the patch worked >>>>> yourself. >>>>> Last time we went through this, I had to stop in the debugger and zap >>> the >>>>> variable by hand. It would make it easier to test if we could >> override >>> in >>>>> some way. >>>>> >>>>> >>>>> On 12/20/12 1:04 PM, "Om" wrote: >>>>> >>>>>> Bump... >>>>>> >>>>>> The more people who can help test the Installer with other >> languages, >>>>> the >>>>>> better it would be for us to make a confident release. Please take >> a >>>>> look >>>>>> when you get a chance. >>>>>> Source code is available here: >>>>>> https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk >>>>>> >>>>>> Thanks, >>>>>> Om >>>>>> >>>>>> On Thu, Dec 20, 2012 at 12:46 AM, Om wrote: >>>>>> >>>>>>> Commit 1424368 (hopefully) fixes this issue. &g
Re: [OT] ApacheCon US Portland
I will be there in Portland. I may bring my family so I can't commit to extra-curricular events. On 12/20/12 6:57 PM, "Justin Mclean" wrote: > Hi, > > Nick Burch just posted a message to the small events list about the BarCamp, > Hackathon and a few other small community events happening around the > ApacheConEU conference. > > Anyone want to help out? > Is there any interest creating a Flex themed event of some sort? > Is anyone actually going along to the conference? > > Thanks, > Justin > > PS I'm giving an intro to Flex session at the conference proper. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer language selection issue
On 12/20/12 2:47 PM, "Chema Balsas" wrote: > Also, since we're no longer incubating, we should probably remove the > suffix from the installer name, right? ;) Yes. And I agree on your points below as well. > > 2012/12/20 Chema Balsas > >> Hi, >> >> I've been digging around the installer, and I think I've found the issue >> with the languages... I'm not very comfortable with the code, so I want to >> ask before breaking anything ;) >> >> The problem seems to come from ViewResourceConstants.as, line 191 >> >> if(n>1) >> messageStringsContentLocalized = ... >> >> This never happens, as the localeChain is initialized inside >> selectDefaultLanguage() as resourceManager.localeChain = [ userLocale ]; >> >> It's also worth noting that if all the strings are not in the locale, an >> error is thrown. Shouldn't we have a base locale to inherit from? Urls for >> instance don't usually need translation, so they could default in general >> to the root locale. >> >> A possible fix is to append the root locale "en_US" when initializing >> localeChain, like >> >> resourceManager.localeChain = [ userLocale, "en_US" ]; >> >> This seems to fix all problems and I can see the existing "es_ES" strings >> and the default "en_US" strings for the missing ones. >> >> It's been a while since I've worked around these, so maybe this is not the >> solution at all... let me know what you think and how should this be >> addressed. >> Cheers, >> Chema >> >> >> 2012/12/20 Chema Balsas >> >>> Hi, >>> >>> I checked the submitted patch, and it does fix the issue of the license >>> agreements box to appear empty. However, I also can't see the labels for >>> the "Browse", "Next" and "Install Log". Was this known before? >>> >>> If you change the locale back and forth in the dropdown, then all texts >>> are shown correctly. >>> >>> >>> 2012/12/20 Alex Harui >>> >>>> I will try to get to it tonight. It would be nice if you could add a >>>> hook >>>> at startup (maybe command-line option or reading from the .xml file) that >>>> overrides the language/locale default it picks up from the player/os. >>>> That >>>> would enable us to simulate what folks in different countries will >>>> experience. That would enable to you verify that the patch worked >>>> yourself. >>>> Last time we went through this, I had to stop in the debugger and zap the >>>> variable by hand. It would make it easier to test if we could override >>>> in >>>> some way. >>>> >>>> >>>> On 12/20/12 1:04 PM, "Om" wrote: >>>> >>>>> Bump... >>>>> >>>>> The more people who can help test the Installer with other languages, >>>> the >>>>> better it would be for us to make a confident release. Please take a >>>> look >>>>> when you get a chance. >>>>> Source code is available here: >>>>> https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk >>>>> >>>>> Thanks, >>>>> Om >>>>> >>>>> On Thu, Dec 20, 2012 at 12:46 AM, Om wrote: >>>>> >>>>>> Commit 1424368 (hopefully) fixes this issue. >>>>>> >>>>>> Stefan Horochovec had provided this patch a while ago and attached it >>>> to >>>>>> the JIRA bug: https://issues.apache.org/jira/browse/FLEX-33223 >>>>>> >>>>>> Can you please test it and see if the issue is gone? >>>>>> >>>>>> Thanks, >>>>>> Om >>>>>> >>>>>> On Wed, Dec 19, 2012 at 12:22 PM, Chema Balsas >>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I was checking the installer, and was starting to add a translation >>>> for >>>>>>> the >>>>>>> es_ES locale. After compiling and launching it, There are lots of >>>> buttons >>>>>>> with empty labels. If you select a different locale and then back to >>>>>>> spanish, then the labels appear. >>>&g
Re: [MENTORS] Post Graduation Steps
On 12/20/12 2:23 PM, "Justin Mclean" wrote: > Hi, > > No need for infra to be involve with Jenkins (hopefully), we can edit the > config there and change the SVN paths. > > There quite a few more github paths that need to change as well as we have > other projects than the SDK. Can you add other paths to the GitHub sub-task? > >> Can anyone think of other things that need migrating? > > Content on the web site re check out code etc ect The first sub-task is supposed to cover the website and SVN, IIUC. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [MENTORS] Post Graduation Steps
OK, I filed INFRA-5688 [2]. Can anyone think of other things that need migrating? [2] https://issues.apache.org/jira/browse/INFRA-5688 -Alex On 12/20/12 1:52 PM, "Greg Reddin" wrote: > I haven't done this before, but I found this: > > http://www.apache.org/dev/infra-contact > > Look for Requesting Podling->TLP Graduation. Part of this is PMC Chair > karma. > > I know infra has been discussing testing an automated process for this > month's graduations, so we might get in on that. Not a bad idea to ask on > the mailing list. > > Greg > > > On Thu, Dec 20, 2012 at 3:37 PM, Alex Harui wrote: > >> Hi Mentors, >> >> It looks like the steps I have to execute listed at [1] are mostly gated by >> this step: "Ensure that they have been added to the PMC chairs group >> (pmc-chairs) in LDAP." >> >> I'm unclear about how to do this. Will Infra automatically take care of it >> from the board minutes or do I have to file a JIRA issue? >> >> [1] >> http://incubator.apache.org/guides/graduation.html#new-project-hand-over >> >> Thanks, >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[MENTORS] Post Graduation Steps
Hi Mentors, It looks like the steps I have to execute listed at [1] are mostly gated by this step: "Ensure that they have been added to the PMC chairs group (pmc-chairs) in LDAP." I'm unclear about how to do this. Will Infra automatically take care of it from the board minutes or do I have to file a JIRA issue? [1] http://incubator.apache.org/guides/graduation.html#new-project-hand-over Thanks, -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Installer language selection issue
I will try to get to it tonight. It would be nice if you could add a hook at startup (maybe command-line option or reading from the .xml file) that overrides the language/locale default it picks up from the player/os. That would enable us to simulate what folks in different countries will experience. That would enable to you verify that the patch worked yourself. Last time we went through this, I had to stop in the debugger and zap the variable by hand. It would make it easier to test if we could override in some way. On 12/20/12 1:04 PM, "Om" wrote: > Bump... > > The more people who can help test the Installer with other languages, the > better it would be for us to make a confident release. Please take a look > when you get a chance. > Source code is available here: > https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk > > Thanks, > Om > > On Thu, Dec 20, 2012 at 12:46 AM, Om wrote: > >> Commit 1424368 (hopefully) fixes this issue. >> >> Stefan Horochovec had provided this patch a while ago and attached it to >> the JIRA bug: https://issues.apache.org/jira/browse/FLEX-33223 >> >> Can you please test it and see if the issue is gone? >> >> Thanks, >> Om >> >> On Wed, Dec 19, 2012 at 12:22 PM, Chema Balsas wrote: >> >>> Hi, >>> >>> I was checking the installer, and was starting to add a translation for >>> the >>> es_ES locale. After compiling and launching it, There are lots of buttons >>> with empty labels. If you select a different locale and then back to >>> spanish, then the labels appear. >>> >>> I remember reading something like this before the previous version was >>> released... is this the same issue? Is it supposed to be fixed before this >>> version is released? >>> >>> Cheers, >>> Chema >>> >>> 2012/12/19 Alex Harui >>> >>>>> -Original Message- >>>>> From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of Om >>>>> Sent: Wednesday, December 19, 2012 9:36 AM >>>>> To: flex-dev@incubator.apache.org >>>>> Subject: Re: [VOTE] Apache Flex 4.9 Release Candidate 4 >>>>> >>>>>> >>>>>>> 1. Would there be value in adding drop downs that let users >>> switch >>>>>> between >>>>>>> FP swc versions and AIR sdk versions? >>>>>> I would say no. I wouldn't want to take the time to test this >>>>>> additional functionality. Could the two URLs it will hit (based on >>>>>> the answer to #2) be stored in an external .XML file? That would >>> make >>>>>> it easier to folks to use different versions and for us to update an >>>>>> already released installer if Adobe goes and moves things around >>>>>> again. >>>>>> >>>>>> >>>>> Yes, we load all the download urls from an external config file: >>>>> http://incubator.apache.org/flex/sdk-installer-config.xml >>>>> >>>>> My thinking is that we will have a different config for each FP/AIR >>>> combination >>>>> we want to support. Just show a simple dropdown at the launch of the >>> app >>>>> (default to 11.4/3.4). Depending on what the user selects, we grab >>> the >>>>> corresponding config url. A pretty straightforward implementation. >>> But >>>> this >>>>> could wait until Installer 2.5 if we dont want to hold up Flex 4.9 >>>> release. >>>>> >>>>> Thanks, >>>>> Om >>>> >>>> I just built and ran the installer from sources on Win7. >>>> FB4.7 accepted the results as a new SDK. >>>> I created a new Flex project and it showed up in IE8 and FF15. >>>> I didn't see any warnings or errors. >>>> >>>> So, I would say we don't take the time to test all of the permutations >>> of >>>> configs. Adobe is not open next week so I will be working from home >>>> and testing the installer is slow because of the internet speeds I get >>> at >>>> home, so >>>> the less downloading I need to do, the better. >>>> >>>> Alex Harui >>>> Apache Flex Team >>>> http://blogs.adobe.com/aharui >>>> >>>> >>>> >>> >> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [FalconJx] New JavaScript runtime format prototype
b pages at > http://fwienber.github.com/as-js-runtime-prototype/index.html > From there, you can reach all ActionScript example sources and the proposed > JavaScript equivalent (so far, hand-coded :-)). > To see the example in action, use the three bottom links which start the > same application in three flavors: > >- debug: Each JS file corresponding to an AS class or interface and the >main bootstrap file is loaded with a single request. This gives you a nice >1:1 mapping of source to output in the JavaScript debugger. Additionally, >there are some "infrastructure" files: require.js itself, the RequireJS >plugin "shim" (shim.js, shims.js), my AS3 runtime helpers defineClass.js >and defineInterface.js, and a couple of built-in AS3 functions (bind, as, >is, trace). If loading in IE < 9, the shim plugin loads several ES5 >polyfills. >- linked: The whole application is merged into one JS file using the >RequireJS optimizer "r.js" without optimizations. Thus you only have two >requests: require.js and hello-worls-all.js are loaded. In IE < 9, the >polyfills are still loaded one-by-one (I didn't bother to optimize this >case, but of course, it can be done). >- minified: Same as "linked", only that require.js and >hellow-world-all.js are minified by Uglify2. This can easily be achieved >using "r.js" with the parameter optimize=uglify2. > > > For the demo, I redirected trace() from the JavaScript console (backed-up > in trace-console.js) to the DOM, so that you can see the log messages > directly. > > Just look into the code and observe how it works in Firebug or any other > JavaScript debugger of your choice, and let me know if anything is unclear, > missing or if you need more reasoning for the design decisions taken. > I know there are still several issues to be fleshed out (e.g. interaction > with "native" JavaScript or package-scope variables, just to name two), but > I think the current state is a solid core of how a modern, efficient, > self-contained, extensive and still concise JavaScript runtime format for > Apache Flex could look like. > Please tell me what you think! > > Have fun, > -Frank- -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
RE: Apache Flex 4.9 Release Candidate 3
If you switch back to 11.1 and regenerate the baseline, you should be ok.
If it turns out that it causes failures for others then just revert and we'll
investigate why.
Alex Harui
Apache Flex Team
http://blogs.adobe.com/aharui
> -Original Message-
> From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
> Sent: Thursday, December 20, 2012 8:04 AM
> To: flex-dev@incubator.apache.org
> Subject: RE: Apache Flex 4.9 Release Candidate 3
>
> Hi,
>
> I choose the second option but that's imply I can regenerate the baseline
> image
> ? (I'm a bit timid now regenerating them)
>
> - Fred
>
> -Original Message-
> From: Alex Harui [mailto:aha...@adobe.com]
> Sent: Thursday, December 20, 2012 8:46 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Apache Flex 4.9 Release Candidate 3
>
> For the TextInput test, I guess I would add a small fudge factor maybe like
> this:
>
> method="value=Number(application.textInput.alpha.toFixed(1)) + 0.003"
>
> Or maybe the better solution is to find an alpha value that is a power of 2.
> It might be more like 0.125.
>
> On 12/19/12 11:11 PM, "Frédéric THOMAS"
> wrote:
>
> > Hi,
> >
> > Thanks for this info, I didn't noticed the old FP gave that kind of
> > output when used with toFixed(0) and internaly, the
> > falsh.globalization.CurrencyFormatter use toFixed(0) for the
> > fractionalDigits property, which is logical anyway.
> >
> > An other one :
> > [1] I would use a rounded value because the > method="value=Number(application.textInput.alpha.toFixed(1))"
> > value="0.1" /> use toFixed and the real alpha is 0.09765625
> >
> > What do you think ?
> > (Sorry, I need to get familiar with those tests and for that, need to
> > ask you many things, at term, it could be good hopefully because, I'll
> > be able to fix them without help)
> >
> > - Fred
> >
> > [1] gumbo/components/TextInput/Properties/TextInput_properties_tester
> > Gumbo_TextInput_alpha_property_01 Failed AssertMethodValue (method
> > cannot be shown)(body:step 1) method returned 0, expected 0.10
> >
> > -Message d'origine-
> > From: Alex Harui
> > Sent: Thursday, December 20, 2012 7:51 AM
> > To: flex-dev@incubator.apache.org
> > Subject: Re: Apache Flex 4.9 Release Candidate 3
> >
> > It appears that in more recent players:
> > Number(0.12345).toFixed(0)
> > returns "0"
> > But older players returns "0."
> > Which is probably a bug (the "." following the "0" that they fixed.
> >
> > For these tests, since they are AssertMethodValue, I would change the
> > method expression to add a "." if it is missing. Maybe something like:
> >
> > var s:String = application.cf_inline.format(...); value =
> > (s.indexOf(".") ==
> > -1) ? s + "." : s;
> >
> >
> > On 12/19/12 10:09 PM, "Frédéric THOMAS"
> wrote:
> >
> >> @Alex,
> >>
> >> Do you think the expected value is good ?
> >>
> >> >>valueExpression="value='RUR0.'"/>
> >>
> >> I think the valueExpression should be "value='RUR0'" because the
> >> fractionalDigits is set to 0, so to me, the result "RUR0" is good.
> >>
> >> - Fred
> >>
> >> -Message d'origine-
> >> From: Frédéric THOMAS
> >> Sent: Thursday, December 20, 2012 6:16 AM
> >> To: flex-dev@incubator.apache.org
> >> Subject: Re: Apache Flex 4.9 Release Candidate 3
> >>
> >> Arff, I'm mixing everything, I shouldn't do that at 6 AM :P
> >>
> >> -Message d'origine-
> >> From: Frédéric THOMAS
> >> Sent: Thursday, December 20, 2012 6:13 AM
> >> To: flex-dev@incubator.apache.org
> >> Subject: Re: Apache Flex 4.9 Release Candidate 3
> >>
> >> But it seems normal to me that the format method removes the decimal
> >> separator when there's no decimal part.
> >>
> >> -Message d'origine-
> >> From: Frédéric THOMAS
> >> Sent: Thursday, December 20, 2012 6:08 AM
> >> To: flex-dev@incubator.apache.org
> >> Subject: Re: Apache Flex 4.9 Release Candidate 3
> >>
> >> Oups, that's the opposite, the expected is "0." and the result is "0".
> >>
> >> -Message d'origine-
> >>
Re: Apache Flex 4.9 Release Candidate 3
For the TextInput test, I guess I would add a small fudge factor maybe like
this:
method="value=Number(application.textInput.alpha.toFixed(1)) + 0.003"
Or maybe the better solution is to find an alpha value that is a power of 2.
It might be more like 0.125.
On 12/19/12 11:11 PM, "Frédéric THOMAS" wrote:
> Hi,
>
> Thanks for this info, I didn't noticed the old FP gave that kind of output
> when used with toFixed(0) and internaly, the
> falsh.globalization.CurrencyFormatter use toFixed(0) for the
> fractionalDigits property, which is logical anyway.
>
> An other one :
> [1] I would use a rounded value because the method="value=Number(application.textInput.alpha.toFixed(1))" value="0.1" />
> use toFixed and the real alpha is 0.09765625
>
> What do you think ?
> (Sorry, I need to get familiar with those tests and for that, need to ask
> you many things, at term, it could be good hopefully because, I'll be able
> to fix them without help)
>
> - Fred
>
> [1] gumbo/components/TextInput/Properties/TextInput_properties_tester
> Gumbo_TextInput_alpha_property_01 Failed AssertMethodValue (method cannot be
> shown)(body:step 1) method returned 0, expected 0.10
>
> -Message d'origine-
> From: Alex Harui
> Sent: Thursday, December 20, 2012 7:51 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Apache Flex 4.9 Release Candidate 3
>
> It appears that in more recent players:
> Number(0.12345).toFixed(0)
> returns "0"
> But older players returns "0."
> Which is probably a bug (the "." following the "0" that they fixed.
>
> For these tests, since they are AssertMethodValue, I would change the method
> expression to add a "." if it is missing. Maybe something like:
>
> var s:String = application.cf_inline.format(...); value = (s.indexOf(".") ==
> -1) ? s + "." : s;
>
>
> On 12/19/12 10:09 PM, "Frédéric THOMAS" wrote:
>
>> @Alex,
>>
>> Do you think the expected value is good ?
>>
>> >valueExpression="value='RUR0.'"/>
>>
>> I think the valueExpression should be "value='RUR0'" because the
>> fractionalDigits is set to 0, so to me, the result "RUR0" is good.
>>
>> - Fred
>>
>> -Message d'origine-
>> From: Frédéric THOMAS
>> Sent: Thursday, December 20, 2012 6:16 AM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Apache Flex 4.9 Release Candidate 3
>>
>> Arff, I'm mixing everything, I shouldn't do that at 6 AM :P
>>
>> -Message d'origine-
>> From: Frédéric THOMAS
>> Sent: Thursday, December 20, 2012 6:13 AM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Apache Flex 4.9 Release Candidate 3
>>
>> But it seems normal to me that the format method removes the decimal
>> separator when there's no decimal part.
>>
>> -Message d'origine-
>> From: Frédéric THOMAS
>> Sent: Thursday, December 20, 2012 6:08 AM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Apache Flex 4.9 Release Candidate 3
>>
>> Oups, that's the opposite, the expected is "0." and the result is "0".
>>
>> -Message d'origine-
>> From: Frédéric THOMAS
>> Sent: Thursday, December 20, 2012 5:52 AM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Apache Flex 4.9 Release Candidate 3
>>
>> Hi,
>>
>> I was looking at the CurrencyFormatter and seen that if the value is set
>> to
>> "0.12345.", the expected result is "0" but only when the value start by
>> "0.", the format method return "0.", with an other numbers, the decimal
>> separator disapear but not with 0, it's at least what's the fail tests
>> shown, do you agree, same for you ?
>>
>> - Fred
>>
>> -Message d'origine-
>> From: Alex Harui
>> Sent: Thursday, December 20, 2012 5:42 AM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Apache Flex 4.9 Release Candidate 3
>>
>> I am not getting the BubbleProperties failure, or the fxg failures on my
>> 11.5 Windows run, but I did get the Image_styles_smoothingQuality,
>> TextInput_properties_tester, and CurrencyFormatter errors. I am going to
>> look into the CurrencyFormatter errors now. Then the TextInput test.
>>
>>
>> On 12/19/12 7:40 PM, "Frédéric THOMAS" wrote:
>>
>>> Waoou, never open the results.txt bef
Re: Apache Flex 4.9 Release Candidate 3
It appears that in more recent players:
Number(0.12345).toFixed(0)
returns "0"
But older players returns "0."
Which is probably a bug (the "." following the "0" that they fixed.
For these tests, since they are AssertMethodValue, I would change the method
expression to add a "." if it is missing. Maybe something like:
var s:String = application.cf_inline.format(...); value = (s.indexOf(".") ==
-1) ? s + "." : s;
On 12/19/12 10:09 PM, "Frédéric THOMAS" wrote:
> @Alex,
>
> Do you think the expected value is good ?
>
> valueExpression="value='RUR0.'"/>
>
> I think the valueExpression should be "value='RUR0'" because the
> fractionalDigits is set to 0, so to me, the result "RUR0" is good.
>
> - Fred
>
> -Message d'origine-
> From: Frédéric THOMAS
> Sent: Thursday, December 20, 2012 6:16 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Apache Flex 4.9 Release Candidate 3
>
> Arff, I'm mixing everything, I shouldn't do that at 6 AM :P
>
> -Message d'origine-
> From: Frédéric THOMAS
> Sent: Thursday, December 20, 2012 6:13 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Apache Flex 4.9 Release Candidate 3
>
> But it seems normal to me that the format method removes the decimal
> separator when there's no decimal part.
>
> -Message d'origine-
> From: Frédéric THOMAS
> Sent: Thursday, December 20, 2012 6:08 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Apache Flex 4.9 Release Candidate 3
>
> Oups, that's the opposite, the expected is "0." and the result is "0".
>
> -Message d'origine-
> From: Frédéric THOMAS
> Sent: Thursday, December 20, 2012 5:52 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Apache Flex 4.9 Release Candidate 3
>
> Hi,
>
> I was looking at the CurrencyFormatter and seen that if the value is set to
> "0.12345.", the expected result is "0" but only when the value start by
> "0.", the format method return "0.", with an other numbers, the decimal
> separator disapear but not with 0, it's at least what's the fail tests
> shown, do you agree, same for you ?
>
> - Fred
>
> -Message d'origine-
> From: Alex Harui
> Sent: Thursday, December 20, 2012 5:42 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Apache Flex 4.9 Release Candidate 3
>
> I am not getting the BubbleProperties failure, or the fxg failures on my
> 11.5 Windows run, but I did get the Image_styles_smoothingQuality,
> TextInput_properties_tester, and CurrencyFormatter errors. I am going to
> look into the CurrencyFormatter errors now. Then the TextInput test.
>
>
> On 12/19/12 7:40 PM, "Frédéric THOMAS" wrote:
>
>> Waoou, never open the results.txt before, very usefull, thanks.
>>
>> =
>> Failed:
>> =
>> components/Charts/Bubble/Properties/BubbleProperties
>> BubbleSeries_multipleAxes_disabledDays Failed CompareBitmap(body:step 1)
>> compare returned[object BitmapData]
>> gumbo/components/Image/styles/Image_styles_smoothingQuality
>> Image_Scale_stretch_smoothingQuality_high Failed CompareBitmap(body:step
>> 6)
>> compare returned[object BitmapData]
>> gumbo/components/TextInput/Properties/TextInput_properties_tester
>> Gumbo_TextInput_alpha_property_01 Failed AssertMethodValue (method cannot
>> be
>> shown)(body:step 1) method returned 0, expected 0.10
>> spark/core/fxg/properties/fxgtemplate_tester filters_filters_blend Failed
>> CompareBitmap(body:step 1) compare returned[object BitmapData]
>> spark/core/fxg/properties/fxgtemplate_tester scale9_bitmapgraphic_scale9
>> Failed CompareBitmap(body:step 1) compare returned[object BitmapData]
>> spark/core/fxg/properties/fxgtemplate_tester
>> scale9_shape_bmpgraphic_scalegridgroup Failed CompareBitmap(body:step 1)
>> compare returned[object BitmapData]
>> spark/formatters/CurrencyFormatter/Fallback/CF_Fallback_format_Main_tester
>>
CF_Fallback_format_currencyISOCode_default_currencySymbol_default_declaration>>
s
>> _test1
>> Failed AssertMethodValue (method cannot be shown)(body:step 3) method
>> returned USD0, expected USD0.
>> spark/formatters/CurrencyFormatter/Fallback/CF_Fallback_format_Main_tester
>> CF_Fallback_format_modify_different_properties_test4 Failed
>> AssertMe
Re: Apache Flex 4.9 Release Candidate 3
>> id=CF_Fallback_format_currencyISOCode_default_currencySymbol_default_de >>> cla >>> rations_test1 result=fail elapsed=187 phase=body started=1355932292064 >>> extraInfo=null msg=AssertMethodValue (method cannot be shown)(body:step >>> 3) method returned USD0, expected USD0. >>> RESULT: >>> scriptName=spark/formatters/CurrencyFormatter/Fallback/CF_Fallback_form >>> at_ Main_tester id=CF_Fallback_format_modify_different_properties_test4 >>> result=fail elapsed=250 phase=body started=1355932292913 extraInfo=null >>> msg=AssertMethodValue (method cannot be shown)(body:step 3) method >>> returned RUR0, expected RUR0. >>> RESULT: >>> scriptName=spark/formatters/CurrencyFormatter/Fallback/CF_Fallback_form >>> at_ Main_tester id=CF_Fallback_format_modify_different_properties_test6 >>> result=fail elapsed=340 phase=body started=1355932293573 extraInfo=null >>> msg=AssertMethodValue (method cannot be shown)(body:step 3) method >>> returned RUR0, expected RUR0. >>> RESULT: >>> scriptName=spark/formatters/CurrencyFormatter/Fallback/CF_Fallback_form >>> at_ Main_tester id=CF_Fallback_format_modify_different_properties_test7 >>> result=fail elapsed=280 phase=body started=1355932293963 extraInfo=null >>> msg=AssertMethodValue (method cannot be shown)(body:step 3) method >>> returned RUR0, expected RUR0. >>> RESULT: >>> scriptName=spark/formatters/CurrencyFormatter/Fallback/CF_Fallback_form >>> at_ Main_tester >>> id=CF_Fallback_format_modify_different_properties_test14 >>> result=fail elapsed=297 phase=body started=1355932296744 extraInfo=null >>> msg=AssertMethodValue (method cannot be shown)(body:step 3) method >>> returned €0, expected €0. >>> RESULT: >>> scriptName=spark/formatters/CurrencyFormatter/Fallback/CF_Fallback_form >>> at_ >>> Main_tester >>> id=CF_Fallback_format_currencyISOCode_default_currencySymbol_default_sc >>> rip >>> t_test15 result=fail elapsed=171 phase=body started=1355932297072 >>> extraInfo=null msg=AssertMethodValue (method cannot be shown)(body:step >>> 3) method returned USD0, expected USD0. >>> RESULT: >>> scriptName=spark/formatters/CurrencyFormatter/Fallback/CF_Fallback_form >>> at_ >>> Main_tester >>> id=CF_Fallback_format_currencyISOCode_CNY_currencySymbol_valid_script_t >>> est >>> 16 result=fail elapsed=253 phase=body started=1355932297290 >>> extraInfo=null msg=AssertMethodValue (method cannot be shown)(body:step >>> 3) method returned CNY0, expected CNY0. >>> >>> >>> -Original Message- >>> From: Alex Harui [mailto:aha...@adobe.com] >>> Sent: Wednesday, December 19, 2012 8:26 AM >>> To: flex-dev@incubator.apache.org >>> Subject: Re: Apache Flex 4.9 Release Candidate 3 >>> >>> >>> >>> >>> On 12/18/12 11:19 PM, "Frédéric THOMAS" wrote: >>> >>>> Hi Alex, >>>> >>>> BTW, "Avertissement" means Warning. >>> >>> Yup, BabelFish is amazing. I learned something today! >>> >>> -- >>> Alex Harui >>> Flex SDK Team >>> Adobe Systems, Inc. >>> http://blogs.adobe.com/aharui >>> >>> >> >> > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [OT] Education version of Flash Builder
On 12/19/12 3:31 PM, "Justin Mclean" wrote: > > So is there any education pricing for FB at all? The PM for FB is already out for the year. Remind me again next year and I will ask him. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
