Aaron,
How about a little pseudo-compiler than can take a header file, suck
out all the constants, and write declares for the functions? To get the
right library, it would plow through DLLs in a folder. That way, these
things would be header file oriented rather than library oriented and
we could apply it to other kits that come along. I'd help.
-Brad
On Sep 29, 2004, at 4:19 PM, Aaron Ballman wrote:
Note: this is a personal side project -- not something endorsed by
REALSoftware. Basically.. this is me talking as an RB-user, not as an
RS-employee. :-)
So I've been thinking of working on another open source project, but
it's a rather large undertaking. So before I dive right into it, I'd
like to see about a few things (we'll get back to that). Basically, I
am looking into porting the Win32 APIs into RB modules so that you can
use them natively from within RB. You don't have to look up what
constants to use, or have to figure out how to write the API yourself.
You can just call it. For example, you could do things like this:
User32.SetWindowLong( myRBWindow, User32.GWL_ID, someNewID )
This is a different concept than the Win32 Declare Library (which will
probably be renamed to avoid confusion) in that this set of
functionality will just wrap APIs -- not string them together to try
to provide new classes or sets of functionality.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://www.realsoftware.com/listarchives/lists.html>
|