Hi. I even go further.
I only distribute 3 files: J.EXE, J.DLL, and one HUGE IJS file. This means that the requires are useless since I really need all the references inside the IJS file. Of course, this is now without its problems. Lately, I encountered problems with both the strings and primitives library declaring "cut". I sorted this out by moving the library reference in the Project Manager to another project. This way of distribution is really handy. Our .NET application is using the SmartClient framework and automatically downloads "required" files at runtime. My module is actually the lightest one: 1 .NET DLL (with the IJS file embedded as a resource), J.EXE and J.DLL. My whole module downloads in less than 2 minutes on a DSL connection. :) r/alex -----Original Message----- From: [EMAIL PROTECTED] on behalf of Sherlock, Ric Sent: Sun 8/17/2008 10:02 AM To: Programming forum Subject: RE: [Jprogramming] Building with a REQUIRE in Project Manger --Oleg Kobchenko wrote: > Still that's not what I described: > Sorry you are correct, I didn't read carefully enough! > Currently there are only two ways: all included or all > referenced. And when > referenced it assumes full J is installed. My idea is like > reference, but > it will recreate a local folder structure with only necessary files. > The advantages is that it preserves the integrity of folder structure, > allows possibly to combine a few apps like that, etc. This will also > work nicely with addons, because there it's not always clear which > files are needed. So this would be similar to the approach of the Application Distribution Installer, but would distribute even less of full J installation, namely only those scripts/components necessary? Given that the Application Distribution script has already dropped big parts of the full J install (~help, ~examples), there may not be that much opportunity for reducing the installation size. Maybe ~system/extras/labs could also be omitted, and the user could specify which tools were necessary? After that it seems to me only small gains are possible. > I ran the Application Building lab. It is very instructive. > But maybe there needs to be or already is, a guide that shows > what to do next after build to produce an installation and how > it is deployed, etc. Then it would show how to build a multi-platform > solution. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
