Awesome, it works!
That is, it works on projects that have no spaces in the path. If a project
path has spaces in it I still get the two errors reported previously (cached
type is null in ASReconcillingStrategy, and doSave cachedType is null). If
you can nail that one, we're home free!
Thanks so much for your hard work Martin, I look forward to using it on my
next Flash project. Where is the best place to get information on the new
features?
Thanks,
Scott
P.S. for other Mac users out there, I finally figured out how to get ANT to
launch a web page in Firefox regardless of whether or not it is already
open. I will post the full ANT task in a new post if anyone is interested,
but here is the important snippet:
<exec executable="open" dir="." spawn="true">
<arg line="-a ${webBrowser} ${deploy_dir}/${htmlFile}" />
</exec>
On 08/06/07, Martin Wood-Mitrovski < [EMAIL PROTECTED]> wrote:
Ok, i got hold of a 10.4.9 machine for testing and I managed to find a few
issues with the Mac build which are now 'solved' (or at least bypassed)
I would tell you to join the asdt-users list but the sourceforge mailman
page
appears to be broken, and the web interface is, quiet frankly, appalling.
So, i'll summarise what i've written so you know what to expect :)
The build is here :
http://aseclipseplugin.sourceforge.net/testreleases/asdt-0.0.9-test-07-06-07.zip
and this is why it took so long :)
The major problem on the Mac is with using the ASDT logging system. This
is
because it uses an XML socket. To be able to connect to localhost asdt
writes
trust files for each project to prevent the security warning from
appearing. Now
on XP and Linux this works fine.
The problem on the Mac is that the contents of the FlashPlayerTrust
directory
are only read once when the flash player (in the embedded safari browser)
is
first opened. So creating more swfs in that eclipse session and trying to
open
them with the ASDT viewer will cause the security prompt to appear (also
pressing the 'settings' button in the dialog does nothing)
So, the best option for viewing new swfs created after the viewer has been
launched is to use the standalone player. Fortunately i've fixed some bugs
with
the ASDT launch system so you can now setup launch configurations to run
your
swfs in an external player and see the trace output in the logger console.
Thats basically it, the other issue was the permissions of the MTASC
executable
and the fact that File.setExecutable is a java 6 only method, not java 5
as i
first thought so we have to manually chmod the binary when the plugin
starts up.
try it out, let me know how you get on and all things being well i'll push
this
build to the update site under a 'beta' category sometime over the
weekend.
thanks for your help and patience.
Martin
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
