Ric and Raul have both made comments which reflect my views as a long term
user. The default way of handling user files made transfering between
versions more complex than it needs to be and specifying where they will be
is at most one additional step of nearly identical structure to the existing
selection of the folder for the system. (A step I always have to use
because I want to keep J as far as I can from my C: drive.)
It seems to me there are three classes of files which need to be considered
in achieving Eric's 4 Requirements:
System files - essentially read only files
Files to control user interactions - set during configuration, storing
information about sessions such as recent files, etc. These files are
written by the system to record user preferences, requirements or actions.
User files - temp files, scripts, projects and sometimes results or data.
Having a clearly defined system folder with the new folder structure (called
HOME in the discussion so far) and another with all of the script and work
files (called j602-user) would be simpler to use than the present structure
but both folders should have defaults which are easy to change at
installation.
Using the Edit/Configure form it should be simple to specify where any of
the script, project and other user files reside later if required but that
is not a solution for files the system must access for user preferences or
past actions or creation of any temp files (the default for creating
scripts) and any folders normally set up at installation.
These should be in the J602-user folder rather than a folder in the HOME
directory. (In J601 on my system, reassigning the temp folder in Config
does not appear to do anything and does not mean the system looks in the new
folder for File/Open or saves temporary script files there).
I do not know enough about the file name usage in the Unix world to comment
on the term HOME for the system folder. Certainly on a large and security
conscious installation under Windows where I have also been using J all J
user's would need to install their J602-user file on a drive other than C: .
I think it is imperative that that process be simple for any new user who
wants to use a system developed in J and would urge the two directories be
confirmed during installation.
Fraser
Ric Sherlock wrote:
---Eric Iverson wrote:
...
Even if it were provided we'd still
require the ability and documentation to change it after the
install was done.
Agreed. As I said, I am satisfied with that for the current version.
The steps are simple and very little
experience is required. If a user had the idea of changing it
they would also have the experience required.
Not so sure I agree with that. Many computer users (well I think it's
not just me!) are "picky" about where their user files reside, and the
concept of separating program and user files is not unique to J. Those
users (and I imagine J's target audience would be well represented in
that group) are generally careful to put user files in the "appropriate"
place when installing programs, despite not having previous experience
in the particular program they are investigating. Not being given that
option, creates an unfavourable first impression.
A default installation where everything just installs without user
intervention (or should that be interference) is desirable, but I
believe it would be an improvement to also give new users some control
so that their first focus post-installation is "Now I am ready to
discover the power of J." not "Now how do I get my user data where I
want it?".
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
