Setting up the J environment (end of step1), and then adding your own scripts (end of step2) is probably the easiest way to share your software with someone else. If you are personally installing the software on your own machine or someone else's then the installation two step is proabably okay. However, if you are distributing software via the internet or CD then you probably would want to have a single install program do both. I suppose the best way is to write an installer that would do everything the J installer does, and then simply add your own scripts. Well, if that's what is needed I guess one might as well get used to it...
/Joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Björn Helgason Sent: Friday, January 26, 2007 5:58 AM To: General forum Subject: Re: [Jgeneral] Lack of software abstractions 2007/1/25, Joe Tibollo <[EMAIL PROTECTED]>: > > Bjorn and Raul: > > I develop software and have programmed for years in a number of different > languages. My favourite languages, somewhat in order, have been APL, J, > Realizer, Delphi, VB, C#, C++. Of all these languages I have enjoyed > writing complete applications in APL, Realizer, VB, and Delphi. I like J > very much but so far have found it difficult to share software written in > J with others. > > Using script files in J is a lot more difficult than using script files in > VB. Until such time that I can use J script files to build a complete > application, and package it so that I can share it with someone else, > without including the entire J distribution library, J will be a package I > thoroughly enjoy for private use only. I suspect others must feel the same > way. > -------------------------- There are no problems just installing the complete J system and then call your scripts. You may of course spend time scaling it down but what is the point. By having the whole system where your system is running makes life very easy. I recently visited a company I did some J work for ca 10 years ago. They are still running the system unchanged. The system is based on J calling several programs and shuffling data between machines using FTP and in some cases calling a small VB routine I made that sends and receives files in e-mail. Only way I did know at the time how to use e-mail from J at the time. The J scripts start in J runtime called from bat files controlled from a scheduler. I described this system in Toronto on the J conference eons ago. Never had any complaints or even heard much about this for a number of years now. Actually thought it had been replaced by something else by now. There is no J skills at this company whatsoever. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
