--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
