|
Joe Pluta wrote: Me, I'm talking about having different filters for different applications within an application suite, as well as for different versions for historical or comparative purposes, so I need lots of filters in one connection. Joe, I've been using the connection per project for some time now and one of the things I really like is that I can easily open the connection for an old project and see what objects were used. It makes going back in time much easier. I also think it simplifies the clutter of multiple filters. I do use filter pools, but my main connection to our development box is still cumbersome to navigate. It contains filters for each of the source files in my library (27 files, each for a different application + personal development/historical files) filters for members of my development team, and filters for our production source. Each in a separate pool. I much prefer a project connection where I can filter just the source files I will need. It's a much smaller list to wade through. Because connections are the top level of RSI it's easy to find things if the names are descriptive. Just my $.02 Rick
-----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta Sent: Thursday, July 06, 2006 10:15 AM To: 'Websphere Development Studio Client for iSeries' Subject: Re: [WDSCI-L] Enhancement Request Oooo scary. The options under right-click/New on the iSeries Objects branch are completely different depending on whether the Show Filter Pools option is selected. I have to go down another level (to the filter pool) to get all the options I normally see under New at the iSeries Objects level. I don't know whether I like this behavior or not, but I guess it makes sense. It definitely can make it a little confusing. The connection per project approach makes a lot of sense if your initial session setup for each project is different; by using the initial library list or initial program on the connection you can make sure your connection is properly configured for each project. Me, I'm talking about having different filters for different applications within an application suite, as well as for different versions for historical or comparative purposes, so I need lots of filters in one connection. So yes, I'd still like the full directory structure. Joe
Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
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.