--- Hahn, Harvey wrote: > Devon McCormick wrote: > |Why not install J and run your scripts as you would do with many other > |packages? > > I don't understand your question. > > A GUI click to trigger the application is what clerical staff "would do > with many other packages"--and that's not how J scripts natively work. > I can't ask them to start up the J .ijx window and then type in command > lines to make things happen--they would strongly balk at that because > it's not how typical applications these days work.
Yes end users are generally accustomed to clicking on a icon/short-cut to start an application. By installing J and creating an appropriate shortcut you can tell J to start without an ijx window and to run a certain script (that may in turn create a GUI for the user). The Target of the short-cut may look something like: "c:\program files\j602\bin\j.exe" -ijx myscript.ijs And the Start in: "c:\users\jbloggs\myapp" Where the path to myscript.ijs is "c:\users\jbloggs\myapp\myscript.ijs" See the following User Manual page for more detailed information http://www.jsoftware.com/help/user/cmdline.htm If you found the Building Applications Lab useful, you may also want to check out the Application Distribution - Installer Lab. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
