Really, you can choose any baseline you want for your XML SWC. Folks targeting something might have to resort to JSON. Or someone else will create an IE9 compatible version. If there is a significant win to having the baseline be IE10 for your swc, it doesn’t require that for other classes. We already have an HTML5 swc that will someday require HTML5 browsers.
-Alex On 11/10/15, 3:34 PM, "Harbs" <harbs.li...@gmail.com> wrote: >Great! > >Minimum of IE10 would make things even easier, but I think IE9 is fine >for what I’m working on now. > >On Nov 11, 2015, at 1:29 AM, Alex Harui <aha...@adobe.com> wrote: > >> We are now saying IE9. We are using Object.defineProperties. >> >> Folks targeting IE8 and older should deploy the SWF version. >> >> -Alex >> >> On 11/10/15, 3:25 PM, "Harbs" <harbs.li...@gmail.com> wrote: >> >>> BTW, what’s our minimum browser target for FlexJS? >>> >>> Are we supporting IE8? I’m kind of hoping I can ignore IE8 WRT XML >>> support. >>> >>> On Nov 11, 2015, at 1:20 AM, Alex Harui <aha...@adobe.com> wrote: >>> >>>> Good luck. >>>> >>>> Setting COMPILE::JS should have no effect on code completion offerings >>>> unless it controls APIs in source code you wrote yourself. The rest >>>>of >>>> the offerings come from the SWCs in the library-path (and >>>> external-library-path) and which flags were on when the SWC was >>>> compiled. >>>> I added some info about that in the wiki page today. >>>> >>>> Having thought about this a bit, I think we will need two sets of >>>> project >>>> files for folks to develop components in FB. I have never tried >>>>project >>>> files with external source folders, but I think that is where we’ll >>>>end >>>> up. The default project files may be for SWFs and have >>>> playerglobal/airglobal as external libraries. Some other set of >>>>project >>>> files will point to the same source folders but have js.swc as an >>>> external >>>> library and no sign of playerglobal/airglobal. If you want to play >>>> around >>>> with that, feel free. Then you should get code hinting from js.swc. >>>> >>>> I think the final folder topology will be quite different from the >>>> as/src, >>>> asjs/src, js/src, js/out you’ll find in the branch right now. I’m >>>> tempted >>>> to just have a src folder and an out folder. Although I’m happy to >>>>try >>>> something else, especially if it affects Maven integration. >>>> >>>> -Alex >>>> >>>> On 11/10/15, 2:57 PM, "Harbs" <harbs.li...@gmail.com> wrote: >>>> >>>>> OK. I’ll try working with ant for now. >>>>> >>>>> I’ll try getting some code to compile in the morning. If there’s no >>>>> code >>>>> completion for now anyway, I’ll just set -define=COMPILE::JS,false >>>>>for >>>>> now. That will at least allow me to use FB as a code editor. Maybe >>>>>I’ll >>>>> see if Sublime give me some code completion. >>>>> >>>>> I see what you did with gecko_xml.js. If I’m missing anything else, I >>>>> think I understand how to add more externs. >>>>> >>>>> Hopefully I got enough to be productive now. >>>>> >>>>> Wish me luck! ;-) >>>>> >>>>> Harbs >>>>> >>>>> On Nov 11, 2015, at 12:47 AM, Alex Harui <aha...@adobe.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> On 11/10/15, 1:50 PM, "Harbs" <harbs.li...@gmail.com> wrote: >>>>>> >>>>>>> I just tried in Core as well. If I set “-define=COMPILE::JS,true” >>>>>>> which >>>>>>> is what I believe we need to get code recognition and completion, I >>>>>>> get >>>>>>> lots of errors in FB. >>>>>>> >>>>>>> Am I going about this wrong? >>>>>> >>>>>> As I said in at the beginning of my last reply, I don’t know what it >>>>>> will >>>>>> take to get FB to accept these definitions from js.swc. I >>>>>>understand >>>>>> it >>>>>> will make it easier for you and others to contribute once we get FB >>>>>> working on these projects, but I would much prefer not to have to >>>>>>take >>>>>> the >>>>>> time to figure it out for the core_js_to_as branch until we are >>>>>>mostly >>>>>> done with the back port and have restructured the folders to a more >>>>>> final >>>>>> topology. Otherwise, I think I will have to keep stopping to tweak >>>>>> the >>>>>> projects as we go and the whole thing will take longer. Do you >>>>>>really >>>>>> have to have code hinting to get started on this XML library? Or >>>>>> maybe >>>>>> just start coding it in a temporary package for now. You can >>>>>>probably >>>>>> add >>>>>> some glue code to the output to map that class to the global scope. >>>>>> >>>>>> The COMPILE::JS flag only controls what code the compiler has to >>>>>> compile, >>>>>> not what definitions it is pulling in from various SWCs. >>>>>> >>>>>> From the command-line with Ant, I just tried building the Core >>>>>>project >>>>>> by >>>>>> switching to frameworks/projects/Core and then: >>>>>> 1) ran “ant -Dis.jenkins=true all” which proved it could build >>>>>>cleanly >>>>>> but >>>>>> skipped the tests >>>>>> 2) Edited Application.as and inside a COMPILE::JS block added: >>>>>> var foo:DOMParser = null; >>>>>> var bar:Document = null; >>>>>> 3) ran “ant -Dis.jenkins=true all” again to see if would compile. >>>>>> >>>>>> It was missing DOMParser which I just added and pushed to >>>>>>flex-falcon >>>>>> so >>>>>> sync up and at least run “ant extern.swcs” there. Then step 3 >>>>>>worked >>>>>> for >>>>>> me. >>>>>> >>>>>> Please first try the Ant steps so at least we know that works for >>>>>>you. >>>>>> >>>>>> -Alex >>>>>> >>>>>>> >>>>>>> On Nov 10, 2015, at 9:40 PM, Alex Harui <aha...@adobe.com> wrote: >>>>>>> >>>>>>>>> I’m not sure you answered my primary question here. How do I >>>>>>>>>target >>>>>>>>> HTML/JS native classes like Document, DOMParser, etc. in >>>>>>>>> ActionScript? >>>>>>>>> I >>>>>>>>> don’t want to do that in js. I’d rather have FlaconJX >>>>>>>>>cross-compile >>>>>>>>> it >>>>>>>>> for me. >>>>>>>> >>>>>>>> Not sure about what FlashBuilder will let you do, but from Ant, >>>>>>>>you >>>>>>>> should >>>>>>>> be able to use Document, DOMParser etc inside COMPILE::JS blocks. >>>>>>>> Try >>>>>>>> adding test code to a class in the Core project and compile it. >>>>>>>> Then >>>>>>>> we’ll worry about FlashBuilder. It should work for Core because >>>>>>>>the >>>>>>>> compile-asjs phase will not use playerglobal/airglobal, it will >>>>>>>>use >>>>>>>> js.swc >>>>>>>> from the Falcon repo which has Document and DOMParser in it. >>>>>>> >>>>>> >>>>> >>>> >>> >> >
