|
That pop-up window is perfect! Now if we could get a shortcut to it. I very rarely have the Table View open. Thanks for the tip Mark, Aaron Bartell -----Original Message----- From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx] Sent: Friday, June 20, 2003 10:12 AM To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] Launch WDSC 5.0 Lpex from PDM I was going to whip up a plugin that let you open a dialog where you could just type in the member info and open it in the editor, but after looking around I found that IBM basically already provides the feature in a much better way. They key is to use the new iSeries Table View. You can open this manually if it is not already open by doing Window -> Show View on the menu bar. On that view, there is a little selection widget on the top right corner. It brings up a drop-down menu with a Work with option. There are then sub-options for libraries, members and objects. If you select members, you can basically type in anything you want, including wildcards. The more you give it the faster it works. Now it is a 2-step process since it just shows the results in the table, and you then have to double-click to open it, but I think it is better than what I would have done because there dialog is very nice and remembers everything you have ever typed in it. Give it a try. Mark MEovino@xxxxxxxxxxxxxxxxx Sent by: wdsci-l-bounces@xxxxxxxxxxxx 06/20/2003 10:49 AM Please respond to Websphere Development Studio Client for iSeries To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> cc: Subject: RE: [WDSCI-L] Launch WDSC 5.0 Lpex from PDM Aaron, Have you played around with filters that use wildcards to narrow things down even further. In our shop, we store nearly all of our source in one library, in three PF-SRC's (QCLSRC, QILESRC, QDDSSRC). We use two character prefixes to keep related programs together. So if I'm working on the "DX" programs, I create a filter using Work With Members to show me all the DX* members in those three files. I can keep all my related stuff organized the way I like it, and it's fast because it's only a few members. Meanwhile, everything is still the same for our PDM/SEU users. Mike E. "Bartell, Aaron L. (TC)" To: "'Websphere Development Studio Client for iSeries'" <ALBartell@xxxxxxx <wdsci-l@xxxxxxxxxxxx> orp.com> cc: Sent by: Subject: RE: [WDSCI-L] Launch WDSC 5.0 Lpex from PDM wdsci-l-bounces@xx drange.com 06/20/2003 10:29 AM Please respond to Websphere Development Studio Client for iSeries I guess I would want to gain all of the new things in WDSc which CODE doesn't have(code assist, outline, etc) without having to pay the penalty of going to a library that may not be used that often, and hence wouldn't already have a filter created for it. I guess the current solution would be to create intuitive filters to save the most time possible. To speed things up a little more I created a filter for just one of the source physical files (mylib/qrpglesrc). Now it only takes about 3 seconds to load (1300 source members) and that is after a fresh reboot of my PC. This will work, but if I have 6 - 7 production libraries and 4 environments (development, testing, QA, production) in each one of those that means I will have to create roughly 28 filters. Granted I don't go into testing and QA nearly as much as development and production, but it still takes some doing. IMO, it should be just as fast to go into a library with the Expand To option and select Source Files, but that took 2 minutes and 20 seconds. It appears that it reads through every object in that library, because I have other libraries with very few objects but the same amount of source file's that take a fraction of the time to load. Maybe that is where the code needs to be corrected - could a different "logical file" be used when the Expand To option is taken? Do-able, but just a little annoying. Aaron Bartell -----Original Message----- From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx] Sent: Friday, June 20, 2003 8:33 AM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Launch WDSC 5.0 Lpex from PDM Aaron, The way I see it, if you do not want to use RSE and the things provided with WDSC, then why would you want to use the LPEX editor? I would think they would just continue to launch Code/400. Hopefully, by the time Code/400 is no longer supplied all of the functionality within WDSC would be good enough to make them want to use RSE and the like. To answer your question, I am pretty sure there is no way to trigger WDSC to open a member from outside of WDSC. Mark "Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 06/20/2003 09:20 AM Please respond to Websphere Development Studio Client for iSeries To: "'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx> cc: Subject: [WDSCI-L] Launch WDSC 5.0 Lpex from PDM I have a co-worker that has used CODE and is now working into WDSC 5.0. He has asked me if there is a way to start an Lpex editor tab in the WDSc 5.0 workbench from PDM. I know this isn't the mindset that WDSc supports, but it would allow you to get to your members quickly rather than wait for 1-2 minutes for a source file with thousands of source members to load. I can't see a way to do it, but am wondering if I am missing something. TIA, Aaron Bartell _______________________________________________ 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. _______________________________________________ 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.