Extensive API Library
-
Hi, I want to make an extensive API library that wraps as many API calls as possible but I don't know how I would implement them. There are a few possibilities: - By DLL (User32, Kernel32, etc.) - By Category (Graphics, Files, XPThemes, etc.) - Alphabeticly (nooooo!!!!) - ??? I would like to have some suggestions on how to do it. The programming itself is no problem, only the maner of implementing them. btw: If you have classes/code to share please I could use them as it will speed up the process a little bit. Thanks in advance. Greets, Poolbeer
Speak Out! Use the Source, Luke! (Dr. GUI .NET #5)
-
Hi, I want to make an extensive API library that wraps as many API calls as possible but I don't know how I would implement them. There are a few possibilities: - By DLL (User32, Kernel32, etc.) - By Category (Graphics, Files, XPThemes, etc.) - Alphabeticly (nooooo!!!!) - ??? I would like to have some suggestions on how to do it. The programming itself is no problem, only the maner of implementing them. btw: If you have classes/code to share please I could use them as it will speed up the process a little bit. Thanks in advance. Greets, Poolbeer
Speak Out! Use the Source, Luke! (Dr. GUI .NET #5)
Have a look at the beta implementation of Win32 security by MS on GotDotNet. Lotsa interop. But it will give you an idea. On the other hand, you want to make you classes as OO as possible. Have a look at my nBASS library where I have to deal with static and "instance" objects. I say "instance" as the interop is on a library written in C hence no OO structure at all and only give me a pointer to work with. It took several (4/5) drafts to get the final OO model in place. Even with to soon to be released version, I have incorporated designer support, which is quite a task when your object is a singleton. You can find the latest source on SourceForge: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/nbass/nBASS/[^] It might be of some interest. All I can say is plan, plan, plan, then action.:) I rated this article 2 by mistake. It deserves more. I wanted to get to the second page... - vjedlicka 3:33 25 Nov '02
-
Have a look at the beta implementation of Win32 security by MS on GotDotNet. Lotsa interop. But it will give you an idea. On the other hand, you want to make you classes as OO as possible. Have a look at my nBASS library where I have to deal with static and "instance" objects. I say "instance" as the interop is on a library written in C hence no OO structure at all and only give me a pointer to work with. It took several (4/5) drafts to get the final OO model in place. Even with to soon to be released version, I have incorporated designer support, which is quite a task when your object is a singleton. You can find the latest source on SourceForge: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/nbass/nBASS/[^] It might be of some interest. All I can say is plan, plan, plan, then action.:) I rated this article 2 by mistake. It deserves more. I wanted to get to the second page... - vjedlicka 3:33 25 Nov '02