-- bill lam wrote: > I once studied the source of project manager a few years ago, > from that experience I would rather leaved it unchanged if I > were the maintainer. > > PS. in order to full utilize program manager, the better way > is to study plot or grid package.
Thanks for the reply Bill. I'll take your advice and check out the plot and grid projects. There is always a cost/benefit to any software enhancement, I'm not sure of the "costs" in this case, obviously the maintainer/developer will be better able to assess those. Obviously the Project Manager code is available for any user who wants to edit it. However it seems sensible to concentrate on things that many users would find useful and benefit from. I suppose I'm trying to gauge support from users as to whether my suggested enhancement would be useful ... so far I'm getting the impression that isn't the case! ;-) The benefits as I seem them follow... My suggestions for improving Project Manager came from my experience of using buildpublic_j_ in startup.ijs to include some installed Addon scripts and some of my own utilities to PUBLIC_j_. Now I have a big long list of scripts in the Library tab of Project Manager (likely to get longer with time!). Being able to distinguish which scripts are Addons, which are part of the J system, and which are mine would: * enable the user to find the script more easily. * give the user some idea of how robust the script might be. * potentially allow differentiation, based on source, of which scripts are included vs. linked in the final built script. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
