I had a better look at the wine 2007 GSOC work - works quite alright, found my
CUPS
spooler; I am surprised that it uses the registry. It builds alright with mingw
cross compiler (I have it around for other stuff and reasonably familiar with
it), but a little surprised that there are a few compiler warnings which should
be fixed,
for code base this small.
--- On Fri, 28/3/08, Detlef Riekenberg <[EMAIL PROTECTED]> wrote:
<snipped>
> I'm away for the weekend, but some quick notes:
>
> - The ddiwrapper-hack works only with a very small amount
> of
> self-contained drivers
Yes, but say, a GSOC project for distinguishing which are self-contained and
which are not?
I haven't got round to look at ddiwrapper yet, but it is in my hard disc now.
> - Most Drivers today are plugins for the unidrv or the
> pscipt5 Driver
> (you can install pscript5 from Adobe since ~ 1/2 Year)
> - Drivers expect dlls, that are not present in wine-2005*
> (They will not load)
> - Rendering with full Drivers (Raster-Mode) need most Eng*
> Functions
> and Friends (This is the DIB-Engine).
> - Rendering with full Drivers (Postscript) need some Eng*
> Functions
> and Friends.
> Nothing in this Area is implemented / exported in current
> Wine:
> Driver will not load
The time frame - GSOC work being a little after wine 1.0 (and the merge of the
other work) - should be interesting and useful?
> - Sending the rendered Data to the Printer need sometimes a
> vendor-
> specific Portmonitor / Languagemonitor
> (Not supported in current Wine)
Yes, I think the epson epl windows driver does that...
A personal question: would be like to be involved if a student comes along, or
in general in this area? (I looked it up, you were the mentor for the 2007 wine
project for the printerproxy).
__________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox http://uk.docs.yahoo.com/nowyoucan.html
