[haXe] Debugger Request.

[Mike Mountain]

John
 
I did read somewhere that firing off a print event causes the player to
pause? It's a hack I know - but maybe it's a useable one?
 
Cheers
 
M


________________________________

	From: haxe-bounces at lists.motion-twin.com
[mailto:haxe-bounces at lists.motion-twin.com] On Behalf Of John Grden
	Sent: 22 August 2006 15:59
	To: The haXe compiler list
	Subject: Re: [haXe] Debugger Request.
	
	
	I just read through all of the threads on this, and thought it
worth mentioning some thoughts.
	
	The problem we immediately face with debugging is simple, yet
only resolvable by adobe or another flash player:  No breakpoints beyond
the control of the Flash Debugger (IE: Xray can't cause the player to
pause). 
	
	If I can't get past that, then Xray will never be a "true"
debugger and I get that.  I've just recently added a new logger to Xray
which supports leves as well as a package filter.  THe UI to support it
isn't done, but it's going to be quite nice to change the log level at
runtime and filter by packages. 
	
	In saying that, it's still not a true debugger ;)  And, the ever
larger picture is that, I need to port it over to AS3/Flex2 for the
connector.  Then, i'm thinking about how I could help with haXe, but
since it compiles to AS2, it seems like feature requests and general
performance improvements are all that I can really do.  Its the player
that ties my hands at this point. 
	
	Xray has helped many in the past, but I'm at a point where I'm
really evaluating it's future and how it fits into all these different
workflows, developer vs. designer, AS2/AS3/FLEX2/haXe/[ insert next cool
thing ].  
	
	The new logger is not only apart of the connector, but you can
simply grab the 5 classes for use with mtasc/ide use if you want without
having to load the connector and it'll still output to Xray's interface.
Now, I waited along time to do this and why?  Because I struggle with
doing the solution that makes sense for everyone involved (IDE
developers, IDE Designers, Eclipse users, Flex2 builder users, Flash
Develop/SEPY users etc).  It's such a vast playing field that it's a
true task to keep a debugger powerful yet usable to many.  What I think
it's coming down to is different flavors of Xray and getting experts in
those areas helping me with it. 
	
	Anyway, just thought I'd ramble from a different POV - 
	
	Thanks for being honest guys, I certainly appreciate it,
	
	jpg
	
	

		 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.motion-twin.com/pipermail/haxe/attachments/20060822/ae49bc62/attachment.htm