On Fri, 2003-11-28 at 02:28, Alexandre Julliard wrote:
> This may cause some duplication, but it's always better to have two
> implementations of something than to risk having none at all if it
> turns out that you can't release the patch in the end.
OK, this is a good point.
> Also make sure tha
Mike Hearn <[EMAIL PROTECTED]> writes:
> b) Notify the Wine community of what the patches do/are but keep their
> contents secret. Pros: Less chance of duplication, Cons: if people need
> the patch, knowing I have one won't be much use and it'd be hard to
> notify people without spamming the maili
On Thu, 2003-11-27 at 22:59, Huw D M Davies wrote:
> We should be doing this already. If cups is installed then we use the
> cups default, otherwise for printcap systems we use the PRINTER
> env variable or if that isn't set the first entry in /etc/printcap.
> Take a look at dlls/winspool/info.c
For all wine files that contain code written by others:
>a) Just keep them "secret" until I get paid, at which point I send them
>in all together. Pros: Simple, Cons: people might duplicate my work.
Good idea
>b) Notify the Wine community of what the patches do/are but keep their
>contents secret.
On Thu, Nov 27, 2003 at 09:37:16PM +, Mike Hearn wrote:
> Hi, I've got a couple of questions tonight:
>
> 1) Currently the default printer is read from win.ini - setting this is
> annoying and doesn't work out of the box. I think it'd make more sense
> to have it also in the wine configuration
Hi, I've got a couple of questions tonight:
1) Currently the default printer is read from win.ini - setting this is
annoying and doesn't work out of the box. I think it'd make more sense
to have it also in the wine configuration, so if no win.ini string is
retrieved it'll still work. I have an app
