From: Mark M. <mie...@gm...> - 2008-07-31 16:05:07
|
One of the things I want to do is add a WindowsShell extension. This extension would provide access to the Windows Shell functionality in much the same manner that ooDialog provides access to the dialog portion of the Win32API. And, I also want to update the WinSystm extension to use the 4.0 native APIs. With the WindowsShell extension, I have a good solid start that I wrote using the API that OleObject used and placed in the incubator. Figuring it would then be relatively easy to convert to the new API when it was ready. Now in both ooDialog and the WindowsShell extension I've developed, started to develop, a number of convenience functions that make working with the 4.0 native API easier, along with general functions that are useful in working with Windows period. Much of this is useful in all 3 Windows extensions and so I'd like to share the code between the 3 extensions. I wonder if Rick, or anyone, has any ideas to contribute on this? I see 2 basic strategies. Either build a static library of the common functions and have each extension link with the static library and just pull in the functions that the extension actually uses. Or develop a DLL that the extensions will link to at load time. My plan at this time is to build a DLL, but I've just started to think about it and would welcome any input. And of course if the DLL was actually useful for Windows extensions, other people writing Windows extensions could use it. -- Mark Miesfeld |