> Here's a rough proposal of a documentation suite for Wine:
>
> --------------------------------------------------
>
> OVERVIEW
> For beginning users; assumes Wine is already installed. Very simple
> language; task-based.
>
> WINE INSTALLATION GUIDE
> For all users; includes FTP, CVS, Redhat, Debian, etc.
> Covers getting it on the system, but not personalizing it.
>
> WINE USER'S GUIDE
> For the day-to-day user; maintaining Wine on your system. How to
> configure the basic services, like fonts, printing, multimedia.
perhaps what's missing is the point of administrating Wine (like instaling
Wine on a multi-user system), which lays across the here above two points
> WINE APPLICATIONS GUIDE
> For dealing with specific applications.
>
> WINE PORTING GUIDE
> For developers trying to migrate their apps to UNIX, using Wine.
I find the title misleading
there are two topics to be covered
- porting apps from Windows to Unix using Wine (which is not IMO wine porting
guide)
- how to port wine to other systems than the ones already supported (linux, freebsd,
partly Solaris...) (which shall be named Wine Porting Guide, and belongs to next
section)
> WINE DEVELOPER'S GUIDE
> For developers wanting to contribute to Wine. How to submit patches,
> what policies to follow, how to debug, and a nice, juicy section on
> the Wine architecture.
>
> WINE DEVELOPER'S GUIDE
> ======================
>
> I. Architecture
> 1. The Wine Server
> 2. DLLs in Wine
> 3. Drivers
> 4. The Kernel
> 5. The graphics subsystem
> 6. OLE Support
> 7. Unicode
1/ you seem willing to mix USER and GDI support into the graphics subsystem
may be there's a need to split that a bit (particulary for the link between
USER and WM...)
2/ 16 bit support, thunking, DLL pairs is also a must have IMO
3/ file systems too (but they can be part of kernel)
anyway, we may have issues with the above layout because the subjects are
not orthogonal. we can either take the Windows point of view (how is this
peculiar DLL implemented) or take the Wine components one by one
I'd favor to stick to Windows' components (because wine tries to mimic them
anyway). lastly, Wine server is IMO part of Kernel (or is the way Wine
implements part of the kernel)
a last point would be to have Alexandre's agreement to use DocBook as
primary format for documentation. I remembered one of his remarks
where he wished to have at least all docs in text format so anyone
could read them (it doesn't mean of course docs must be written in text
format)
A+
--
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle
