-----Original Message-----> From: programming-bounces at jsoftware.com
[mailto:programming-bounces at jsoftware.com] On Behalf Of Kip Murray> Sent:
Friday, September 05, 2008 7:07 AM> To: Programming forum> Subject:
[Jprogramming] Working with J> > Where does a beginner learn good J work habits?
Good habits depend on what you use J for. Speaking of presonal experiences
andpreferences, here is what I converged to.
I must mention that I use J almost exclusively on small "projects" where
thegoal is "get an answer", rather than "create an application which is
featurerich and user friendly".
> To begin, how to use ijs and ijx windows, how to save your work at the end of
> a session and resume it at the next.
According to J developers (I cannot quote, the message was postedseveral years
ago), .ijx windows are not intended as multiple sessions, or evenas multiple
"logins" into same session, so you should not have more then one.On the other
hand, if you are using gui frontend, you must have at least oneopened.
I personally do not use .ijs windows at all, mostly because I am used
todifferent text editor, but also because sometimes J freezes and you may
looseyour changes if you were making them in .ijs window. On a plus side,
.ijswindow has some integration with J session, like "run line", "run
window"shortcuts, form editor, Ctrl+F1 keyword help and, possibly something
else. Iremember missing these features for some time after I made a switch.
Iimplemented "run window" in the following way: when I save file in my
editor,it puts "load '<full_path_to_current_file'" string on a clipboard which
I canthen paste and execute in .ijx. Ctrl+F1 is usually no good anyway, and I
do notmake forms too often, so the only thing which remains missing is "run
line".(If anyone has good solution how to run J line from vim, I would like to
seethat)
I keep all my J files in a directory structure which is completely separatefrom
J subdirectories. The only change I make in new J configuration isan alias to
this structure.
Almost all of my projects are single files and I go to certain length of
effortto keep it this way. For example, when I need to use verbs from other
projector even non-standard library, I prefer to copy them into project rather
thenrequire library file. This gives at least some assurance that the file
willexecute some time later.
Since all projects are single files, RCS is perfectly suitable as
versioncontrol mechanism, when need in version control arises.
_________________________________________________________________
See how Windows connects the people, information, and fun that are part of your
life.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093175mrt/direct/01/----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
