Yes your are correct. I guess it would sufficient to provide menu item or keyboard shortcut to run the following project specific scripts.
1. run the 'load.ijs' script which will load all project script 2. run the 'run.ijs' script 3. run the 'test.ijs' script Having these (or similar) file names fixed so that they need not be explicitly mentioned inside .proj file. On Fri, 16 Oct 2009, Sherlock Ric wrote: > My understanding (may be wrong) of the Wiki proposal is that the pre-build > hook will not exist in the new PM, but that the buildfile will be the > equivalent of the current post-build script. (i.e. the creation of the > targetfile is the "build" step). > > As Chris says, trying to provide lots of flexibility starts to make a GUI > quite complex, but isn't necessarily hard in a J script. > > Perhaps the preload, postload functionality can be provided by the proposed > testfile. Rather than a whole lot of GUI options one solution might be to > provide the user with a testfile template that they can edit. > e.g. > > NB.===== testfile template ======== > NB. Add any pre-load processing here > > load targetfile > NB. Add any post-load processing here > > NB. call any test scripts here > load ,&'_test.ijs'_4}. Targetfile NB. default name for test script > > NB. Add any post-test processing here > NB.================================ > > Alternatively a bunch of templates could be presented for the user to choose > from, or to a custom template could be built on the fly based on the user's > answers to a dialog or wizard. > > This solution could potentially also cater for Anssi's suggestion for a > "Clear & Load" button. > > [---=| TOFU protection by t-prot: 19 lines snipped |=---] -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
