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
WebSphere Development Studio Client for iSeries
IBM Toronto Lab
Phone: (905) 413-4476
IBM internal:  IBMCA(yantzi)  -  Internet: yantzi@ca.ibm.com




                      Vernon Hamberg
                      <vhamberg@attbi.c        To:       wdsci-l@midrange.com
                      om>                      cc:
                      Sent by:                 Subject:  [WDSCI-L] Projects 
questions
                      wdsci-l-admin@mid
                      range.com


                      10/09/2002 08:51
                      AM
                      Please respond to
                      wdsci-l





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

Would you like to see a challenging little arithmetic puzzle
that might get you or your kids or grandkids more interested
in math? Go to <http://cgi.wff-n-proof.com/MSQ-Ind/I-1E.htm>

Sillygism--

Something is better than nothing.
Nothing is better than a ham sandwich.
Ergo
Something is better than a ham sandwich.

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing 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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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