MLC - Lightweight Console for haXe

[Edo Rivai]

Hi Guys,

We proudly present MLC, a lightweight debugging tool for haXe. Please check it out at google code.

Using MLC can help you with debugging, since it allows you to change the state of your application at runtime. It also contains a neat AVM2 implementation that clearly outputs traces. The console is currently optimized for the AVM2 target, but also contains an implementation that writes traces to firebug.

We've added MLC to haxelib, so it be easily installed using the following terminal command: haxelib install mlc-1

At google code you will find more help setting up MLC with examples and explanation. Feel free to come up with ideas that could improve MLC.

Edo Rivai

--
haXe - an open source web programming language
http://haxe.org

[Blue Sans douze]

Wow ! That's a really cool feature !

I'm trying it out right now !
Thanks :D

--
haXe - an open source web programming language
http://haxe.org

[Blue Sans douze]

Just a simple thing : When I send many lines to the console (let's say 5000), it crashes the flashplayer when I try to show it... Maybe you should limit the number of line that can be kept in the console...
Note that the regular trace works just fine with 5000 lines.

Anyway, it's still a great tool !

--
haXe - an open source web programming language
http://haxe.org

[Edo Rivai]

Well, the regular trace works fine, because it does not allow you to view more traces than the amount that fits in your window. In MLC you can scroll upwards and view more traces.

If you are planning to trace a whole bunch of stuff, but you do not want to view all of it, you can call the "clear" method. No explanation needed, right?

If you still think the max should be built in, I can give you commit rights, and you could write it yourself!

On Wed, Jul 7, 2010 at 9:51 AM, Blue Sans douze <[hidden email]> wrote:

Just a simple thing : When I send many lines to the console (let's say 5000), it crashes the flashplayer when I try to show it... Maybe you should limit the number of line that can be kept in the console...
Note that the regular trace works just fine with 5000 lines.

Anyway, it's still a great tool !

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Lee Sylvester]

I think this is an awesome tool. It would be good if it was bundled in the haXe distribution, I think.

Lee

On 7 Jul 2010, at 09:26, Edo Rivai <[hidden email]> wrote:

Well, the regular trace works fine, because it does not allow you to view more traces than the amount that fits in your window. In MLC you can scroll upwards and view more traces.

If you are planning to trace a whole bunch of stuff, but you do not want to view all of it, you can call the "clear" method. No explanation needed, right?

If you still think the max should be built in, I can give you commit rights, and you could write it yourself!

On Wed, Jul 7, 2010 at 9:51 AM, Blue Sans douze <[hidden email]> wrote:

Just a simple thing : When I send many lines to the console (let's say 5000), it crashes the flashplayer when I try to show it... Maybe you should limit the number of line that can be kept in the console...
Note that the regular trace works just fine with 5000 lines.

Anyway, it's still a great tool !

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Pimm Hogeling]

Besides what Edo mentioned, you can also turn the buffer off entirely. That way, traces and writes will only end up in the console visualization after it has been opened.

On 7 July 2010 09:51, Blue Sans douze <[hidden email]> wrote:

Just a simple thing : When I send many lines to the console (let's say 5000), it crashes the flashplayer when I try to show it... Maybe you should limit the number of line that can be kept in the console...
Note that the regular trace works just fine with 5000 lines.

Anyway, it's still a great tool !

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Benjamin Dasnois]

Hi,

I do agree with you Lee. This is a very useful tool, and it could certainly be embedded in the standard distribution. I just have a reserve on it : it has to get an implementation for all platforms before. Let's not segment the standard library anymore! :)

Regards,

On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email]> wrote:

Besides what Edo mentioned, you can also turn the buffer off entirely. That way, traces and writes will only end up in the console visualization after it has been opened.

On 7 July 2010 09:51, Blue Sans douze <[hidden email]> wrote:

