Re: [FlexJS] Testing current API and bugs
Mike, That’s great that you can help out. Every little bit helps. On 5/14/15, 3:49 PM, Michael Schmalle teotigraphix...@gmail.com wrote: I will just ask this here but, how do you have your setup for testing the javascript compiler fixing? Say I find a bug, I know the problem is say in an emitter, right now I am building from the nightly. Is there a streamlined way that I don't have to build the compiler but say run the main class? Yes, I have Eclipse Debug Configs to recompile the app. Then I hit it in a browser and see what happens. Now thinking about it, it probably is a thing where I have to nail exactly what is wrong and make a test for it in falconjx and not even worry about the app, if I fix the bug then it's fixed. I'm still really trying to just figure out the framework, where the line is as/javascript where you had to write custom .js and where you draw the line of what .as file in asjs/src gets cross compiled. Well, when we first started out, I thought we’d write everything once in AS and once in JS. It was later that I realized with the right abstractions we could cross-compile a lot more of our framework code. So really, the line is drawn at the low-level where you are abstracting the differences. For example, by creating PlatformWiper, I can then write the Wipe class in as and cross-compile it. Honestly I don't know how long it's going to take me for the light bulb to turn on. Question: Say I had a goal of taking a mobile UI framework such as jQuery mobile and I wanted to wrap that for a ui extension. I know that I would have to create the api that mirror jQuery mobile, and then I would have to backasswards create .as Sprite components that would mirror the jQuery ones right? So what would be the steps and things I would have todo to get it to work? We already have a Jquery library. Jquery mobile may or may not be its own library or just be more components in the Jquery library. To wrap any existing JS framework, figure out what it’s OO API surface would look like and create JS wrappers if necessary. Then for the AS equivalent, try to re-use the components we have or write custom beads that fill in what is missing. That’s another benefit of beads: they hopefully allow more re-purposing of code as you mock up the AS version of the JS frameworks. -Alex
Re: [FlexJS] Testing current API and bugs
I will just ask this here but, how do you have your setup for testing the javascript compiler fixing? Say I find a bug, I know the problem is say in an emitter, right now I am building from the nightly. Is there a streamlined way that I don't have to build the compiler but say run the main class? Now thinking about it, it probably is a thing where I have to nail exactly what is wrong and make a test for it in falconjx and not even worry about the app, if I fix the bug then it's fixed. I'm still really trying to just figure out the framework, where the line is as/javascript where you had to write custom .js and where you draw the line of what .as file in asjs/src gets cross compiled. Honestly I don't know how long it's going to take me for the light bulb to turn on. Question: Say I had a goal of taking a mobile UI framework such as jQuery mobile and I wanted to wrap that for a ui extension. I know that I would have to create the api that mirror jQuery mobile, and then I would have to backasswards create .as Sprite components that would mirror the jQuery ones right? So what would be the steps and things I would have todo to get it to work? I am trying to do something that throws me right down to the lowlevel, I learn fastest this way. Knock on wood but, I really want to see this project succeed, I know it doesn't fit all dev's workflow but I really think after studying the plugin nature of the component framework, it could be really powerful and hopefully perform on a level of the other js frameworks right now. MXML is the key for me really wanting to put time into it. So for now I can devote 2-3 hours a day give or take my schedule. Mike On Thu, May 14, 2015 at 5:17 PM, Alex Harui aha...@adobe.com wrote: On 5/14/15, 1:52 PM, Michael Schmalle teotigraphix...@gmail.com wrote: Hi, Well now that I have a really efficient workflow setup with IntelliJ, I can start to tackle this project. What is the best way to setup bug reports for JIRA? There should already be a FlexJS component in Apache Flex JIRA. Some day, if FlexJS really gets going we could ask or a FLEXJS project in JIRA, but I’d worry that folks will file bugs in the wrong project. Try creating the smallest project possible, if so include it where? Small test cases are always great, even better might be a new test case for our automated testing. I’ve really bad about that though. Or post code and the error that might be the culprit. That’s also an option, especially if you just want some hints on how to fix it yourself. Remember, I am trying to remember all the apache protocol and stuff, so have patients with my questions. :) Your reappearance has already saved me enough time to be more patient. Thanks again for pitching in. -Alex
Re: [FlexJS] Testing current API and bugs
On 5/14/15, 1:52 PM, Michael Schmalle teotigraphix...@gmail.com wrote: Hi, Well now that I have a really efficient workflow setup with IntelliJ, I can start to tackle this project. What is the best way to setup bug reports for JIRA? There should already be a FlexJS component in Apache Flex JIRA. Some day, if FlexJS really gets going we could ask or a FLEXJS project in JIRA, but I’d worry that folks will file bugs in the wrong project. Try creating the smallest project possible, if so include it where? Small test cases are always great, even better might be a new test case for our automated testing. I’ve really bad about that though. Or post code and the error that might be the culprit. That’s also an option, especially if you just want some hints on how to fix it yourself. Remember, I am trying to remember all the apache protocol and stuff, so have patients with my questions. :) Your reappearance has already saved me enough time to be more patient. Thanks again for pitching in. -Alex
