Chris Burke wrote:
> 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.
It's not my goal to avoid the IDE altogether. In fact, I developed
the application to run under jconsole with the IDE. That's what was
so puzzling: the code would run just fine from the IDE but yield the
infamous "script error" when run from jconsole.
> 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?
Basically yes. My client is a developer, too. We have no problem
defining project shortcuts. One does it once and is done with it.
Most importantly, it allows us to maintain source sets which are
location-independent without any further manual adjustments (and
hence deltas from the repository).
> Or are you sending a copy of your own config.ijs or
> startup_console.ijs, and asking him to fix this up?
This is exactly what we avoid by a one-time USERFOLDERS entries
which can be kept outside of the projects themselves.
SYSTEMFOLDERS *is* the available in both contexts. I cannot
understand why USERFOLDERS gets second rate treatment under jconsole.
Martin
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
