Looking forward to it, Alex. If people can write them in ActionScript
directly instead of converting Closure externs or TypeScript definitions,
that's going to be way easier!
- Josh
On Thu, Jan 19, 2017 at 8:14 AM, Alex Harui <aha...@adobe.com> wrote:
> And you could cheat a little bit and add it to missing.js in
> flex-typedefs/js if you don't want to bother setting up a whole new
> typedef SWC.
>
> BTW, I will be checking in changes to Falcon that make it really easy to
> use AS to generate typedefs.
>
> -Alex
>
> On 1/19/17, 7:33 AM, "Josh Tynjala" <joshtynj...@gmail.com> wrote:
>
> >If you don't mind the string property reference, that would be the easiest
> >way to access it. :)
> >
> >- Josh
> >
> >On Thu, Jan 19, 2017 at 7:21 AM, Harbs <harbs.li...@gmail.com> wrote:
> >
> >> window[“dialogPolyfill”].registerDialog(dialog) should do it.
> >>
> >> > On Jan 19, 2017, at 2:01 PM, Carlos Rovira <carlosrov...@apache.org>
> >> wrote:
> >> >
> >> > Hi,
> >> >
> >> > while we already need to solve how to make dialog polyfill work, I
> >>found
> >> a
> >> > new problem that hope you guys have already managed.
> >> >
> >> > I need to put the following lines in my Dialog MDL component:
> >> >
> >> > if (! dialog.showModal) {
> >> > dialogPolyfill.registerDialog(dialog);
> >> > }
> >> >
> >> > I have dialog var in my AS3 so this is ok, but I don't have
> >> > "dialogPolyfill" var
> >> > So the question is...how make FlexJS aware of "dialogPolyfil" that is
> >> setup
> >> > by the JS loaded as an external resource so I can compile my AS3 class
> >> and
> >> > make it work in the browser?
> >> >
> >> >
> >> > --
> >> > Carlos Rovira
> >> > http://about.me/carlosrovira
> >>
> >>
>
>
