|
> From: Mark Phippard > > Presumably you do not wish to use this tool to edit source directly in > production. That's pretty presumptuous of you! Seriously, people have multiple shared development libraries, too. We always did. We didn't have separate libraries for every individual programmer's tasks, since often they were working in a team on a single task. > iSeries Projects allow you to pull in source from multiple > libraries, it is just that it will only push it back to one library - a > development library. And who thought this was a good idea? Why should Vern have to pull from one place and return to another? Who thought it was their job to tell him how to do his job? > Is there no way to make that work in your environment? Overriding question: why should he have to? The tool should help the programmer, not dictate his actions. As soon as the tool starts telling me what to do and when, it is no longer a tool, it is a set of rules, and it will usually have problems outside of the laboratory. Trust me, I've dealt with this time and again. That's why every product I've ever designed lets you decide where your libraries are and what they are used for. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.