× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Isn't there a procedure wizard built-in already?  If not, I seem to
recollect that Eric's article just used subroutines as an example.  But,
when all was said and done, it just has some Java code that is inserting
stock RPGLE code.  It could be modified to do anything.

I do not recall any mention of a central site.  Perhaps you are thinking of
the old site for Code/400 macros?

Mark



      To:   "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
      cc:
      bcc:
      Subject:    RE: [WDSCI-L] Article on extending LPEX Editor
"Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/08/2003 05:08 PM CST
Please respond to Websphere Development Studio Client for iSeries
<font size=-1></font>





















That worked!  Thanks Mark.

Anybody developed one for sub procedures that I could build off of?  I
don't
do sub routines that much. . .

I seem to remember hearing about a repository for LPEX extensions, anybody
remember where that is?  I looked on the midrange.com site but didn't find
it.

Aaron Bartell

-----Original Message-----
From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx]
Sent: Monday, December 08, 2003 4:56 PM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] Article on extending LPEX Editor



When you are developing a plug-in, it only works in the runtime workspace.
If you want to use it in your default workspace, you need to package it up
and install it.  The process of running it in the runtime workspace does
this for you on the fly so that you can debug your code.

Mark



To:   "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
cc:
bcc:
Subject:    RE: [WDSCI-L] Article on extending LPEX Editor
"Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/08/2003 04:20 PM CST
Please respond to Websphere Development Studio Client for iSeries
<font size=-1></font>





















Good article.  Now I have a question:-)

I went all of the way through the article and got the plug-in working in
the
"second DSc window" but it doesn't work in my existing WDSc window.  ??  I
have closed my existing WDSc window and restarted it but to no avail.  I
looked in the Keys mapping under Workbench in Preferences, but it doesn't
seem that CTL+W is mapped to anything that would conflict.

Any ideas to what I may have changed from the original install that would
make CTL+W not work in LPEX?  This is probably the same problem I was
having
last week where another WDSc employee was trying to help me out - I
couldn't
get the shortcut keys to work for opening a iSeries Source Member while the
LPEX editor was in view, but it worked just fine if the LPEX editor wasn't
the perspective I was in.

Thanks for any info towards a solution,
Aaron Bartell

-----Original Message-----
From: Eric Simpson [mailto:esimpson@xxxxxxxxxx]
Sent: Monday, December 08, 2003 2:57 PM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Article on extending LPEX Editor






There is a new article available now on how to write LPEX Editor User
profiles in WDSC 5.1.  With a user profile, you can scope any user commands
or user actions you have written to a document (instead of being globally
scoped).  The article is in the December edition of eServer magazine,
iSeries edition.

Here is the link:
http://eservercomputing.com/iseries/articles/index.asp?id=795


Eric Simpson
WebSphere Development Studio Client, IBM Toronto Lab, D1/140/8200/MKM
Phone:  (905) 413-3226,  T/L:  969-3226,  Fax: (905) 413-4850,  Email:
esimpson@xxxxxxxxxx

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






_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
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 On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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