[EMAIL PROTECTED] wrote: > Chris Burke wrote: >> If you build scripts in Jwd for running in jconsole, then these should >> not refer to USERFOLDERS. If you really need such references, then >> include them explicitly in the target scripts or in the console startup >> script, startup_console.ijs. > > I share code between myself and my clients. Projects reside in > different paths at different sites/computers. USERFOLDERS is a way > (as far as I am aware the only way) to abstract from this system > dependency and to write portable code. Absolut paths anyware are > unportable, also in target scripts. To maintain USERFOLDERS twice > seems silly to me. Please make it usable independently of the > wd/console issue.
A portable application can be built as a single script, plus a custom config file. The config file can contain path assignments, and be set up so that no knowledge of J is needed to customize it. This way you avoid the IDE altogether. Using the J IDE for configuration just shifts the problem around. For example, if your app requires USERFOLDERS, then how does the client get this defined? Do you expect him to load the J IDE, then use Edit|Configure? Or are you sending a copy of your own config.ijs or startup_console.ijs, and asking him to fix this up? All these are more troublesome than having your own custom config file. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
