- Wine-Devel - list.winehq.org

Re: wine button
by Mike Hearn Nov. 9, 2002

Nov. 9, 2002

[ps i assumed by what was written you meant for this to go to wine-devel but didn't hit reply-to-all, sorry if it was meant for me only] > There's the application, and button with a wine bottle, that says > 'works with wine'. You could come up with quite a few jokes with that. heh, true. It doesn't look good with the first letter capitalized, at least imho, and probably wouldn't alter the impression non-initiates would get. I tried putting "windows emulator" underneath, but it looks a bit out of place and kind of reduces the impact. It also makes it harder to scale down, at 50% of the size you can still read the "works with wine" text, but not the "windows emulator" underneath. It might also piss off people who say "Wine is not an emulator" :) Actually, letting people make jokes about it might be a good thing - I doubt many people would actually take it literally and assuming they do find out, if they're talking and joking about it, they're more likely to remember it too. On Fri, 2002-11-08 at 15:35, Rick Romero wrote: > > On Fri, 2002-11-08 at 08:53, Mike Hearn wrote: > > Here is my first attempt. I'm hardly an ace designer, so feel free to > > criticize, tell me to junk it etc. > I think it looks great, but if I were a Windows app owner, how would my > potential users see it? > > There's the application, and button with a wine bottle, that says > 'works with wine'. You could come up with quite a few jokes with that. > > Of course we all know what it means, should the 'W' be capitalized to > differentiate it from alcohol? > > I don't intend to start a logo flame war, but I think perceptions are > everything. > > Good thing I'm only around for another 90 minutes today :P > > Rick > > > > > > > -- > -- > Rick Romero > IT Manager > Valeo, Inc. ph: 262.695.4841 > Sussex, WI. fax: 262.695.4850 > Rick(a)valeoinc.com > >

3 2

wine button
by Mike Hearn Nov. 9, 2002

Nov. 9, 2002

Here is my first attempt. I'm hardly an ace designer, so feel free to criticize, tell me to junk it etc. I did try at first to make a browser style button, but it was very hard to make the wine logo fit in a way that didn't look odd, as it's largely a vertical type of logo. Also, is the Windows logo usable? I'd assume it's trademarked or something, but i've seen the 4 colour blocks used in for instance icon overlays in KDE. If it's thought that this is too large, I can either scale it, or try and make another from scratch that is more button sized. thanks -mike

7 10

Wine 0.9 TODO v0.1
by Dimitrie O. Paun Nov. 9, 2002

Nov. 9, 2002

