Re: Looking for information on implemented API's in wine
David Miller <compsol(a)ptd.net> wrote:
I am ready to begin work on the actual database aspect of cross referencing the windows dlls. As part of the database I would like to include the status of a given API in wine so it will be possible to do things like query for all unimplemented APIs in a given dll. The first questions I have are whether or not I can depend on the spec files to give a complete list, and can someone either point me to documentation on the spec files or explain everything I need to know in order to determine the status of APIs defined there?
I'm sure this will not really be enough, although it is at least a start. There are a lot of functions which are implemented according to the spec file but only consists of an empty function body with a FIXME, or is only partly implemented with again a FIXME somewhere in the function. Rolf Kalbermatter
Sounds to me like I can use the spec files as a reference, but to be accurate I'll need to scan the source code as well for any APIs which the spec files claim are implemented in order to determine if they are only FIXMEs. :( I'll see if I can understand how winapi_check does it. ----- Original Message ----- From: "Rolf Kalbermatter" <rolf.kalbermatter(a)citeng.com> To: "David Miller" <compsol(a)ptd.net> Cc: <wine-devel(a)winehq.com> Sent: Thursday, February 13, 2003 6:04 PM Subject: Re: Looking for information on implemented API's in wine
David Miller <compsol(a)ptd.net> wrote:
I am ready to begin work on the actual database aspect of cross referencing the windows dlls. As part of the database I would like to include the status of a given API in wine so it will be possible to do things like query for all unimplemented APIs in a given dll. The first questions I have are whether or not I can depend on the spec files to give a complete list, and can someone either point me to documentation on the spec files or explain everything I need to know in order to determine the status of APIs defined there?
I'm sure this will not really be enough, although it is at least a start. There are a lot of functions which are implemented according to the spec file but only consists of an empty function body with a FIXME, or is only partly implemented with again a FIXME somewhere in the function.
Rolf Kalbermatter
On February 13, 2003 07:42 pm, Dave Miller wrote:
I am ready to begin work on the actual database aspect of cross referencing the windows dlls.
Hi Dave, I'm not sure if you intend to use a real database (like MySql, or PostgreSQL) to implement this, but if you do, I'd strongly advise against it. Doing so will limit its usefulness tremendously, as few people are willing to go through the pain of installing and setting the database up just for this script. Ideally all information would be stored in ASCII flat files, read in core at startup, and processed in memory. This way everybody can play with the script. -- Dimi.
Hmm. I did intend to use a database, specifically MySQL was my thinking. What I hoped was there would be a web interface to query the database and so everyone would not have to have MySQL to use it. Of course it needs to be hosted somewhere but I figured I'd cross that bridge when it became a problem. :) The move from flat file to SQL could be done with one 'mysqlimport command so right now I'll focus on gathering the information and placing it in a flat file. The question then will be how to query it, but I suppose it's best to deal with one problem at a time. ----- Original Message ----- From: "Dimitrie O. Paun" <dpaun(a)rogers.com> To: "Dave Miller" <compsol(a)ptd.net> Cc: <wine-devel(a)winehq.com> Sent: Thursday, February 13, 2003 7:31 PM Subject: Re: Looking for information on implemented API's in wine
On February 13, 2003 07:42 pm, Dave Miller wrote:
I am ready to begin work on the actual database aspect of cross referencing the windows dlls.
Hi Dave, I'm not sure if you intend to use a real database (like MySql, or PostgreSQL) to implement this, but if you do, I'd strongly advise against it. Doing so will limit its usefulness tremendously, as few people are willing to go through the pain of installing and setting the database up just for this script.
Ideally all information would be stored in ASCII flat files, read in core at startup, and processed in memory. This way everybody can play with the script.
-- Dimi.
On Thu, 13 Feb 2003 20:20:06 -0500, "Dave Miller" <compsol(a)ptd.net> wrote:
Hmm. I did intend to use a database, specifically MySQL was my thinking. What I hoped was there would be a web interface to query the database and so everyone would not have to have MySQL to use it. Of course it needs to be
Personally I don't have any objections to use a real database. You could provide a small script that unloads the data to a flat ASCII file anyway, so this wouldn't be a problem for anybody not using MySQL. I have it installed for other things, so it wouldn't matter to me and if you intend to use a webinterface you can easily download it. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)
Gerhard W. Gruber wrote:
On Thu, 13 Feb 2003 20:20:06 -0500, "Dave Miller" <compsol(a)ptd.net> wrote:
Hmm. I did intend to use a database, specifically MySQL was my thinking. What I hoped was there would be a web interface to query the database and so everyone would not have to have MySQL to use it. Of course it needs to be
Personally I don't have any objections to use a real database. You could provide a small script that unloads the data to a flat ASCII file anyway, so this wouldn't be a problem for anybody not using MySQL. I have it installed for other things, so it wouldn't matter to me and if you intend to use a webinterface you can easily download it.
I can't but think that MySQL is way overkill. Let's define the queries we want to do, and see if awk isn't up to them :-) It probably is, and it's far easier to set up than MySQL. Those who can't think in anything but SQL really should try learning the traditional unix programmer's workbench tools for relational database processing. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
On Fri, 14 Feb 2003 12:59:50 -0800, Dan Kegel <dank(a)kegel.com> wrote:
I can't but think that MySQL is way overkill.
Tha'ts true if you have to install it for just that purpose. Otherwise it is a rather convenient way to handle this data and you don't have to write some script for the queries. :)
Let's define the queries we want to do, and see if awk isn't up to them :-) It probably is, and it's far easier to
I don't think that you can't handle it with a script. :) And I also see the point of users not wanting to install MySQL for such a small task. :)
set up than MySQL. Those who can't think in anything but SQL really should try learning the traditional unix programmer's workbench tools for relational database processing.
I have no problem with either. If it is in MySQL I can handle it and if it is a flat file in an organized manner I can also handle it. I have written enough shell scripts so I don't see any problem for that. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)
have you thought about xml? --matt On Fri, Feb 14, 2003 at 10:09:37PM +0100, Gerhard W. Gruber wrote:
On Fri, 14 Feb 2003 12:59:50 -0800, Dan Kegel <dank(a)kegel.com> wrote:
I can't but think that MySQL is way overkill.
Tha'ts true if you have to install it for just that purpose. Otherwise it is a rather convenient way to handle this data and you don't have to write some script for the queries. :)
Let's define the queries we want to do, and see if awk isn't up to them :-) It probably is, and it's far easier to
I don't think that you can't handle it with a script. :) And I also see the point of users not wanting to install MySQL for such a small task. :)
set up than MySQL. Those who can't think in anything but SQL really should try learning the traditional unix programmer's workbench tools for relational database processing.
I have no problem with either. If it is in MySQL I can handle it and if it is a flat file in an organized manner I can also handle it. I have written enough shell scripts so I don't see any problem for that. -- Gerhard Gruber
F?r jedes menschliche Problem gibt es immer eine einfache L?sung: Klar, einleuchtend und falsch. (Henry Louis Mencken)
On February 14, 2003 06:45 pm, Matthew Stump wrote:
have you thought about xml?
Please, don't. It's a lot harder to process with standard Unix tools, and they are uglier to read :). If we can work with a flat file, we should. -- Dimi.
I've never actually had any intention of everyone needing to install MySQL in order to make use of the database. I had planned on it being a single database, accessible via the web. Querying would be done via forms. It seemed the easiest way to present all the data in a single place. I also thought it might be possible to enter application data, so that it can be queried for APIs the app requires, etc. Right now I will certainly work toward a flat file. I had intended to start with that anyway, and it is easily imported into SQL if choose to move in that direction. But as I've said, I'm certainly not an experienced programmer and so I have no real idea of what is possible with perl plus the power of awk. But I am sure once we can gather the data someone will be happy to help find ways to query it. :) ----- Original Message ----- From: "Dan Kegel" <dank(a)kegel.com> To: "Gerhard W. Gruber" <sparhawk(a)gmx.at> Cc: <wine-devel(a)winehq.com> Sent: Friday, February 14, 2003 3:59 PM Subject: Re: Looking for information on implemented API's in wine
Gerhard W. Gruber wrote:
On Thu, 13 Feb 2003 20:20:06 -0500, "Dave Miller" <compsol(a)ptd.net> wrote:
Hmm. I did intend to use a database, specifically MySQL was my thinking. What I hoped was there would be a web interface to query the database and so everyone would not have to have MySQL to use it. Of course it needs to be
Personally I don't have any objections to use a real database. You could provide a small script that unloads the data to a flat ASCII file anyway, so this wouldn't be a problem for anybody not using MySQL. I have it installed for other things, so it wouldn't matter to me and if you intend to use a webinterface you can easily download it.
I can't but think that MySQL is way overkill. Let's define the queries we want to do, and see if awk isn't up to them :-) It probably is, and it's far easier to set up than MySQL. Those who can't think in anything but SQL really should try learning the traditional unix programmer's workbench tools for relational database processing. - Dan
-- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
Dave Miller wrote:
I've never actually had any intention of everyone needing to install MySQL in order to make use of the database. I had planned on it being a single database, accessible via the web. Querying would be done via forms. It seemed the easiest way to present all the data in a single place. I also thought it might be possible to enter application data, so that it can be queried for APIs the app requires, etc. Right now I will certainly work toward a flat file. I had intended to start with that anyway, and it is easily imported into SQL if choose to move in that direction. But as I've said, I'm certainly not an experienced programmer and so I have no real idea of what is possible with perl plus the power of awk. But I am sure once we can gather the data someone will be happy to help find ways to query it. :)
Another advantage of it being in a flat file is that different people can work on different versions of it and use diff, patch, cvs, etc to maintain them. This wouldn't be possible just through having a simple web interface. David
participants (7)
-
Dan Kegel -
Dave Miller -
David Fraser -
Dimitrie O. Paun -
Gerhard W. Gruber -
Matthew Stump -
Rolf Kalbermatter