(I re-respond to this message due to messed-up indents)
> From: bill lam <[email protected]> > > On Thu, 12 Nov 2009, Oleg Kobchenko wrote: > > > It would be the project configuration file, same as the current xxx.ijp > > > file except with updated definitions. > > > > Another approach is have one project.ijp and have different targets in it > > for build, test, run, etc. > > It's a good idea, just like there are multiple targets inside a > MakeFile, it can be called with optional arguments, such as > > make > make clean > make install install-doc > > It should be easily done with typing the these commands in jconsole. > However for a gui front-end with only one 'load' or 'test' button, it > need some method to pass these optional arguments. In GUI, targets are selected: - for each short-cut button (Build, Run, Test): a default target is assigned, but can be changed - there is also a generic "Run Target" which allows to pick any target for a single execution Like in Xcode Organizer, there may be certain patterns to match a selected file with a likely target. For example, if file is called "test.ijs" or "xxx_test.ijs" to execute a "test" target against it. Targets can also be non-J-specific, such as a shell script, some kind of pre-processor etc. In fact, targets could be business tasks, such as generate a report using a report definition and the format/publish addon; or to run a statistical processing on a data file, etc. Or those could be actions in a larger target "dojob", etc. Interestingly, the gui/jobs addon is similar to this project/task/operation paradigm, except that it allows for additional UI for parameters and viewing the results. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
