wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

Re: Another systray patch
by Grant Williamson 06 Dec '04

06 Dec '04

Mike, I tried saving the patch in various ways, maybe its me, but it would appear its corrupted, can u resend as attachment, thanks. [root@trax wine-20041201]# patch -p0 -i /usr/src/redhat/SOURCES/systray-20041206.patch patching file dlls/x11drv/event.c patching file dlls/x11drv/window.c patching file dlls/x11drv/x11drv.h patching file programs/wineshell/Makefile.in patching file programs/wineshell/wineshell.c patching file programs/wineshell/wineshell.h patching file programs/wineshell/systray.c patch: **** malformed patch at line 485:

1 0

Re: wine/dlls/ntdll directory.c
by Mike Hearn 06 Dec '04

06 Dec '04

On Mon, 06 Dec 2004 10:48:16 -0600, Alexandre Julliard wrote: > Log message: > Use a direct getdents syscall on Linux to avoid relying on > implementation details of seekdir/telldir. > > Patch: http://cvs.winehq.org/patch.py?id=14699 Does this fix the hang on Reiser4 by any chance? thanks -mike

2 1

Re: Turn off Antialiasing for Rendering with Palette - Take 2
by Dmitry Timoshkov 06 Dec '04

06 Dec '04

"Glenn Wurster" <glenn(a)electric.ath.cx> wrote: > ret = dc->funcs->pExtTextOut(dc->physDev,x,y,flags|ETO_IGNORELANGUAGE, > - lprect,lpReorderedString,count,lpDx,dc->breakExtra); > + lprect,lpReorderedString,count,lpDx,dc->breakExtra,antialias); I think that it should be the ExtTextOut's backend responsibility whether to use antialiasing or not, taking into account ANTIALIASED_QUALITY and CLEARTYPE_QUALITY value of the LOGFONT.lfQuality field. -- Dmitry.

2 1

Wine failed during HEAP_CreateSystemHeap
by Tobias Grosser 06 Dec '04

06 Dec '04

Hi, i tried to use the new FreeBSD Wine port und FreeBSD 5.3. And I am able to start wine, but while executing "wine ie6setup.exe" an error during CreateSystemHeap shows up. Unfortunately I am not able to solve this problem by myself, and need some advice how to debug this correct. Here the output, after which wine exits: fixme:file:get_default_drive_device auto detection of DOS devices not supported on this platform fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x80000000 not availablefixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x80000000 not availableerr:heap:HEAP_CreateSystemHeap system heap base address 0x80000000 not availableerr:heap:HEAP_GetPtr Invalid heap 0x0! err:heap:HEAP_GetPtr Invalid heap 0x0! err:heap:HEAP_GetPtr Invalid heap 0x0! err:heap:HEAP_GetPtr Invalid heap 0x0! I tried to change SYSTEM_HEAP_BASE to 0xC0000000 for testing, but this shows an equal output. If I open wine in gdb I am not able to set a breakpoint at line 96 "if(!(base = MapViewOfFileEx( map, FILE_MAP_ALL_ACCESS, 0, 0, 0, SYSTEM_HEAP_BASE )))" to start debugging. Starting at the beginning of the function throws me into inline assambler and some "valgrind" code, but nothing i can deal with. It would be great to give me some debugging advice. Thanks in advance Tobias

2 1

needing some help...
by MyComputer Store 06 Dec '04

06 Dec '04

Hey... I am just getting into this whole wine thing and I have already run into a problem. I am working on switching my Media Matrix servers over to linux, but the software that I need to run is still windows based. Here is the link to the software. http://mm.peavey.com/downloads/mware335.exe when I try to run this file with wine (20041201) it locks up before the installer has finished loading... any advise?? Caleb Miller

1 0

Re: mdi.c/MDI_ChildActivate query
by Jeremy White 06 Dec '04

06 Dec '04

Works nicely; thank you (and my schools chess club, soon to have a tourney, thanks you <grin>). Cheers, Jeremy Dmitry Timoshkov wrote: > "Jeremy White" <jwhite(a)codeweavers.com> wrote: > > >>When trying to run 'Swiss Perfect' (www.swissperfect.com, >>free download available), the app crashes and burns while >>processing a WM_MDIACTIVATE message when the prevWnd is 0. > > > This is due to a long standing hack in X11DRV_ShowWindow which > forces MDI child activation. > > Attached patch adds a couple of new MDI message tests using existing > message sequences for ordinary child windows and confirms that > ShowWindow does the same job for MDI children in respect to activation. > > This fixes a crash in Swiss Perfect. > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > ShowWindow activates only a being maximized child window, > add a couple of message tests for MDI child activation. >

1 0

Kernel 2.6.10... and amd64
by Jose Alberto Reguero 06 Dec '04

06 Dec '04

I can't use wine with kernels 2.6.10-rc2.... With kernel 2.6.9 it works. My system is an amd64 linux. Thanks. Jose Alberto

1 2

IME question
by Ivan Leo Puoti 05 Dec '04

05 Dec '04

According to MSDN, windows creates an IME window and an input context for every thread, should wine do the same? Ivan. ____________________________________________________________ Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega, senza costi di attivazione. Abbonati subito su http://www.libero.it

1 0

Re: Implemented CreateAsyncBindCtx
by Mike Hearn 05 Dec '04

05 Dec '04

On Fri, 03 Dec 2004 23:01:36 -0500, Jacek Caban wrote: > + hres = IBindCtx_RegisterObjectParam(bctx, (LPOLESTR)BSCBHolder, (IUnknown*)callback); > + > + *pbind = bctx; > + > + return S_OK; > } You don't do anything with hres here, is that intentional? Can RegisterObjectParam fail? thanks -mike

2 1

mdi.c/MDI_ChildActivate query
by Jeremy White 05 Dec '04

05 Dec '04

Hi, When trying to run 'Swiss Perfect' (www.swissperfect.com, free download available), the app crashes and burns while processing a WM_MDIACTIVATE message when the prevWnd is 0. If I modify the code as in the attached patch, everything works. I can't determine if the app is flawed or if this is a good change to Wine; I'm hoping an MDI expert can kibitz. Cheers, Jeremy

1 0

Wrapper for Winelib
by Sam Lauber 05 Dec '04

05 Dec '04

I *think* I've figured out a way to make regular Unix programs with winelib. My idea is, make winemaker generate a C file called "winelib-wrap.c" that contains: #include <stddef.h> int main(void) { return (int) WinMain(NULL, NULL, NULL, NULL); } Then link it with the EXE encapusulated in a .so, and it SHOULD work. I'll try it on the 01-stdole32.c. It gave me a SIGSEGV, but maybe someone would fix it. Samuel Lauber -- _____________________________________________________________ Web-based SMS services available at http://www.operamail.com. >From your mailbox to local or overseas cell phones. Powered by Outblaze

2 1

Re: msvcrt: set mode bits in _fstati64
by Dmitry Timoshkov 05 Dec '04

05 Dec '04

"Juan Lang" <juan_lang(a)yahoo.com> wrote: > + buf->st_mode = S_IFREG; > + if (!(hfi.dwFileAttributes & (FILE_ATTRIBUTE_HIDDEN | FILE_ATTRIBUTE_SYSTEM))) > + { > + buf->st_mode |= S_IREAD; > + if (!(hfi.dwFileAttributes & FILE_ATTRIBUTE_READONLY)) > + buf->st_mode |= S_IWRITE; > + } Why do you take into account (FILE_ATTRIBUTE_HIDDEN | FILE_ATTRIBUTE_SYSTEM) at all? They have nothing to do with an ability to read/write files. What you probably need to consider is a type of a file passed in. -- Dmitry.

2 5

questions dlls/d3d8/shader.c
by Eric Pouech 05 Dec '04

05 Dec '04

while toying with Intel compiler on Wine source, I came across a couple of interesting stuff. To whom it may concern. in dlls/d3d8/shader.c: vshader_m4x3 (and vsharer_m3x4) don't use correctly row & columns with respect to the matrice definition. I let the D3D folks decide whether the matrix definition, or the implementation is to blame IDirect3DVertexShaderImpl_ExecuteSW: you miss one in size of p_send (and likely p) in windows/sys_params.c SystemParametersInfoW, for the case SPI_GETLOWPOWERACTIVE, this index is out of the bounds of spi_loaded in dlls/shell32/shlview.c ShellView_OnNotify, case LVN_BEGINDRAG and LVN_BEGINRDRAG, the dwEffect value is not initialized before calling DoDragDrop !!! A+

2 1

Re: Mirroring support take 1
by Juan Lang 05 Dec '04

05 Dec '04

This doesn't look right: @@ -2071,6 +2077,7 @@ WIN_ReleasePtr( wndPtr ); return retval; } + break; /* fall through */ If the break is missing, why does the comment say fall through? I think it was intentional. If the break should be there, please remove the comment as well. --Juan __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo

1 0

Re: Janitorial: WinMM conversion of 32 bit low level drivers to Unicode interface
by Eric Pouech 05 Dec '04

05 Dec '04

Eric Pouech a écrit : > This patch is based on work by Filip Navara from ReactOS. > He did the Winmm part (+wave & midi mapper), I did the rest (+ 16 > message mapping) > A+ well, another take (I forgot a couple of places...) I also removed the SB related code. What's missing it's the proper registry settings when a device is chosen, and we'd better do it either in winecfg or wine.inf, but not in the drivers themselves A+

1 0

Problem to draw a bitmap
by Rémi Assailly 05 Dec '04

05 Dec '04

I tested a program ( an other one, with source code this time ) On my Windows XP system I have no problem. When I use Wine I just get a window. ( where is my bitmap ? ) Then I tried this : "WINEDEBUG=gdi wine progtest" and as Wine is slower I could see my bitmap, which disappeared as fast as it appeared... Here the source code : > #include <windows.h> > #include <wingdi.h> > > void PrintBmp(HWND hWnd, char *filename) > { > HBITMAP hBmp; > HDC hDC; > hBmp=(HBITMAP)LoadImage(NULL,filename,IMAGE_BITMAP,0,0,LR_LOADFROMFILE); > hDC=GetDC(hWnd); > DrawState(hDC,NULL,NULL,(LPARAM)hBmp,NULL,0,0,0,0,DST_BITMAP); > DeleteObject(hBmp); > ReleaseDC(hWnd,hDC); > } > > /* Declare Windows procedure */ > LRESULT CALLBACK WindowProcedure (HWND, UINT, WPARAM, LPARAM); > > /* Make the class name into a global variable */ > char szClassName[ ] = "WindowsApp"; > > > int WINAPI > WinMain (HINSTANCE hThisInstance, > HINSTANCE hPrevInstance, > LPSTR lpszArgument, > int nFunsterStil) > > { > HWND hwnd; /* This is the handle for our window */ > MSG messages; /* Here messages to the application are saved */ > WNDCLASSEX wincl; /* Data structure for the windowclass */ > > /* The Window structure */ > wincl.hInstance = hThisInstance; > wincl.lpszClassName = szClassName; > wincl.lpfnWndProc = WindowProcedure; /* This function is called by windows */ > wincl.style = CS_DBLCLKS; /* Catch double-clicks */ > wincl.cbSize = sizeof (WNDCLASSEX); > > /* Use default icon and mouse-pointer */ > wincl.hIcon = LoadIcon (NULL, IDI_APPLICATION); > wincl.hIconSm = LoadIcon (NULL, IDI_APPLICATION); > wincl.hCursor = LoadCursor (NULL, IDC_ARROW); > wincl.lpszMenuName = NULL; /* No menu */ > wincl.cbClsExtra = 0; /* No extra bytes after the window class */ > wincl.cbWndExtra = 0; /* structure or the window instance */ > /* Use Windows's default color as the background of the window */ > wincl.hbrBackground = (HBRUSH) COLOR_BACKGROUND; > > /* Register the window class, and if it fails quit the program */ > if (!RegisterClassEx (&wincl)) > return 0; > > /* The class is registered, let's create the program*/ > hwnd = CreateWindowEx ( > 0, /* Extended possibilites for variation */ > szClassName, /* Classname */ > "Windows App", /* Title Text */ > WS_OVERLAPPEDWINDOW, /* default window */ > CW_USEDEFAULT, /* Windows decides the position */ > CW_USEDEFAULT, /* where the window ends up on the screen */ > 544, /* The programs width */ > 375, /* and height in pixels */ > HWND_DESKTOP, /* The window is a child-window to desktop */ > NULL, /* No menu */ > hThisInstance, /* Program Instance handler */ > NULL /* No Window Creation data */ > ); > > > /* Make the window visible on the screen */ > ShowWindow (hwnd, nFunsterStil); > PrintBmp(hwnd, "BOARD.bmp"); > /* Run the message loop. It will run until GetMessage() returns 0 */ > while (GetMessage (&messages, NULL, 0, 0)) > { > /* Translate virtual-key messages into character messages */ > TranslateMessage(&messages); > /* Send message to WindowProcedure */ > DispatchMessage(&messages); > } > > /* The program return-value is 0 - The value that PostQuitMessage() gave */ > return messages.wParam; > } > > > /* This function is called by the Windows function DispatchMessage() */ > > LRESULT CALLBACK > WindowProcedure (HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam) > { > switch (message) /* handle the messages */ > { > case WM_DESTROY: > PostQuitMessage (0); /* send a WM_QUIT to the message queue */ > break; > default: /* for messages that we don't deal with */ > return DefWindowProc (hwnd, message, wParam, lParam); > } > > return 0; > }

3 4

RFC: Use editline in winedbg
by Jeremy White 05 Dec '04

05 Dec '04

Hi folks, The attached patch dynamically detects and uses the BSD licensed editline library (a pretty close replacement for readline), if it's available. This gives winedbg command line recall. This gets around readline's license requirements. I'm nervous because I wasn't sure if that was the only issue with readline, or if there were further issues. Wack me with a clue bat if this is wrong, otw, I'll submit it. Cheers, Jeremy

5 6

Re: Janitorial: WinMM conversion of 32 bit low level drivers to Unicode interface
by Steven Edwards 05 Dec '04

05 Dec '04

--- Eric Pouech <pouech-eric(a)wanadoo.fr> wrote: > This patch is based on work by Filip Navara from ReactOS. > He did the Winmm part (+wave & midi mapper), I did the rest (+ 16 message mapping) > A+ Eric I just want you to know you are my personal hero. Someday they will write songs about you that I will listen to under ReactOS <g>. Thanks Steven __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com

1 0

Re: Fix for winedbg; disassemble range was flawed
by Jeremy White 05 Dec '04

05 Dec '04

This updated version prevents an infinite loop in the (currently impossible) case of a poorly specified disassembly range. Truth is, this functions interface is a bit awkward. Jeremy White wrote: > Changelog: > Properly respect a disassemble x,y command > (prior behavior would do y-x instructions, no matter > how wide each instruction was) > > > ------------------------------------------------------------------------ > > Index: programs/winedbg/debugger.h > =================================================================== > RCS file: /cvstrees/crossover/office/wine/programs/winedbg/debugger.h,v > retrieving revision 1.17 > diff -u -r1.17 debugger.h > --- programs/winedbg/debugger.h 28 Nov 2004 16:23:50 -0000 1.17 > +++ programs/winedbg/debugger.h 5 Dec 2004 04:30:24 -0000 > @@ -317,7 +317,7 @@ > extern BOOL memory_get_current_frame(ADDRESS* address); > extern BOOL memory_get_string(HANDLE hp, void* addr, BOOL in_debuggee, BOOL unicode, char* buffer, int size); > extern BOOL memory_get_string_indirect(HANDLE hp, void* addr, BOOL unicode, char* buffer, int size); > -extern void memory_disassemble(const struct dbg_lvalue*, const struct dbg_lvalue*, int offset); > +extern void memory_disassemble(const struct dbg_lvalue*, const struct dbg_lvalue*, int instruction_count); > extern BOOL memory_disasm_one_insn(ADDRESS* addr); > extern void print_bare_address(const ADDRESS* addr); > extern void print_address(const ADDRESS* addr, BOOLEAN with_line); > Index: programs/winedbg/memory.c > =================================================================== > RCS file: /cvstrees/crossover/office/wine/programs/winedbg/memory.c,v > retrieving revision 1.1.1.13 > diff -u -r1.1.1.13 memory.c > --- programs/winedbg/memory.c 28 Nov 2004 15:36:39 -0000 1.1.1.13 > +++ programs/winedbg/memory.c 5 Dec 2004 04:30:24 -0000 > @@ -598,9 +598,11 @@ > } > > void memory_disassemble(const struct dbg_lvalue* xstart, > - const struct dbg_lvalue* xend, int offset) > + const struct dbg_lvalue* xend, int instruction_count) > { > static ADDRESS last = {0,0,0}; > + int stop = 0; > + int i; > > if (!xstart && !xend) > { > @@ -613,7 +615,10 @@ > last.Mode = AddrModeFlat; > last.Offset = types_extract_as_integer(xstart); > } > - if (xend) offset = types_extract_as_integer(xend) - last.Offset + 1; > + if (xend) > + stop = types_extract_as_integer(xend); > } > - while (offset-- > 0 && memory_disasm_one_insn(&last)); > + for (i = 0; (instruction_count == 0 || i < instruction_count) && > + (stop == 0 || last.Offset <= stop); i++) > + memory_disasm_one_insn(&last); > }

1 0

Re: COMCTL32: Minor corrections
by Robert Shearman 05 Dec '04

05 Dec '04

Filip Navara wrote: > Changelog: > - Tooltip icons must be destroyed with DestroyIcon and not with > DeleteObject. > - Don't use DrawEdge with NULL device context, it's invalid call and > sets last error. > >------------------------------------------------------------------------ > >Index: lib/comctl32/datetime.c >=================================================================== >RCS file: /CVS/ReactOS/reactos/lib/comctl32/datetime.c,v >retrieving revision 1.5 >diff -u -r1.5 datetime.c >--- lib/comctl32/datetime.c 19 Sep 2004 09:50:06 -0000 1.5 >+++ lib/comctl32/datetime.c 4 Dec 2004 22:59:42 -0000 >@@ -1170,10 +1170,10 @@ > > TRACE("Height=%ld, Width=%ld\n", infoPtr->rcClient.bottom, infoPtr->rcClient.right); > >- /* use DrawEdge to adjust the size of rcEdge to get rcDraw */ > memcpy((&infoPtr->rcDraw), (&infoPtr->rcClient), sizeof(infoPtr->rcDraw)); > >- DrawEdge(NULL, &(infoPtr->rcDraw), EDGE_SUNKEN, BF_RECT | BF_ADJUST); >+ /* subract the size of the edge drawn by DrawEdge */ >+ InflateRect(&infoPtr->rcDraw, -2, -2); > > Please use GetSystemMetrics(SM_CXEDGE) and GetSystemMetrics(SM_CYEDGE). > > /* set the size of the button that drops the calendar down */ > /* FIXME: account for style that allows button on left side */ >Index: lib/comctl32/tooltips.c >=================================================================== >RCS file: /CVS/ReactOS/reactos/lib/comctl32/tooltips.c,v >retrieving revision 1.9 >diff -u -r1.9 tooltips.c >--- lib/comctl32/tooltips.c 20 Oct 2004 08:36:55 -0000 1.9 >+++ lib/comctl32/tooltips.c 4 Dec 2004 23:18:56 -0000 >@@ -2818,7 +2818,7 @@ > TOOLTIPS_Unregister (void) > { > int i; >- for (i = 0; i < TTI_ERROR+1; i++) >- DeleteObject(hTooltipIcons[i]); >+ for (i = TTI_INFO; i <= TTI_ERROR; i++) >+ DestroyIcon(hTooltipIcons[i]); > UnregisterClassW (TOOLTIPS_CLASSW, NULL); > } > > Someone already sent a patch for this (and it is my buggy code, sorry). Not sure why it didn't go in, but it should. Rob

3 2

Re: implement DllCanUnloadNow for dmusic
by Robert Shearman 04 Dec '04

04 Dec '04

James Hawkins wrote: >Changelog > * properly implement DllCanUnloadNow ref counting > > > Sorry, still isn't correct. Please see my comments below. >------------------------------------------------------------------------ > >Index: dlls/dmusic/buffer.c >=================================================================== >RCS file: /home/wine/wine/dlls/dmusic/buffer.c,v >retrieving revision 1.8 >diff -u -r1.8 buffer.c >--- dlls/dmusic/buffer.c 6 Sep 2004 21:34:25 -0000 1.8 >+++ dlls/dmusic/buffer.c 4 Dec 2004 20:52:16 -0000 >@@ -38,6 +38,9 @@ > ULONG WINAPI IDirectMusicBufferImpl_AddRef (LPDIRECTMUSICBUFFER iface) { > IDirectMusicBufferImpl *This = (IDirectMusicBufferImpl *)iface; > TRACE("(%p): AddRef from %ld\n", This, This->ref); >+ >+ DMUSIC_LockModule(); >+ > return ++(This->ref); > } > >@@ -45,9 +48,13 @@ > IDirectMusicBufferImpl *This = (IDirectMusicBufferImpl *)iface; > ULONG ref = --This->ref; > TRACE("(%p): ReleaseRef to %ld\n", This, This->ref); >+ > if (ref == 0) { > HeapFree(GetProcessHeap(), 0, This); > } >+ >+ DMUSIC_UnlockModule(); >+ > return ref; > } > >@@ -160,6 +167,8 @@ > } > dmbuff->lpVtbl = &DirectMusicBuffer_Vtbl; > dmbuff->ref = 0; /* will be inited by QueryInterface */ >+ >+ DMUSIC_LockModule(); > > return IDirectMusicBufferImpl_QueryInterface ((LPDIRECTMUSICBUFFER)dmbuff, lpcGUID, ppobj); > } > > Ok, think about this sequence of events that should leave the DLL ref count at 0: 1. Create an IDirectMusicBufferImpl object. 1a. Calls LockModule. 1b. Calls QueryInterface which calls LockModule. 2. Call Release, which calls LockModule. The solution is to either remove the LockModule from the constructor, or to remove the LockModule from the AddRef and only call UnlockModule in the destructor part of Release. This issue is also present in the other files in your patch (not quoted here). I should have thought about this before when I commented on your last patch. I guess I need to put some tests together for this feature. Rob

2 2

DInput has been broken for about 6 months now
by Scott Ritchie 04 Dec '04

04 Dec '04

