I've been going through the Wine API documentation and there seem to be
some things that I think should be changed:
- There are references to Wine documents that do not include links to
the pages. The links should be included.
- Some 'implementation' sections claim that
On Fri, Jul 2, 2010 at 12:01 PM, Peter Davies wrote:
> I think the speed and freedom provided by wiki is more important than
> vetting. Most problems would be due to vandalism (easily reverted),
> people will keep an eye on Recent Changes. If the problem is
> overwhelming, we will make editing pr
> I don't know about the 'respectability' of SF, but I'm more concerned with
> the content and who gets to change it. There are folks that may decide to
> enter incorrect or even bogus information. I would like it if all added
> information that is not already present in the Wine API be vetted
On Wed, 2005-11-09 at 05:31 -0600, Alexandre Julliard wrote:
> Robert Shearman <[EMAIL PROTECTED]> writes:
>
> > *It appears that this was previously generated at release time by the
> > wine_release script (http://cvs.winehq.org/cvsweb/tools/wine_release),
> > but was disabled over 2 years ago.
Robert Shearman <[EMAIL PROTECTED]> writes:
> *It appears that this was previously generated at release time by the
> wine_release script (http://cvs.winehq.org/cvsweb/tools/wine_release),
> but was disabled over 2 years ago. I was wondering what the reason was,
> but I guess it is that it take
On 11/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Wed, 09 Nov 2005 00:38:19 +0100, Robert Shearman <[EMAIL PROTECTED]>
> wrote:
>
> > We don't really want the WineHQ web server to be running at 100% CPU
> > for ~20 minutes while it builds the API documentation.
>
> couldn't it just be
On Wed, 09 Nov 2005 00:38:19 +0100, Robert Shearman <[EMAIL PROTECTED]>
wrote:
We don't really want the WineHQ web server to be running at 100% CPU
for ~20 minutes while it builds the API documentation.
couldn't it just be niced down to a low priority ? Even if it took a day
to compile.
Robert Shearman wrote:
*It appears that this was previously generated at release time by the
wine_release script (http://cvs.winehq.org/cvsweb/tools/wine_release),
but was disabled over 2 years ago. I was wondering what the reason was,
but I guess it is that it takes a long time to build and a
On 11/8/05, Robert Shearman <[EMAIL PROTECTED]> wrote:
> *I believe that the API documentation is important for a number of reasons:
> 1. It might provide info to ISVs that might think about porting an app
> to Wine as to whether the APIs that they use are implemented or not.
> 2. It provides info
Hi,
At the moment we have a very outdated version of the auto-generated
"make htmlpages" Wine API documentation at http://source.winehq.org/WineAPI/
I want to fix this.
*
*I believe that the API documentation is important for a number of reasons:
1. It might provide info to ISVs
10 matches
Mail list logo
