Hey all, introducing myself and my GSoC idea...
My name is Alex. I'm an 18 year old Freshman at the University of South Florida. I'm an electrical engineer, but I've been coding since I was 13. I love low-level stuff, like assembly and ugly C, machine code, etc. I like to be able to smell the processor I'm so close to the metal. I made a proposal on GSoC to improve support for the Native API, an undocumented API in Windows. I'd really like to code for the Wine Project, since I like Windows, I like Linux, and I especially like low-level scrounging. I'm usually available by MSN, and generally fairly friendly. Send me an IM, or reply here to critique my proposal. It's entitled " Proposal to improve Wine's support of the Native API". I'm registered as cholinesterase(a)gmail.com. Will someone look it over and tell me what they think? Also, suggested reading would be nice, especially if it pertains to the project idea and Wine's code base! Thanks for reading.
On Mon, Mar 31, 2008 at 7:30 PM, a a <cholinesterase(a)gmail.com> wrote:
I made a proposal on GSoC to improve support for the Native API, an undocumented API in Windows. I'd really like to code for the Wine Project, since I like Windows, I like Linux, and I especially like low-level scrounging. I'm usually available by MSN, and generally fairly friendly. Send me an IM, or reply here to critique my proposal. It's entitled " Proposal to improve Wine's support of the Native API". I'm registered as cholinesterase(a)gmail.com.
Find a suite of third party applications and drivers that depend on the undocumented APIs otherwise your not going to get very far with getting your code in. -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
Find a suite of third party applications and drivers that depend on the undocumented APIs otherwise your not going to get very far with getting your code in.
Why is that? There are varying amounts of "undocumented." Not documented on MSDN doesn't mean that no documentation exists. For instance, there's Gary Nebbett's "Windows NT/2000 Native API Reference." Personally, I've thought that playing around with the native LPC API might be interesting. I'm sure there are other areas of the native API that are sparsely documented, and for which some test cases might prove useful. --Juan
On Mon, Mar 31, 2008 at 8:11 PM, Juan Lang <juan.lang(a)gmail.com> wrote:
Find a suite of third party applications and drivers that depend on the undocumented APIs otherwise your not going to get very far with getting your code in.
Why is that? There are varying amounts of "undocumented." Not documented on MSDN doesn't mean that no documentation exists. For instance, there's Gary Nebbett's "Windows NT/2000 Native API Reference." Personally, I've thought that playing around with the native LPC API might be interesting. I'm sure there are other areas of the native API that are sparsely documented, and for which some test cases might prove useful.
But is the API in question useful for the Wine project as far as fixing apps? I don't think we should devote SOC resources to a project that doesn't progress Wine beyond just implementing more APIs. -- James Hawkins
But is the API in question useful for the Wine project as far as fixing apps? I don't think we should devote SOC resources to a project that doesn't progress Wine beyond just implementing more APIs.
That's a good point. Alex, you'd probably want to specify which APIs in particular you're thinking of testing and implementing, and why they'd be useful for the Wine project. An app that uses them would be the easiest way to address their usefulness. And notice that in both my emails I said testing. Good test cases, in the form of regression tests added to Wine's test suite, are probably more important than the implementation would be. This is especially true of undocumented or poorly documented functions. Good luck, --Juan
James Hawkins wrote:
On Mon, Mar 31, 2008 at 8:11 PM, Juan Lang <juan.lang(a)gmail.com> wrote:
Personally, I've thought that playing around with the native LPC API might be interesting. I'm sure there are other areas of the native API that are sparsely documented, and for which some test cases might prove useful.
But is the API in question useful for the Wine project as far as fixing apps? I don't think we should devote SOC resources to a project that doesn't progress Wine beyond just implementing more APIs.
It is useful for getting native rpcrt4 to work, which in turn is useful for getting other COM DLLs to work, and so is potentially useful for bug triage and identifying the source of bugs in builtin COM DLLs. -- Rob Shearman
On Tue, Apr 1, 2008 at 3:58 AM, Robert Shearman <rob(a)codeweavers.com> wrote:
James Hawkins wrote:
On Mon, Mar 31, 2008 at 8:11 PM, Juan Lang <juan.lang(a)gmail.com> wrote:
Personally, I've thought that playing around with the native LPC API might be interesting. I'm sure there are other areas of the native API that are sparsely documented, and for which some test cases might prove useful.
But is the API in question useful for the Wine project as far as fixing apps? I don't think we should devote SOC resources to a project that doesn't progress Wine beyond just implementing more APIs.
It is useful for getting native rpcrt4 to work, which in turn is useful for getting other COM DLLs to work, and so is potentially useful for bug triage and identifying the source of bugs in builtin COM DLLs.
LPC, yes, but the student just said the Native API. -- James Hawkins
participants (5)
-
a a -
James Hawkins -
Juan Lang -
Robert Shearman -
Steven Edwards