Re: RDi Open a unique member type as a 'DSPF' in screen designer

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 09/01/2018 09:42:28 AM:

----- Message from Paul Therrien <paultherrien@xxxxxxxxxxxxxxxxxx>
on Fri, 31 Aug 2018 12:29:16 -0400 -----

To:

Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] RDi Open a unique member type as a 'DSPF' in screen designer.

I am trying to create a new DSPF source member type to distinguish DSPFs
that have been modified for a GUI tool. The idea is that if someone
goes to change a display file on the IBM I the member type of GDSPF will
tell them that there is a GUI component to this application and please
take the necessary steps to incorporate changes into the GUI tool.

I have a source member type for a display file that is GDSPF. It is a
display file and it has display file dds, but the member type happens to
be 'GDSPF'.

In RDi I am trying to open the file in the screen designer, but the only
option I have been able to get it to open with is the LPEX editor.

I have done the following:

* Created a file type under Remote Systems called .gdspf
* Created a File association for .gdspf for editors: Screen Designer
(default), and Remote systems LPEX Editor
* Created a Pasrer Association to have GDSPF parsed by the dds

parser

On the Remote Systems explorer when I right click on a .GDSPF member the
only 'Open With' option I get is 'LPEX Editor' - I do not see Screen
Designer.

When I edit the source code it does not parse the source as a DDS
display file. It does recognize that a '*' in column 7 is a comment,
and that's about it.

Are there more configuration options I need to set up to handle .gdspf
as a .dspf?

Is it possible to set up a new member type in RDi that get handled as a
DSPF?

Paul

I've been meaning to respond to this, but I keep getting tied up with
responsibilities. Before I give my response, let me qualify that I do not
have knowledge of RDi internals.

My understanding is that the parser associations are for the LPEX editor
not the DDS Designer. There is probably some code sharing, but setting an
association a source member type won't get it to open the DDS Designer.

If someone entered in RFE which would allow that, I would vote for it.

Michael Quigley
Computer Services
The Way International