---Kip Murray wrote: > An eventual topic would be a smooth way to transfer work, > favorite programs, and favorite > additions to PUBLIC_j_ from one version of J to the next. >
Firstly note that if you use the "shortcuts" (created by adding to entries to PUBLIC_j_) in your code, the code will not be portable to other users' setups who haven't made the same additions. Also adding scripts to PUBLIC_j_, makes those scripts available in the Library tab in Project Manager. Having said that the forum post below describes a portable way to add to PUBLIC_j_. The code is added to the startup.ijs file in the users' ~config folder which (unless custom specified by the user) is in a separate, independent location to the ~install folders and so won't be affected by the installation of a new version of J. <http://www.jsoftware.com/pipermail/programming/2008-August/011777.html> Installing a new version of J will create a new, version-specific ~user folder. Whether it makes sense to rename/move your old ~user folder to the new one will depend on whether there are any code incompatibilities introduced by the new J version. I *think* my strategy will be to copy my current startup.ijs to the new ~user/config folder to start with, and migrate the rest of my old ~user folder to the new version as I become convinced that there are no incompatibilities. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
