I think I know what Sherlock was talking about. One of the features of the PM is that it will automatically add dependency scripts/libraries that were reference by your project through a "require" command. You can also manually add this dependency though library tab.
I too find that this feature as very useful particularly when building distribution files and/or tracking down bugs when the script has been built/compiled. :) So yes, if the standalone script is decommitted ... a tool should be built to display the dependencies. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of bill lam Sent: Thursday, October 15, 2009 10:59 AM To: [email protected] Subject: Re: [Jbeta] decommit standalone script May be write that a [note] section ;-) Actually PM, as now. cannot infer the dependency by itself, it relies on what you told it. On Thu, 15 Oct 2009, 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. -- 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 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