This is based upon the Wine 0.8 TODO v0.2 send earlier to the list. It is important to get a comprehensive list of what needs to be done, in order to have a successful 0.9 release. This includes all things Wine-related, not only the code. I can not do it alone -- I need your input. Before I start, a quick reminder for the 0.9 criteria: -- Users can start using Wine -- works well for a fair number of apps -- no MS DLLs required (from real Windows) -- User facing stuff (website, docs, etc.) are in a decent state, to avoid scaring them away What is NOT in 0.9: -- stable server protocol (no binary compatibility) -- DLL separation (phase 2) Please review it, and let me know if: - I've left something out - Something is in, and it doesn't belong in here (for 0.9 that is) - I have put your name on a task you are not working on - I have NOT put your name on a task you are working on - You have a status update (if you're working on something) - You want to start working on some of these. Comments, flames, suggestions, are appreciated, as always. A. WineHQ work (Beta at: http://lostwages.winehq.org) 0. Website redesign [IN PROGRESS] - worker: Jeremy Newman <jnewman(a)codeweavers.com> 1. Reorganize the navigational menu [BETA] - wine-devel consensus merged into new site 2. Create some really sexy screenshots [IN PROGRESS] -- one app per screenshot, avoid cluttered desktop -- minimize size, if possible by using 'Positioned Color Dithering' 3. Rework the FAQ interface [IN PROGRESS] - workers: Dimitrie Paun, Keith Matthews, Thomas Wickline) 4. Enlist some 'official' distribution maintainers [TODO] (at the minimum RedHat, SUSE, Mandrake, Debian) 5. Create nice page with apps that run virtually flawless [IN PROGRESS] They should not require MS dlls, tricks, etc. to run - worker: Carlos <clozano(a)andago.com> B. Documentation work 0. We need to first figure _what_ is out of date. [TODO] 1. Convert man pages to SGML [TODO] 2. Move CVS docu from User Guide to Devel Guide [TODO] C. Wine configuration 0. Merge configuration into the registry [TODO] 1. Write control panel applets for editing it [TODO] 2. Have decent defaults so we can start control panel without prior configuration [TODO] 3. Have wizard like app to autoconfigure wine [TODO] WineSetupTk proposed by Jeremy White <jwhite(a)codeweavers.com> 4. Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg [TODO] 5. Write .inf script to setup a new Wine installation [TODO] 6. Have a wineboot script for RunOnce stuff [IN PROGRESS] - worker: Shachar Shemesh <wine-devel(a)sun.consumer.org.il> D. Stabilize utilities 0. Get rid of the init directive from .spec files [DONE] - worker: Alexandre Julliard <julliard(a)winehq.com> 1. Make sure the .spec file format is fairly stable [TODO] Any other things that may need changing here? 2. Ensure the various utilities' options are stable [IN PROGRESS] - Alexandre fixed winebuild options Anything here? E. Important fixes 0. Window management rewrite, so we can install apps in managed mode. - worker: Alexandre Julliard <julliard(a)winehq.com> 1. Finish DLL separation Phase 1 [IN PROGRESS] That is, DLLs should use only functions exported through .spec file. Phase 2 is getting rid of unwanted functions from .spec file, and this is not a target for 0.9. -- Dimi.

10 25

Re: dosconf move try 2
by Jukka Heinonen Nov. 9, 2002

Nov. 9, 2002

György 'Nog' Jeney wrote: > ChangeLog: > * dlls/winedos/dosconf.c > * include/callback.h > * msdos/dmpi.c > * msdos/dosconf.c (removed) > * dlls/ntdll/Makefile.in > * dlls/winedos/winedos.spec > * dlls/winedos/Makefile.in > Move dosconf to winedos. This still won't work if Dos3Call is called directly before winedos.dll has been loaded. If this is fixed, I don't see any reason why this patch couldn't be applied. This reminds me that int21 handling is quite messy. Interrups call first DOSVM_Int21Handler and might be chained to Dos3Call. But, if you call Dos3Call directly, execution does not go through DOSVM_Int21Handler. This causes some code duplication and makes things like dosconf unnecessarily complicated. I was hoping that I could leave this stuff to its current state until I had cleaned up other interrupts. Simple solution would be to make Dos3Call load winedos.dll and call DOSVM_Int21Handler through function pointer, move all common code from old Dos3Call to DOSVM_Int21Handler and move code that is difficult to handle in winedos to INT_Int21Handler which would be chained to from DOSVM_Int21Handler when a few selected functions need to be emulated. But this requires lots of work because each int21 function must be separately evaluated in order to see how it must be emulated to properly support both Win16 and DOS; first step would probably just add check if(DOSVM_IsWin16()) to each DOSVM_Int21Handler function and chain to INT_Int21Handler if true. -- Jukka Heinonen <http://www.iki.fi/jhei/>

2 1

Fun projects
by Dimitrie O. Paun Nov. 9, 2002

Nov. 9, 2002

Folks, It's Friday, I'm out of my meetings, weather is superb here in Toronto (so I'm gonna go for a ride on my bike); this calls for some lighter, more entertaining stuff. So, if someone feels like doing something fun, here is a list of interesting Wine-related projects: 1. compile & run Wine under Cygwin (in Windows) This is too cool for words, when it's going to work. It will stress the heck out of Cygwin (good test case), improve out portability 2. compile & run Cygwin under Wine (in Linux) This is also way cool, being the complement of 1. It will stress Wine a lot (another good test case), improve Cygwin portability 3. compile wxWindows/QT/Gtk+ (in Linux), under Wine All of these libraries compile under Windows. So they should compile under Wine just fine. Another superb test case for Wine. 4. make a ghostscript driver that uses Wine to print When we are going to support native Windows printer drivers, this is going to allow ghostscript to use any of the existing gazillion printer drivers out there. 5. compile OSS apps that compile under Windows under Wine This includes stuff like Mozilla, Gimp-Win32, etc. Lots of these are around, many of them hosted at http://sourceforge.net In fact, imagine if we get 3 done, and we can get all KDE/GNOME working in Wine! (I know it's not easily possible, but just the possibility is there :)) And yeah, don't ask me 'why would you want to do that?'. The answer is: Because We Can! :) Really folks, just think how cool these are! ;) Comments, suggestions, additions, are welcome. -- Dimi.

3 2

Re: StretchDIBits
by Dmitry Timoshkov Nov. 9, 2002

Nov. 9, 2002

<steve.lustbader(a)philips.com> wrote: > According to my quick test on WinXP, StretchDIBits returns 0 if > lpBits or lpBitsInfo is NULL. Wine currently produces an unhandled > exception if lpBitsInfo is null. > > ChangeLog: > Prevent StretchDIBits from producing an unhandled exception if > lpBitsInfo is null. > > (See attached file: stretchdibits.diff) > --- objects/dib.c 23 Oct 2002 18:50:10 -0000 1.70 > +++ objects/dib.c 8 Nov 2002 18:49:19 -0000 > @@ -157,6 +157,9 @@ > DC *dc = DC_GetDCUpdate( hdc ); > if(!dc) return FALSE; > + if (!bits || !info) > + return 0; You have to verify parameters before DC pointer and GDI lock are grabbed, otherwise we'll get a nice dead lock. -- Dmitry.

1 0

Re: Small fix for db2html-winehq
by Jeremy White Nov. 9, 2002

Nov. 9, 2002

> -if [ -f /etc/redhat_release ]; then > +if [ -f /etc/redhat-release ]; then afaik, mandrake has this file as well: [weaver(a)test-d weaver]$ cat /etc/redhat-release Mandrake Linux release 9.0 (dolphin) for i586 [weaver(a)test-d weaver]$ Jer

1 0

Cabextract offered to WINE under LGPL..
by Ender Nov. 9, 2002

Nov. 9, 2002

There you go, now who wants to look into merging cabextract with WINE? [http://www.kyz.uklinux.net/cabextract.php3] It'll be useful for at least three things: - Remove external dependency in urlmon (dlls/urlmon/umon.c) - Implement advapi32:ExtractFiles and fix dlls/setupapi/queue.c - Implement cabinet.dll - Probably some other misc cabinet functions here and there - CHM viewer (in the future) I don't think it would be too hard to merge the 0.7 changes into any merging work done with 0.6, so I wouldn't think it necessary to hold out until then. The only major bug he mentions is fixed by simply changing scope of a variable, so.... :) - Ender ---------- Forwarded message ---------- Date: Wed, 06 Nov 2002 12:37:51 +0000 From: Stuart Caie <kyzer(a)4u.net> To: "J.Brown (Ender/Amigo)" <ender(a)enderboi.com> Subject: Re: cabextract licensing Hello J.Brown On 01-Nov-02, you wrote: > Quick question - would it be possible for you to release/give permission > to use the cabextract code under the LGPL? That would allow it's > integration into WINE, and make things a lot easier for WINE.. Sure, I donate to the WINE project the current cabextract 0.6 code (and next release, 0.7, when it is out) for all uses under the LGPL. Just a few technical things: - as it says in the code, cabextract is not a library. It doesn't bother freeing memory except for the 2MB LZX/QTM windows between folders. You'll have to handle memory freeing yourself :) - further, there is a real bug in 0.6: when an LZX or QTM folder follows a ZIP folder, the LZX(window) and QTM(window) pointer in the methods union will be muddied by ZIP state data and will be non-zero and therefore assumed to be valid window pointers. They're not (they're random ZIP state), so it segfaults. To fix this now, remove the "window" field from LZXstate and QTMstate, and put it in the general decomp_state, then change all references of LZX(window) and QTM(window) to CAB(window). - there are also some minor bugs that you'll see fixed in 0.7 (which is why I gifted you this one as well) If you have any other questions, feel free to ask! Regards -- Stuart Kyzer Caie -- kyzer(a)4u.net http://zap.to/kyz ICQ: 45612337 the golden rule; he who has the gold, makes the rules.

1 0

Some dead links on winehq
by Martin Wilck Nov. 8, 2002

Nov. 8, 2002

A small contribution to the winehq fixes: A list of dead or non-functional links on the Development/References page. (http://www.winehq.com/development/index.php?refs) Wine Wine API - mostly useless, IMHO (is this really up-to-date? - at least it shouldn't be on top of the page). Vintage wine sources - ftpsearch.ntnu.no unfortunately out of service. Win32 Win32 API intro - dead WinDoc - only the "Local Mirror" works, the "at microsoft.com" links bring you to the main MSDN site. Unix Unix98 - needs registration LinuxThreads - why is this linked here? AFAIK not used by wine anyway. X The motif zone - dead lamentation - dead Fonts Internet Font archive - gone. X11R6 fonts - dead t1lib -dead Curvesoft - have ceased operations, a few tools still available. x86 Assembly Intel Documentation - dead Writings on software development Homesteading the Noosphere - dead Lisp... - I don't know why it's there, but I love it :-) The Open Source-revolution - dead Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

2 1

GetCurrentObject
by steve.lustbader＠philips.com Nov. 8, 2002

Nov. 8, 2002

My app calls GetCurrentObject with a valid HDC and OBJ_BITMAP. It returns 0, however, which causes my app to crash. What further info can I provide to help debug this? -Steve

1 0