Re: Next Donation from Adobe
Can you update me on the status of FlexPMD? When I try to install the Eclipse plugin I get challenged for a username and password. The same happens when I try to browse the SVN repo linked from the Sourceforge site. Is that because the transfer to Apache Flex is in progress? On Fri, Mar 28, 2014 at 11:42 AM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the Adobe-hosted videos and images. G) Some articles point to zip files. In the donation, the zip files are expanded and the actual zip file is missing because we should be checking source and not zips into our repos. Build scripts will be needed to create zips that go with the production articles. And then we need to decide where to still all of this source. I guess flex-utilities for most of it. I would probably create a branch of flex-sdk for the FDB code. The XML Merge code will go in the BlazeDS repo with the rest of BlazeDS. Where should be put all of the devnet html files until they are ready? Thanks, -Alex Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbuil der.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex.h tml http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklist .html http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html http://www.adobe.com/devnet/flex/articles/spark_layouts.html http://www.adobe.com/devnet/flex/articles/flex-mobile-development-tips-tric ks-pt4.html
Re: Next Donation from Adobe
Sorry, ignore previous email. I did not read carefully before sending. On Mon, Aug 4, 2014 at 10:33 AM, Jim Robson dadrob...@gmail.com wrote: Can you update me on the status of FlexPMD? When I try to install the Eclipse plugin I get challenged for a username and password. The same happens when I try to browse the SVN repo linked from the Sourceforge site. Is that because the transfer to Apache Flex is in progress? On Fri, Mar 28, 2014 at 11:42 AM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the Adobe-hosted videos and images. G) Some articles point to zip files. In the donation, the zip files are expanded and the actual zip file is missing because we should be checking source and not zips into our repos. Build scripts will be needed to create zips that go with the production articles. And then we need to decide where to still all of this source. I guess flex-utilities for most of it. I would probably create a branch of flex-sdk for the FDB code. The XML Merge code will go in the BlazeDS repo with the rest of BlazeDS. Where should be put all of the devnet html files until they are ready? Thanks, -Alex Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbuil der.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbuilder.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex.h tml http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex.html http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html
Re: Next Donation from Adobe
Thanks, I see it now. I forgot to checkout the develop branch. On Sat, Aug 2, 2014 at 2:36 AM, Alex Harui aha...@adobe.com wrote: On 8/1/14 10:39 AM, Darrell Loverin darrell.love...@gmail.com wrote: 9. The source code for a prototype of a code coverage utility that I wrote. Has this code been donated? Yes, it is the flex-utilities repo in the CodeCoverage folder. I've used this code to do a tracing profiler and started in on trying to use it for code coverage as well. It uses a preloader swf that sets up flash.trace.Trace and sends output to a server app that actually saves the data so the file I/o is in a separate process. For code coverage, you would swfdump a swf and pull out all of the debug line data, then run the app and grab the output from flash.trace.Trace and see how many of the debug lines you hit. For tracing profiler, the problem is that there is no clean end-of-function marker. I want to experiment with adding a dummy debug line (like -1) to the SWF at each return ABC code as the end-of-function marker, then you could grab the output data and determine what ran and when without having to annotate a SWF with more abc code. -Alex
Re: Next Donation from Adobe
Hi, When I try to install the Eclipse plugin I get challenged for a username and password. The same happens when I try to browse the SVN repo linked from the Sourceforge site. Is that because the transfer to Apache Flex is in progress? No it because Adobe in their infinite wisdom have decided to password protect their open source SVN repo without telling people what the name and password is. Thanks, Justin
Re: Next Donation from Adobe
On 8/1/14 10:39 AM, Darrell Loverin darrell.love...@gmail.com wrote: 9. The source code for a prototype of a code coverage utility that I wrote. Has this code been donated? Yes, it is the flex-utilities repo in the CodeCoverage folder. I've used this code to do a tracing profiler and started in on trying to use it for code coverage as well. It uses a preloader swf that sets up flash.trace.Trace and sends output to a server app that actually saves the data so the file I/o is in a separate process. For code coverage, you would swfdump a swf and pull out all of the debug line data, then run the app and grab the output from flash.trace.Trace and see how many of the debug lines you hit. For tracing profiler, the problem is that there is no clean end-of-function marker. I want to experiment with adding a dummy debug line (like -1) to the SWF at each return ABC code as the end-of-function marker, then you could grab the output data and determine what ran and when without having to annotate a SWF with more abc code. -Alex
Re: Next Donation from Adobe
9. The source code for a prototype of a code coverage utility that I wrote. Has this code been donated? -Darrell On Fri, Mar 28, 2014 at 11:42 AM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the Adobe-hosted videos and images. G) Some articles point to zip files. In the donation, the zip files are expanded and the actual zip file is missing because we should be checking source and not zips into our repos. Build scripts will be needed to create zips that go with the production articles. And then we need to decide where to still all of this source. I guess flex-utilities for most of it. I would probably create a branch of flex-sdk for the FDB code. The XML Merge code will go in the BlazeDS repo with the rest of BlazeDS. Where should be put all of the devnet html files until they are ready? Thanks, -Alex Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbuil der.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex.h tml http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklist .html http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html http://www.adobe.com/devnet/flex/articles/spark_layouts.html http://www.adobe.com/devnet/flex/articles/flex-mobile-development-tips-tric ks-pt4.html http://www.adobe.com/devnet/flex/articles/flex4_skinning.html http://www.adobe.com/devnet/flex/articles/flex4_viewport_scrolling.html http://www.adobe.com/devnet/flex/articles/flex4_effects_pt1.html FlexPMD
Re: Next Donation from Adobe
Thanks you Alex and Adobe! EdB On Sat, Apr 26, 2014 at 6:27 AM, Alex Harui aha...@adobe.com wrote: Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Next Donation from Adobe
Hi, Yep great news! And that's everything Adobe was going to donate right - there's nothing left outstanding? Thanks, Justin
RE: Next Donation from Adobe
Thanks Alex (and Adobe). Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : samedi 26 avril 2014 06:28 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
Oh Btw, I won't continue tomorrow as I can't but on Monday. Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 19:54:01 +0100 Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
Another point, at the moment I'm integrating it to make it work with our compiler and the fixes I pushed before but the donated version uses the Flacon AST Classes to evaluate expresions, so, I wonder, once Flacon will be completed we could switch back to its classes or we don't need to wait ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 19:54:01 +0100 Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right now. So feel free to jump in. Thanks, -Alex
RE: Next Donation from Adobe
Something I don't get: Adobe is still selling FDB as part of Flash Builder, right? So why is this called a donation ? Maurice -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : samedi 26 avril 2014 21:39 À : dev@flex.apache.org Objet : RE: Next Donation from Adobe Another point, at the moment I'm integrating it to make it work with our compiler and the fixes I pushed before but the donated version uses the Flacon AST Classes to evaluate expresions, so, I wonder, once Flacon will be completed we could switch back to its classes or we don't need to wait ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 19:54:01 +0100 Ok, I've been able to pick up the needed code to make it run with our compiler classes used to evaluate expressions, unfortunately I can only test debugging session on command line, I haven't a FB license and my version expired time ago but I've got good result already, I can set a breakpoint in a worker and read values, more tests tomorrow. Btw, is there a open source license available for FB ? I tried with IntelliJ but didn't work, I guess it needs some integration code, not sure thought, so, Alexander, if you are around, please tell me if I can do something on my side or not pls. Will do more tests tomorrow and when good, open a Jira with the compiled fdb.jar for testing purposes and commit on the branch. I noticed the headers in the source files are not the same, there are a * before and after the license text in the current version and not in the new one, which one should we keep ? Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 15:10:11 +0100 I ponderate my Great news with bad news because the new FDB is using classes from Falcon, not our actual compiler, so, I'm trying to check if it is possible to cherry pick the code used to debug the workers only (big work), ... Frédéric THOMAS From: webdoubl...@hotmail.com To: dev@flex.apache.org Subject: RE: Next Donation from Adobe Date: Sat, 26 Apr 2014 11:04:10 +0100 Great news. Just had a look at FDB and seen the code for the workers, the optim I did before has to be merged and tested and maybe also more cleanup. I hope I can do all that today. Frédéric THOMAS From: aha...@adobe.com To: dev@flex.apache.org Subject: Re: Next Donation from Adobe Date: Sat, 26 Apr 2014 04:27:38 + Hi Folks, I've checked in everything in the donation. I was able to use some tools to quickly get the headers right and the IP cleared by the Incubator. The next step is for volunteers to work with the donated content and turn it into something real. The pieces are: 1. Several Flex articles from the ADC web-site. These are check into the little-used flex-external git repo under ADC. Missing images need to be replaced. Some videos probably also need replacing. The main content videos can be linked back to the Adobe site for now. 2. An updated version of the FDB debugger that contains support for ActionScript Workers This is checked into the flex-sdk repo in a FDBWorkers branch. The files are in modules/fdbworkers. A volunteer is needed to make sure it builds, then decide whether to completely replace fdb or merge it into fdb. 3. The FlexPMD source code This is in the flex-utilities repo under FlexPMD. I have no idea if it builds or runs. 4. The Mobile Trader demo application This is in the flex-utilities repo under MobileTrader. Peter has checked in a modified version into the flex-asjs repo. His version works with FlexJS. 5. The specification for the MXML language This is in flex-externals under specifications. I would imagine this will end up on the web site or wiki? 6. BlazeDS This is in the flex-blazeds repo. It has a pretty good chance of actually building the library we use for Flex. Not sure about the tests though. 7. The Squiggly spell-checker source code This is in the flex-utilities repo under Squiggly 8. The Tour De Flex application source code This is in the flex-utilities repo under TourDeFlex. There are three subfolders. TourDeFlex3 is the Flex 3 version of TourDeFlex. The TourDeFlex folder is the Flex 4 version. The TourDeFlex_content.com is the content from TourDeFlex.com. These files need re-branding and missing images and videos need to be replaced. 9. The source code for a prototype of a code coverage utility that I wrote. This is in flex-utilites under CodeCoverage. I'm not planning to spend any more time on the donation right
Re: Next Donation from Adobe
Only thing I can think that is still outstanding is the donation of the docs (http://help.adobe.com/en_US/flex/using/index.html). Otherwise, I think that is just about everything I can think of.. -Nick On Sat, Apr 26, 2014 at 2:54 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, Yep great news! And that's everything Adobe was going to donate right - there's nothing left outstanding? Thanks, Justin
Re: Next Donation from Adobe
On 4/26/14 12:45 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Something I don't get: Adobe is still selling FDB as part of Flash Builder, right? So why is this called a donation ? It is the term we use for 'granting a license to Apache'. -Alex
Re: Next Donation from Adobe
From the pre-incubation promises, that's pretty much it except maybe Flex 3.x. Since then, folks have asked for other things: 1) the search capability in asdoc 2) the docs Nick mentioned 3) the original FlexUnit 4) pieces of Flash Builder I have not done any work on those yet and they are not high on my list. -Alex On 4/26/14 1:07 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Only thing I can think that is still outstanding is the donation of the docs (http://help.adobe.com/en_US/flex/using/index.html). Otherwise, I think that is just about everything I can think of.. -Nick On Sat, Apr 26, 2014 at 2:54 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, Yep great news! And that's everything Adobe was going to donate right - there's nothing left outstanding? Thanks, Justin
RE: Next Donation from Adobe
Understood. In this case, it would be nice to get the license to use the improved ASDOC tools ( the ones that generate searchable classes etc...) Like in: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/ Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : samedi 26 avril 2014 23:51 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe On 4/26/14 12:45 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Something I don't get: Adobe is still selling FDB as part of Flash Builder, right? So why is this called a donation ? It is the term we use for 'granting a license to Apache'. -Alex
Re: Next Donation from Adobe
And it is official, the Apache Secretary has filed the donation paperwork. Apache Flex now owns all of the content below. (Apache doesn't really own it, but rather, has a license to it). I recently found out that post-graduation donations from Adobe were not handled properly by the Flex PMC. We have to get Incubator approval for all post-graduation donations so I can't just dump all of these files into our repo. So, over the course of the next several days/weeks, I will be scrubbing this donation to double-check on headers, etc, and asking for Incubator approval before they go into the repo. I will probably do this in chunks instead of one giant pile of files. I also have to do this for the BlazeDS files. To me, this is not top priority. The FalconJX/FlexJS releases are top priority along with a 4.12.1 and releasing Installer 3.0. And 360|Flex prep also takes priority over donation scrubbing. Once approved, the BlazeDS files will go into its own repo, but everything in this donation will go into the flex-utilities repo, unless someone has a better idea. Even the ADC html files until they get re-branded, unless those of you who work on our website want to see them in our site's SVN. Thanks, -Alex On 3/28/14 8:42 AM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the Adobe-hosted videos and images. G) Some articles point to zip files. In the donation, the zip files are expanded and the actual zip file is missing because we should be checking source and not zips into our repos. Build scripts will be needed to create zips that go with the production articles. And then we need to decide where to still all of this source. I guess flex-utilities for most of it. I would probably create a branch of flex-sdk for the FDB code. The XML Merge code will go in the BlazeDS repo with the rest of BlazeDS. Where should be put all of the devnet html files until they are ready? Thanks, -Alex Here are links to the ADC articles:
Re: Next Donation from Adobe
Alex, Let me know if I can help with the scrubbing effort. My work-load will lighten up at the office in a few weeks and I can put a few cycles towards that. -Nick On Thu, Apr 17, 2014 at 3:58 PM, Alex Harui aha...@adobe.com wrote: And it is official, the Apache Secretary has filed the donation paperwork. Apache Flex now owns all of the content below. (Apache doesn't really own it, but rather, has a license to it). I recently found out that post-graduation donations from Adobe were not handled properly by the Flex PMC. We have to get Incubator approval for all post-graduation donations so I can't just dump all of these files into our repo. So, over the course of the next several days/weeks, I will be scrubbing this donation to double-check on headers, etc, and asking for Incubator approval before they go into the repo. I will probably do this in chunks instead of one giant pile of files. I also have to do this for the BlazeDS files. To me, this is not top priority. The FalconJX/FlexJS releases are top priority along with a 4.12.1 and releasing Installer 3.0. And 360|Flex prep also takes priority over donation scrubbing. Once approved, the BlazeDS files will go into its own repo, but everything in this donation will go into the flex-utilities repo, unless someone has a better idea. Even the ADC html files until they get re-branded, unless those of you who work on our website want to see them in our site's SVN. Thanks, -Alex On 3/28/14 8:42 AM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the Adobe-hosted videos and images. G) Some articles point to zip files. In the donation, the zip files are expanded and the actual zip file is missing because we should be checking source and not zips into our repos. Build scripts will be needed to create zips that go with the production articles. And then we need to decide where to still all of this source.
Re: Next Donation from Adobe
Hi Nick, Thanks for volunteering. Yeah, I think I can use your help. I should have a better understanding of the steps we need to take to get Incubator sign off by time you get freed up a bit. So ping me when you are sure you're going to have cycles and we'll figure it out. Thanks, -Alex On 4/17/14 1:00 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Alex, Let me know if I can help with the scrubbing effort. My work-load will lighten up at the office in a few weeks and I can put a few cycles towards that. -Nick On Thu, Apr 17, 2014 at 3:58 PM, Alex Harui aha...@adobe.com wrote: And it is official, the Apache Secretary has filed the donation paperwork. Apache Flex now owns all of the content below. (Apache doesn't really own it, but rather, has a license to it). I recently found out that post-graduation donations from Adobe were not handled properly by the Flex PMC. We have to get Incubator approval for all post-graduation donations so I can't just dump all of these files into our repo. So, over the course of the next several days/weeks, I will be scrubbing this donation to double-check on headers, etc, and asking for Incubator approval before they go into the repo. I will probably do this in chunks instead of one giant pile of files. I also have to do this for the BlazeDS files. To me, this is not top priority. The FalconJX/FlexJS releases are top priority along with a 4.12.1 and releasing Installer 3.0. And 360|Flex prep also takes priority over donation scrubbing. Once approved, the BlazeDS files will go into its own repo, but everything in this donation will go into the flex-utilities repo, unless someone has a better idea. Even the ADC html files until they get re-branded, unless those of you who work on our website want to see them in our site's SVN. Thanks, -Alex On 3/28/14 8:42 AM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the
Re: Next Donation from Adobe
Looks like we have to have a [VOTE] to accept the donation. Stay tuned. -Alex On 4/17/14 1:19 PM, Alex Harui aha...@adobe.com wrote: Hi Nick, Thanks for volunteering. Yeah, I think I can use your help. I should have a better understanding of the steps we need to take to get Incubator sign off by time you get freed up a bit. So ping me when you are sure you're going to have cycles and we'll figure it out. Thanks, -Alex On 4/17/14 1:00 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Alex, Let me know if I can help with the scrubbing effort. My work-load will lighten up at the office in a few weeks and I can put a few cycles towards that. -Nick On Thu, Apr 17, 2014 at 3:58 PM, Alex Harui aha...@adobe.com wrote: And it is official, the Apache Secretary has filed the donation paperwork. Apache Flex now owns all of the content below. (Apache doesn't really own it, but rather, has a license to it). I recently found out that post-graduation donations from Adobe were not handled properly by the Flex PMC. We have to get Incubator approval for all post-graduation donations so I can't just dump all of these files into our repo. So, over the course of the next several days/weeks, I will be scrubbing this donation to double-check on headers, etc, and asking for Incubator approval before they go into the repo. I will probably do this in chunks instead of one giant pile of files. I also have to do this for the BlazeDS files. To me, this is not top priority. The FalconJX/FlexJS releases are top priority along with a 4.12.1 and releasing Installer 3.0. And 360|Flex prep also takes priority over donation scrubbing. Once approved, the BlazeDS files will go into its own repo, but everything in this donation will go into the flex-utilities repo, unless someone has a better idea. Even the ADC html files until they get re-branded, unless those of you who work on our website want to see them in our site's SVN. Thanks, -Alex On 3/28/14 8:42 AM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust
Re: Next Donation from Adobe
I'm in, if you let me know how I can participate. Is it already committed somewhere? I can't see anything on https://git-wip-us.apache.org/repos/asf... Franck -- @graniteds 2014-04-04 6:57 GMT+02:00 Alex Harui aha...@adobe.com: Volunteers are welcome to freshen the donated content Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Igor Costa igorco...@gmail.com wrote: That's good to know. Overall articles will be outdated for Flex 4.12, isn't? Best Regards Igor Costa www.igorcosta.com www.igorcosta.org On Thu, Apr 3, 2014 at 12:25 PM, Alex Harui aha...@adobe.com wrote: Good question. Any screenshots you take will be of the Adobe version. I think you could argue that one or two screenshots for a presentation is nominative fair use. Once donated, we will have to generate a new icon for Tour De Flex for Apache Flex and probably change up the colors and layout a bit. -Alex From: Christofer Dutz [christofer.d...@c-ware.de] Sent: Thursday, April 3, 2014 2:16 AM To: dev@flex.apache.org Subject: AW: Next Donation from Adobe Am I allowed to make some screenshots from TourDeFlex then? I wanted to add some screenshots to my ApacheCon presentation Von: Franck Wolff frawo...@gmail.com Gesendet: Donnerstag, 3. April 2014 11:10 An: dev@flex.apache.org Betreff: Re: Next Donation from Adobe Tour de Flex was much more than style explorer: it was also a way for third-party players (advanced component providers, frameworks, server solutions, etc.) to show their products with their main features. It would be great to have an updated Tour de Flex with an opened architecture, allowing people to plug in dedicated demos. Franck. @graniteds 2014-04-03 7:14 GMT+02:00 Deepak MS megharajdee...@gmail.com: These were the explorers that I was referring to: Original link: http://examples.adobe.com/flex3/componentexplorer/explorer.html Archived: http://web.archive.org/web/20120918204503/http://examples.adobe.com/flex3/componentexplorer/explorer.html Original link: http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Arhchived: http://web.archive.org/web/20120516031743/http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Those were of great help for me at the beginning when I started working on flex and I'm sure it would be very helpful for beginners too, who are looking out for both functionalities and the code together, for learning and referring quickly. Ofcourse that was on MX and I'm not sure if that was updated for spark. On Wed, Apr 2, 2014 at 8:37 PM, Alex Harui aha...@adobe.com wrote: Is Tour De Flex different from the explorers? I've never used any of them since I already know the code. Is there a link to explorers on Adobe.com that you are interested in? -Alex From: Deepak MS [megharajdee...@gmail.com] Sent: Tuesday, April 1, 2014 11:42 PM To: dev@flex.apache.org Subject: Re: Next Donation from Adobe That's great! Very keen to know if it includes component explorer and style explorer. On Fri, Mar 28, 2014 at 9:12 PM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us
Re: Next Donation from Adobe
We're still waiting for one more signature Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Franck Wolff frawo...@gmail.com wrote: I'm in, if you let me know how I can participate. Is it already committed somewhere? I can't see anything on https://git-wip-us.apache.org/repos/asf... Franck -- @graniteds 2014-04-04 6:57 GMT+02:00 Alex Harui aha...@adobe.com: Volunteers are welcome to freshen the donated content Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Igor Costa igorco...@gmail.com wrote: That's good to know. Overall articles will be outdated for Flex 4.12, isn't? Best Regards Igor Costa www.igorcosta.com www.igorcosta.org On Thu, Apr 3, 2014 at 12:25 PM, Alex Harui aha...@adobe.com wrote: Good question. Any screenshots you take will be of the Adobe version. I think you could argue that one or two screenshots for a presentation is nominative fair use. Once donated, we will have to generate a new icon for Tour De Flex for Apache Flex and probably change up the colors and layout a bit. -Alex From: Christofer Dutz [christofer.d...@c-ware.de] Sent: Thursday, April 3, 2014 2:16 AM To: dev@flex.apache.org Subject: AW: Next Donation from Adobe Am I allowed to make some screenshots from TourDeFlex then? I wanted to add some screenshots to my ApacheCon presentation Von: Franck Wolff frawo...@gmail.com Gesendet: Donnerstag, 3. April 2014 11:10 An: dev@flex.apache.org Betreff: Re: Next Donation from Adobe Tour de Flex was much more than style explorer: it was also a way for third-party players (advanced component providers, frameworks, server solutions, etc.) to show their products with their main features. It would be great to have an updated Tour de Flex with an opened architecture, allowing people to plug in dedicated demos. Franck. @graniteds 2014-04-03 7:14 GMT+02:00 Deepak MS megharajdee...@gmail.com: These were the explorers that I was referring to: Original link: http://examples.adobe.com/flex3/componentexplorer/explorer.html Archived: http://web.archive.org/web/20120918204503/http://examples.adobe.com/flex3/componentexplorer/explorer.html Original link: http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Arhchived: http://web.archive.org/web/20120516031743/http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Those were of great help for me at the beginning when I started working on flex and I'm sure it would be very helpful for beginners too, who are looking out for both functionalities and the code together, for learning and referring quickly. Ofcourse that was on MX and I'm not sure if that was updated for spark. On Wed, Apr 2, 2014 at 8:37 PM, Alex Harui aha...@adobe.com wrote: Is Tour De Flex different from the explorers? I've never used any of them since I already know the code. Is there a link to explorers on Adobe.com that you are interested in? -Alex From: Deepak MS [megharajdee...@gmail.com] Sent: Tuesday, April 1, 2014 11:42 PM To: dev@flex.apache.org Subject: Re: Next Donation from Adobe That's great! Very keen to know if it includes component explorer and style explorer. On Fri, Mar 28, 2014 at 9:12 PM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily
Re: Next Donation from Adobe
Tour de Flex was much more than style explorer: it was also a way for third-party players (advanced component providers, frameworks, server solutions, etc.) to show their products with their main features. It would be great to have an updated Tour de Flex with an opened architecture, allowing people to plug in dedicated demos. Franck. @graniteds 2014-04-03 7:14 GMT+02:00 Deepak MS megharajdee...@gmail.com: These were the explorers that I was referring to: Original link: http://examples.adobe.com/flex3/componentexplorer/explorer.html Archived: http://web.archive.org/web/20120918204503/http://examples.adobe.com/flex3/componentexplorer/explorer.html Original link: http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Arhchived: http://web.archive.org/web/20120516031743/http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Those were of great help for me at the beginning when I started working on flex and I'm sure it would be very helpful for beginners too, who are looking out for both functionalities and the code together, for learning and referring quickly. Ofcourse that was on MX and I'm not sure if that was updated for spark. On Wed, Apr 2, 2014 at 8:37 PM, Alex Harui aha...@adobe.com wrote: Is Tour De Flex different from the explorers? I've never used any of them since I already know the code. Is there a link to explorers on Adobe.com that you are interested in? -Alex From: Deepak MS [megharajdee...@gmail.com] Sent: Tuesday, April 1, 2014 11:42 PM To: dev@flex.apache.org Subject: Re: Next Donation from Adobe That's great! Very keen to know if it includes component explorer and style explorer. On Fri, Mar 28, 2014 at 9:12 PM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images
RE: Next Donation from Adobe
Good question. Any screenshots you take will be of the Adobe version. I think you could argue that one or two screenshots for a presentation is nominative fair use. Once donated, we will have to generate a new icon for Tour De Flex for Apache Flex and probably change up the colors and layout a bit. -Alex From: Christofer Dutz [christofer.d...@c-ware.de] Sent: Thursday, April 3, 2014 2:16 AM To: dev@flex.apache.org Subject: AW: Next Donation from Adobe Am I allowed to make some screenshots from TourDeFlex then? I wanted to add some screenshots to my ApacheCon presentation Von: Franck Wolff frawo...@gmail.com Gesendet: Donnerstag, 3. April 2014 11:10 An: dev@flex.apache.org Betreff: Re: Next Donation from Adobe Tour de Flex was much more than style explorer: it was also a way for third-party players (advanced component providers, frameworks, server solutions, etc.) to show their products with their main features. It would be great to have an updated Tour de Flex with an opened architecture, allowing people to plug in dedicated demos. Franck. @graniteds 2014-04-03 7:14 GMT+02:00 Deepak MS megharajdee...@gmail.com: These were the explorers that I was referring to: Original link: http://examples.adobe.com/flex3/componentexplorer/explorer.html Archived: http://web.archive.org/web/20120918204503/http://examples.adobe.com/flex3/componentexplorer/explorer.html Original link: http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Arhchived: http://web.archive.org/web/20120516031743/http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Those were of great help for me at the beginning when I started working on flex and I'm sure it would be very helpful for beginners too, who are looking out for both functionalities and the code together, for learning and referring quickly. Ofcourse that was on MX and I'm not sure if that was updated for spark. On Wed, Apr 2, 2014 at 8:37 PM, Alex Harui aha...@adobe.com wrote: Is Tour De Flex different from the explorers? I've never used any of them since I already know the code. Is there a link to explorers on Adobe.com that you are interested in? -Alex From: Deepak MS [megharajdee...@gmail.com] Sent: Tuesday, April 1, 2014 11:42 PM To: dev@flex.apache.org Subject: Re: Next Donation from Adobe That's great! Very keen to know if it includes component explorer and style explorer. On Fri, Mar 28, 2014 at 9:12 PM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version
Re: Next Donation from Adobe
That's good to know. Overall articles will be outdated for Flex 4.12, isn't? Best Regards Igor Costa www.igorcosta.com www.igorcosta.org On Thu, Apr 3, 2014 at 12:25 PM, Alex Harui aha...@adobe.com wrote: Good question. Any screenshots you take will be of the Adobe version. I think you could argue that one or two screenshots for a presentation is nominative fair use. Once donated, we will have to generate a new icon for Tour De Flex for Apache Flex and probably change up the colors and layout a bit. -Alex From: Christofer Dutz [christofer.d...@c-ware.de] Sent: Thursday, April 3, 2014 2:16 AM To: dev@flex.apache.org Subject: AW: Next Donation from Adobe Am I allowed to make some screenshots from TourDeFlex then? I wanted to add some screenshots to my ApacheCon presentation Von: Franck Wolff frawo...@gmail.com Gesendet: Donnerstag, 3. April 2014 11:10 An: dev@flex.apache.org Betreff: Re: Next Donation from Adobe Tour de Flex was much more than style explorer: it was also a way for third-party players (advanced component providers, frameworks, server solutions, etc.) to show their products with their main features. It would be great to have an updated Tour de Flex with an opened architecture, allowing people to plug in dedicated demos. Franck. @graniteds 2014-04-03 7:14 GMT+02:00 Deepak MS megharajdee...@gmail.com: These were the explorers that I was referring to: Original link: http://examples.adobe.com/flex3/componentexplorer/explorer.html Archived: http://web.archive.org/web/20120918204503/http://examples.adobe.com/flex3/componentexplorer/explorer.html Original link: http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Arhchived: http://web.archive.org/web/20120516031743/http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Those were of great help for me at the beginning when I started working on flex and I'm sure it would be very helpful for beginners too, who are looking out for both functionalities and the code together, for learning and referring quickly. Ofcourse that was on MX and I'm not sure if that was updated for spark. On Wed, Apr 2, 2014 at 8:37 PM, Alex Harui aha...@adobe.com wrote: Is Tour De Flex different from the explorers? I've never used any of them since I already know the code. Is there a link to explorers on Adobe.com that you are interested in? -Alex From: Deepak MS [megharajdee...@gmail.com] Sent: Tuesday, April 1, 2014 11:42 PM To: dev@flex.apache.org Subject: Re: Next Donation from Adobe That's great! Very keen to know if it includes component explorer and style explorer. On Fri, Mar 28, 2014 at 9:12 PM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS
Re: Next Donation from Adobe
Volunteers are welcome to freshen the donated content Sent via the PANTECH Discover, an ATT 4G LTE smartphone. Igor Costa igorco...@gmail.com wrote: That's good to know. Overall articles will be outdated for Flex 4.12, isn't? Best Regards Igor Costa www.igorcosta.com www.igorcosta.org On Thu, Apr 3, 2014 at 12:25 PM, Alex Harui aha...@adobe.com wrote: Good question. Any screenshots you take will be of the Adobe version. I think you could argue that one or two screenshots for a presentation is nominative fair use. Once donated, we will have to generate a new icon for Tour De Flex for Apache Flex and probably change up the colors and layout a bit. -Alex From: Christofer Dutz [christofer.d...@c-ware.de] Sent: Thursday, April 3, 2014 2:16 AM To: dev@flex.apache.org Subject: AW: Next Donation from Adobe Am I allowed to make some screenshots from TourDeFlex then? I wanted to add some screenshots to my ApacheCon presentation Von: Franck Wolff frawo...@gmail.com Gesendet: Donnerstag, 3. April 2014 11:10 An: dev@flex.apache.org Betreff: Re: Next Donation from Adobe Tour de Flex was much more than style explorer: it was also a way for third-party players (advanced component providers, frameworks, server solutions, etc.) to show their products with their main features. It would be great to have an updated Tour de Flex with an opened architecture, allowing people to plug in dedicated demos. Franck. @graniteds 2014-04-03 7:14 GMT+02:00 Deepak MS megharajdee...@gmail.com: These were the explorers that I was referring to: Original link: http://examples.adobe.com/flex3/componentexplorer/explorer.html Archived: http://web.archive.org/web/20120918204503/http://examples.adobe.com/flex3/componentexplorer/explorer.html Original link: http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Arhchived: http://web.archive.org/web/20120516031743/http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Those were of great help for me at the beginning when I started working on flex and I'm sure it would be very helpful for beginners too, who are looking out for both functionalities and the code together, for learning and referring quickly. Ofcourse that was on MX and I'm not sure if that was updated for spark. On Wed, Apr 2, 2014 at 8:37 PM, Alex Harui aha...@adobe.com wrote: Is Tour De Flex different from the explorers? I've never used any of them since I already know the code. Is there a link to explorers on Adobe.com that you are interested in? -Alex From: Deepak MS [megharajdee...@gmail.com] Sent: Tuesday, April 1, 2014 11:42 PM To: dev@flex.apache.org Subject: Re: Next Donation from Adobe That's great! Very keen to know if it includes component explorer and style explorer. On Fri, Mar 28, 2014 at 9:12 PM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe
RE: Next Donation from Adobe
Is Tour De Flex different from the explorers? I've never used any of them since I already know the code. Is there a link to explorers on Adobe.com that you are interested in? -Alex From: Deepak MS [megharajdee...@gmail.com] Sent: Tuesday, April 1, 2014 11:42 PM To: dev@flex.apache.org Subject: Re: Next Donation from Adobe That's great! Very keen to know if it includes component explorer and style explorer. On Fri, Mar 28, 2014 at 9:12 PM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the Adobe-hosted videos and images. G) Some articles point to zip files. In the donation, the zip files are expanded and the actual zip file is missing because we should be checking source and not zips into our repos. Build scripts will be needed to create zips that go with the production articles. And then we need to decide where to still all of this source. I guess flex-utilities for most of it. I would probably create a branch of flex-sdk for the FDB code. The XML Merge code will go in the BlazeDS repo with the rest of BlazeDS. Where should be put all of the devnet html files until they are ready? Thanks, -Alex Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbuil der.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex.h tml http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklist .html http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html http://www.adobe.com
Re: Next Donation from Adobe
Hi, Tour De Flex replaced the explorers (although some of the explorers did a bit more). The explorers were released by Adobe Consulting and were no longer updated past 2.0.1. There were some Flex 3 updates - but even so - they would need a bit of of overhaul if they were donated. This link does include the source code to the style explorer and link to the others: http://stackoverflow.com/questions/16169722/where-is-the-adobe-flex-style-explorer-sample-app Justin
Re: Next Donation from Adobe
Either way, they would require quite an overhaul because they were all MX based. Tour De Flex was supposed to incorporate their functionality for the most part. On Wed, Apr 2, 2014 at 5:09 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Tour De Flex replaced the explorers (although some of the explorers did a bit more). The explorers were released by Adobe Consulting and were no longer updated past 2.0.1. There were some Flex 3 updates - but even so - they would need a bit of of overhaul if they were donated. This link does include the source code to the style explorer and link to the others: http://stackoverflow.com/questions/16169722/where-is-the-adobe-flex-style-explorer-sample-app Justin
Re: Next Donation from Adobe
These were the explorers that I was referring to: Original link: http://examples.adobe.com/flex3/componentexplorer/explorer.html Archived: http://web.archive.org/web/20120918204503/http://examples.adobe.com/flex3/componentexplorer/explorer.html Original link: http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Arhchived: http://web.archive.org/web/20120516031743/http://examples.adobe.com/flex3/consulting/styleexplorer/Flex3StyleExplorer.html Those were of great help for me at the beginning when I started working on flex and I'm sure it would be very helpful for beginners too, who are looking out for both functionalities and the code together, for learning and referring quickly. Ofcourse that was on MX and I'm not sure if that was updated for spark. On Wed, Apr 2, 2014 at 8:37 PM, Alex Harui aha...@adobe.com wrote: Is Tour De Flex different from the explorers? I've never used any of them since I already know the code. Is there a link to explorers on Adobe.com that you are interested in? -Alex From: Deepak MS [megharajdee...@gmail.com] Sent: Tuesday, April 1, 2014 11:42 PM To: dev@flex.apache.org Subject: Re: Next Donation from Adobe That's great! Very keen to know if it includes component explorer and style explorer. On Fri, Mar 28, 2014 at 9:12 PM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the Adobe-hosted videos and images. G) Some articles point to zip files. In the donation, the zip files are expanded and the actual zip file is missing because we should be checking source and not zips into our repos. Build scripts will be needed to create zips that go with the production articles. And then we need to decide where to still all of this source. I guess flex-utilities for most of it. I would probably create a branch
Re: Next Donation from Adobe
great news :) hopefully Squiggly come out of beta.. On Fri, Mar 28, 2014 at 9:45 PM, Alex Harui aha...@adobe.com wrote: On 3/28/14 8:54 AM, João Fernandes joaopedromartinsfernan...@gmail.com wrote: Great news Alex! The source code for a prototype of a code coverage utility that I wrote. How does this work? This is the prototype I've mentioned before. It uses flash.trace.Trace to output every debug line your code passes through. The total set of debug lines can be compared to debug lines pulled from the SWF to compute coverage. It won't tell you as much as some other coverage technology that puts smarter information in the code paths, but it should have less drag on performance. It should also help with creating a tracing profiler. -Alex -- Warm Regards, *Rush-me*
Re: Next Donation from Adobe
On 28/03/14 15:42, Alex Harui wrote: 7. The Squiggly spell-checker source code Awe-*some* ! Tom
Re: Next Donation from Adobe
This one is really 雪中送炭 which means giving coal to us when it snows much!! An updated version of the FDB debugger that contains support for ActionScript Workers On Fri, Mar 28, 2014 at 11:42 AM, Alex Harui aha...@adobe.com wrote: Hi folks, Adobe legal and business folks have approved the donation of several Flex-related items to Apache. The donation paperwork is on its way to get VP signature (yes there could be some delay or reversal there, but I don't expect any), but I'm bringing this up now because we should start thinking about how to handle the contents of the donation. In the donation is: 1. Several Flex articles from the ADC web-site. 2. An updated version of the FDB debugger that contains support for ActionScript Workers 3. The FlexPMD source code 4. The Mobile Trader demo application 5. The specification for the MXML language 6. An XML merging utility source code from the Flex QA team. 7. The Squiggly spell-checker source code 8. The Tour De Flex application source code 9. The source code for a prototype of a code coverage utility that I wrote. Links to the original Adobe content is at the end of this email. When you go to the Adobe links you see a complete web article, but when donated, several things will be missing and several things will need adjusting before hosting the content at Apache. A) None of the videos in the VideoTraining article are being donated because the videos are heavily branded by Adobe watermarks. Adobe says our version of the article can link to the Adobe videos, but Apache does not want us to host Adobe videos on Apache servers. At some point in time, I will try to get these videos posted on YouTube so we don't have to worry about them being taken off of Adobe servers someday. Adobe Legal has ok'd posting the videos on YouTube, but I need to get some other approvals before doing it. We also need to get approval from Apache to link to the Adobe-hosted videos in the interim. We have approval to link to them when posted on YouTube. B) All of the devnet articles load Adobe CSS files. Our version of these articles should not look exactly like the Adobe colors so we need to create our own CSS file and adjust the articles to load those CSS files instead. I am not the right person to do this work, so a volunteer is needed. C) The Adobe icon and all head shots of authors are not being donated. The Apache version of these articles should not link to the head shots on the Adobe servers. D) The articles have sidebars and footers that point to lots of other Adobe content. Those sidebars and footers should be removed/replaced. E) Not all of the Tour De Flex content is being donated. Both TDF3 and TDF4 source code is in the donation, but articles written by non-Adobe authors are not in the donation. TDF will need to be adjusted to not reference the missing articles. The non-Adobe authors need to be contacted to donate their article to Apache. F) Other videos and images used in examples are missing from TDF and devnet articles if they were of real people or third-party brands. We will need to generate replacements, or adjust the articles to work without the missing videos and images. We will have to be careful as the articles may still point to the Adobe-hosted videos and images. G) Some articles point to zip files. In the donation, the zip files are expanded and the actual zip file is missing because we should be checking source and not zips into our repos. Build scripts will be needed to create zips that go with the production articles. And then we need to decide where to still all of this source. I guess flex-utilities for most of it. I would probably create a branch of flex-sdk for the FDB code. The XML Merge code will go in the BlazeDS repo with the rest of BlazeDS. Where should be put all of the devnet html files until they are ready? Thanks, -Alex Here are links to the ADC articles: http://www.adobe.com/devnet/flex/videotraining.html http://www.adobe.com/devnet/flex/testdrive.html http://www.adobe.com/devnet/flex/testdrivemobile.html http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbuil der.html http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex.h tml http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklist .html http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html http://www.adobe.com/devnet/flex/articles/spark_layouts.html http://www.adobe.com/devnet/flex/articles/flex-mobile-development-tips-tric ks-pt4.html http://www.adobe.com/devnet/flex/articles/flex4_skinning.html http://www.adobe.com/devnet/flex/articles/flex4_viewport_scrolling.html
RE: Next Donation from Adobe
Great news. -Message d'origine- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : vendredi 28 mars 2014 16:48 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe On 28/03/14 15:42, Alex Harui wrote: 7. The Squiggly spell-checker source code Awe-*some* ! Tom
Re: Next Donation from Adobe
On 3/28/14 8:54 AM, João Fernandes joaopedromartinsfernan...@gmail.com wrote: Great news Alex! The source code for a prototype of a code coverage utility that I wrote. How does this work? This is the prototype I've mentioned before. It uses flash.trace.Trace to output every debug line your code passes through. The total set of debug lines can be compared to debug lines pulled from the SWF to compute coverage. It won't tell you as much as some other coverage technology that puts smarter information in the code paths, but it should have less drag on performance. It should also help with creating a tracing profiler. -Alex
Re: Next Donation from Adobe
Great news Alex! The source code for a prototype of a code coverage utility that I wrote. How does this work? On 28 March 2014 15:50, Maurice Amsellem maurice.amsel...@systar.comwrote: Great news. -Message d'origine- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : vendredi 28 mars 2014 16:48 À : dev@flex.apache.org Objet : Re: Next Donation from Adobe On 28/03/14 15:42, Alex Harui wrote: 7. The Squiggly spell-checker source code Awe-*some* ! Tom -- João Fernandes
Re: Next Donation from Adobe
Great news! exciting stuff like FDB/Workers or FlexPMD. Thanks! :) 2014-03-28 18:02 GMT+01:00 Rushme Nayak rushme.nay...@gmail.com: great news :) hopefully Squiggly come out of beta.. On Fri, Mar 28, 2014 at 9:45 PM, Alex Harui aha...@adobe.com wrote: On 3/28/14 8:54 AM, João Fernandes joaopedromartinsfernan...@gmail.com wrote: Great news Alex! The source code for a prototype of a code coverage utility that I wrote. How does this work? This is the prototype I've mentioned before. It uses flash.trace.Trace to output every debug line your code passes through. The total set of debug lines can be compared to debug lines pulled from the SWF to compute coverage. It won't tell you as much as some other coverage technology that puts smarter information in the code paths, but it should have less drag on performance. It should also help with creating a tracing profiler. -Alex -- Warm Regards, *Rush-me* -- Carlos Rovira http://about.me/carlosrovira
