|
I will just respond about the workspace issue. If all you are doing is iSeries development, there is virtually no reason to need multiple workspaces. Having multiple workspaces would mainly be of benefit for people that either: a) Have a large number of Java/Web projects and want to spread them out for performance b) Someone like a consultant that has sets of "unrelated" work that they want to keep separate. Mark wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/20/2004 08:52:25 AM: > I've been using it for about 4 months now. I generally like it. However, I > have not made a complete switch. I tend to use WDSCi as a replacement for > SEU and SDA (and WebFacing, which has no equivalent in ADTS). But I tend not > to use WDSCi as a replacement for green screen PDM or ISDB. I'm still much > more efficient with green screen PDM than with RSE, and I find ISDB simpler > than debugging with WSDCi. I'm also not making effective use of workspaces. > It takes me so long to set up and customize views, connections, filters, and > commands that I frequently reuse the same workspace. > > Are there any good articles for someone who has a few months experience with > WDSCi and needs some intermediate or advanced tips to get truly efficient > with RSE, debugging, and workspace utilization? > > Thanks, > Kelly > _______________________________________________ > This is the Websphere Development Studio Client for iSeries (WDSCI- > L) mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l.
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.