There are a number of ways you can proceed
with making an addition to the existing system library:
a patch or addon script, or an enhancement request.
Patch or Addon Script
is a script which "overrides" existing library code:
- identify the changed definitions, use a diff tool
between original file(s) and changed files
- place whole changed definitions into a separate script
- place script into ~addons/system/misc/script_name.ijs
- provide loading mechanism in startup.ijs or just end of
profile.ijs, as one line of code
load '~addons/system/misc/script_name.ijs'
- supply description, installation, loading notes
in the script comments
- publish script in
http://www.jsoftware.com/jwiki/Scripts
Examples
http://www.jsoftware.com/jwiki/Scripts/WD_Spy
http://www.jsoftware.com/jwiki/Scripts/Viewmat_Spy
http://www.jsoftware.com/jwiki/Scripts/Session_Utilities
Note: for longer definitions, it's better instead of
duplicating most of existing definition body to make a wrapper
and save original definition, substitute existing definition with yours
and call the saved original if necessary.
See http://www.jsoftware.com/jwiki/JAL for an idea of
Addons folder layout. This is an ongoing effort subject
to changes, but the suggusted path to store you script
is likely to stay.
Enhancement request
is a set of changes to existing libraries submitted
for applying in next versions of libraries
- identify the changes
- describe them in terms of new or changed lines of code
using your discretion in terms of format, etc.
- submit to J Wiki System/Library/Requests
Examples
http://www.jsoftware.com/jwiki/System/Beta/RGB_Bitmap
http://www.jsoftware.com/jwiki/System/Library/Requests
--- Jose Mario Quintana <[EMAIL PROTECTED]> wrote:
> > On Behalf Of Oleg Kobchenko
> > I think I failed to get #2 accross, which is the main thing:
> > not amount of K or if it's attachemnt or wiki.
> > There is no need to modify an existing (system) file.
> > Instead, all the changed definitions are collected
> > in a small separate file, which is loaded at
> > startup.
> >
> > The advantages: it's small, it's visible what's
> > changed, it's manageable.
> >
> > Suppose, another user made a different set of enhancements
> > to the jijs.ijs file: in your scenario we would have
> > two different changed files. How would we go about that?
>
> I have customized the JIJS.IJS files for both the PC and the PocketPC
> versions and it is indeed a pain to maintain them over time. Your
> suggestion looks like a winner but I am afraid I still do not know how to
> proceed. Can you point me to the relevant information or documentation?
> Failing that, can you provide a simple example?
>
> Thanks in advance.
>
> >
> >
> > BTW, the enhancement to enable labs of PocketPC is
> > a great idea. Running labs in that environment is a
> > convenient and useful thing.
> >
> >
> > --- Jose Mario Quintana <[EMAIL PROTECTED]> wrote:
>
>
> > > and I do not know how to generate a patch that would automatically
> > produce a
> > > useable patched file either. How do you do that?
> > >
____________________________________________________________________________________
Get your email and see which of your friends are online - Right on the New
Yahoo.com
(http://www.yahoo.com/preview)
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
