I have seen how, in WDSCi, you can relate an editor to a source file.
However, I would like to use the Code Editor (which I find much more useful
than the LPEX editor) as my DEFAULT.  That way when I double-click on the
source file, the Code editor would pop right up, instead of having to
right-click and choose it.  Is this possible?

Ric LuBell

-----Original Message-----
From: wdsci-l-request@midrange.com [mailto:wdsci-l-request@midrange.com]
Sent: Sunday, October 13, 2002 1:00 PM
To: wdsci-l@midrange.com
Subject: WDSCI-L digest, Vol 1 #45 - 1 msg

Send WDSCI-L mailing list submissions to
        wdsci-l@midrange.com

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/cgi-bin/listinfo/wdsci-l
or, via email, send a message with subject or body 'help' to
        wdsci-l-request@midrange.com

You can reach the person managing the list at
        wdsci-l-admin@midrange.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WDSCI-L digest..."


Today's Topics:

   1. Re: Projects questions (Vernon Hamberg)

--__--__--

Message: 1
Date: Sun, 13 Oct 2002 07:49:37 -0500
To: wdsci-l@midrange.com
From: Vernon Hamberg <vhamberg@attbi.com>
Subject: Re: [WDSCI-L] Projects questions
Reply-To: wdsci-l@midrange.com

Thanks, Don

1. I guess I want the CODE editor in the popup list, just as it is in the
RSE perspective. The internal LPEX editor is not adequate as a replacement.
(I know, you're getting there).

While I'm in this area, I notice that when I start a project, it asks for
what connection to use. But once in the project view, I couldn't see any
reference to that. Also, it does not use the filters from the connection
when importing something into the project. (I'm glad to see that the entire
connection list was available.) not having the filters makes the import
function less pleasant, shall we say?

2. The build command concept sort of fits us. We do build entire products
with one command - but only the 400 part. We use Delphi, and that part is
not done with the 400 build command.

I'm probably reading my hopes into the design of projects, so here goes.
There is linkage to cvs for versioning, right? We can import source from
multiple connections, right? It promises so much, that it's irksome not to
have some of the simple things in the same environment. I mean, a project
can be a fix - not all the components of a product will be included. Again,
you already have the ability (or concept) of storing a create (build)
command with each source file. Give us a Build all option for a project.
Again, Visual Studio does this sort of thing, IIRC.

3. I meant building individual objects - CRTPGM, CRTxxxMOD, CRTBNDxxx, etc.
I was hoping for the ability to create individual elements of a project -
pick a CRTxxxMOD. Maybe you say that's for ACMS or TurnOver. But you
already store, in the RSE perspective, create commands with individual
objects.

4. Cool.

Thanks again

Vern

At 09:47 PM 10/9/02 -0400, you wrote:
>Vern,
>
>1.  Yes, the CODE editor is registered with Windows (the system) as an
>editor for .h files when the product is installed.  For editors within the
>workbench we only associated LPEX with the predefined SEU/PDM member types
>which does not include H.  If you create a member called abc.rpgle in your
>iSeries project you will see the LPEX editor as an option.  For your .H
>files or any others you come across that are not associated with the LPEX
>editor you can add the associated by:
>
>a.  Open the preferences dialog (Window->Preferences)
>b.  Expand Workbench and select File editors
>c.  Here you can define the file type (*.h) and associate the LPEX editor
>with it.
>d.  Now you should see LPEX in the Open With menu item for your .h member.
>
>2.  iSeries projects are closely tied to native iSeries development, just
>like Java projects are tied to Java development.  The build command you
>give is supposed to compile your members, create any data areas / data
>queues you need, etc...  But all related to your native iSeries RPG / COBOL
>/ C / C++ development.
>
>3.  By create do you mean creating new source files and members?  You can
>do this by right clicking on the project and using the New -> iSeries
>Source Physical File and iSeries Member wizards.  These create local source
>physical files (a folder) and members (files.)  When you "push" the changes
>to the iSeries the actual source physical file and member get created.
>
>4.  We will add this to our requirements.
>
>Thanks.
>
>Don Yantzi
>
>I have WDSC v4 installed, sp2 applied.
>
>1.  When I right-click a source member in a connection from the RSE
>perspective, Open with... gives me both LPEX and CODE editors. If I put the
>same member into a project and right-click, Open with... has Default text
>and System editors listed. The former is not even the LPEX editor, the
>latter gives me the CODE editor for, in the test case, a .h include file. I
>assume this is because CODE was made the associated app at installation.
>
>2. When creating a project, it asks for an optional build command. But I
>envision cross-platform content - iSeries source, Delphi, Word documents -
>so a single build command does not do.
>
>3. How are creates handles, anyway? Seems like no option to do so in a
>project perspective.
>
>4. When I want to populate a project, I see the RSE perspective sitting
>there, just begging for drag-drop functionality. Please!
>
>Regards
>
>Vern Hamberg



--__--__--

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
digest list
To post a message email: WDSCI-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l
or email: WDSCI-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


End of WDSCI-L Digest


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 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.