> From: "Sherlock, Ric" <[EMAIL PROTECTED]>
>
> ---Oleg Kobchenko wrote:
> > > From: "Sherlock, Ric"
> > >
> > > buildpublic_j_ 0 : 0
> > > tara ~addons/tables/tara/tara
> > > zip ~addons/arc/zip/zfiles
> > > ziptrees ~addons/arc/ziptrees/ziptrees
> > > csv ~addons/tables/csv/csv
> > > )
> > >
> > > Another bonus is that you can then refer to these addons in
> > > the session as you
> > > would other defined library scripts. Eg.
> > > load 'tara'
> > > open 'zip'
> > >
> > > Note-To-Self: other users may/will not have the same addons
> > > defined as me -
> > > something to keep in mind when I post to the forum! In that
> > > situation it is safer to use the full JAL format. Eg.
> > > load 'tables/tara'
> > > open 'arc/zip/zfiles'
> >
> > Yes it absolutely true that it is better to use canonical way
> > to load addons
> > load 'tables/tara'
> >
> > All other ways are non-portable and not recommended.
>
> Just to be clear, I was not suggesting the use of the "load 'tara'" format in
> scripts, I agree that in that case it is safer to use "load 'tables/tara'".
> However for interactive use in the session, there is nothing wrong with the
> simpler format. It seems to me that there is no advantage to the user of
> having
> to remember both the category and the name of the addon in order to reference
> it
> - but we have had this discussion before! :-).
Still even in session, it's not too much to type 'tables/tara'.
But it provided canonical way, same the addon referred to speech.
It is one of the design feature of JAL. It is well defined in
the documentation.
> > To get the main forlder for addon:
> >
> > jpath'~addons/tables/tara'
> > D:\stuff\j602\addons\tables\tara
> >
> > We will need to discuss how to integrate addons in
> > Project Manager (PM).
> >
> > One aspect of PM build process: combining external libraries
> > into one file, AFAIK, would probably be better to replace with
> > the approach of "referencing" standard base and addon library.
> > So instead of a one file, to create a target folder structure
> > with external libraries in their place. And only internal scripts
> > would be then combined into one file. Maybe there is already such
> > build "mode" in PM, I don't know. But such approach seems to
> > be very optimal and portable. Code is not repeated and result
> > can easily be incorporated into existing J installations, providing
> > version compatibility.
>
> If I understand you correctly, then yes this is already possible in the
> current
> PM. You can decide whether the project source and/or the project libraries
> should be included or required (referenced) in the final built script. The
> syntax PM uses for referencing was what I was referring to above. If you
> select
> a Library script to be used in your Project using the Library tab and specify
> in
> the Project|Build Options dialog to "require" (the default) rather than
> include
> library scripts, then the syntax the PM uses to reference the library script
> is:
>
> script_z_ '~addons/tables/tara/tara.ijs'
>
> This syntax and functionality is portable and has the benefits you describe.
>
> One thing that I saw as an advantage of my Library Request on the wiki was
> that
> you would be able to independently choose to include vs require, project
> scripts, addon scripts and base library scripts (see mockup of Build Options
> dialog).
Still that's not what I described:
> > So instead of a one file, to create a target folder structure
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.
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
