Buck:
Go to the editor command line and type in 'help query' for a list of query
command parameters.
I was reviewing that Eric said earlier and found some APIs that look
interesting on a page titled 'RSE iSeries Remote Resource API'. The ones of
particular interest for me are ISeriesRecord and ISeriesField.
Also from the command line, enter 'help samples' for sample editor
extensions. I have played with some of them and I've been able to make them
work but I've not had a chance to try to build my own.
John
----------------------------------------------------------------------
message: 1
date: Thu, 27 Sep 2007 11:44:37 -0400
from: Buck <kc2hiz@xxxxxxxxx>
subject: Re: [WDSCI-L] Eclipse scripting
Eric Simpson wrote:
If you are willing to write Java, then you can call the existing APIs in
WDSC. In the Help Contents under the RSE Developer Guide, there is some
information and an API reference.
Thanks Eric. What I know of Java is just enough to get me frustrated.
I'm not a Java programmer by trade, and I only dabble once every so
often. Without constant use, my meagre Java skills wither on the vine.
David has started a separate list specifically for full scale plug-ins;
that seems an appropriate place for community work on a plug-in.
Speaking to the documentation, I'm looking at
WDSCi
Reference
API reference
LPEX API documentation
I don't see anything about an RPG parser, although I do see one for JCL.
I won't disparage IBM for including a mainframe document parser in an
iSeries client, but it illustrates that I have looked at the
documentation :-)
My last go round with this left me with the impression that I would need
to become a proficient Java programmer in order to write macros/scripts
to automate repetitive tasks. Alas I haven't the time to dedicate to
learning Java because extending Eclipse would be the only place I would
use it! It's an unfortunate set of circumstances. I don't bear a
grudge. Eclipse is written in Java, pretty much for Java people,
although the C++ people have some hope with CDT.
My hope with the scripting tool is to be able to do simple repetitive
chores that are just beyond the ability of 'play/record' but don't
require mastering Java (to build a plug-in.)
One of the things I used to do in Code was 'compress out' subroutines
and conditionally expand the one I was working on. There's a macro
called subzoom.lx that does this. It used a trick/state of the editor.
You do a View>Show>Subroutines and the INCLUDE variable would be set
to 'SUBROUTINE'
The macro did an extract CLASS to see if it was on a subroutine (BEGSR
or ENDSR) It would then set a custom CLASS called SUBZOOM and do an
INCLUDE 'current include setting' + SUBZOOM so we can now see all the
compressed out subroutines as well as the single expanded one the macro
just worked on. The gist of the code was
do
if class
set class 'class' SUBZOOM
next
end
end
show 'include' SUBZOOM
Doing the equivalent in Java seems beyond my ability to wrestle with the
documentation.
http://127.0.0.1:58864/help/topic/com.ibm.lpex.doc.isv/api/com/ibm/lpex/core
/package-summary.html
describes the relationship between a view and a window and seems the
logical starting point. Bear in mind that I have not looked at the V7
documentation for the first time yesterday, but I'm stymied at the very
get-go.
I want to know what language the program that I'm editing is. In ReXX
that was extract DOCTYPE. I could also run on the command line 'query
DOCTYPE' to see what it is.
I can't find a canonical list of properties I can query. Not
surprising, considering all the plug-ins that have their own properties.
How does one navigate through the documentation to find a property
like this one? Or perhaps I'm approaching this the wrong way entirely?
--buck
midrange.com
