Jee Labs Talk

This forum has moved to forum.jeelabs.net - this read-only archive is for reference only!

1. mnmis
   

   Does anyone have the command line options for running Jeemon?

   I know that it automatically runs the application.tcl file but is there a way to do debugging, running other files, etc...

   Thanks

   Posted 15/05/2010 01:07:15

2. jcw
   

   This is still work in progress. I'm trying to decide what set of features will be least confusing, yet powerful enough to support multi-platform use, and remote debugging (since JeeMon is also for use on small embedded Linux boxes).

   First off, you can give the path to a Tcl script and JeeMon will run it more or less like a tclsh/wish command would. I use that to run some standard Tcl scripts I have (not all JeeMon-related). This does not use the "rig" mechanism, i.e. no "proc start" etc.

   You can give the name of a directory, and JeeMon will look for "application.tcl" inside that directory. This is a way to launch the same JeeMon for different uses.

   For simple examples, I now often try things out with "application.tcl" next to JeeMon, and once it is done, I move it into a new subdir with some appropriate name. Freeing me to use application.tcl for new experiments again.

   You can start as "JeeMon Console" to launch the built-in TkCon GUI console. That in turn can be used to connect to another instance of JeeMon running locally or elsewhere on the network (see ). This is not JeeMon-specific but Tcl functionality. This is probably the approach I'll be focusing on for debugging, i.e. a local TkCon GUI app connected to any running instance of JeeMon so you can inspect (and alter) a running process. I also intend to support on-the-fly-reloading so that you can edit Tcl code and have it picked up by the running JeeMon. I've used this technique in a previous project and it works really well, because you can keep going and improving the code without have to stop and restart the application all the time.

   For the recent simple JeeMon projects, though, I did none of the above. Just used "puts" and "Log" calls to debug and restart. Very primitive, but still effective if you develop things progressively.

   Posted 15/05/2010 13:34:25