On 4/26/13 10:21 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> I'm all for reducing size and optimisation, when functionality is not
> compromised ;-)
>
> I'll be gone for a week, away from all but my iPad, so I'll merge the
> 'goog.events' branch into develop when I get back.
>
> Thank you for the compromise, I'm looking forward to the next time I
> have to stamp my feet and threaten to quit if I don't "get my way" ;-)
> Or I just might decide to argue the point on technical details right
> away, you never know...
I'm hoping to crank out a bunch of containers next week. I think that means
adding more subclasses and maybe some new properties to UIBase. I guess new
classes shouldn't cause merge hell?
>
> EdB
>
>
>
> On Sat, Apr 27, 2013 at 6:00 AM, Alex Harui <aha...@adobe.com> wrote:
>>
>>
>>
>> On 4/26/13 1:13 PM, "Alex Harui" <aha...@adobe.com> wrote:
>>
>>>>
>>>> I have no idea how to add 'goog.events' as a polyfil, as it is compiled
>>>> into the code on publishing, long before we know which browser we're
>>>> addressing.
>>>>
>>> It looked like we could use --externs so the polyfill doesn't get baked in
>>> and then pull it in from the html after a browser check. But I haven't
>>> tried it and I might be misunderstanding the doc.
>> BTW, if you are not opposed to the polyfill concept and the notion that we
>> might someday revert HTMLEventWrapper to proxy to the browser code instead
>> of goog.events, then I'm not opposed to you checking in your changes as you
>> have them and we can look into polyfills later.
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
