I do not write applications for others, only myself. I never did learn to use the Project Manager, but my applications are not so complicated that require more than a few scripts. In Windows I defined the file type ijs to be run by J with the parameter -jijs and pass arguments as needed to the application. Then in the main script for the application I put the run verb at the bottom to start the application just as would be done with Project Manager. So to test under J I simply press Ctrl-W to run it. Once I'm satisfied I simply can double-click the script.ijs to run it without the ijx window. In other words - I never see that it's a J application. This approach does bring in the entire J development environment but not displaying the ijx window but the load time is so little that it is not noticeable. Especially when compared to the start-up time of JAVA. In J5 I had modified the nasty message J gives when it encounters an error without an ijx window to bring up the ijx window and display the error. Hey! I'm ready to start debugging already. Haven't done that for J6 yet.
I find it very convenient to have the same environment for both testing and production. Really simplifies going to production. If I want I simply create a shortcut for the script.ijs and put it on the desktop. I'm done. If you are interested in details on how I do this, let me know and I'll get you them. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
