Jump to content

How to programmatically fight with WPS: Difference between revisions

From EDM2
Newer edit →
Created page with "By [[]] * DESCRIPTION * TOOLS * [[How to programmatically fight with WPS:..."
 
No edit summary
Line 6: Line 6:
* [[How to programmatically fight with WPS:PMWP entries in POPUPLOG.OS2|PMWP entries in POPUPLOG.OS2]]
* [[How to programmatically fight with WPS:PMWP entries in POPUPLOG.OS2|PMWP entries in POPUPLOG.OS2]]
* [[How to programmatically fight with WPS:Lost/broken desktop or broken Templates or Startup|Lost/broken desktop or broken Templates or Startup]]
* [[How to programmatically fight with WPS:Lost/broken desktop or broken Templates or Startup|Lost/broken desktop or broken Templates or Startup]]
* [[How to programmatically fight with WPS:|URL objects]]
* [[How to programmatically fight with WPS:URL objects|URL objects]]
* [[How to programmatically fight with WPS:|WPObjData and "Hammer and ..." icons]]
* [[How to programmatically fight with WPS:WPObjData and "Hammer and ..." icons|WPObjData and "Hammer and ..." icons]]
* [[How to programmatically fight with WPS:|WPVault, x:/NOWHERE, NOTVISIBLE, SHOWALLINTREEVIEW]]
* [[How to programmatically fight with WPS:WPVault, x:/NOWHERE, NOTVISIBLE, SHOWALLINTREEVIEW|WPVault, x:/NOWHERE, NOTVISIBLE, SHOWALLINTREEVIEW]]
* [[How to programmatically fight with WPS:|.HLP not shown in view.exe]]
* [[How to programmatically fight with WPS:.HLP not shown in view.exe|.HLP not shown in view.exe]]
* [[How to programmatically fight with WPS:|Drag & Drop of .dev and printers]]
* [[How to programmatically fight with WPS:Drag & Drop of .dev and printers|Drag & Drop of .dev and printers]]
* [[How to programmatically fight with WPS:|Start a VIO window with a changed font size]]
* [[How to programmatically fight with WPS:Start a VIO window with a changed font size|Start a VIO window with a changed font size]]
* [[How to programmatically fight with WPS:|Desktop background]]
* [[How to programmatically fight with WPS:Desktop background|Desktop background]]
* [[How to programmatically fight with WPS:|Properties of the root directory]]
* [[How to programmatically fight with WPS:Properties of the root directory|Properties of the root directory]]
* [[How to programmatically fight with WPS:|PM_Workplace:Location]]
* [[How to programmatically fight with WPS:PM_Workplace:Location|PM_Workplace:Location]]
* [[How to programmatically fight with WPS:|PM_Workplace:Templates]]
* [[How to programmatically fight with WPS:PM_Workplace:Templates|PM_Workplace:Templates]]
* [[/CREDITS|CREDITS]]
* [[How to programmatically fight with WPS:CREDITS|CREDITS]]
 
Programmatic access to WPS is complicated due to several reasons:
 
* Most APIs are accessible only from inside the WPS process (the second copy of PMSHELL.EXE), or via DSOM/CORBA via remote method call.
* To call things from inside the WPS process one needs to "inject" a WPS class into the system; possible bugs in the object will jeopardize the WPS integrity, thus the usability of the computer. This makes WPS classes much harder to design than "ordinary" applications.
* The current implementation of DSOM lacks run-time method-dispatch-by-name, thus one needs to use CORBA (DII) to make arbitrary method calls from scripts. AFAIK, there is no scripting solution which uses DII for its operation.
* Even with this hard-to-reach API, there is no API to fetch the data which allows reconstruction of the object state (serialization/deserialization, marshalling etc). Thus one needs to use undocumented ways to fetch the object state.
* There is a small subset of API (Win*Object* (C) and Sys*Object* (REXX) API) usable from outside of the WPS process. However, the control provided by this API is very restricted.
 
However, some stuff can be done even with such low-grade stuff as plain REXX.

Revision as of 16:07, 11 October 2012

By [[]]

Retrieved from "https://www.edm2.com/index.php?title=How_to_programmatically_fight_with_WPS&oldid=9976"