How to programmatically fight with WPS:Tools

Object REXX

injects a class into WPS, so provides a direct access to WPS objects (with limitations w.r.t. marshalling etc).

REXX without extensions

provides access (via and Sys*Object* API) to the Win*Object* (C) subset of API.

icon.exe (GUI for WPTOOLS.DLL) (by Kelder)

among others shows many things:

1/2-decyphered contents of .CLASSINFO
Init strings for objects;
Contents of NOWHERE
Get/Set Object ID, location

WPTOOLS.DLL is also accessible from REXX. Beware: there are tools which require uncompatible versions of this DLL... WPTOOLS.DLL uses undocumented hacks to get the object data for EA and .INI files.

ObjectSpy Class

class-DLL, ID, location, class ancessors, icon styles (no-delete etc), methods, interface.

WP Class list Application

Class Tree => create an object of the given class, (un)replace a class.

RWX

Class Tree => metaclass/parent, DLL, Cause?, instance/class methods/datasize.

Object Utility/2

D&D => Class, DLL, object-id, location, get/set style flags (no-delete etc).

Setup strings list

http://www.os2ezine.com/v3n07/wpsetup.txt

a complete listing of setup strings for common object classes, along with a list of the values used with.

WPObjData

http://www.os2ezine.com/v3n07/hammer.htm

tame WPObjData _and_ to put it to work doing something useful.

WPSTools

 mo create/modify-by-string-id objects 
 eo modify by handle 
 fo create shadows in TARGET by the *-pattern in ./
 qo report the handle by the string-id
 wplist list classes/dll
 wpkill delete class 
 wpmake add class

Perl

has access to Win*Object* API (C) (via OS2::WinObject module). The module SOM gives access to all the SOM objects and the object repository, but (currently) only a limited access to DSOM objects (due to the absense of an interface to DII).