[WDSCI-L] Getting a little better with RSE

[Kelly Cookson <KCookson@xxxxxxxxxxxx>]

Thanks for all the tips last week on improving efficiency with RSE. I've had
a chance to read a few of the references and am already getting results. 

The two biggest things that have helped me are these...

First, I had taken a strategy of finding ways to minimize the startup time
of WDSCi. Bad idea. It lead me away from from creating and resolving filters
for the source physical files that contain most of our code. Having these
filters is really helpful, especially with the ability to type text on the
tree and be positioned to a member.  I have also moved the Properties view
to the right side of the perspective so I can see the full text of members
without having to scroll. Plus the filters let me copy and rename members
with a couple of mouse clicks. Having these capabilities is well worth the
6-9 minutes required to start WDSCi and resolve all my source file filters
by clicking on them.  I've just made the longer startup part of my morning
routine.

Second, I needed to start thinking about RSE as a *perspective* and not get
so locked into the Remote Systems view. I definitely use the Remote Systems
view as described above.  But sometimes the iSeries Table View is a quicker
way to get what I want, and sometimes using CTL+SHFT+N is the quickest way
to get what I want. There's not one way of doing things for a reason. 

I find having two perspectives best suits my needs (though everyone will
differ). I have the RSE perspective, which I now primarily use to copy,
rename, browse, and open source members and set up test libraries. This
perspective is pretty much filled by the Remote Systems, iSeries Tables, and
Properties views. I keep a sliver of LPEX at the top just to see what
members I have open. The other perspective is a customized perspective with
only the LPEX editor and the Outline view.  I use this perspective to code
and complile (when the compile is finished a new view automatically appears
with all the compile errors, and clicking on an error message takes you to
the offending code).

This is getting nice!

Thanks,
Kelly