Just a simple thing : When I send many lines to the console (let's say 5000), it crashes the flashplayer when I try to show it... Maybe you should limit the number of line that can be kept in the console...
Note that the regular trace works just fine with 5000 lines.

Anyway, it's still a great tool !

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
DASNOIS Benjamin
http://www.benjamindasnois.com

--
haXe - an open source web programming language
http://haxe.org

[Lee Sylvester]

Not sure how it would work with PHP, though. Is there a means to do
this? Perhaps using remoting? Hmmmm....

Lee





Benjamin Dasnois wrote:

> Hi,
>
> I do agree with you Lee. This is a very useful tool, and it could
> certainly be embedded in the standard distribution. I just have a
> reserve on it : it has to get an implementation for all platforms
> before. Let's not segment the standard library anymore! :)
>
> Regards,
>
> On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Besides what Edo mentioned, you can also turn the buffer off
>     entirely. That way, traces and writes will only end up in the
>     console visualization after it has been opened.
>
>     On 7 July 2010 09:51, Blue Sans douze <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         Just a simple thing : When I send many lines to the console
>         (let's say 5000), it crashes the flashplayer when I try to
>         show it... Maybe you should limit the number of line that can
>         be kept in the console...
>         Note that the regular trace works just fine with 5000 lines.
>
>         Anyway, it's still a great tool !
>
>         --
>         haXe - an open source web programming language
>         http://haxe.org
>
>
>
>     --
>     haXe - an open source web programming language
>     http://haxe.org
>
>
>
>
> --
> DASNOIS Benjamin
> http://www.benjamindasnois.com

--
haXe - an open source web programming language
http://haxe.org

[Pimm Hogeling]

The console was designed to be able to receive input from any source, and send output to any handler. We could store the output in a file, or database, in case of PHP backends.

I agree that having full support for all targets is a must when distributing it along with the haXe package. haxelib is fine for now.

On 7 July 2010 12:48, Lee McColl Sylvester <[hidden email]> wrote:

Not sure how it would work with PHP, though. Is there a means to do this? Perhaps using remoting? Hmmmm....

Lee





Benjamin Dasnois wrote:

Hi,

I do agree with you Lee. This is a very useful tool, and it could certainly be embedded in the standard distribution. I just have a reserve on it : it has to get an implementation for all platforms before. Let's not segment the standard library anymore! :)

Regards,

On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email] <mailto:[hidden email]>> wrote:

   Besides what Edo mentioned, you can also turn the buffer off
   entirely. That way, traces and writes will only end up in the
   console visualization after it has been opened.

   On 7 July 2010 09:51, Blue Sans douze <[hidden email]

   <mailto:[hidden email]>> wrote:

       Just a simple thing : When I send many lines to the console
       (let's say 5000), it crashes the flashplayer when I try to
       show it... Maybe you should limit the number of line that can
       be kept in the console...
       Note that the regular trace works just fine with 5000 lines.

       Anyway, it's still a great tool !

       --
       haXe - an open source web programming language
       http://haxe.org



   --
   haXe - an open source web programming language
   http://haxe.org




--
DASNOIS Benjamin
http://www.benjamindasnois.com

--

haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Edo Rivai]

Hi Guys,

Just like Pimm said, in case of PHP, we could store the output of a trace in a file or database. These were mere ideas that came to our mind, but we are no real PHP experts, perhaps you guys can come up with a better way to implement a PHP console output handler.

Currently we have written implementations for AVM2 and javascript (firebug), if there is anyone who would like to write a PHP, neko or C++ implementation, we would like to grant you svn acces to the project!

Edo

On Wed, Jul 7, 2010 at 3:05 PM, Pimm Hogeling <[hidden email]> wrote:

The console was designed to be able to receive input from any source, and send output to any handler. We could store the output in a file, or database, in case of PHP backends.

I agree that having full support for all targets is a must when distributing it along with the haXe package. haxelib is fine for now.

On 7 July 2010 12:48, Lee McColl Sylvester <[hidden email]> wrote:

Not sure how it would work with PHP, though. Is there a means to do this? Perhaps using remoting? Hmmmm....

Lee





Benjamin Dasnois wrote:

Hi,

I do agree with you Lee. This is a very useful tool, and it could certainly be embedded in the standard distribution. I just have a reserve on it : it has to get an implementation for all platforms before. Let's not segment the standard library anymore! :)

Regards,

On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email] <mailto:[hidden email]>> wrote:

   Besides what Edo mentioned, you can also turn the buffer off
   entirely. That way, traces and writes will only end up in the
   console visualization after it has been opened.

   On 7 July 2010 09:51, Blue Sans douze <[hidden email]

   <mailto:[hidden email]>> wrote:

       Just a simple thing : When I send many lines to the console
       (let's say 5000), it crashes the flashplayer when I try to
       show it... Maybe you should limit the number of line that can
       be kept in the console...
       Note that the regular trace works just fine with 5000 lines.

       Anyway, it's still a great tool !

       --
       haXe - an open source web programming language
       http://haxe.org



   --
   haXe - an open source web programming language
   http://haxe.org




--
DASNOIS Benjamin
http://www.benjamindasnois.com

--

haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Mark de Bruijn | Dykam]

Thinking of it, you could write all console output to some hidden div, which appears and floats mid-window when a certain key-combo is pressed using javascript.
--
Mark

