Oleg Kobchenko wrote:
It would be useful if interested J users would share their order of use cases for J environment. Here's mine:
My own use is quite different. There are just two choices - if I don't need to keep a script, it will be created in temp, and blown away when I do a periodic clean up of temp. Otherwise, the script goes into project manager.
I have a large number of projects, many of which are simply collections of related scripts, and not single applications. In effect, I distinguish the various cases you listed as belonging to different projects. This is also why I have no qualms about deleting all files in temp.
I see project manager as being a J source code manager, and perhaps the name "project manager" is misleading. I also see it as being part of the J session - rarely do I use J without it.
It sounds like there is a need to better integrate project manager (or its successor) into the session. Incidentally, my goal for the next release (603) is to rework the IDE, specifically the session, debug, and project manager - so suggestions are welcome.
---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
