Re: Customizing WDSC

[qsrvbas@xxxxxxxxxxxx]

wdsci-l-request@xxxxxxxxxxxx wrote:

> "What I really want is to extend the editor and only have to push a couple
> of buttons.  One to get the data, the other to output the formatted
> records."
>
> We raised the absence of a Rexx-type facility with IBM way back when the
> first release of WDSC came out - but it has never happened and since we now
> on V7 I doubt it ever will.  They have this weird notion that we'll program
> the extensions in Java I guess!
Like others, I can't quite catch on to how IBM is putting things 
together. My WDSc installs have had an implementation of Object REXX 
built in to them for some time, but it hasn't been clear what good 
that is. (I.e., I have used it to run a couple ooRexx programs that 
were simply easier to write on my PC than on any of our AS/400s due 
to what the programs needed to do; but I don't know how WDSc uses 
the rexx.exe itself, if it does.)
But one thing that keeps me thinking is that Object REXX _can_ 
interface with JAVA functions. The free open-source BSF4Rexx (Bean 
Scripting Framework for ooRexx) utilities seem promising.
Maybe it's a matter of loading BSF4Rexx and just knowing what 
methods to call from ooRexx. Both BSF4Rexx and Object Rexx 
originally came out of IBM and were turned into open-source.
Naah... can't be... Buck would've had that mastered by now.

Of course, I'm not clear at all how to create a 
'record/playback'-function that would capture key-strokes entered 
into a dialog such as with 'Find'. Just trying to imagine the steps 
that would be needed...?
As I understand things, that's where real troubles start to 
complicate it all. Macros seem relatively easy for some functions; 
but 'record/playback' for keystrokes -- I'd be hard-pressed to make 
that work under any editor where access to keystrokes isn't built in.
Tom Liotta