Re: Mustella News
Awesome Peter! that's a huge effort and I'm happy of your success. Great news for Apache Flex :D 2013/1/29 Avi Kessner akess...@gmail.com Thank you On Jan 29, 2013 9:17 AM, Om bigosma...@gmail.com wrote: On Mon, Jan 28, 2013 at 11:06 PM, Avi Kessner akess...@gmail.com wrote: I was really looking forward to the tests being part of the sdk. I can understand the desire not to release it, but would like to request a page or wiki on how a any random person can see how the tests are written and see them running. I think it can really help elevate the standards of the community. Here is an overview of Mustella: https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview Getting it from svn and running it is quite straightforward actually. It takes a very very long time to run, though. Thanks, Om On Jan 29, 2013 2:14 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Also, I believe that we decided we dont want to include Mustella in an Apache Flex release. Do you think we should? IMO no need to include it as It's probably not a huge amount of use to users of the SDK only to people who are actively working on changing/fixed the SDK. Justin PS Be nice if moved into it own project in SVN as well. -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
Re: ASJS question - MXML vs. AS
Any particular reason the TextButton instance is displayed using this.addChild(button) instead of a button.addToParent(this) ? On Mon, Jan 28, 2013 at 11:52 PM, Om bigosma...@gmail.com wrote: That worked. Thanks! Om On Mon, Jan 28, 2013 at 6:22 PM, Alex Harui aha...@adobe.com wrote: And you will need to update MXMLDataInterpreter.as from SVN. On 1/28/13 5:21 PM, Alex Harui aha...@adobe.com wrote: OK, here it is: FlexJSTest.as: package { import controllers.MyController; import flash.display.Sprite; import flash.text.TextField; import models.MyModel; import org.apache.flex.core.Application; public class FlexJSTest extends Application { public function FlexJSTest() { valuesImpl = new MySimpleValuesImpl(); model = new MyModel(); model.labelText = Hello World!; initialView = new MyInitialView(); controller = new MyController(this); } private var controller:MyController; } } MyInitialView.as: package { import flash.events.Event; import org.apache.flex.binding.SimpleBinding; import org.apache.flex.core.ViewBase; import org.apache.flex.html.staticControls.Button; import org.apache.flex.html.staticControls.Label; import org.apache.flex.html.staticControls.TextButton; public class MyInitialView extends ViewBase { public function MyInitialView() { super(); } override public function initUI(model:Object):void { super.initUI(model); lbl = new Label(); lbl.addToParent(this); lbl.initModel(); lbl.x = 100; lbl.y = 25; var sb:SimpleBinding = new SimpleBinding(); sb.setDocument(this); sb.destinationPropertyName = text; sb.sourceID = applicationModel; sb.eventName = labelTextChanged; sb.sourcePropertyName = labelText; lbl.addBead(sb); lbl.initSkin(); var btn:TextButton = new TextButton(); addChild(btn); btn.initModel(); btn.text = OK; btn.x = 100; btn.y = 75; btn.addEventListener(click, clickHandler); btn.initSkin(); } public var lbl:Label; private function clickHandler(event:Event):void { dispatchEvent(new Event(buttonClicked)); } } } On 1/28/13 3:41 PM, Alex Harui aha...@adobe.com wrote: OK, I'll put together the AS version of the app. On 1/28/13 3:35 PM, Om bigosma...@gmail.com wrote: On Sun, Jan 27, 2013 at 11:20 PM, Alex Harui aha...@adobe.com wrote: On 1/27/13 10:50 PM, Om bigosma...@gmail.com wrote: But they dont seem to match up. Can you please respond with how the mxml would look when redone as a pure actionscript file? There are two possible answers to this question. One is for the question: what would the generated AS for the MXML file look like? It would look somewhat like the FlexJSTest.as that you found, but it is a bit different because when I finally got the compiler working it was easier to change some of the 'generated' code a bit. If you are really interested, I will try to hand-code it. This would be good. I played my hand around hand-coding based on this wiki note [1] But I would rather see your version. I'm not sure why you want to be hand-coding AS versions of MXML files. The other answer is for the question: How would you write this app in ActionScript? If I were to do it, it would not use the data array at all, it would call new Button and new Label and set properties and add event handlers. -- I am curious how this would work behind the scenes. But I am not in a hurry to look at the implementation details. A couple other questions while I have your attention: Will the FlexJSTest_again app compile with the current mxmlc? I saw your note in the wiki that says that it wont. Is there any way to make it work? The status page supercedes the original wiki page. FalconJS converts FlexJSTest.mxml to FlexJSTest.js. Falcon (assuming you set the mxml.children-as-data flag) will convert FlexJSTest.mxml to a running SWF. I have hooked up the falcon compiler to my flash builder (4.6) as an external run tool. The app compiles fine, but the IDE keeps showing errors. Any way I can jerry rig Flash Builder to use the Falcon mxmlc? I haven't tried. I assume you can swap out the original MXMLC compiler for the Falcon JARs. I do have Flash Builder 4.7 installed. I am willing to switch if that would make this process any simpler. Sorry for so many
Re: Project Apache Flex
I can't even keep up with all the activity going on here! On Tue, Jan 29, 2013 at 3:08 PM, Avi Kessner akess...@gmail.com wrote: Very leet (1337) :-) On Jan 28, 2013 8:57 PM, Harbs harbs.li...@gmail.com wrote: I have 13307 emails from the dev list since 3/2/12! On Jan 28, 2013, at 8:26 PM, Kessler CTR Mark J wrote: Since I started a pst just for the dev list I have... 8356 emails alone since 6/25/2012 I wonder how many I had before that. -Mark -Original Message- From: Gordon Smith [mailto:gosm...@adobe.com] Sent: Monday, January 28, 2013 1:10 PM To: dev@flex.apache.org Subject: RE: Project Apache Flex Friends, how is the Apache Flex project? Active! 400 emails/week on this list! - Gordon
Re: A code name for Apache Flex 5?
Wasn't there a plan to dedicate something in Apache Flex to Doug Arthur after he passed away last year? So how about we call it 'dougart', code names are mostly used internally anyways, the official release will be called 'Apache Flex 5' with perhaps a separate dedication to Doug. thoughts? On 29 January 2013 12:02, Michael Schmalle apa...@teotigraphix.com wrote: My vote is 'Apache Flex 5' Mike Quoting Sebastian Mohr flex.masul...@gmail.com: Hi there, Since using code names for Adobe Flex seemed to be a good practise (e.g. 'Halo', 'Gumbo', 'Hero'), I wonder if we should find a code name for Apache Flex 5? Thoughts? -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/**masuland/wiki/LoginExamplehttp://code.google.com/p/masuland/wiki/LoginExample -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- regards, Roland -- Roland Zwaga Senior Consultant | Stack Heap BVBA +32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com http://zwaga.blogspot.com http://www.springactionscript.org http://www.as3commons.org
Re: A code name for Apache Flex 5?
Quoting Roland Zwaga rol...@stackandheap.com: Wasn't there a plan to dedicate something in Apache Flex to Doug Arthur after he passed away last year? Missed this conversation, sounds good, I know I was absent when he passed but him and I worked on the logo contest like mad, he was definitely in support of this project. So how about we call it 'dougart', code names are mostly used internally This was exactly my point, there is no internal operations at Apache, thus a code name sounds like it would be weird in the Apache setting. Maybe if we didn't call it a code name, that sounds to 007 I guess for me. We are not hiding anything before a release, there are no NDAs... Please if we name a prerelase, don't call it a code name! anyways, the official release will be called 'Apache Flex 5' with perhaps a separate dedication to Doug. thoughts? I agree. Mike On 29 January 2013 12:02, Michael Schmalle apa...@teotigraphix.com wrote: My vote is 'Apache Flex 5' Mike Quoting Sebastian Mohr flex.masul...@gmail.com: Hi there, Since using code names for Adobe Flex seemed to be a good practise (e.g. 'Halo', 'Gumbo', 'Hero'), I wonder if we should find a code name for Apache Flex 5? Thoughts? -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/**masuland/wiki/LoginExamplehttp://code.google.com/p/masuland/wiki/LoginExample -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- regards, Roland -- Roland Zwaga Senior Consultant | Stack Heap BVBA +32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com http://zwaga.blogspot.com http://www.springactionscript.org http://www.as3commons.org -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
RE: A code name for Apache Flex 5?
Hi, I thought it was much more plan to do a 4.10 instead of a 5.0 until UIComponent/Styles has been reviewed (rewrited). Did I miss something ? -Fred -Original Message- From: Sebastian Mohr [mailto:flex.masul...@gmail.com] Sent: Tuesday, January 29, 2013 11:59 AM To: dev@flex.apache.org Subject: A code name for Apache Flex 5? Hi there, Since using code names for Adobe Flex seemed to be a good practise (e.g. 'Halo', 'Gumbo', 'Hero'), I wonder if we should find a code name for Apache Flex 5? Thoughts? -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample
Re: A code name for Apache Flex 5?
Excalibur, sword (tool) of the legendary King Arthur, King Arthur is a legendary British leader of the late 5th and early 6th centuries So for Apache Flex 5 and in memory of Doug Arthur I present Excalibur as codename Fréderic Cox On 29/01/13 12:21, Michael Schmalle apa...@teotigraphix.com wrote: Quoting Roland Zwaga rol...@stackandheap.com: Wasn't there a plan to dedicate something in Apache Flex to Doug Arthur after he passed away last year? Missed this conversation, sounds good, I know I was absent when he passed but him and I worked on the logo contest like mad, he was definitely in support of this project. So how about we call it 'dougart', code names are mostly used internally This was exactly my point, there is no internal operations at Apache, thus a code name sounds like it would be weird in the Apache setting. Maybe if we didn't call it a code name, that sounds to 007 I guess for me. We are not hiding anything before a release, there are no NDAs... Please if we name a prerelase, don't call it a code name! anyways, the official release will be called 'Apache Flex 5' with perhaps a separate dedication to Doug. thoughts? I agree. Mike On 29 January 2013 12:02, Michael Schmalle apa...@teotigraphix.com wrote: My vote is 'Apache Flex 5' Mike Quoting Sebastian Mohr flex.masul...@gmail.com: Hi there, Since using code names for Adobe Flex seemed to be a good practise (e.g. 'Halo', 'Gumbo', 'Hero'), I wonder if we should find a code name for Apache Flex 5? Thoughts? -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/**masuland/wiki/LoginExamplehttp://code.googl e.com/p/masuland/wiki/LoginExample -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- regards, Roland -- Roland Zwaga Senior Consultant | Stack Heap BVBA +32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com http://zwaga.blogspot.com http://www.springactionscript.org http://www.as3commons.org -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
[jira] [Commented] (FLEX-33367) flash.display.Loader intermitently causing children of loaded swf to loose type
[ https://issues.apache.org/jira/browse/FLEX-33367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565290#comment-13565290 ] Tim Leslie commented on FLEX-33367: --- Hi Alex, I'm afraid that's not the issue. They're all single frame movieclips and it's been reproduced by someone else on Stack Overflow without sharing my FLA. The weirdest thing is it only seems to happen over a network. I'm pretty sure this is a genuine bug. Where is the correct place to post it? Cheers, Tim flash.display.Loader intermitently causing children of loaded swf to loose type --- Key: FLEX-33367 URL: https://issues.apache.org/jira/browse/FLEX-33367 Project: Apache Flex Issue Type: Bug Components: .Unspecified - Framework Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Seen on windows, mac and linux, various OS. Reporter: Tim Leslie Labels: loader Have a look at this stack overflow for a complete explaination and instruction on how to reproduce: http://stackoverflow.com/questions/14464898/flash-display-loader-intermitently-causing-children-of-loaded-swf-to-loose-type When two movieclips are loaded into an application using a flash.display.Loader and Event.COMPLETE is dispatched from both loaders on different frames, some instances in the first movieclip to be loaded loose their type when the second movieclip becomes available. For example, a recursive search for all decendents of type MC_Circle fails when normally it works. I have been recomended to report this issue by users of Stack Overflow who were able to reproduce it. I'm not sure of the full list of affected SDKs or Flash Player versions but I have been using 4.6. I have only tried hosting the swfs to be loaded on linux machine though the problem is reproducing with the loader swf on various OS. It's possible the problem only occurs when loading over a network. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: A code name for Apache Flex 5?
I think Frederic as a most comon sense for Apache Flex. Apache foundation doesn't have internal moves for codenames like we had previous at inc. company. This isn't the right spot to start working a major release with flag Apache Flex 5 We need to focus on the following things before: - Fix the current open-bugs - Adapt the Falcon to the SDK - Integrate other dependencies from Adobe donations like Squiggly and TLF. Than on the begin release of Apache Flex 5 we can add the support of output for HTML/JS. Best Regards Igor Costa www.igorcosta.com www.igorcosta.org On Tue, Jan 29, 2013 at 9:25 AM, Fréderic Cox coxfrede...@gmail.com wrote: Excalibur, sword (tool) of the legendary King Arthur, King Arthur is a legendary British leader of the late 5th and early 6th centuries So for Apache Flex 5 and in memory of Doug Arthur I present Excalibur as codename Fréderic Cox On 29/01/13 12:21, Michael Schmalle apa...@teotigraphix.com wrote: Quoting Roland Zwaga rol...@stackandheap.com: Wasn't there a plan to dedicate something in Apache Flex to Doug Arthur after he passed away last year? Missed this conversation, sounds good, I know I was absent when he passed but him and I worked on the logo contest like mad, he was definitely in support of this project. So how about we call it 'dougart', code names are mostly used internally This was exactly my point, there is no internal operations at Apache, thus a code name sounds like it would be weird in the Apache setting. Maybe if we didn't call it a code name, that sounds to 007 I guess for me. We are not hiding anything before a release, there are no NDAs... Please if we name a prerelase, don't call it a code name! anyways, the official release will be called 'Apache Flex 5' with perhaps a separate dedication to Doug. thoughts? I agree. Mike On 29 January 2013 12:02, Michael Schmalle apa...@teotigraphix.com wrote: My vote is 'Apache Flex 5' Mike Quoting Sebastian Mohr flex.masul...@gmail.com: Hi there, Since using code names for Adobe Flex seemed to be a good practise (e.g. 'Halo', 'Gumbo', 'Hero'), I wonder if we should find a code name for Apache Flex 5? Thoughts? -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/**masuland/wiki/LoginExample http://code.googl e.com/p/masuland/wiki/LoginExample -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- regards, Roland -- Roland Zwaga Senior Consultant | Stack Heap BVBA +32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com http://zwaga.blogspot.com http://www.springactionscript.org http://www.as3commons.org -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
[jira] [Commented] (FLEX-33291) Apache Flex Mavenized SDK Generator Bug
[ https://issues.apache.org/jira/browse/FLEX-33291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565428#comment-13565428 ] Gary Yang commented on FLEX-33291: -- I just checked out the source and encounter the same problem: - java.util.zip.ZipException: ZIP file must have at least one entry at java.util.zip.ZipOutputStream.finish(ZipOutputStream.java:304) at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:140) at java.util.zip.ZipOutputStream.close(ZipOutputStream.java:321) at flex.FlexFrameworkGenerator.writeDummyResourceBundleSwc(FlexFrameworkGenerator.java:582) at flex.FlexFrameworkGenerator.process(FlexFrameworkGenerator.java:179) at SDKGenerator.generateFlex(SDKGenerator.java:123) at SDKGenerator.generateAllFlex(SDKGenerator.java:111) at SDKGenerator.main(SDKGenerator.java:153) Apache Flex Mavenized SDK Generator Bug --- Key: FLEX-33291 URL: https://issues.apache.org/jira/browse/FLEX-33291 Project: Apache Flex Issue Type: Bug Components: Installation Packaging Affects Versions: InstalApacheFlex 1.0 Reporter: Jose Barragan Assignee: Jose Barragan Fix For: InstalApacheFlex 1.0 Ir reference to this issue: My first error is: Exception in thread main java.lang.NoClassDefFoundError: org/apache/commons/compress/compressors/gzip/GzipCompressorInputStream at air.AirRuntimeGenerator.processFlashRuntime(AirRuntimeGenerator.java:139) at air.AirRuntimeGenerator.process(AirRuntimeGenerator.java:41) at SDKGenerator.generateAir(SDKGenerator.java:82) at SDKGenerator.generateAllAir(SDKGenerator.java:67) at SDKGenerator.main(SDKGenerator.java:145) Caused by: java.lang.ClassNotFoundException: org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 5 more So it seems the GzipCompressorInputStream is not available in the flex-sdk-generator-1.0.jar. That's easily overcome by using the maven shade plugin. The problem occurs when running any command using the flex-sdk-generator jar, and is caused by the mavenizer.jar not including the org.apache.commons.compress dependency - you can test this, by opening up the flex-sdk-generator.jar and see there are no classes from the org.apache.commons.compress dependency. The maven shade plugin ensures dependencie's classes are packaged in final flex-sdk-generator.jar. - or maybe you could use the standard integrated java zip api's: http://docs.oracle.com/javase/6/docs/api/java/util/zip/package-summary.html http://www.javaworld.com/community/node/8362 I'm running the following java: java version 1.6.0_37 Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-11M3909) Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01-434, mixed mode) The second problem: Srens-MacBook-Pro-2:mavenizer soren$ java -cp target/flex-sdk-converter-1.0.jar SDKGenerator sdkhome fdktarget - -- Generating Air SDK version: 3.5 - - - -- Generating Air SDK version: 3.1 - - - -- Generating Flex SDK version: 4.6.0.23201 - Exception in thread main java.util.zip.ZipException: ZIP file must have at least one entry at java.util.zip.ZipOutputStream.finish(ZipOutputStream.java:304) at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:140) at java.util.zip.ZipOutputStream.close(ZipOutputStream.java:321) at flex.FlexFrameworkGenerator.writeDummyResourceBundleSwc(FlexFrameworkGenerator.java:576) at flex.FlexFrameworkGenerator.process(FlexFrameworkGenerator.java:175) at SDKGenerator.generateFlex(SDKGenerator.java:120) at SDKGenerator.generateAllFlex(SDKGenerator.java:108) at SDKGenerator.main(SDKGenerator.java:148) Might be resolved by using the integrated zip api of java, as mentioned in the first problem?!? Regards. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact
Re: [ASJS] debugging output JS?
On Tue, Jan 29, 2013 at 9:38 AM, Roland Zwaga rol...@stackandheap.comwrote: We have 2 camps now, performance vs debugging features. I believe you are incorrect. The debugging features are only relevant when compiling in debug mode. Every camp here agrees that release mode should output the most optimized JS possible. Totally agree with Alex and Roland. Daniel, did you have a look at Erik's demo? http://people.apache.org/~erikdebruin/vanillasdk/ It is not a performance demo, but what you can see is that, from the same AS sources, the compiler produces a debuggable version (intermediate JS version) and a minified version (release JS version) which packs the whole application into merely 11.5 kb. While this is only a small demo application, it shows that there is no bloat or large overhead. So the solution to first create debuggable code, then minify for production, seems to work well. We'll do performance tests later, when we have a larger example working. Greetings -Frank-
Re: How to diffrence between TLF 2.0 and TLF 3.0
Hello So, Actually Apache Flex 4.9 was tested with TLF 3.0.33, right? thanks Shigeru Nakagaki 2013/1/29 Harbs harbs.li...@gmail.com: Thanks. I know I should upgrade, but I'm always nervous upgrading the code base on active projects… ;-) On Jan 28, 2013, at 7:42 PM, Carol Frampton wrote: frameworks/projects/textLayout/src/flashx/textLayout/ReleaseNotes.txt has a running list of changes There were a couple of important bug fixes in TLF 2.something that was a later version than the version in Adobe Flex 4.6. Carol On 1/28/13 12 :34PM, Harbs harbs.li...@gmail.com wrote: Is there a list somewhere of changes between TLF 2 and TLF 3? I have not switched over yet, but looking at TLF 3, it looks like I will be soon. I'd like to be aware of any changes I might come acrossŠ Harbs On Jan 28, 2013, at 5:53 PM, Carol Frampton wrote: frameworks/projects/textLayout/src/flashx/textLayout/TextLayoutVersion.as . Apache Flex 4.6 was TLF 2.0 build 232. Carol On 1/28/13 6 :45AM, sanjay.prasad sanjay.pra...@excelindia.com wrote: Hello, I am currently working for open page reader using Adobe Flex 4.6 with TLF. I didn't able to find out which TLF version is currently using in my application. Is there any way to find out which TLF version is currently working. Thanks Regards
Re: A code name for Apache Flex 5?
Excalibur sounds great for whatever is nicknamed next :-) On Jan 29, 2013 1:26 PM, Fréderic Cox coxfrede...@gmail.com wrote: Excalibur, sword (tool) of the legendary King Arthur, King Arthur is a legendary British leader of the late 5th and early 6th centuries So for Apache Flex 5 and in memory of Doug Arthur I present Excalibur as codename Fréderic Cox On 29/01/13 12:21, Michael Schmalle apa...@teotigraphix.com wrote: Quoting Roland Zwaga rol...@stackandheap.com: Wasn't there a plan to dedicate something in Apache Flex to Doug Arthur after he passed away last year? Missed this conversation, sounds good, I know I was absent when he passed but him and I worked on the logo contest like mad, he was definitely in support of this project. So how about we call it 'dougart', code names are mostly used internally This was exactly my point, there is no internal operations at Apache, thus a code name sounds like it would be weird in the Apache setting. Maybe if we didn't call it a code name, that sounds to 007 I guess for me. We are not hiding anything before a release, there are no NDAs... Please if we name a prerelase, don't call it a code name! anyways, the official release will be called 'Apache Flex 5' with perhaps a separate dedication to Doug. thoughts? I agree. Mike On 29 January 2013 12:02, Michael Schmalle apa...@teotigraphix.com wrote: My vote is 'Apache Flex 5' Mike Quoting Sebastian Mohr flex.masul...@gmail.com: Hi there, Since using code names for Adobe Flex seemed to be a good practise (e.g. 'Halo', 'Gumbo', 'Hero'), I wonder if we should find a code name for Apache Flex 5? Thoughts? -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/**masuland/wiki/LoginExample http://code.googl e.com/p/masuland/wiki/LoginExample -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- regards, Roland -- Roland Zwaga Senior Consultant | Stack Heap BVBA +32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com http://zwaga.blogspot.com http://www.springactionscript.org http://www.as3commons.org -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
AW: A code name for Apache Flex 5?
I wouldn't recommend using the name Excalibur as I remember Apache Cocoon and quite a lot of other projects used to use the IoC Container Excalibur, which seems to be a retired Apache project ... and whenever I think of Excalibur in the context of IT-Stuff, the second thought thank god we don't have to use that anymore :-) Just my 50tc ;-) Chris -Ursprüngliche Nachricht- Von: Fréderic Cox [mailto:coxfrede...@gmail.com] Gesendet: Dienstag, 29. Januar 2013 12:26 An: dev@flex.apache.org Betreff: Re: A code name for Apache Flex 5? Excalibur, sword (tool) of the legendary King Arthur, King Arthur is a legendary British leader of the late 5th and early 6th centuries So for Apache Flex 5 and in memory of Doug Arthur I present Excalibur as codename Fréderic Cox On 29/01/13 12:21, Michael Schmalle apa...@teotigraphix.com wrote: Quoting Roland Zwaga rol...@stackandheap.com: Wasn't there a plan to dedicate something in Apache Flex to Doug Arthur after he passed away last year? Missed this conversation, sounds good, I know I was absent when he passed but him and I worked on the logo contest like mad, he was definitely in support of this project. So how about we call it 'dougart', code names are mostly used internally This was exactly my point, there is no internal operations at Apache, thus a code name sounds like it would be weird in the Apache setting. Maybe if we didn't call it a code name, that sounds to 007 I guess for me. We are not hiding anything before a release, there are no NDAs... Please if we name a prerelase, don't call it a code name! anyways, the official release will be called 'Apache Flex 5' with perhaps a separate dedication to Doug. thoughts? I agree. Mike On 29 January 2013 12:02, Michael Schmalle apa...@teotigraphix.com wrote: My vote is 'Apache Flex 5' Mike Quoting Sebastian Mohr flex.masul...@gmail.com: Hi there, Since using code names for Adobe Flex seemed to be a good practise (e.g. 'Halo', 'Gumbo', 'Hero'), I wonder if we should find a code name for Apache Flex 5? Thoughts? -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/**masuland/wiki/LoginExamplehttp://code.go ogl e.com/p/masuland/wiki/LoginExample -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com -- regards, Roland -- Roland Zwaga Senior Consultant | Stack Heap BVBA +32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com http://zwaga.blogspot.com http://www.springactionscript.org http://www.as3commons.org -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
Re: [ASJS] debugging output JS?
To give an impression of how you could switch between different debug levels and also to see how the AMD approach compares to the goog approach, I re-compiled Erik's VanillaSDK demo with Jangaroo 3 to AMD-style JavaScript output. This is the output format Mike Schmalle will be implementing as an alternative emitter for FalconJx. (Sorry I had to use Jangaroo to build this demo now; Mike is working hard on the FalconJx AMD emitter and eventually, the result will be much better than Jangaroo, since Falcon is the better AS3 compiler.) Here is the result: http://www.jangaron.net/vanilla-sdk-poc/ In total, there are four variants. The first and last version correspond to Erik's intermediate JS and release JS versions. To show the full bandwidth of debug levels, I added linked and linked and minified ... (bootstrapped). The former is a build where all AMD modules are merged into a single file, but not minified. The latter is a build where all AMD modules are merged and minified, but this one file is still loaded via RequireJS. So if you really want only one big JS file loaded with one request, you have to use the release JS version. The resulting release version (9.5 kb) is quite similar in size to the goog version (11.5 kb), although it has only been minified with SIMPLE_OPTIMIZATIONS, while the goog version uses ADVANCED_OPTIMIZATIONS. I think this underpins my point that starting from standard JavaScript code respecting rules like avoid accessing global variables, you can do without Google Closure Compiler's ADVANCED_OPTIMIZATIONS. But of course, we need a larger example before I'd dare to generalize this conclusion. All three debuggable versions actually load the same HTML page debug.html, the difference is coded into the URL hash joo.debug and evaluated by the bootstrap script new.js: - #joo.debug=true or #joo.debug -- load each class by a single request, so that you can easily find them in any (good) JavaScript debugger. Each file contains full white-space, comments, and non-minified JavaScript code. - #joo.debug=linked -- load all classes by one single request, but still with full white-space, comments, and non-minified. - #joo.debug=false or no hash -- load all classes by one single request, minified. All corresponding artifacts are automatically created as part of the build process. Of course, you can choose to only build the ones you actually need. *Source Maps* For the #joo.debug=true versionhttp://www.jangaron.net/vanilla-sdk-poc/debug.html#joo.debug, Jangaroo's experimental JavaScript source map support has been used. As far as I know, the only browser that currently supports source maps is Chrome. So if you want to see it in action, please use Chrome. And you might have to enable it first: 1. In the developer tools (F12), click on the button with the gear icon on the bottom right 2. In the settings dialog that appears, set the check mark in section *Sources*, labelled Enable source maps 3. Reload the page Now, in the Sources tab, when you open the navigator (arrow button top left), you'll find an *.as file next to each *.js file that has been generated from AS. Try and set a breakpoint e.g. in Example.as, line 66, inside the first click handler method. Then click on the demo button labelled Click me. The debugger should stop at your breakpoint and show the corresponding Call Stack, Scope Variables, and so on. You can now step through your ActionScript code, and the corresponding JavaScript code gets executed. Magic, isn't it? And it can be done for FalconJx, too! The vision is to combine the minified or at least the linked version with source maps, so that actually only one JS file is loaded, but is appears in the debugger as many AS files. To achieve this, we will have to combine the source map generated by our compiler and the source map generated by the JS minifier into a direct mapping. Using the source maps API that GCC provides, this should be quite straight-forward. Have fun! -Frank-
RE: [ASJS] debugging output JS?
Big yes, that's impressive :) -Fred -Original Message- From: Frank Wienberg [mailto:fr...@jangaroo.net] Sent: Tuesday, January 29, 2013 5:04 PM To: dev@flex.apache.org Subject: Re: [ASJS] debugging output JS? To give an impression of how you could switch between different debug levels and also to see how the AMD approach compares to the goog approach, I re-compiled Erik's VanillaSDK demo with Jangaroo 3 to AMD-style JavaScript output. This is the output format Mike Schmalle will be implementing as an alternative emitter for FalconJx. (Sorry I had to use Jangaroo to build this demo now; Mike is working hard on the FalconJx AMD emitter and eventually, the result will be much better than Jangaroo, since Falcon is the better AS3 compiler.) Here is the result: http://www.jangaron.net/vanilla-sdk-poc/ In total, there are four variants. The first and last version correspond to Erik's intermediate JS and release JS versions. To show the full bandwidth of debug levels, I added linked and linked and minified ... (bootstrapped). The former is a build where all AMD modules are merged into a single file, but not minified. The latter is a build where all AMD modules are merged and minified, but this one file is still loaded via RequireJS. So if you really want only one big JS file loaded with one request, you have to use the release JS version. The resulting release version (9.5 kb) is quite similar in size to the goog version (11.5 kb), although it has only been minified with SIMPLE_OPTIMIZATIONS, while the goog version uses ADVANCED_OPTIMIZATIONS. I think this underpins my point that starting from standard JavaScript code respecting rules like avoid accessing global variables, you can do without Google Closure Compiler's ADVANCED_OPTIMIZATIONS. But of course, we need a larger example before I'd dare to generalize this conclusion. All three debuggable versions actually load the same HTML page debug.html, the difference is coded into the URL hash joo.debug and evaluated by the bootstrap script new.js: - #joo.debug=true or #joo.debug -- load each class by a single request, so that you can easily find them in any (good) JavaScript debugger. Each file contains full white-space, comments, and non-minified JavaScript code. - #joo.debug=linked -- load all classes by one single request, but still with full white-space, comments, and non-minified. - #joo.debug=false or no hash -- load all classes by one single request, minified. All corresponding artifacts are automatically created as part of the build process. Of course, you can choose to only build the ones you actually need. *Source Maps* For the #joo.debug=true versionhttp://www.jangaron.net/vanilla-sdk-poc/debug.html#joo.debug, Jangaroo's experimental JavaScript source map support has been used. As far as I know, the only browser that currently supports source maps is Chrome. So if you want to see it in action, please use Chrome. And you might have to enable it first: 1. In the developer tools (F12), click on the button with the gear icon on the bottom right 2. In the settings dialog that appears, set the check mark in section *Sources*, labelled Enable source maps 3. Reload the page Now, in the Sources tab, when you open the navigator (arrow button top left), you'll find an *.as file next to each *.js file that has been generated from AS. Try and set a breakpoint e.g. in Example.as, line 66, inside the first click handler method. Then click on the demo button labelled Click me. The debugger should stop at your breakpoint and show the corresponding Call Stack, Scope Variables, and so on. You can now step through your ActionScript code, and the corresponding JavaScript code gets executed. Magic, isn't it? And it can be done for FalconJx, too! The vision is to combine the minified or at least the linked version with source maps, so that actually only one JS file is loaded, but is appears in the debugger as many AS files. To achieve this, we will have to combine the source map generated by our compiler and the source map generated by the JS minifier into a direct mapping. Using the source maps API that GCC provides, this should be quite straight-forward. Have fun! -Frank-
[jira] [Commented] (FLEX-33366) The candidate input method can not follow
[ https://issues.apache.org/jira/browse/FLEX-33366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565535#comment-13565535 ] Alex Harui commented on FLEX-33366: --- What feature of TLF do you need that TextField does not provide? The candidate input method can not follow - Key: FLEX-33366 URL: https://issues.apache.org/jira/browse/FLEX-33366 Project: Apache Flex Issue Type: Bug Components: Spark: TextArea, Spark: TextInput Affects Versions: Apache Flex 4.8 (parity release) Environment: windows,IE8 Reporter: zy The spark:TextArea and TextInput Chinese candidate input method can not follow. But mx:TextArea and TextInput not this issue. I guess you only test the English input method, Chinese input methods all have this problem, it is affecting the user experience. you can test this Chinese input method.all chinese use this. http://dl_dir.qq.com/invc/qqpinyin/QQPinyin_Setup_1.1.1224.400.exe I made a picture to illustrate the problem. http://img.my.csdn.net/uploads/201301/24/1359028348_2400.jpg If you are unclear, please let me know. I don't know english.I am very sorry. Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: ASJS question - MXML vs. AS
Not really, mostly just to see what happens if you use widgets that are not based on UIBase. As of right now, buttons are based on SimpleButton to save writing a bunch of code and are not a UIBase, but yesterday I started leaning towards making an IUIBase and making Button implement that. Feel free to make that change if it is getting in your way. On 1/29/13 12:49 AM, Om bigosma...@gmail.com wrote: Any particular reason the TextButton instance is displayed using this.addChild(button) instead of a button.addToParent(this) ? On Mon, Jan 28, 2013 at 11:52 PM, Om bigosma...@gmail.com wrote: That worked. Thanks! Om On Mon, Jan 28, 2013 at 6:22 PM, Alex Harui aha...@adobe.com wrote: And you will need to update MXMLDataInterpreter.as from SVN. On 1/28/13 5:21 PM, Alex Harui aha...@adobe.com wrote: OK, here it is: FlexJSTest.as: package { import controllers.MyController; import flash.display.Sprite; import flash.text.TextField; import models.MyModel; import org.apache.flex.core.Application; public class FlexJSTest extends Application { public function FlexJSTest() { valuesImpl = new MySimpleValuesImpl(); model = new MyModel(); model.labelText = Hello World!; initialView = new MyInitialView(); controller = new MyController(this); } private var controller:MyController; } } MyInitialView.as: package { import flash.events.Event; import org.apache.flex.binding.SimpleBinding; import org.apache.flex.core.ViewBase; import org.apache.flex.html.staticControls.Button; import org.apache.flex.html.staticControls.Label; import org.apache.flex.html.staticControls.TextButton; public class MyInitialView extends ViewBase { public function MyInitialView() { super(); } override public function initUI(model:Object):void { super.initUI(model); lbl = new Label(); lbl.addToParent(this); lbl.initModel(); lbl.x = 100; lbl.y = 25; var sb:SimpleBinding = new SimpleBinding(); sb.setDocument(this); sb.destinationPropertyName = text; sb.sourceID = applicationModel; sb.eventName = labelTextChanged; sb.sourcePropertyName = labelText; lbl.addBead(sb); lbl.initSkin(); var btn:TextButton = new TextButton(); addChild(btn); btn.initModel(); btn.text = OK; btn.x = 100; btn.y = 75; btn.addEventListener(click, clickHandler); btn.initSkin(); } public var lbl:Label; private function clickHandler(event:Event):void { dispatchEvent(new Event(buttonClicked)); } } } On 1/28/13 3:41 PM, Alex Harui aha...@adobe.com wrote: OK, I'll put together the AS version of the app. On 1/28/13 3:35 PM, Om bigosma...@gmail.com wrote: On Sun, Jan 27, 2013 at 11:20 PM, Alex Harui aha...@adobe.com wrote: On 1/27/13 10:50 PM, Om bigosma...@gmail.com wrote: But they dont seem to match up. Can you please respond with how the mxml would look when redone as a pure actionscript file? There are two possible answers to this question. One is for the question: what would the generated AS for the MXML file look like? It would look somewhat like the FlexJSTest.as that you found, but it is a bit different because when I finally got the compiler working it was easier to change some of the 'generated' code a bit. If you are really interested, I will try to hand-code it. This would be good. I played my hand around hand-coding based on this wiki note [1] But I would rather see your version. I'm not sure why you want to be hand-coding AS versions of MXML files. The other answer is for the question: How would you write this app in ActionScript? If I were to do it, it would not use the data array at all, it would call new Button and new Label and set properties and add event handlers. -- I am curious how this would work behind the scenes. But I am not in a hurry to look at the implementation details. A couple other questions while I have your attention: Will the FlexJSTest_again app compile with the current mxmlc? I saw your note in the wiki that says that it wont. Is there any way to make it work? The status page supercedes the original wiki page. FalconJS converts FlexJSTest.mxml to FlexJSTest.js. Falcon (assuming you set the mxml.children-as-data flag) will convert FlexJSTest.mxml to a running SWF. I have hooked up the falcon compiler to my flash builder (4.6) as an external run tool. The app compiles fine, but the IDE keeps showing errors.
[jira] [Commented] (FLEX-33367) flash.display.Loader intermitently causing children of loaded swf to loose type
[ https://issues.apache.org/jira/browse/FLEX-33367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565545#comment-13565545 ] Alex Harui commented on FLEX-33367: --- Adobe Flash Player bugs should be reported at bugbase.adobe.com. flash.display.Loader intermitently causing children of loaded swf to loose type --- Key: FLEX-33367 URL: https://issues.apache.org/jira/browse/FLEX-33367 Project: Apache Flex Issue Type: Bug Components: .Unspecified - Framework Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Seen on windows, mac and linux, various OS. Reporter: Tim Leslie Labels: loader Have a look at this stack overflow for a complete explaination and instruction on how to reproduce: http://stackoverflow.com/questions/14464898/flash-display-loader-intermitently-causing-children-of-loaded-swf-to-loose-type When two movieclips are loaded into an application using a flash.display.Loader and Event.COMPLETE is dispatched from both loaders on different frames, some instances in the first movieclip to be loaded loose their type when the second movieclip becomes available. For example, a recursive search for all decendents of type MC_Circle fails when normally it works. I have been recomended to report this issue by users of Stack Overflow who were able to reproduce it. I'm not sure of the full list of affected SDKs or Flash Player versions but I have been using 4.6. I have only tried hosting the swfs to be loaded on linux machine though the problem is reproducing with the loader swf on various OS. It's possible the problem only occurs when loading over a network. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: A code name for Apache Flex 5?
I'm sorry, but what is 'we removed the Flash dependency' supposed to mean? Is Flex becoming a HTML5 framework? Pardon my ignorance but I haven't been following the Flex JS discussions at all, so a quick heads up would be nice. Frank
Re: Should the compiler also fix up the HTML wrapper?
I agree that building everything in one command should be the goal. I do not think that HTML should be part of the compiler. Isn't there a way to wrap both the compile step and the HTML generation into one script, like I did in ant with the publisher, but maybe in an extended version of MXMLC? EdB On Tue, Jan 29, 2013 at 6:58 PM, Alex Harui aha...@adobe.com wrote: Any objections to adding a feature to Falcon/FalconJS/FalconJX to take additional arguments and fix up the HTML wrapper (or –app.xml for AIR)? I know compilers really should just compile, but the compiler knows much of the information that needs to be substituted into those files. For Falcon, I would add an option like –html.template=path to html template and –air.template=path to –app.xml template FalconJS/FalconJX would also support –js.source-path=path to more JS source to point to the framework (and goog if we use that) files. Thoughts? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: To support like ?
We support As3Xls and Alive PDF(Pure PDF coming soon) in Flash4j. It s possible. 2013/1/29 Jarosław Szczepankiewicz jszczepankiew...@gmail.com Hi, those requirements are always better supported on the server side. Imagine the actionscript library size for Excel full PDF support, apart from the library size it is almost always required to print / export full content of the table and not the current page, 2013/1/29 Patel Amit amitpowerpe...@gmail.com: Hi . It would be better if someone can implement the custom advanced datagridusing built in support for the Export To CSV , Export To Excel , Export to PDF. Regards Ap
Re: ASJS question - MXML vs. AS
On Jan 29, 2013 9:16 AM, Alex Harui aha...@adobe.com wrote: Not really, mostly just to see what happens if you use widgets that are not based on UIBase. As of right now, buttons are based on SimpleButton to save writing a bunch of code and are not a UIBase, but yesterday I started leaning towards making an IUIBase and making Button implement that. Feel free to make that change if it is getting in your way. I was thinking of an IUIBase myself. Will go ahead with that idea now. Thanks, Om On 1/29/13 12:49 AM, Om bigosma...@gmail.com wrote: Any particular reason the TextButton instance is displayed using this.addChild(button) instead of a button.addToParent(this) ? On Mon, Jan 28, 2013 at 11:52 PM, Om bigosma...@gmail.com wrote: That worked. Thanks! Om On Mon, Jan 28, 2013 at 6:22 PM, Alex Harui aha...@adobe.com wrote: And you will need to update MXMLDataInterpreter.as from SVN. On 1/28/13 5:21 PM, Alex Harui aha...@adobe.com wrote: OK, here it is: FlexJSTest.as: package { import controllers.MyController; import flash.display.Sprite; import flash.text.TextField; import models.MyModel; import org.apache.flex.core.Application; public class FlexJSTest extends Application { public function FlexJSTest() { valuesImpl = new MySimpleValuesImpl(); model = new MyModel(); model.labelText = Hello World!; initialView = new MyInitialView(); controller = new MyController(this); } private var controller:MyController; } } MyInitialView.as: package { import flash.events.Event; import org.apache.flex.binding.SimpleBinding; import org.apache.flex.core.ViewBase; import org.apache.flex.html.staticControls.Button; import org.apache.flex.html.staticControls.Label; import org.apache.flex.html.staticControls.TextButton; public class MyInitialView extends ViewBase { public function MyInitialView() { super(); } override public function initUI(model:Object):void { super.initUI(model); lbl = new Label(); lbl.addToParent(this); lbl.initModel(); lbl.x = 100; lbl.y = 25; var sb:SimpleBinding = new SimpleBinding(); sb.setDocument(this); sb.destinationPropertyName = text; sb.sourceID = applicationModel; sb.eventName = labelTextChanged; sb.sourcePropertyName = labelText; lbl.addBead(sb); lbl.initSkin(); var btn:TextButton = new TextButton(); addChild(btn); btn.initModel(); btn.text = OK; btn.x = 100; btn.y = 75; btn.addEventListener(click, clickHandler); btn.initSkin(); } public var lbl:Label; private function clickHandler(event:Event):void { dispatchEvent(new Event(buttonClicked)); } } } On 1/28/13 3:41 PM, Alex Harui aha...@adobe.com wrote: OK, I'll put together the AS version of the app. On 1/28/13 3:35 PM, Om bigosma...@gmail.com wrote: On Sun, Jan 27, 2013 at 11:20 PM, Alex Harui aha...@adobe.com wrote: On 1/27/13 10:50 PM, Om bigosma...@gmail.com wrote: But they dont seem to match up. Can you please respond with how the mxml would look when redone as a pure actionscript file? There are two possible answers to this question. One is for the question: what would the generated AS for the MXML file look like? It would look somewhat like the FlexJSTest.as that you found, but it is a bit different because when I finally got the compiler working it was easier to change some of the 'generated' code a bit. If you are really interested, I will try to hand-code it. This would be good. I played my hand around hand-coding based on this wiki note [1] But I would rather see your version. I'm not sure why you want to be hand-coding AS versions of MXML files. The other answer is for the question: How would you write this app in ActionScript? If I were to do it, it would not use the data array at all, it would call new Button and new Label and set properties and add event handlers. -- I am curious how this would work behind the scenes. But I am not in a hurry to look at the implementation details. A couple other questions while I have your attention: Will the FlexJSTest_again app compile with the current mxmlc? I saw your note in the wiki that says that it wont. Is there any way to make it work? The status page supercedes the original wiki page. FalconJS converts
Re: Should the compiler also fix up the HTML wrapper?
On 1/29/13 10:20 AM, Michael Schmalle apa...@teotigraphix.com wrote: If you view a discussion started by Roland and commented on by myself, you will see that configuration is what we are after and FLEXC compiler will answer this question. Yeah, I know... head in the clouds, but this is the EXACT reason we are going to do what we were talking about with a modular compiler. It's ridiculous to even ask this question and then go implement it in 3 different compilers. I was unable to follow that thread. I don't think we have three compilers right now. MXMLC and COMPC are pretty small front-ends to a common set of classes and have their own configuration options. What isn't modular about that? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [ASJS] debugging output JS?
On Tue, Jan 29, 2013 at 7:52 PM, Erik de Bruin e...@ixsoftware.nl wrote: It seems you needed to make changes to VanillaSDK to make it work with Jangaroo. What alternative for the 'goog' UI framework will you be using on the AMD side? The only change to VanillaSDK is that I removed the dependency on the goog library. I didn't need to make that change to make it work with Jangaroo, it just didn't seem to make much sense to remove goog for the class setup, but keep it just to create a DOM element and attach an event listener (VanillaJS can do that quite well). And since your prototype didn't work in IE8 (mode) anyway, nothing was lost. As discussed in the thread [ASJS] Integration with existing JS libraries and components, the AMD solution integrates well with *any* JavaScript library. So if you wanted to use AMD plus goog UI, that would be possible, too. The other thread contains some details on what possibilities you have to shim an existing library that does not natively support AMD, and discusses proposals for a [Native] annotation. I also mentioned on that thread that we (= CoreMedia) use Ext JS as the UI component library (and DOM abstraction). It is possible to instantiate Ext JS components (or any other Ext JS objects) from ActionScript and MXML, as well as to subclass existing components. You virtually do not notice that Ext's components are implemented in JavaScript, not in ActionScript. One thing I asked myself when I looked at your VanillaSDK code is why you checked in the JavaScript code of the framework classes (everything but Example.as). Aren't they written in AS3 and cross-compiled, too? At least that's how I thought you'd do it, even if this code is never compiled to run in the FlashPlayer or AIR. Take into account that you are intending to implement a complete UI component framework, you wouldn't want to do that in JavaScript directly, would you? Greetings -Frank-
Re: [ASJS] debugging output JS?
One thing I asked myself when I looked at your VanillaSDK code is why you checked in the JavaScript code of the framework classes (everything but Example.as). Aren't they written in AS3 and cross-compiled, too? At least that's how I thought you'd do it, even if this code is never compiled to run in the FlashPlayer or AIR. Take into account that you are intending to implement a complete UI component framework, you wouldn't want to do that in JavaScript directly, would you? No, I don't. I will use the Closure Library on the JS side. I am not even going to implement a framework on the AS side. I use the Flex SDK. The VanillaSDK JS framework is just a very thin wrapper around these frameworks. It have the same API on the JS side as on the AS side: the only thing I need to compile to JS is the project AS and MXML. All development takes place on the AS/MXML side (e.g. in Flash Builder), no need for current Flex developers to learn anything new. JS is a release format, for when your project is ready to be deployed. The idea is: low learning curve, easy acceptance, high impact, good marketability. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [ASJS] debugging output JS?
On Tue, Jan 29, 2013 at 3:13 AM, Daniel Wasilewski devudes...@gmail.comwrote: I do understand that Frank might have personal interest in getting Flex close to Jangaroo for compatibility purposes, or maybe I am wrong and this just came from experience building that very tool. Dan, to put that right, my personal interest, as you call it, is actually to open up the possibility for Jangaroo developers to one day migrate to Apache Flex without too much headaches, and, that is the point in bringing in my experience, without the feeling that this is a step backwards in any way. If you accept that developers will be using Apache Flex to develop primarily or solely for JS/HTML5, you can imagine that once you got used to source level debugging in the browser, you wouldn't want to miss it when using the successor tool. -Frank-
[jira] [Commented] (FLEX-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565735#comment-13565735 ] OmPrakash Muppirala commented on FLEX-33371: Erik, I dont have my USB cable with me, so I am not able to test your project. Have you tried listening to Event.EXITING and Event.DEACTIVATE events thrown by NativeApplication.nativeApplication to do your cleanup? That way, you can bypass the spurious viewDeactivate events by not listening to them. The docs [1] seems to suggest that this is the correct way. I apologize if this is not related to your problem. I will get a chance to look at this later tonight if you havent solved your issue by then. Thanks, Om [1] http://help.adobe.com/en_US/flex/mobileapps/WSa122979b4619725672e48c412a3e152164-8000.html On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events Key: FLEX-33371 URL: https://issues.apache.org/jira/browse/FLEX-33371 Project: Apache Flex Issue Type: Bug Components: Mobile: MobileApplication Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Samsung Galaxy Express and Galaxy S III Android Phones, FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as deployed release builds, iPhone and iPad, but the problem doesn't exist on iOS devices, only Android Reporter: Erik Thomas Priority: Critical Fix For: Adobe Flex SDK 4.6 (Release) Attachments: AndroidDeactivateOnOrientationChangeDefect.zip Orientation changes on Android devices always fire the following events in this order: ViewNavigatorEvent.VIEW_DEACTIVATE Event.DEACTIVATE StageOrientationEvent.ORIENTATION_CHANGE The first two events are a defect. They must not fire simply because the user changed the orientation of the phone. The result of this defect is that we cannot do two very important things: 1. Use view state changes to hide/show layouts, using includeIn property on containers and components. On Android, components that are not included for a given state are destroyed yet they have state we want to maintain which is why we don't change Views. 2. We cannot know when the user navigates away from our application, for example to press the Home key. We have certain cleanup we must do in our complex connected app that streams FMS data, etc., and cannot keep sockets open for hours or days. On iOS, this is not a problem. Only Android has this bug and it's blocking us from releasing our product on Android. iOS does not have this defect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Performance expectations for Flex JS
How would AS3 and JS versions of a typical app perform? If the AS3 version is running 100% at 30fps, could the JS version keep up? Or do you expect the JS version to out-perform? I guess its too early to answer these questions with any degree of certainty, but what are the expectations? I think the current state of JS VMs will ensure at least comparable performance. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
[jira] [Commented] (FLEX-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565789#comment-13565789 ] Erik Thomas commented on FLEX-33371: Hi OmPrakash: The NativeApplication DEACTIVATE event also fires on orientation change events. Event.DEACTIVATE event was fired! NativeApplication.Event.DEACTIVATE event was fired! StageOrientationEvent.ORIENTATION_CHANGE event was fired! Also, NativeApplication.EXITING never fires when the user presses the Home button or switches applications. This event seems useless and never fires for any reason. Thanks for taking a look! BTW, I plan to look into joining as a contributor after my current contract is finished, but I don't have time to do that now or I might look into this issue. Thanks! Erik Erik J. Thomas CEO | Principal Developer E. J. Thomas Associates, LLC 266 Peakview Rd, Boulder, CO 80302 303-440-8384 (office) | 303-304-1466 (mobile) ejtho...@ejthomas.com CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events Key: FLEX-33371 URL: https://issues.apache.org/jira/browse/FLEX-33371 Project: Apache Flex Issue Type: Bug Components: Mobile: MobileApplication Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Samsung Galaxy Express and Galaxy S III Android Phones, FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as deployed release builds, iPhone and iPad, but the problem doesn't exist on iOS devices, only Android Reporter: Erik Thomas Priority: Critical Fix For: Adobe Flex SDK 4.6 (Release) Attachments: AndroidDeactivateOnOrientationChangeDefect.zip Orientation changes on Android devices always fire the following events in this order: ViewNavigatorEvent.VIEW_DEACTIVATE Event.DEACTIVATE StageOrientationEvent.ORIENTATION_CHANGE The first two events are a defect. They must not fire simply because the user changed the orientation of the phone. The result of this defect is that we cannot do two very important things: 1. Use view state changes to hide/show layouts, using includeIn property on containers and components. On Android, components that are not included for a given state are destroyed yet they have state we want to maintain which is why we don't change Views. 2. We cannot know when the user navigates away from our application, for example to press the Home key. We have certain cleanup we must do in our complex connected app that streams FMS data, etc., and cannot keep sockets open for hours or days. On iOS, this is not a problem. Only Android has this bug and it's blocking us from releasing our product on Android. iOS does not have this defect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: release changelog
On 1/29/13 10:25 AM, Rick Winscot rick.wins...@gmail.com wrote: Are releases accompanied by a changelog? I don't think we listed every change, but key changes are noted in the RELEASE_NOTES file. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[jira] [Commented] (FLEX-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565840#comment-13565840 ] OmPrakash Muppirala commented on FLEX-33371: This particular comment on the bugbase could be a possible workaround: For workaround this issue, you can put uses-sdk android:targetSdkVersion=11/ in manifest inside of the app.xml to avoid invoke Event trigger by surface Change. On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events Key: FLEX-33371 URL: https://issues.apache.org/jira/browse/FLEX-33371 Project: Apache Flex Issue Type: Bug Components: Mobile: MobileApplication Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Samsung Galaxy Express and Galaxy S III Android Phones, FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as deployed release builds, iPhone and iPad, but the problem doesn't exist on iOS devices, only Android Reporter: Erik Thomas Priority: Critical Fix For: Adobe Flex SDK 4.6 (Release) Attachments: AndroidDeactivateOnOrientationChangeDefect.zip Orientation changes on Android devices always fire the following events in this order: ViewNavigatorEvent.VIEW_DEACTIVATE Event.DEACTIVATE StageOrientationEvent.ORIENTATION_CHANGE The first two events are a defect. They must not fire simply because the user changed the orientation of the phone. The result of this defect is that we cannot do two very important things: 1. Use view state changes to hide/show layouts, using includeIn property on containers and components. On Android, components that are not included for a given state are destroyed yet they have state we want to maintain which is why we don't change Views. 2. We cannot know when the user navigates away from our application, for example to press the Home key. We have certain cleanup we must do in our complex connected app that streams FMS data, etc., and cannot keep sockets open for hours or days. On iOS, this is not a problem. Only Android has this bug and it's blocking us from releasing our product on Android. iOS does not have this defect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565919#comment-13565919 ] Erik Thomas commented on FLEX-33371: Awesome, OmPrakash! This did the trick! I'm still getting DEACTIVATE when leaving the app as we needed, and we no longer get any of these bogus events fired for orientation changes. I searched a lot and never saw this one. Sorry to waste your time. Hope this could get fixed anyway though. Cheers, Erik Erik J. Thomas CEO | Principal Developer E. J. Thomas Associates, LLC 266 Peakview Rd, Boulder, CO 80302 303-440-8384 (office) | 303-304-1466 (mobile) ejtho...@ejthomas.com CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events Key: FLEX-33371 URL: https://issues.apache.org/jira/browse/FLEX-33371 Project: Apache Flex Issue Type: Bug Components: Mobile: MobileApplication Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Samsung Galaxy Express and Galaxy S III Android Phones, FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as deployed release builds, iPhone and iPad, but the problem doesn't exist on iOS devices, only Android Reporter: Erik Thomas Priority: Critical Fix For: Adobe Flex SDK 4.6 (Release) Attachments: AndroidDeactivateOnOrientationChangeDefect.zip Orientation changes on Android devices always fire the following events in this order: ViewNavigatorEvent.VIEW_DEACTIVATE Event.DEACTIVATE StageOrientationEvent.ORIENTATION_CHANGE The first two events are a defect. They must not fire simply because the user changed the orientation of the phone. The result of this defect is that we cannot do two very important things: 1. Use view state changes to hide/show layouts, using includeIn property on containers and components. On Android, components that are not included for a given state are destroyed yet they have state we want to maintain which is why we don't change Views. 2. We cannot know when the user navigates away from our application, for example to press the Home key. We have certain cleanup we must do in our complex connected app that streams FMS data, etc., and cannot keep sockets open for hours or days. On iOS, this is not a problem. Only Android has this bug and it's blocking us from releasing our product on Android. iOS does not have this defect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565922#comment-13565922 ] Erik Thomas commented on FLEX-33371: Thanks Justin. OmPrakash found an obscure mention of using uses-sdk android:targetSdkVersion=11 manifest element and it works perfectly. I still think this is a bug, probably in the AIR runtime, but this manifest entry solved my problems perfectly. Erik Erik J. Thomas CEO | Principal Developer E. J. Thomas Associates, LLC 266 Peakview Rd, Boulder, CO 80302 303-440-8384 (office) | 303-304-1466 (mobile) ejtho...@ejthomas.com CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events Key: FLEX-33371 URL: https://issues.apache.org/jira/browse/FLEX-33371 Project: Apache Flex Issue Type: Bug Components: Mobile: MobileApplication Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Samsung Galaxy Express and Galaxy S III Android Phones, FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as deployed release builds, iPhone and iPad, but the problem doesn't exist on iOS devices, only Android Reporter: Erik Thomas Priority: Critical Fix For: Adobe Flex SDK 4.6 (Release) Attachments: AndroidDeactivateOnOrientationChangeDefect.zip Orientation changes on Android devices always fire the following events in this order: ViewNavigatorEvent.VIEW_DEACTIVATE Event.DEACTIVATE StageOrientationEvent.ORIENTATION_CHANGE The first two events are a defect. They must not fire simply because the user changed the orientation of the phone. The result of this defect is that we cannot do two very important things: 1. Use view state changes to hide/show layouts, using includeIn property on containers and components. On Android, components that are not included for a given state are destroyed yet they have state we want to maintain which is why we don't change Views. 2. We cannot know when the user navigates away from our application, for example to press the Home key. We have certain cleanup we must do in our complex connected app that streams FMS data, etc., and cannot keep sockets open for hours or days. On iOS, this is not a problem. Only Android has this bug and it's blocking us from releasing our product on Android. iOS does not have this defect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33371) On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events
[ https://issues.apache.org/jira/browse/FLEX-33371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565968#comment-13565968 ] Erik Thomas commented on FLEX-33371: Hi OmPrakash: This is almost a perfect workaround. Unfortunately, listening for the NativeApplication.DEACTIVATE event to unload is not reliable. It seems to fire randomly and not related to orientation changes. I've only tried a couple times, but as I work through my app workflows, everything is working great on Android now, just like iOS, but something is triggering the DEACTIVATE event during a workflow and the app is unloading because I'm calling exit(). So I'm not out of the woods yet, but this is a huge improvement. Erik Erik J. Thomas CEO | Principal Developer E. J. Thomas Associates, LLC 266 Peakview Rd, Boulder, CO 80302 303-440-8384 (office) | 303-304-1466 (mobile) ejtho...@ejthomas.com CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. On Android, changing orientation fires Event.DEACTIVATE and FlexEvent.VIEW_DEACTIVATE events Key: FLEX-33371 URL: https://issues.apache.org/jira/browse/FLEX-33371 Project: Apache Flex Issue Type: Bug Components: Mobile: MobileApplication Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Samsung Galaxy Express and Galaxy S III Android Phones, FlashBuilder 4.7 Premium on Windows 7, debugging through USB as well as deployed release builds, iPhone and iPad, but the problem doesn't exist on iOS devices, only Android Reporter: Erik Thomas Priority: Critical Fix For: Adobe Flex SDK 4.6 (Release) Attachments: AndroidDeactivateOnOrientationChangeDefect.zip Orientation changes on Android devices always fire the following events in this order: ViewNavigatorEvent.VIEW_DEACTIVATE Event.DEACTIVATE StageOrientationEvent.ORIENTATION_CHANGE The first two events are a defect. They must not fire simply because the user changed the orientation of the phone. The result of this defect is that we cannot do two very important things: 1. Use view state changes to hide/show layouts, using includeIn property on containers and components. On Android, components that are not included for a given state are destroyed yet they have state we want to maintain which is why we don't change Views. 2. We cannot know when the user navigates away from our application, for example to press the Home key. We have certain cleanup we must do in our complex connected app that streams FMS data, etc., and cannot keep sockets open for hours or days. On iOS, this is not a problem. Only Android has this bug and it's blocking us from releasing our product on Android. iOS does not have this defect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Flash Platform Whitepaper
Hi Folks, Adobe published an update to the Flash Platform Whitepaper today. Most of it doesn¹t directly affect us, but one item does: Adobe has decided to focus its future runtime development on top of the existing architecture, as opposed to a completely new architecture (Flash ³Next²) and language (ActionScript ³Next²). So Apache Flex doesn¹t have to worry about porting to a new VM/language. That should save us lots of time and distraction. Go Apache Flex! -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
RE: Flash Player 11.5 - Debug trace in release player
I just have to get my users to update their flash player ... Yes well, that's the trick isn't it. I'm still trying to get some of mine onto 11.x -Ian
Re: Flash Platform Whitepaper
Thats the way i'm reading it - dumb but predictable On 30/01/2013 00:39, Mark Fuqua wrote: In reading over the latest version, it seems like Adobe is saying no Air for Windows 8 tablets/phones...is that a correct reading? Seems like a dumb move for both Microsoft and Adobe. Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, January 29, 2013 6:42 PM To: dev@flex.apache.org Subject: Flash Platform Whitepaper Hi Folks, Adobe published an update to the Flash Platform Whitepaper today. Most of it doesn¹t directly affect us, but one item does: Adobe has decided to focus its future runtime development on top of the existing architecture, as opposed to a completely new architecture (Flash ³Next²) and language (ActionScript ³Next²). So Apache Flex doesn¹t have to worry about porting to a new VM/language. That should save us lots of time and distraction. Go Apache Flex! -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Flash Platform Whitepaper
On 1/29/13 4:33 PM, Igor Costa igorco...@gmail.com wrote: Hi there Alex In some points Alex we will be affected, since if we still want to be relay only on flash player. We have to move on for Flex output for N platforms and stop depending only on one vendor. Is that what you mention or no, I'm wrong? IMO, the only thing that affects us is the fact that we don't have to worry about a new VM and language. None of the other changes published today affects the Apache Flex Project's exploration into Flex output for other platforms. There's definitely lots of exploring going on. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Flash Platform Whitepaper
That part of text is a bit fuzzy, but it doesn't sound positive at all about AIR on Win8 mobile. Also, no mention of Blackberry OS. Tomislav On 30.1.2013. 1:39, Mark Fuqua wrote: In reading over the latest version, it seems like Adobe is saying no Air for Windows 8 tablets/phones...is that a correct reading? Seems like a dumb move for both Microsoft and Adobe. Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, January 29, 2013 6:42 PM To: dev@flex.apache.org Subject: Flash Platform Whitepaper Hi Folks, Adobe published an update to the Flash Platform Whitepaper today. Most of it doesn¹t directly affect us, but one item does: Adobe has decided to focus its future runtime development on top of the existing architecture, as opposed to a completely new architecture (Flash ³Next²) and language (ActionScript ³Next²). So Apache Flex doesn¹t have to worry about porting to a new VM/language. That should save us lots of time and distraction. Go Apache Flex! -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[Website] New website going live
Hey everybody! We got final permission from a few different groups at Apache to make the website live. If you have any pending commits to the site/ directory in SVN, please make sure those go in soon as things are about to be all moved around there. After the website goes live, I'll put in the download tracking code. -Nick
[jira] [Updated] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Hilbert updated FLEX-33372: -- Component/s: Spark: RichEditableText Windows 8 on-screen touch keyboard not displaying - Key: FLEX-33372 URL: https://issues.apache.org/jira/browse/FLEX-33372 Project: Apache Flex Issue Type: Bug Components: Spark: RichEditableText, Spark: TextArea, Spark: TextInput Affects Versions: Adobe Flex SDK 4.6 (Release) Environment: Windows 8 Metro Internet Explorer (IE) 10.0.1 Flash Player 11,3,378,5 Reporter: Stepan Hilbert On-screen touch keyboard is not being displayed for spark text input components. It should get displayed just as it gets displayed for TextField based components. Additionally, it would be desirable to control the keyboard using: - needsSoftKeyboard property - requestSoftKeyboard() function These currently have no effect. Steps to reproduce: 1. Create a Flex application that features s:TextInput and mx:TextInput 2. Open this application in the Metro Internet Explorer on a touch-enabled Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) 3. Tap the mx:TextInput - on-screen keyboard shows 4. Tap the s:TextInput - on-screen keyboard doesn't show Note: This bug has been discussed on the web (i.e. here: http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepan Hilbert updated FLEX-33372: -- Affects Version/s: Apache Flex 4.9.0 Windows 8 on-screen touch keyboard not displaying - Key: FLEX-33372 URL: https://issues.apache.org/jira/browse/FLEX-33372 Project: Apache Flex Issue Type: Bug Components: Spark: RichEditableText, Spark: TextArea, Spark: TextInput Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 Environment: Windows 8 Metro Internet Explorer (IE) 10.0.1 Flash Player 11,3,378,5 Reporter: Stepan Hilbert On-screen touch keyboard is not being displayed for spark text input components. It should get displayed just as it gets displayed for TextField based components. Additionally, it would be desirable to control the keyboard using: - needsSoftKeyboard property - requestSoftKeyboard() function These currently have no effect. Steps to reproduce: 1. Create a Flex application that features s:TextInput and mx:TextInput 2. Open this application in the Metro Internet Explorer on a touch-enabled Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) 3. Tap the mx:TextInput - on-screen keyboard shows 4. Tap the s:TextInput - on-screen keyboard doesn't show Note: This bug has been discussed on the web (i.e. here: http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Mustella News
I'm kinda split on this one. On one hand, I know most flex users won't need the tests... On the other hand, anybody interested in contributing bug fixes, new components, etc. should easily be able to run the test suite against them. Maybe we include another variation of the source downloads to have a tests package? It would be great if Mustella was as easy to run as downloading the ZIP, making a few env.properties changes and the tests run.. Mustella is 100x easier to run now than it was even 6 months ago when we first got them, but making the barrier to entry even smaller would rock. -Nick On Tue, Jan 29, 2013 at 6:36 PM, Carol Frampton cfram...@adobe.com wrote: On Jan 28, 2013, at 7:14 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Also, I believe that we decided we dont want to include Mustella in an Apache Flex release. Do you think we should? IMO no need to include it as It's probably not a huge amount of use to users of the SDK only to people who are actively working on changing/fixed the SDK. Agree. Justin PS Be nice if moved into it own project in SVN as well. I don't disagree but we might have to add some provision for flex versions if there is only one directory. Carol
Re: On vacation Feb 4 - Mar 1
Have fun! On Mon, Jan 28, 2013 at 1:00 PM, Gordon Smith gosm...@adobe.com wrote: I'll be working this week and then on vacation for four weeks. I won't be reading email during vacation. I'll be back at work on March 4. - Gordon
Re: Mustella News
On 1/29/13 7:10 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: I'm kinda split on this one. On one hand, I know most flex users won't need the tests... On the other hand, anybody interested in contributing bug fixes, new components, etc. should easily be able to run the test suite against them. Maybe we include another variation of the source downloads to have a tests package? It would be great if Mustella was as easy to run as downloading the ZIP, making a few env.properties changes and the tests run.. I don't disagree, but it is worth the time investment at this point? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Mustella News
I think the question then begs -- do we expect people (non-committers) to run bug fixes / new features against Mustella, or do we only do it when we commit them to SVN, or do we only run Mustella against the source tree when we package up a release? I think that will have the most baring if it will be worth making a release that includes testing suite -Nick On Tue, Jan 29, 2013 at 11:04 PM, Alex Harui aha...@adobe.com wrote: On 1/29/13 7:10 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: I'm kinda split on this one. On one hand, I know most flex users won't need the tests... On the other hand, anybody interested in contributing bug fixes, new components, etc. should easily be able to run the test suite against them. Maybe we include another variation of the source downloads to have a tests package? It would be great if Mustella was as easy to run as downloading the ZIP, making a few env.properties changes and the tests run.. I don't disagree, but it is worth the time investment at this point? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Website] New website going live
The new website is sitting on staging now. I'm going to push it to production at Noon EDT tomorrow (~12 hours from now) unless somebody finds a compelling reason why we shouldn't. http://flex.staging.apache.org/ -Nick On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski nicho...@spoon.aswrote: Hey everybody! We got final permission from a few different groups at Apache to make the website live. If you have any pending commits to the site/ directory in SVN, please make sure those go in soon as things are about to be all moved around there. After the website goes live, I'll put in the download tracking code. -Nick
RE: [Website] New website going live
One comment, and I apologize if this has been discussed already, but I would make sure that we have permission to use the photos on the page. mike chambers m...@adobe.com -Original Message- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Tuesday, January 29, 2013 8:29 PM To: dev@flex.apache.org Subject: Re: [Website] New website going live The new website is sitting on staging now. I'm going to push it to production at Noon EDT tomorrow (~12 hours from now) unless somebody finds a compelling reason why we shouldn't. http://flex.staging.apache.org/ -Nick On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski nicho...@spoon.aswrote: Hey everybody! We got final permission from a few different groups at Apache to make the website live. If you have any pending commits to the site/ directory in SVN, please make sure those go in soon as things are about to be all moved around there. After the website goes live, I'll put in the download tracking code. -Nick
RE: [Website] New website going live
Which page? I think the only content that want generated by us directly is the links to the ADC/videos. On Jan 29, 2013 11:34 PM, Mike Chambers mcham...@adobe.com wrote: One comment, and I apologize if this has been discussed already, but I would make sure that we have permission to use the photos on the page. mike chambers m...@adobe.com -Original Message- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Tuesday, January 29, 2013 8:29 PM To: dev@flex.apache.org Subject: Re: [Website] New website going live The new website is sitting on staging now. I'm going to push it to production at Noon EDT tomorrow (~12 hours from now) unless somebody finds a compelling reason why we shouldn't. http://flex.staging.apache.org/ -Nick On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Hey everybody! We got final permission from a few different groups at Apache to make the website live. If you have any pending commits to the site/ directory in SVN, please make sure those go in soon as things are about to be all moved around there. After the website goes live, I'll put in the download tracking code. -Nick
RE: [Website] New website going live
Actually, I see what is going on. I noticed a picture of Ryan Stewart on the front, which seems to be automatically pulled in from the article it is linking to. Disregard my previous email. Looks great btw... mike chambers -Original Message- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Tuesday, January 29, 2013 8:37 PM To: dev@flex.apache.org Subject: RE: [Website] New website going live Which page? I think the only content that want generated by us directly is the links to the ADC/videos. On Jan 29, 2013 11:34 PM, Mike Chambers mcham...@adobe.com wrote: One comment, and I apologize if this has been discussed already, but I would make sure that we have permission to use the photos on the page. mike chambers m...@adobe.com -Original Message- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Tuesday, January 29, 2013 8:29 PM To: dev@flex.apache.org Subject: Re: [Website] New website going live The new website is sitting on staging now. I'm going to push it to production at Noon EDT tomorrow (~12 hours from now) unless somebody finds a compelling reason why we shouldn't. http://flex.staging.apache.org/ -Nick On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Hey everybody! We got final permission from a few different groups at Apache to make the website live. If you have any pending commits to the site/ directory in SVN, please make sure those go in soon as things are about to be all moved around there. After the website goes live, I'll put in the download tracking code. -Nick
[jira] [Commented] (FLEX-33372) Windows 8 on-screen touch keyboard not displaying
[ https://issues.apache.org/jira/browse/FLEX-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566166#comment-13566166 ] Stepan Hilbert commented on FLEX-33372: --- Hi Alex, Thanks for looking into this. I cannot try 11.5 or 11.6 beta as they refuse to install on Windows 8 (I think they're not compatible). I have tried 11,3,378,5 debugger - same behavior as the non-debug version. Windows 8 on-screen touch keyboard not displaying - Key: FLEX-33372 URL: https://issues.apache.org/jira/browse/FLEX-33372 Project: Apache Flex Issue Type: Bug Components: Spark: RichEditableText, Spark: TextArea, Spark: TextInput Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.9.0 Environment: Windows 8 Metro Internet Explorer (IE) 10.0.1 Flash Player 11,3,378,5 Reporter: Stepan Hilbert On-screen touch keyboard is not being displayed for spark RichEditableText based text input components. It does get displayed when displayAsPassword property is set to true. It does get displayed for TextField based components. Additionally, it would be desirable to control the keyboard using: - needsSoftKeyboard property - requestSoftKeyboard() function These currently have no effect. Steps to reproduce: 1. Create a Flex application that features s:TextInput, s:TextInput with displayAsPassword=true and mx:TextInput mx:TextInput text=mx:TextInput / s:TextInput text=s:TextInput / s:TextInput text=s:TextInput password displayAsPassword=true / 2. Open this application in the Metro Internet Explorer on a touch-enabled Windows 8 PC/Tablet. You might need to edit the DebugDomain variable (see http://msdn.microsoft.com/en-au/library/ie/jj193557%28v=vs.85%29.aspx) 3. Tap the mx:TextInput - on-screen keyboard shows 4. Tap the s:TextInput with displayAsPassword=true - on-screen keyboard shows 5. Tap the s:TextInput - on-screen keyboard doesn't show Note: This bug has been discussed on the web (i.e. here: http://flexcoders.10928.n7.nabble.com/windows-8-store-app-onscreen-keyboard-invoking-td111950.html) but no resolution has been reached, so that is why I'm logging this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ASJS] VanillaSDK as part of the SDK
Something isn't clear to me. Are you proposing that the AS3 code for Flex contains 3 groups of components? (mx or it's equivilent, spark, and goog) Or are you proposing that there are 2 groups of AS3 components, mx and spark, and one set of JS components (goog) which have different levels of compatibility with the first 2 groups? brought to you by the letters A, V, and I and the number 47 On Tue, Jan 29, 2013 at 9:30 PM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, One of the goals behind the vanilla SDK is to create a JS compatible framework that closely resembles the Flex SDK. The idea is that the coding and workflow in the AS IDE (likely Flash Builder) closely matches working with Flex as we know it. This way ASJS has no learning curve at all: it's just another release build option. JS output that just works :-) In order to do accomplish this, I'm working on integrating the VanillaSDK into the SDK proper. Don't worry, it's all happening in my whiteboard for now. But I'd like your feedback on some of my ideas, while the implementation is still in it's early stages: 1) create a new namespace in the SDK: http://flex.apache.org/js/goog 2) add only the components to this namespace that are compatible with JS output 3) create JS compatible versions of spark (and other?) components, using composition 4) create JS versions of these components: the VanillaSDK This way hope to achieve the following: 1) isolate the new components from the rest of the SDK, to avoid confusion for developers 2) allow for incremental development, since only properly prepared components will be available 3) by using composition instead of inheritance we keep control over what we expose to the developer, allowing for API compatibility on the JS and AS side, while still use Flex components on the AS side There's (much) more to it, but for now I'd like to ask: does this make any sense, and if it does, how might we improve on this idea to make it work better? EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Flash Platform Whitepaper
I read the whole thing as Flash entering sunset mode. Basically, Adobe doesn't want to make their AIR package competitive, so they are throwing in the towel, while allowing Flash Player in the browser to coast to it's inevitable demise. That's my read anyway. Kevin N.
Re: Flash Platform Whitepaper
On 1/29/2013 8:14 PM, Tianzhen Lin wrote: I hope Adobe, with its new focus on gaming, would not repeat its misstep and make some waves into console market. The right play in my opinion would be to do exactly that - focus on gaming - then expand out to other types of apps like they did when Flash moved from animation, to video, to RIAs. They have a strong multi-platform app-store middleware product. But if you read closely, Adobe's narrative was never about a real focus on gaming, and was always more about leveraging their installed base, and desktop/laptop browser ubiquity. That failed when they couldn't sell premium features, and so they've cancelled the plans they had to advance Flash and AIR further, and have instead entered Flash into its end of life. It's really a shame they'll put stage3d and AGAL to sleep with Flash. Any hope they'll mix those APIs with a new language, and create a preplacement middleware product (I'm voting for GoLang as the core language!)? A new brand couldn't hurt at this point. Kevin N.
Re: [Website] New website going live
On 1/29/13 8:29 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: The new website is sitting on staging now. I'm going to push it to production at Noon EDT tomorrow (~12 hours from now) unless somebody finds a compelling reason why we shouldn't. http://flex.staging.apache.org/ I poked around for a few minutes and didn't see any obvious issues. Great job! -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Flash Platform Whitepaper
Read to me like they are working on making AS3 the new Javascript. Just saying. :) brought to you by the letters A, V, and I and the number 47 On Wed, Jan 30, 2013 at 7:56 AM, Kevin Newman capta...@unfocus.com wrote: I read the whole thing as Flash entering sunset mode. Basically, Adobe doesn't want to make their AIR package competitive, so they are throwing in the towel, while allowing Flash Player in the browser to coast to it's inevitable demise. That's my read anyway. Kevin N.
Re: Mustella News
The way I see it, when someone downloads the source package, it means that they will be messing around with the code. All the more reason to have a testing suite packaged with the source kit. I agree with Nick that we should lower the barrier for folks to fix bugs and run tests. The utilities like I worked on a while ago - OneClickMustella [1] will make it easy to run the whole test suite or just the ones relevant to the files that got modified. This could increase more drive by patches. The more patches someone contributes, the better are our chances to get new committers into the project. Thanks, Om [1] http://markmail.org/message/iehxp5cpl62yp7gw On Tue, Jan 29, 2013 at 8:23 PM, Alex Harui aha...@adobe.com wrote: On 1/29/13 8:17 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: I think the question then begs -- do we expect people (non-committers) to run bug fixes / new features against Mustella, or do we only do it when we commit them to SVN, or do we only run Mustella against the source tree when we package up a release? I think that will have the most baring if it will be worth making a release that includes testing suite I wouldn't expect non-committers to run mustella unless they have a desire to become a committer, in which case they should have the full SVN tree. Committers reviewing patches before submitting should definitely run mustella regardless if the patch author said they did nor not. We've made some utilities that select the fewest tests to run to ensure that nothing in mustella breaks. I would like to see PMC members run mustella before voting on a release candidate. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Website] New website going live
Looks great! Small thing: On the team page http://flex.staging.apache.org/about-people.html, the last three rows are 3/1/1 rather than two rows of 4/3. On Jan 30, 2013, at 4:22 AM, Nicholas Kwiatkowski wrote: Hey everybody! We got final permission from a few different groups at Apache to make the website live. If you have any pending commits to the site/ directory in SVN, please make sure those go in soon as things are about to be all moved around there. After the website goes live, I'll put in the download tracking code. -Nick
Re: [Website] New website going live
On Tue, Jan 29, 2013 at 8:29 PM, Nicholas Kwiatkowski nicho...@spoon.aswrote: The new website is sitting on staging now. I'm going to push it to production at Noon EDT tomorrow (~12 hours from now) unless somebody finds a compelling reason why we shouldn't. http://flex.staging.apache.org/ -Nick The installer badge on this page [1] is broken. I guess it is because of a crossdomain issue and we dont have a policy file. I wouldnt worry about it because it seems to be working fine here [2] When you make it go live, please sure you test this page first, though! Thanks, Om [1] http://flex.staging.apache.org/installer.html [2] http://flex.apache.org/v2/installer.html On Tue, Jan 29, 2013 at 9:22 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote: Hey everybody! We got final permission from a few different groups at Apache to make the website live. If you have any pending commits to the site/ directory in SVN, please make sure those go in soon as things are about to be all moved around there. After the website goes live, I'll put in the download tracking code. -Nick
Re: Mustella News
On 1/29/13 11:21 PM, Om bigosma...@gmail.com wrote: The way I see it, when someone downloads the source package, it means that they will be messing around with the code. All the more reason to have a testing suite packaged with the source kit. I agree with Nick that we should lower the barrier for folks to fix bugs and run tests. The utilities like I worked on a while ago - OneClickMustella [1] will make it easy to run the whole test suite or just the ones relevant to the files that got modified. This could increase more drive by patches. The more patches someone contributes, the better are our chances to get new committers into the project. Hey, if you guys believe in it, I certainly won't stop you from working on it. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui