Hello,

I was just going through my old mail and I noticed
Shachar's email (below) on Jan. 26. Just to let you
know, I do try to keep up with the wine devel
discussions, but as you can see, I'm not very
successful. I still have a bug assigned to me that is
almost a year old now. I'd like to work on wine more,
but I've been really busy with school lately.
Hopefully, I'll have more time when I graduate.

Anyway, I chose that green color in winemine
specifically to make it annoying ;). Actually, at the
time I didn't want it to have a boring old gray
background, so I chose green in order to make it would
look like grass (a mine field). But I guess it's
pretty annoying. Do you have a color preference? Do
you or anyone else have more suggestions for improving
winemine? Maybe ideas for a 3D minesweeper game or
something? I wrote it like four years ago, and I
didn't know a whole lot about what I was doing (I was
in Comp. Sci. 1 when I wrote it). I'd like it to be
more fun than your typical minesweeper game. Also,
when I originally submitted it, someone complained
that it was slow. Is this still the case for anyone
out there?

Thanks,

Josh

--------------------------------
>From Shachar Shemesh on Jan. 26:

Tom Wickline wrote:

> I am in the process of updating section 3.1. ( Wine
Static and 
> Shareable Files ) of the
> Packagers Guide : 
>
http://www.winehq.com/Docs/wine-pkg/pkg-components.shtml#PKG-STATIC
>
> Below is a list of what I have so far. This list is
by no means done 
> or correct .
> I would like to submit it here for overview. If you
are aware of 
> something that
> is out of place, incorrect, or just out right wrong
could you please give
> feed back on it.
>
> This could also serve to start as a mini Wine
Dictionary :))
> That is not my current goal but if others think it
could be of use
> I could spend some time on one after the Packagers
Guide is updated.
>
> Tom
>
>
> --------------------------------------------
>
> -- = files that are listed in this Doc but are not
installed on my 
> system.
> *  = files are in this Doc and on my system
> @ = files that are on my system but not in the Doc
> #  = files that are not in the Doc or on my System (
wineboot ) 

Then how do you know of their existance ;-). If
wineboot is not 
installed, that's a bug. We should fix it.

I'll try to help with the things I know. This is far
from authorative on 
most, however.

> @ regedit : A tool to browse/edit your regestory or
for exporting a 
> windows registory to Wine. 

Not browse. At least, not yet.

> # wineboot : A Winelib application that's executed
by Wine on startup 
> of the first wine process of a particular user.
>         * wininit.ini processing
>         * registry RenameFiles entries
>         * RunServices* / RunOnce* / Run registry
keys
>         * win.ini Load= / Run= entries
>         * StartUp folder processing 

the last two are not yet done. Also not yet done is
for wineboot to 
automatically run when needed. Currently you have to
manually run it 
after you install something.

> @ winemine :  A winmine clone "Windows Minesweeper"
??? 

Yep, using horrid green colors. I'm sorry if I have
offended the author 
(Joshua Thielen, are you still with us?)

> @ winepath : Specifies the path(s) in which to
search for builtin dlls 
> and Winelib applications. 

I think this is an executable that, given a Unix path,
will tell you 
what Wine sees it like (i.e. - you tell it
~/c/windows, and it tells you 
C:\Windows). I'm not sure on that one.

> -- winesetup : This is a Tcl/Tk based front end that
provides a user 
> friendly tool to edit and configure the
WINECONFDIR/config file. 

Anyone knows where it is? It was never based on the
winehq sources.

            Shachar

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com

Reply via email to