Well, one of my favorite games, Fallout 2, didn't work when I tried it. This is strange though, as it was working about 3 years ago. Looking through the AppDB page, http://appdb.winehq.org/appview.php?appId=194&versionId=319 - it looks like it's been broken since June. Specifically, here's the symptoms: "DXGRAB" = "Y" will cause the app to completely takeover and lockup the system, except no input into the app (mouse or keyboard) works. I have to ctrl-alt-f2 and killall -9 wine-preloader to get back to work. Turning off DXGRAB causes the app to respond to keyboard input, but the mouse still doesn't work. Some very strange things happened in gnome when I brought my email window in front of the app (the mouse would skip from the edge of the gnome window past the app, making it impossible to click on, and other wierdness. However, none of this translated into the in-game cursor moving) I'm running the app in Desktop=640x480 mode. Furthermore, it appears that some of the old problems listed in the AppsDB page are still there - the game is very slow at certain points (well, the loading and unloading I can do with the keyboard...), and I'm running a computer roughly 10 times as fast as was designed for the game. After asking about on the channel a bit, the finger was pointed at DINPUT. I think some of the problems with DINPUT would make a fairly good candidate for something to tackle on Sunday, although doing a >6 month regression test could be annoying. I personally know about 3 people I could get to switch to Wine entirely if we could get this working :) I haven't filed a bugzilla report yet, but if it helps I will. Thoughts? -Scott Ritchie

1 0

Re: New Canadian keyboard layout
by Dmitry Timoshkov 04 Dec '04

04 Dec '04

"Jean-Michel Dault" <jmdault(a)revolutionlinux.com> wrote: > I'm doing a pilot project for the Quebec government, and we have one > major problem: they have a keyboard layout that's unsupported by Wine, > though it was commited to XFree about 3 years ago. What do you mean by "unsupported by Wine", is that just a warning that you see? What exactly doesn't work without this patch? -- Dmitry.

4 4

Making the Documentation into help files
by Scott Ritchie 04 Dec '04

04 Dec '04

While making the Debian package, I had to do a special hack to compile wine's documentation because it's made seperately. This isn't a really big deal, but what I did realize is that Wine's documentation doesn't get installed to the help menu now coming standard on systems. When I select Applications->Help from the menu in Ubuntu, there's a whole list of documentation for available installed applications. I managed to get the install script to copy txt versions of the stuff in the documentation folder to the standard /usr/share/doc/wine, but this place remains bereft of wine documentation. So, how is this done? I presume there's a freedesktop.org standard for these things, as both Gnome and KDE have them in the same way, but currently we're not converting the documentation sgml files into these help files. Coincidentally, this might tie in very well to the desktop integration tasks suggested this week. Perhaps we should create a desktop integration tasklist or even append it onto the 1.0 todo? Trying to further improve usability, Scott Ritchie

3 2

Wine book
by Brian Vincent 04 Dec '04

04 Dec '04

