From: Buck Calabro <kc2hiz@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Date: 16/07/2014 10:15 AM
Subject: Re: [WDSCI-L] Porting workbench settings from WDSc to
RDi 9.1?
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>

On 7/15/2014 5:04 PM, Vernon Hamberg wrote:
Hi Buck

I have to reply on the use of the outline.

If you want to find a procedure, I see at least 3 ways to do it -

1. Ctrl-F, type in proc name, Alt-A to get them all, then find the
procedure itself
2. Right-click and filter by procedures, then find it and click on the
plus sign to open it
3. Go to the outline, open the procedures item, click on the one you
want and you are there

Assuming I'm looking for a procedure named PROC1, this works great:
findText regularExpression d.*proc1.*pi

Now that I've found it, I might Ctrl-2 to open a second editor pane.
Now I can scroll around the calculations and keep the PI right in front
of my eyes. The idea being that I don't have to keep mousing over to
the Outline to click (and jump) here, then click (and jump) there - it's
always 'there'. I tried jumping around with the Outline when I needed
to change a DS and I could not find a rhythm.

The crazy part about this is that I spent 20 years flipping through
green bar printouts to find things like this. You'd think it would be
an easy transition to use an Outline, but I... I think I'm mouse-phobic
or something!

How to use the outline view using only key strokes

In the editor (has to be 9.1)
Ctrl-F7 - Enter (takes you to the outline view)
Shift-Tab (puts focus on the filter entry field of the outline view)
PROC1 (as you type each char, the outline view is subsetted to declarations
containing what you have typed so far. )
Tab (focus in the tree view)
Arrow down to the proc (only decl there)
+ (expands to show references)
Arrowing up and down will highlight the reference you want in the editor

All are good ways to do it - the outline adds things like where
something is used - similar to #1, where you'll see all references to

Ish. I created the following brand new source member to test my memory:

0100 /copy qrpglesrc,stdhspec
0400 // break out the first 8 bytes for comparison
0500 dcl-ds *n;
0600 UADDR1 char(30);
0700 UADR8 char(8) pos(1);
0800 end-ds;
1000 if uadr8 = *blanks;
1100 dsply uaddr1;
1200 endif;

The Outline View shows this:

Data Structures
11 (M)

11 (M)

The compiler cross reference shows this:

Field References (D=Defined M=Modified)
UADDR1 000600D 2000012M 001100
UADR8 000700D 001000

When I tried to click on the Files section I got a 'press Refresh'
notice. Even though I DO have the 'Update Outline View' preference
enabled. [1] So I did.

The 'Update outline view' preference means that the outline view is updated
on every keystroke. Since that has to be pretty responsive, we only look
at the what is in the editor. Getting host definitions takes longer, so we
let you hit Reference to let us know when you want to get that information.
If you change the host DB files, hit Refresh again to get the latest
definitions. Clearly this does not happen that frequently.

Now here's what the Outline View looks like:

6 (D)
11 (M)

Data Structures
2 (D)
11 (M)

2 (D)
11 (M)

I appreciate that I can use the Outline to drill down into a file and
see what fields are coming in to the program, but I'm not sure that I
appreciate seeing one set of 'references' under 'Files' and another,
different set under 'Fields'.

Clicking on the field name does different things depending on which
section of the Outline I'm in. In Files, I'm taken to the F-spec. The
utility of that completely escapes me, and I have a good imagination. I
just drilled down from the File to the Record Format to the Field and
the Outline wants to take me to the F-spec. OK, so... don't click that
field name.

- some people want to know where this file is referenced and exactly which
fields within it are referenced where
- others just want to know where the fields in the RPG name space (defined
in many possible different ways) are referenced
So we provide both
The field under the File was defined by the file, if you want references
to it, expand it and you will see the other definition

Clicking on the field name in Fields or Data Structures takes me to the
other definition line, the Data Structure. Which makes sense, but why
isn't the implied definition made explicit in the list of references?

Not sure what is missing here. You see the definition reference on
line 2 which comes from the file, and clicking on UADDR1 will take you
to the Data Structure definition which is the main explicit definition.
2 (D)

outline also gives you direct view of fields in files and of keys and
keylists and data structures and all - I find it invaluable.


It does help, Vern. I think I myself find the value proposition much
higher when I'm in exploratory mode - looking at some monstrous thing
I've never seen before and I'm trying to suss out what's what.

[1] As a programmer, I very much understand that there's a technical
distinction between fields in the edit buffer and fields in the 'Files
cache'. The point is that even with 'update Outline View' enabled, you
need to remember to refresh if you've added or removed files. Is there
anything else? Auto-copy members?

As described above, any requests that would require a trip to the host to
are only done on demand when you hit refresh. Yes that includes updated
copy files.

On 7/15/2014 3:56 PM, Buck Calabro wrote:
On 7/15/2014 4:08 PM, Koester, Michael wrote:
Thanks for that suggestion, Buck.
Curious though -- is the evolution of RDi so great between WDSc and
today that many of the preferences from then don't fit today? I'm
anticipating that some (or many?) preference labels may have
different names now?
With the greatest respect for the team, RDi is very similar to WDSC,
especially if you are an RPG/DSPF/CL programmer like me.

I don't do any webbish work, so there may be some wonderful stuff there
that I just never had a need for. This bears repeating: the way that I
work, I may never use a feature that others simply cannot live without.
The Outline View comes immediately to mind. I just can't seem to find
the value proposition. The point isn't that it's bad; it's just not the
way I work.

I hope that others jump in and add comments about post-WDSC features
they really like. It'll do me good to give some stuff a whirl too!

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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.