Yuvaraj Athur Raghuvir wrote: > Aha! So, there has been an explicit decision to not support workspaces. > > Just wondering - given that the learning of J has a lot to do with > experimentation, a whole load of expressions are tried before finalizing on > a form that one wants to store in a script file for later use. And in real > life there are interruptions that means the session has to be shut down > with > an intention of carrying on at a later point in time. > > I thought that preserving the sessions could be one way of getting back to > that context fast. > > Currently my practice is as follows: > 1) Keep a J Session active > 2) Keep a J Script file open > 3) Experiment with real data in the J Session. > 4) When satisfied, transfer the learning & code into the Script file > 5) Save the script file. > 6) Missing: Save the session that has unfinished experiments.... > > Since Step 6 is not recommended, how do you accomplish that part?
It sounds like you are coming from APL, in which case a good starting point is http://www.jsoftware.com/jwiki/Doc/J4APL, in particular see section Workspaces and Scripts. The workspace or saved-session approach is not used in J. Also, you need not create definitions in the ijx window and then copy them to a script once you have them working. Typically, ijx is used only for trivial experimentation. Instead, create your definitions in scripts, and run the scripts. The script files are saved each time they are loaded, so work in progress is always being saved. The J IDE makes working with scripts pretty easy. Project Manager can organize them, and a click of the Test button, or running a test script from a programmed function key, can save all open scripts, then run your application. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
