at any point of the code.
One other solution, which isn't really interactive, but looks useful nevertheless
is Omniscient Debugger
http://www.lambdacs.com/debugger/debugger.html
This would require to log all assignments and function calls. Shouldn't be
too hard to implement.If you, Nicolas are interested, i'll try to get more
information about the log format.
Cheers,
Ralf.
On 3/31/06, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
> Hi Vicente,
>
> since the time i published the preview, nothing really happened.
> I'm under the impression, that people aren't interested too much,
> it seems like they are quite happy with tools like AdminTool and
> LuminicBox.
> Also note, that Nicolas would have to do a major update of MTASC to make
> it work.
> Probably this will not happen, until haxe is stable.
>
> Sorry for the bad news,
> Ralf.
It's true that this would require a big update. However I'm willing do
work on that for haXe, since it would be great to be able to debug
haXe/Flash programs. Other haXe platforms have good error reporting :
the _javascript_ console and Neko exceptions traces. Flash is lacking
there, this might be improved with 8.5 Player.
Once it's done for haXe I might port it back to MTASC. I think that
should be pretty easy, since both haXe and MTASC use mostly the same
architecture for SWF generation.
I can definitly see a great interest in having such a debugger. I don't
like so much the Flash IDE one, the interface is difficult to handle and
the variables display is painful to use, making the whole interactive
debugging process almost useless, and then favorizing debug-traces
methods. I can see how an alternative debugger could improve things there.
The only drawback is that you need the Flash Debug Player installed to
be able to debug the SWF. That player is shipped with Flash IDE and is
not redistributable. That might not be a problem for people having
already a FlashIDE license but for some mtasc/haXe users that don't or
can't own one it's a bit problematic.
Making an OS tool that depends on an not-OS tool to work is somehow
wrong. It's not like MTASC. While using Flash IDE + MTASC makes sense,
MTASC can still be used as a standalone OS program, and can run on
various platform. That would not be the case for OFD. That's one of the
reasons why I stopped documenting the protocol.
Nicolas
_______________________________________________
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
