No feedback and apparently no interest in the WineAPI project on SourceForge. Understandable since there is now a WineAPI on the regular Wine Wiki. Unless someone objects, I'm going to ask that it be shutdown on SourceForge.
Max
Am 05.02.2011 06:36, schrieb Max TenEyck Woodbury:
No feedback and apparently no interest in the WineAPI project on SourceForge. Understandable since there is now a WineAPI on the regular Wine Wiki. Unless someone objects, I'm going to ask that it be shutdown on SourceForge.
Which WineAPI on the regular Wine Wiki??? URL?
On 02/05/2011 08:59 AM, André Hentschel wrote:
Am 05.02.2011 06:36, schrieb Max TenEyck Woodbury:
No feedback and apparently no interest in the WineAPI project on SourceForge. Understandable since there is now a WineAPI on the regular Wine Wiki. Unless someone objects, I'm going to ask that it be shutdown on SourceForge.
Which WineAPI on the regular Wine Wiki??? URL?
Sorry, not Wiki. http://source.winehq.org/WineAPI/
Max
On 02/05/2011 06:36 AM, Max TenEyck Woodbury wrote:
No feedback and apparently no interest in the WineAPI project on SourceForge.
The subject has been debated before you launched the WineAPI project on SF. Some questions may help to understand why does nobody is interested : + Why a WineAPI should be needed ? + Who would use it ? + What can people using it expect to see ?
Understandable since there is now a WineAPI on the regular Wine Wiki.
On 02/05/2011 02:59 PM, André Hentschel wrote:
Which WineAPI on the regular Wine Wiki??? URL?
I guess he's talking about this http://source.winehq.org/WineAPI/
It says "generated automatically" but where is the script ?
Max, if you want, you can still improve the script and make it more useful. For instance, instead of "Statistics" which give simple numbers, I think a link to each function in the wine source code should be great. I have some ideas like adding a "search" feature, a link to the test that implement the selected function ..etc
It may be useful when you want modify a function but you don't know where it is. For instance, wine_dbgstr_w() is used everywhere. But where is it defined ? It should be a usage of the WineAPI but that's only my point of view.
Hope that helps !
On Sat, 5 Feb 2011, GOUJON Alexandre wrote:
On 02/05/2011 02:59 PM, André Hentschel wrote:
Which WineAPI on the regular Wine Wiki??? URL?
I guess he's talking about this http://source.winehq.org/WineAPI/
It says "generated automatically" but where is the script ?
Max, if you want, you can still improve the script and make it more useful. For instance, instead of "Statistics" which give simple numbers, I think a link to each function in the wine source code should be great. I have some ideas like adding a "search" feature, a link to the test that implement the selected function ..etc
It may be useful when you want modify a function but you don't know where it is. For instance, wine_dbgstr_w() is used everywhere. But where is it defined ? It should be a usage of the WineAPI but that's only my point of view.
I've seen this discussion come and go a few times... Would something like LXR be appropriate for generating a web front-end to searching and indexing the Wine source code? I've used the various Linux kernel sites a time or two:
http://sourceforge.net/projects/lxr/
Steve Brown sbrown7@umbc.edu
On 02/05/2011 10:38 AM, Steve Brown wrote:
On Sat, 5 Feb 2011, GOUJON Alexandre wrote:
On 02/05/2011 02:59 PM, André Hentschel wrote:
Which WineAPI on the regular Wine Wiki??? URL?
I guess he's talking about this http://source.winehq.org/WineAPI/
It says "generated automatically" but where is the script ?
Max, if you want, you can still improve the script and make it more useful. For instance, instead of "Statistics" which give simple numbers, I think a link to each function in the wine source code should be great. I have some ideas like adding a "search" feature, a link to the test that implement the selected function ..etc
It may be useful when you want modify a function but you don't know where it is. For instance, wine_dbgstr_w() is used everywhere. But where is it defined ? It should be a usage of the WineAPI but that's only my point of view.
I've seen this discussion come and go a few times... Would something like LXR be appropriate for generating a web front-end to searching and indexing the Wine source code? I've used the various Linux kernel sites a time or two:
http://sourceforge.net/projects/lxr/
Steve Brown sbrown7@umbc.edu
Script is 'tools/c2man.pl'.
There are several things in it that need improvement. See my other thread from yesterday.
Max
Steve Brown sbrown7@umbc.edu writes:
I've seen this discussion come and go a few times... Would something like LXR be appropriate for generating a web front-end to searching and indexing the Wine source code?
Yes, and it's been in place for years: http://source.winehq.org
-
Alexandre Julliard -
André Hentschel -
GOUJON Alexandre -
Max TenEyck Woodbury -
Steve Brown