On 12/6/12 10:40 AM, "Michael Schmalle" <apa...@teotigraphix.com> wrote:

> Well considering I know exactly what the task is.
> 
> I will warn you, as I have said previously I am green when it comes to
> complex build scripts, that is eomthing you will have to do.
> 
> I think my task is right now to get the output inline with what Erik
> is proposing. Does this sound correct?
Yes, but after that, the publisher still has to work.  I haven't looked at
it, but when manually "publishing" the prototype example, it involved
copying the adobe.js file.  If the new solution involves having a base.js
handy, I think we need to download it instead of checking it into our repo.

> 
> Mike
> 
> 
> Quoting Alex Harui <aha...@adobe.com>:
> 
>> OK, I am assuming you will complete this task?
>> 
>> 
>> On 12/6/12 10:21 AM, "Michael Schmalle" <apa...@teotigraphix.com> wrote:
>> 
>>> 
>>> Ok, that was an idiot question, I just answered my own with a cliche
>>> "google search"
>>> 
>>> base.js is what the closure compiler uses and exactly what I just
>>> switched to. :)
>>> 
>>> Yeah, I'm smart...
>>> 
>>> Mike
>>> 
>>> Quoting Michael Schmalle <apa...@teotigraphix.com>:
>>> 
>>>> 
>>>> Quoting Alex Harui <aha...@adobe.com>:
>>>> 
>>>>> I just fixed another issue when you don't copy the SDK.
>>>>> 
>>>>> I am running unit tests from a command shell on MacOSX.   All the
>>>>> tests run
>>>>> by the default ant target pass for me.
>>>>> 
>>>>> I am about to embark on switching the output to base.js.
>>>> 
>>>> What does this exactly mean? Changing code in the JSEmitter? I just
>>>> spent 4-5 hours looking at the output and debugging it with break
>>>> points. The JSEmitter is only about 1/3 of the emitting logic.
>>>> 
>>>> Mike
>>>> 
>>>> 
>>>>> -Alex
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> Michael Schmalle - Teoti Graphix, LLC
>>>> http://www.teotigraphix.com
>>>> http://blog.teotigraphix.com
>>>> 
>>>> 
>> 
>> --
>> 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

Reply via email to