I’m not sure why you’d be getting that error.

I’m done for the day.

> On Apr 19, 2017, at 2:48 AM, Alex Harui <aha...@adobe.com> wrote:
> 
> I got an error looking for FactoryBackgroundManager.  Am I doing something
> wrong?
> 
> -Alex
> 
> On 4/18/17, 10:57 PM, "Harbs" <harbs.li...@gmail.com> wrote:
> 
>> I have committed my changes to the tlf branch. Theoretically, you should
>> get the same errors when trying to compile TLF.
>> 
>>> On Apr 19, 2017, at 1:54 AM, Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> JS compile.
>>> 
>>> I added the following to the library-paths:
>>> 
>>> <path-element>../../../../../libs/XMLJS.swc</path-element>
>>> 
>>> -compiler.strict-xml is set to true.
>>> 
>>> I tried changing it to false and it did not help.
>>> 
>>>> On Apr 19, 2017, at 1:48 AM, Alex Harui <aha...@adobe.com> wrote:
>>>> 
>>>> Is this the SWF or JS compile?  Where do the definitions for XML and
>>>> Error
>>>> come from?  JS.swc, playerglobal?
>>>> 
>>>> Did you try -compiler.strict-xml true and false?
>>>> 
>>>> Thanks,
>>>> -Alex
>>>> 
>>>> On 4/18/17, 10:29 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>>>> 
>>>>> TLF was missing EditManager. I added that, but it required XML as
>>>>> well,
>>>>> so I added XMLJS to the list of depenedencies.
>>>>> 
>>>>> After fixing an issue with appendChild() I’m currently getting a
>>>>> number
>>>>> of errors:
>>>>> 
>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.
>>>>> apa
>>>>> 
>>>>> che.org%2F73uW&data=02%7C01%7C%7Ccdc125b47a9641a0699d08d486e51999%7Cfa7
>>>>> b1b
>>>>> 
>>>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636281765918578149&sdata=lGeWSLtMI
>>>>> 00o
>>>>> MnXOWAL4be%2FJJpWHF2Sty4BVW%2BDb%2BUo%3D&reserved=0
>>>>> 
>>>>> Basically, they fall into two categories:
>>>>> 1. some_xml.@someattribute = some_value gets an error that
>>>>> someattribute
>>>>> is undefined.
>>>>> 2. Attempted access of inaccessible method toString through a
>>>>> reference
>>>>> with static type Error.
>>>>> 
>>>>> Any ideas here?
>>>>> 
>>>>> Harbs
>>>> 
>>> 
>> 
> 

Reply via email to