×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I do not have an issue with the single development library per project thing. I like that it gives me an easier filter for the objects that I am working with. Yes I can change the RSE filters to add individual programs, but I have found that cumbersome, and once the objects get promoted out of the development library I no longer see them. With a project I still have visibility to the specific source objects that I worked on until I delete the project out of mu workspace. I do that when the project is finally promoted to production. I am still using WDSC though. Maybe RDp has improved the filters a bit. There are several things I would like improved in that arena.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----wdsci-l-bounces@xxxxxxxxxxxx wrote: -----
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
From: Joe Pluta
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
Date: 05/22/2011 04:42PM
Subject: Re: [WDSCI-L] Tutorial on RDP i Projects ?
On 5/22/2011 2:49 PM, Jon Paris wrote:
Biggest problem I had with projects was that it enforces a one library model, which made it impractical for at least part of its intended purpose for many people. I suspect that that had a lot to do with folks not adopting it.
Jon's absolutely correct here - the single library design stopped me
dead. I never understood it and couldn't abide by it, so I never really
worked with projects as Phil intended them.
Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.