On Thu, Jul 8, 2010 at 10:40 PM, Edo Rivai <[hidden email]> wrote:

Hi Guys,

Just like Pimm said, in case of PHP, we could store the output of a trace in a file or database. These were mere ideas that came to our mind, but we are no real PHP experts, perhaps you guys can come up with a better way to implement a PHP console output handler.

Currently we have written implementations for AVM2 and javascript (firebug), if there is anyone who would like to write a PHP, neko or C++ implementation, we would like to grant you svn acces to the project!

Edo

On Wed, Jul 7, 2010 at 3:05 PM, Pimm Hogeling <[hidden email]> wrote:

The console was designed to be able to receive input from any source, and send output to any handler. We could store the output in a file, or database, in case of PHP backends.

I agree that having full support for all targets is a must when distributing it along with the haXe package. haxelib is fine for now.

On 7 July 2010 12:48, Lee McColl Sylvester <[hidden email]> wrote:

Not sure how it would work with PHP, though. Is there a means to do this? Perhaps using remoting? Hmmmm....

Lee





Benjamin Dasnois wrote:

Hi,

I do agree with you Lee. This is a very useful tool, and it could certainly be embedded in the standard distribution. I just have a reserve on it : it has to get an implementation for all platforms before. Let's not segment the standard library anymore! :)

Regards,

On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email] <mailto:[hidden email]>> wrote:

   Besides what Edo mentioned, you can also turn the buffer off
   entirely. That way, traces and writes will only end up in the
   console visualization after it has been opened.

   On 7 July 2010 09:51, Blue Sans douze <[hidden email]

   <mailto:[hidden email]>> wrote:

       Just a simple thing : When I send many lines to the console
       (let's say 5000), it crashes the flashplayer when I try to
       show it... Maybe you should limit the number of line that can
       be kept in the console...
       Note that the regular trace works just fine with 5000 lines.

       Anyway, it's still a great tool !

       --
       haXe - an open source web programming language
       http://haxe.org



   --
   haXe - an open source web programming language
   http://haxe.org




--
DASNOIS Benjamin
http://www.benjamindasnois.com

--

haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Pimm Hogeling]

Great idea, Mark.

On 8 July 2010 22:44, Mark de Bruijn | Dykam <[hidden email]> wrote:

Thinking of it, you could write all console output to some hidden div, which appears and floats mid-window when a certain key-combo is pressed using javascript.
--
Mark

On Thu, Jul 8, 2010 at 10:40 PM, Edo Rivai <[hidden email]> wrote:

Hi Guys,

Just like Pimm said, in case of PHP, we could store the output of a trace in a file or database. These were mere ideas that came to our mind, but we are no real PHP experts, perhaps you guys can come up with a better way to implement a PHP console output handler.

Currently we have written implementations for AVM2 and javascript (firebug), if there is anyone who would like to write a PHP, neko or C++ implementation, we would like to grant you svn acces to the project!

Edo

On Wed, Jul 7, 2010 at 3:05 PM, Pimm Hogeling <[hidden email]> wrote:

The console was designed to be able to receive input from any source, and send output to any handler. We could store the output in a file, or database, in case of PHP backends.

I agree that having full support for all targets is a must when distributing it along with the haXe package. haxelib is fine for now.

On 7 July 2010 12:48, Lee McColl Sylvester <[hidden email]> wrote:

Not sure how it would work with PHP, though. Is there a means to do this? Perhaps using remoting? Hmmmm....

Lee





Benjamin Dasnois wrote:

Hi,

I do agree with you Lee. This is a very useful tool, and it could certainly be embedded in the standard distribution. I just have a reserve on it : it has to get an implementation for all platforms before. Let's not segment the standard library anymore! :)

Regards,

On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email] <mailto:[hidden email]>> wrote:

   Besides what Edo mentioned, you can also turn the buffer off
   entirely. That way, traces and writes will only end up in the
   console visualization after it has been opened.

   On 7 July 2010 09:51, Blue Sans douze <[hidden email]

   <mailto:[hidden email]>> wrote:

       Just a simple thing : When I send many lines to the console
       (let's say 5000), it crashes the flashplayer when I try to
       show it... Maybe you should limit the number of line that can
       be kept in the console...
       Note that the regular trace works just fine with 5000 lines.

       Anyway, it's still a great tool !

       --
       haXe - an open source web programming language
       http://haxe.org



   --
   haXe - an open source web programming language
   http://haxe.org




--
DASNOIS Benjamin
http://www.benjamindasnois.com

--

haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Randy Stauner]

the php implementation could use firebug much like the js one does.

The haxe.Firebug class has parts in it for neko/php (they print out script tags)... is that sufficient?

If not perhaps the haxe.Firebug class could be enhanced for those 2 platforms.

It looks like haxe.Firebug.trace prints out directly (php.Lib.print) so you might need some sort of caching mechanism (in case you haven't sent the headers yet), but again I'd say that would be a useful enhancement for haxe.Firebug in general.

On Thu, Jul 8, 2010 at 1:40 PM, Edo Rivai <[hidden email]> wrote:

Hi Guys,

Just like Pimm said, in case of PHP, we could store the output of a trace in a file or database. These were mere ideas that came to our mind, but we are no real PHP experts, perhaps you guys can come up with a better way to implement a PHP console output handler.

Currently we have written implementations for AVM2 and javascript (firebug), if there is anyone who would like to write a PHP, neko or C++ implementation, we would like to grant you svn acces to the project!

Edo

On Wed, Jul 7, 2010 at 3:05 PM, Pimm Hogeling <[hidden email]> wrote:

The console was designed to be able to receive input from any source, and send output to any handler. We could store the output in a file, or database, in case of PHP backends.

I agree that having full support for all targets is a must when distributing it along with the haXe package. haxelib is fine for now.

On 7 July 2010 12:48, Lee McColl Sylvester <[hidden email]> wrote:

Not sure how it would work with PHP, though. Is there a means to do this? Perhaps using remoting? Hmmmm....

Lee





Benjamin Dasnois wrote:

Hi,

I do agree with you Lee. This is a very useful tool, and it could certainly be embedded in the standard distribution. I just have a reserve on it : it has to get an implementation for all platforms before. Let's not segment the standard library anymore! :)

Regards,

On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email] <mailto:[hidden email]>> wrote:

   Besides what Edo mentioned, you can also turn the buffer off
   entirely. That way, traces and writes will only end up in the
   console visualization after it has been opened.

   On 7 July 2010 09:51, Blue Sans douze <[hidden email]

   <mailto:[hidden email]>> wrote:

       Just a simple thing : When I send many lines to the console
       (let's say 5000), it crashes the flashplayer when I try to
       show it... Maybe you should limit the number of line that can
       be kept in the console...
       Note that the regular trace works just fine with 5000 lines.

       Anyway, it's still a great tool !

       --
       haXe - an open source web programming language
       http://haxe.org



   --
   haXe - an open source web programming language
   http://haxe.org




--
DASNOIS Benjamin
http://www.benjamindasnois.com

--

haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Mark de Bruijn | Dykam]

Yeah, firebug would be great as the default highliter. But yes, you should cache all debug output to some array and hook into php's exit, or something, to render that to a script tag just before the html tag. There must be some hook in the boot class... not sure if scripts work after the closing html tag.
--
Mark

On Fri, Jul 9, 2010 at 2:30 AM, Randy Stauner <[hidden email]> wrote:

the php implementation could use firebug much like the js one does.

The haxe.Firebug class has parts in it for neko/php (they print out script tags)... is that sufficient?

If not perhaps the haxe.Firebug class could be enhanced for those 2 platforms.

