RE: Re: Re: Opening a member without filters

>Even though I have the filter defined, when I select the member it takes it
a bit to load.
For the record I have satisfactory download rates for the displaying of
source members in LPEX, it is just to display a list of source members that
is time consuming.  IMO, WDSC 5.0 seems to _open_ members faster than CODE,
but that is just my perception (which is what counts right:-).  It
_definitely_ opens them faster the second time you go into them!

Aaron Bartell

-----Original Message-----
From: Paul Pendleton [mailto:pnpendleto@xxxxxxxxxxxxxxx]
Sent: Tuesday, May 27, 2003 1:12 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Re: Re: Opening a member without filters


It is the same with me.  Even though I have the filter defined, when I
select the member it takes it a bit to load.  Though CODE/400 does not load
as fast as SEU it does work quickly enough to be acceptable.  My contention
is if CODE/400 can load the files that quick then WDSC should be able to!
It was touted as being as fast as SEU.  I really wanted this to be so,
because I love the features in the WDSC and CODE/400 for that matter.  We
are just very disappointed in the performance.  We can not talk management
into buying new computers so that is out of the question.  Based on what you
have said it doesn't really matter if you have a faster machine.  I just
want speed!  Everything else would fit into place if it was faster, even the
loading of the member.

--
PAUL PENDLETON
"Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>
wrote in message
news:2497EFFF2CEDF746A51832AD269D45D947E2BD@xxxxxxxxxxxxxxxxxxxxxxxxx
> I am running P4 2.0Ghz 512MB with plenty of HD space and I also sit and
wait
> for a couple minutes to see the list of source members.  I don't know how
> many members you do your tests on, but I have 5000+ source members in our
> main production library which I am guessing is quite common in the iSeries
> community.  Even if I create a filter for each source physical file
> (QDDSSRC, QRPGLESRC, QPNLSRC, QDSPSRC, QSRVSRC, QMODSRC, etc) it still
takes
> more time than I have - I can go back to the green screen and get it near
> immediately.
>
> I am guessing the reason it is slower than PDM is because PDM probably
isn't
> loading all the members from a source physical file - it probably does it
> page by page.
>
> Aaron Bartell
>
> -----Original Message-----
> From: Paul Pendleton
[mailto:pnpendleto@xxxxxxxxxxxxxxx]
> Sent: Tuesday, May 27, 2003 12:26 PM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: [WDSCI-L] Re: Opening a member without filters
>
>
> Well different working environments do call for the ide being capable of
> this.  As a matter of fact there are several out there that do.
>
> In the environment that I have worked in there always comes a time where
you
> need to pull up a source quickly to look at a problem.  You do not want to
> have to go through the "filtering process".  In my case I want to hit a
hot
> key which splashes a screen up with the last keyed entry.  This means just
> keying the member name in and slapping ENTER.  This gives me all the
> functionality of the editor without having to save a filter or anything
like
> that.
>
> It is simply for those quick fixes.  You said you wanted to hear if the
> loading of a filter is slow.  Well you have one right here.
>
> I am running on a 700mhz machine with 512mb of RAM.  I have plenty of disk
> space.  It takes about a minute(haven't timed it exact) to load the source
> files in my test library.  If I want to open a file quickly I can not use
> this new WDSC.  It takes to long to do that.  So I have to resort to the
> green screen(boring).
>
> Or, I go to CODE/400 where I have written a little java lpexlet for a open
> file dialogue which has some default values for the Server, library, and
> file.  It retains the last keyed member name value.  You just key in the
> member name if it is different and slap ENTER.  Takes about 10 seconds at
> the most(according to how fast you type).
>
> My IDE should handle the quick little projects or fixes and the big time
> consuming projects.  I appreciate and look forward to you improving WDSC
to
> do this.
>
> Thanks!
>
> --
> PAUL PENDLETON
> "Phil Coulthard" <coulthar@xxxxxxxxxx> wrote
in
> message
>
news:OFBD5519C9.A71C5C5E-ON85256D33.005B8EA5-85256D33.005CDB0E=r0JSptLoWH3ZZ
qz5F8Q3Hw@xxxxxxxxxxxxxxxx
> om...
> > "Is there any way to open a member on the as400 without creating a
> > filter?"
> >
> > No, there currently is no way, but we will note it as a requirement. It
is
> > a bit against the
> > grain of an IDE, however. Note that an older-style open dialog would
need
> > to prompt for
> > the member's library, file and member name, which is exactly what the
Work
> > With Members
> > filter prompt asks for. The only difference is it requires one more
> <enter>
> > to get to the
> > 2nd page, and then a name to be entered, and then a double click on the
> > member once
> > you see it. The good news is that you only have to enter these few extra
> > keystrokes once,
> > after that you simply double click on the member forever more ... you
> don't
> > even have to
> > expand the filter again unless you collapse it. So, it saves you typing
> the
> > library, file and
> > member every time you wish to open it. Further, it also gives you access
> to
> > the other
> > right click actions like rename, copy, paste and delete.
> >
> > For these reasons, IDEs tend not to have actions for directly opening
the
> > editor without
> > going through a resource tree of some kind.
> >
> > Someone commented on the going through the libl being slow. If there is
a
> > performance
> > problem in expanding your libl then we'd like to hear about it. In
general
> > though, we have
> > such exhaustive filtering capability precisely so that you don't have to
> > drill down to the member,
> > much as you would rarely drill down from WRKLIBPDM in order to edit a
> > member, although
> > you can. That being said, have you noticed the Expand To action on a
> > library? It will allow
> > you expand it to show just source files, which might help if you do like
> > drilling down versus
> > directly accessing.
> >
> > Phil Coulthard, iSeries AD,  IBM Canada Ltd.
> coulthar@xxxxxxxxxxx
> >
> > _______________________________________________
> > 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.
> _______________________________________________
> 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.