Raul's example is good for jconsole. But also >> IJX windows don't update properly
You will see the output in IJX if together with smoutput you will call wd'msgs' as was suggested earlier. In addition you can use the J Break icon to interrupt. ----- Original Message ---- From: Thomas Costigliola <[EMAIL PROTECTED]> To: Beta forum <[email protected]> Sent: Thursday, June 29, 2006 3:39:32 PM Subject: Re: Re: RE: [Jbeta] Tardy graphics (again) Could you please elaborate. To run my program I do: j -jijx "myprogram.ijs" "options" My program runs some script e.g. 0!:001 <'somescript.ijs' I want to see the output. Unless I open an ijx window I can not see this output. IJX windows don't update properly therefore I choose not to open one. So what you are saying I can do is instead do: jconsole "myprogram.ijs" And somehowtell jconsole to write to let's say stdout? Or even more interestingly a file. Again please elaborate. Thank you. >From: Oleg Kobchenko <[EMAIL PROTECTED]> >Date: Thu Jun 29 13:44:43 CDT 2006 >To: Beta forum <[email protected]> >Subject: Re: RE: [Jbeta] Tardy graphics (again) >Why do you need the redirection? > >Maybe then you might as well use and redirect jconsole. > >Or one of these > >jee -- console front end that connects to j.exe or j.jar with sockets >jep -- front end that supports the J Engine Protocol > > > >----- Original Message ---- >From: Thomas Costigliola >To: Beta forum >Sent: Thursday, June 29, 2006 2:18:16 PM >Subject: Re: RE: [Jbeta] Tardy graphics (again) > > >To me, the most flexible solution would be to redirect all output from the J >interpreter to a file. Perhaps a global variable that holds the handle of an >open file that could be a pipe or socket. Then ALL output that would normally >be sent to the ijx window would be sent to this file. > >Any feedback for this idea? Is it already possible? > >>From: Jose Mario Quintana >>Date: Wed Jun 28 21:35:21 CDT 2006 >>To: 'Beta forum' >>Subject: RE: [Jbeta] Tardy graphics (again) > >> >>> Behalf Of Dan Bron >>> Jose, >>> >>> Have you tried mucking with wd'msgs' ? Using the following verb, I can >>> refocus window between delays: >>> >>> countdown=. ''"_@:(<"0@:|.@:i.@:[ >@:((1!:2&2@:[ ] 6!:3@:] >>> [ wd@:('msgs'"_))&.>/@:(|.@:[ , <@:])) ]) >>> 10 countdown 1 >> >>Dan, thank you very much for your suggestion; it should make some of our >>applications behave as we want them to behave. >> >>> >>> Note the difference in behavior if one does the wd'msgs' AFTER the >>delay. >>> >> >>Very interesting! >> >>> countdown=. ''"_@:(<"0@:|.@:i.@:[ >@:((1!:2&2@:[ ] 'msgs' >>> wd@:[ 6!:3@:])&.>/@:(|.@:[ , <@:])) ]) >>> 10 countdown 1 >>> >>> -Dan >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >> >> >>---------------------------------------------------------------------- >>For information about J forums see http://www.jsoftware.com/forums.htm > >---------------------------------------------------------------------- >For information about J forums see http://www.jsoftware.com/forums.htm >---------------------------------------------------------------------- >For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