It looks like haxe.Firebug.trace prints out directly (php.Lib.print) so you might need some sort of caching mechanism (in case you haven't sent the headers yet), but again I'd say that would be a useful enhancement for haxe.Firebug in general.

On Thu, Jul 8, 2010 at 1:40 PM, Edo Rivai <[hidden email]> wrote:

Hi Guys,

Just like Pimm said, in case of PHP, we could store the output of a trace in a file or database. These were mere ideas that came to our mind, but we are no real PHP experts, perhaps you guys can come up with a better way to implement a PHP console output handler.

Currently we have written implementations for AVM2 and javascript (firebug), if there is anyone who would like to write a PHP, neko or C++ implementation, we would like to grant you svn acces to the project!

Edo

On Wed, Jul 7, 2010 at 3:05 PM, Pimm Hogeling <[hidden email]> wrote:

The console was designed to be able to receive input from any source, and send output to any handler. We could store the output in a file, or database, in case of PHP backends.

I agree that having full support for all targets is a must when distributing it along with the haXe package. haxelib is fine for now.

On 7 July 2010 12:48, Lee McColl Sylvester <[hidden email]> wrote:

Not sure how it would work with PHP, though. Is there a means to do this? Perhaps using remoting? Hmmmm....

Lee





Benjamin Dasnois wrote:

Hi,

I do agree with you Lee. This is a very useful tool, and it could certainly be embedded in the standard distribution. I just have a reserve on it : it has to get an implementation for all platforms before. Let's not segment the standard library anymore! :)

Regards,

On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email] <mailto:[hidden email]>> wrote:

   Besides what Edo mentioned, you can also turn the buffer off
   entirely. That way, traces and writes will only end up in the
   console visualization after it has been opened.

   On 7 July 2010 09:51, Blue Sans douze <[hidden email]

   <mailto:[hidden email]>> wrote:

       Just a simple thing : When I send many lines to the console
       (let's say 5000), it crashes the flashplayer when I try to
       show it... Maybe you should limit the number of line that can
       be kept in the console...
       Note that the regular trace works just fine with 5000 lines.

       Anyway, it's still a great tool !

       --
       haXe - an open source web programming language
       http://haxe.org



   --
   haXe - an open source web programming language
   http://haxe.org




--
DASNOIS Benjamin
http://www.benjamindasnois.com

--

haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

[Benjamin Dasnois]

How about hooking a console via sockets to it? This way one could get the output in a clean way and also the script may wait to get some input. Also, PHP is not only used to develop web applications but also to develop some CLI interfaces or even GUI ones (ermm.... not often for this last one). This solution would provide a great way of interacting in real time with a PHP script.

On Fri, Jul 9, 2010 at 12:38 PM, Mark de Bruijn | Dykam <[hidden email]> wrote:

Yeah, firebug would be great as the default highliter. But yes, you should cache all debug output to some array and hook into php's exit, or something, to render that to a script tag just before the html tag. There must be some hook in the boot class... not sure if scripts work after the closing html tag.
--
Mark

On Fri, Jul 9, 2010 at 2:30 AM, Randy Stauner <[hidden email]> wrote:

the php implementation could use firebug much like the js one does.

The haxe.Firebug class has parts in it for neko/php (they print out script tags)... is that sufficient?

If not perhaps the haxe.Firebug class could be enhanced for those 2 platforms.

It looks like haxe.Firebug.trace prints out directly (php.Lib.print) so you might need some sort of caching mechanism (in case you haven't sent the headers yet), but again I'd say that would be a useful enhancement for haxe.Firebug in general.

On Thu, Jul 8, 2010 at 1:40 PM, Edo Rivai <[hidden email]> wrote:

Hi Guys,

Just like Pimm said, in case of PHP, we could store the output of a trace in a file or database. These were mere ideas that came to our mind, but we are no real PHP experts, perhaps you guys can come up with a better way to implement a PHP console output handler.

Currently we have written implementations for AVM2 and javascript (firebug), if there is anyone who would like to write a PHP, neko or C++ implementation, we would like to grant you svn acces to the project!

Edo

On Wed, Jul 7, 2010 at 3:05 PM, Pimm Hogeling <[hidden email]> wrote:

The console was designed to be able to receive input from any source, and send output to any handler. We could store the output in a file, or database, in case of PHP backends.

I agree that having full support for all targets is a must when distributing it along with the haXe package. haxelib is fine for now.

On 7 July 2010 12:48, Lee McColl Sylvester <[hidden email]> wrote:

Not sure how it would work with PHP, though. Is there a means to do this? Perhaps using remoting? Hmmmm....

Lee





Benjamin Dasnois wrote:

Hi,

I do agree with you Lee. This is a very useful tool, and it could certainly be embedded in the standard distribution. I just have a reserve on it : it has to get an implementation for all platforms before. Let's not segment the standard library anymore! :)

Regards,

On Wed, Jul 7, 2010 at 11:53 AM, Pimm Hogeling <[hidden email] <mailto:[hidden email]>> wrote:

   Besides what Edo mentioned, you can also turn the buffer off
   entirely. That way, traces and writes will only end up in the
   console visualization after it has been opened.

   On 7 July 2010 09:51, Blue Sans douze <[hidden email]

   <mailto:[hidden email]>> wrote:

       Just a simple thing : When I send many lines to the console
       (let's say 5000), it crashes the flashplayer when I try to
       show it... Maybe you should limit the number of line that can
       be kept in the console...
       Note that the regular trace works just fine with 5000 lines.

       Anyway, it's still a great tool !

       --
       haXe - an open source web programming language
       http://haxe.org



   --
   haXe - an open source web programming language
   http://haxe.org




--
DASNOIS Benjamin
http://www.benjamindasnois.com

--

haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
haXe - an open source web programming language
http://haxe.org

--
DASNOIS Benjamin
http://www.benjamindasnois.com

--
haXe - an open source web programming language
http://haxe.org