The main problem I found with the standalone script business is that the build is often too complex to be done entirely by clicking options in a dialog, but still easy to do in J. So I found myself writing fairly simple scripts that did builds.
I still want to retain a simple build capability in future, just to assemble the set of scripts in the project into one, but no more than that. This is good enough for many projects. The dependencies tool could be a standalone utility. The code is already there in Project Manager, but needs to be extended to support addons. Sherlock, Ric wrote: > I'm thinking that even if standalone script logic was decommitted, it would > still be nice to have some sort of tool for listing the dependencies of a > script or project? > >> From: bill lam >> >> One reason why code in PM is so complicated is the requirement to >> build standalone script. But it is, as now, still incomplete in that >> only J base library can be handled, all other script including addon >> cannot. > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
