On Mon, Nov 9, 2015 at 11:00 AM, Harbs <harbs.li...@gmail.com> wrote:
> I’m not 100% clear on the status of the back-ports or the best way to go > about it. I figured I’d wait until we’re done with the release and then > coordinate with you and Peter. > > In the meantime, I started work on some XML classes. I pretty much decided > on departing a bit from classic E4X for two reasons: 1. It’s just about > impossibly to reproduce the E4X behavior. 2. E4X was always awkward to use. > I’m going to more or less copy the public API of XML, but my version of > XMLList is going to work differently. Both XML and XMLList (I’m calling > them XMLNode and XMLNodeList) will have filter functions which work similar > to Array filter functions. The only E4X expression I have used over and over is the ability to get an array of child nodes using the double-dot expression. For example: var mySVG:XML = <svg> <desc /> <rect /> <ellipse /> <path /> <path /> <path /> <ellipse /> <path /> <path /> </svg>; We could write: var paths:XMLList = mySVG..path; I think if we can add support to just this (maybe a few more based on popular usage), we should be able to get existing Flex apps easily ported. Although, I am not sure how hard something like this would be to implement. Thoughts? Thanks, Om > This should allow getting chunks of XML in a more sane method than using > hard-to-read E4X expressions. > > I’m hoping to have something commit-able on that front by the end of the > week. > > I’ll try to follow what you are doing with DragDrop and Effects so I get a > better feel of how it’s done. > > On Nov 9, 2015, at 7:36 PM, Alex Harui <aha...@adobe.com> wrote: > > > Harbs, > > > > Thanks for the commits for the back port. Let us know if you actually > > start work on porting an existing SWC. I’m going to wait another day > > before cutting the FalconJX RC2 in case Justin has more feedback on the > > LICENSE. So I am going to try to port dragdrop and effects. > > > > -Alex > > > > On 11/9/15, 12:12 AM, "Alex Harui" <aha...@adobe.com> wrote: > > > >> > >> > >> On 11/8/15, 11:55 PM, "Harbs" <harbs.li...@gmail.com> wrote: > >>> > >>>> Meanwhile, Peter and I are back porting the SWCs one-by-one in the > >>>> core_js_to_as branch of flex-asjs. We haven’t written a how-to or > >>>> anything, but you can look at Binding, Core, Collections and HTML as > >>>> examples. > >>> > >>> Color me confused, but I still see all 3 source folders after switching > >>> to the back port branch. It looks like you’re doing the back-port in > the > >>> as folder? The folder clean-up will happen after the port is complete? > >> > >> The asjs folders should be empty (more or less) in Binding, Core, and > >> other completed SWCs. We move all .as files to the as/src folder and > fix > >> up the compile-asjs-config.xml files. We are keeping the js/src folders > >> for now, then we’ll delete them once we feel good we’ve ported them > >> correctly. > >>> > >>>> I think Peter is working on Charts and Mobile. Graphics builds > cleanly > >>>> but Peter needs to verify it. So, if you want, let us know what SWC > >>>> you > >>>> want to try and see if you can see the patterns from the other > projects > >>>> and change logs. > >>> > >>> I’ll spend some time studying this today. I just added compiler > arguments > >>> to the Flash Builder project files so AFB does not choke on the > compiler > >>> arguments. I’ll commit those changes shortly. FWIW, the only real error > >>> I'm getting is in HTML IScrollingLayoutParent that ILayoutParent is not > >>> found. > >> > >> I have to stop for the night, but I don’t think IScrollingLayoutParent > >> should be there anymore. Check the logs in the develop branch to > verify. > >> > >> Thanks for helping. > >> -Alex > >> > > > >