Just wanted to give everyone a heads up.. I followed up with Jeremy's email a few months ago about a publisher wanting to put together a book on Wine. Yep, I have no life and 400 pages can't be that hard to write. Well, we started the ball rolling and now it looks like it's going to happen. I should be signing the contract in a few days. There's lots of details I thought you guys might be interested in. You'll find the chapter outlines[1] at the bottom of this email. This book is oriented at users and Winelib developers. It's not a book about how to hack Wine internals. One thing I'll try to keep in mind as I'm writing is how to entice people to get involved with development. I think it's important to try to get people involved in the community. I'm not going to be writing this alone. Ira Krakow, a Boston native, will be writing the Winelib parts. I didn't feel comfortable doing those and Ira had approached the publisher separately about doing a book on porting Windows apps. We've chatted a few times and I'm confident that given his experience he'll do well. I'm cc:ing him on this email by way of introduction and I'm sure at some point in the future he'll have a question or two (or 50.) The publisher is Prentice-Hall. Thus far they've been excellent to work with and they really seem to just "get it" when it comes to open source projects. Specifically, this book will fall into their Bruce Perens' Open Source Series [2]. After the book is published, it will be available for a short time only in a dead tree version. After a few months it will be available under the Open Publication License [3]. It's a good license and contains many things I think are important. Also, I'd like to thank everyone who reviewed the initial proposal. That process happened really fast and I wasn't even aware it had been sent out for review until after you guys got the emails. There was lots of good feedback in there and I incorporated a lot of it in the final proposal that got approved (you may even notice some changes in the chapters below as a result.) Some other things you guys mentioned aren't specifically in this chapter outline, but I made some notes as to what needs to be addressed. Thanks again. Anyone who didn't see that proposal, you didn't miss much. It was lots of marketspeak. The key is the chapter outline below, so if you have any comments about what I'm overlooking, _please_ let me know. [1] Chapter outlines: Title: "Wine: Running Windows Applications on Linux" [4] 1. Wine Introduction[15 pages] What is Wine? How Can Wine Help You? An Introduction to Windows Components Overview of Wine's Components Recent Changes to Wine A History of the Wine Project How Can You Get Wine? 2. Installing Wine [20 pages] System Requirements Bundled Versions Downloading Packaged Versions Accessing CVS Compiling and Installing Wine Uninstalling Wine 3. Configuring Wine [35 pages] Introduction to Winecfg Windows Versions Libraries: Native vs. Builtin Application Settings Drive Configuration Serial and Parallel Ports Network Shares Fonts Printing Database Access 4. Installing Applications [35 pages] Basic Installation Common Installation Pitfalls Resources to Help With Installation Adding Native Libraries Installing Games Copy Protection Pitfalls Using Native DirectX 5. Installing Common Programs [35 pages] Microsoft Office Adobe Photoshop File Utilities Peer-to-Peer Applications Further Help: The Wine Application Database 6. Linux, Wine, and Windows Integration [40 pages] Integrating with Desktop Environments KDE and GNOME Integration Wine Tools Introduction Wineshelllink Wineprefixcreate Regedit Understanding the Wine Registry Changing the Registry Importing an Existing Registry Using an Existing Windows Partition 7. Enterprise Deployment [30 pages] Licensing Considerations Understanding Windows and Wine Security Automating Deployment of Applications Scripting Wine Citrix Killer: Wine and the Linux Terminal Server Project Performance Tweaks Reporting Bugs and Working with Developers 8. Commercial Alternatives: CodeWeaver's CrossOver Office [25 pages] Introduction to CrossOver Office Downloading and Installing CrossOver Configuring CrossOver Installing Applications with CrossOver 9. Commercial Alternatives: TransGaming's Cedega [25 pages] Introduction to Cedega Downloading and Installing Cedega Configuring Cedega Installing Games with Cedega 10. Introduction to Winelib [20 pages] Introduction to Winelib Licensing Considerations Portability Considerations Getting Started Understanding the Winelib toolkit A Roadmap for Porting Installation of the MinGW Compiler 11. Using Winelib for Porting [45 pages] Installation of the MinGW compiler Moving From Visual Studio to MinGW Tips and Tricks for Changing Compilers Moving Development to Linux Using Winemaker Using the Wine Resource Compiler Using the Wine Message Compiler Linking it Together: winegcc Debugging with the Wine debugger 12. Case Study: Porting a To-Be-Determined Application [30 pages] 13. Advanced Porting Techniques [25 pages] C++ Problems Working with Microsoft Foundation Classes Working with Templates Moving From Visual Studio to MinGW 14. dvanced Library Techniques [20 pages] Getting Started: Why Share Libraries? Using Linux Libraries with Winelib Applications Using Windows Libraries with Winelib Applications Why Wine is not a Shared Library [2] Peren's Open Source Series info: http://phptr.com/promotion/1484?redir=1 [3] OPL license: http://www.opencontent.org/openpub/ a good discussion of it: http://lwn.net/Articles/108250/ [4] With regards to the title, I'll be sure to mention in Wine runs on other operating systems. PS. This still leaves the door open for someone to write an O'Reilly book. PPS. I'd like to think this won't affect WWN because I really have no life. However, that's not too realistic. Hopefully WWN won't suffer too much. - Brian Vincent

7 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel