Oleg wrote:
> It would be useful if interested J users would share their
> order of use cases for J environment.
Mine is probably something like this:
1. Run J and use session as calculator, occasionally
load scripts or addons to use in one-liners.
Nothing is persisted unless to email or forum.
2. Using Project Manager to work with my own projects
3. Make a temp script and edit it running in session
(Ctrl+R, Ctrl+W, Ctrl+E). Then decide either to
paste it to Wiki or to save to ~user.
4. Use a new temp script to paste a snippet or Literate
script from Wiki, experiment with it. Delete on close.
5. Using Project Manager to work with projects that others
have created.
6. Deliberately creating a script by saving to ~user.
Then doing all edits in it.
If it is something that I'm deliberately setting out to do, I would
probably be most likely to use the project manager, other things "grow"
out of playing in the session and with temp scripts. Sometimes my
emphasis is more on working in the session and copying good stuff to the
temp script that I might decide to save to a file in ~user later, other
times I write more in the temp script and the test out in the session
using Ctrl+R, Ctrl+E, Ctrl+W.
Chris wrote:
> > I am a little surprised that temp is being used for files
> that need to
> > be preserved. For such, project manager seems much better.
> There is no
> > problem in setting up a project that contains a bunch of unrelated
> > scripts, and this surely is easier to work with than temp.
> >
Sounds interesting, I think I'll try this approach out and see how it
works for me.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
