Hallo,
1) I have the book "OS/2 Warp Workplace Shell API" (ISBN: 0-471-03872-5). It's very helpful to understand some of the things like object lifetime etc. that the OS/2 toolkit docs won't properly explain. It's completely independent of any compiler but it might be outdated here and there as it refers to Warp 3.
2) you can create a WPS DLL with about any C/C++ compiler. You use "sc.exe" from the toolkit to create code skeleton (C/C++ code and header files). Forget about "Direct To SOM". You don't necessarily need it in order to write a WPS DLL.
3) I advise to use the C++-emitter from "sc.exe" even if you program in C. It's so much more elegant to code as naturally, SOM/WPS is object oriented (think about methods ...).
4) I once started writing a "post-it" class. It's finished to the point where it is usable but it was more of a learning project to me. It shows how to set up exception handling where necessary (an important thing to do in a WPS DLL). If anyone is interested, I can zip it up and send it to you.
1) I have the book "OS/2 Warp Workplace Shell API" (ISBN: 0-471-03872-5). It's very helpful to understand some of the things like object lifetime etc. that the OS/2 toolkit docs won't properly explain. It's completely independent of any compiler but it might be outdated here and there as it refers to Warp 3.
2) you can create a WPS DLL with about any C/C++ compiler. You use "sc.exe" from the toolkit to create code skeleton (C/C++ code and header files). Forget about "Direct To SOM". You don't necessarily need it in order to write a WPS DLL.
3) I advise to use the C++-emitter from "sc.exe" even if you program in C. It's so much more elegant to code as naturally, SOM/WPS is object oriented (think about methods ...).
4) I once started writing a "post-it" class. It's finished to the point where it is usable but it was more of a learning project to me. It shows how to set up exception handling where necessary (an important thing to do in a WPS DLL). If anyone is interested, I can zip it up and send it to you.