- Wine-devel - list.winehq.org

Re: lostwages (alpha 1)
by Jeremy Newman 04 Nov '02

04 Nov '02

On Mon, 2002-11-04 at 02:48, Keith Matthews wrote: > Do please try not to have more javascript than is really necessary. Sexy > looking features are nice from a designer's point of view, but to a No js on this site at all. I prefer to do most on the server side. Works across more browsers that way. > Looks rather black rather than red (Konq 2.2 on laptop). /me loads up Konq and looks. > I prefer the screenshot to the one Francois has, but it could still be > improved by having rather more background that is obviously an OSS > desktop. Both screen shots were made by me. I made a quick new one that didn't have a CodeWeavers logo on it somewhere. The idea is to have that screenshot be random, so feel free to submit me screenshots. I prefer whole desktops, and several Win apps/games running at once. That shows real power. > I'm getting a debug log panel at the bottom, no idea if that is > intentional, critical or what. That's intentional, the site is in debug mode as it's in development. When I say alpha I mean it. The final will look NOTHING like this, this is a rough draft. The fist round it mainly work on the back end code and general layout of the boxes and nav. Everything thing else colors/images/logo will change. -- __ _WebGeek/SysAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | / -_) | | / ' \/ _` | ' \ -= jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

1 0

Re: lostwages (alpha 1)
by Jeremy Newman 04 Nov '02

04 Nov '02

On Mon, 2002-11-04 at 02:13, David Fraser wrote: > Just wondering, is it really neccessary to have the URLs as queries i.e. > http://lostwages.winehq.org/?page=Support&view=page-support > Couldn't they just be > http://lostwages.winehq.org/support I plan on something similar, the urls will be something like: http://lostwages.winehq.org/index.php/support/ The shorter urls (ie without the index.php) will also work with redirects hard coded in a .htaccess file. We love shortcuts. -- __ _WebGeek/SysAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | / -_) | | / ' \/ _` | ' \ -= jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

1 0

Re: msvcrt-A08: _dup
by Jaco Greeff 04 Nov '02

04 Nov '02

Jaco Greeff wrote: > This patch in the msvcrt-A?? series implements the _dup function, > allowing you to duplicate msvcrt file descriptors. I've got a strange feeling that I stuffed up here, comments will be appreciated. Is the intention that it (_dup/_dup2) should duplicate the associated HANDLE as well? At present I don't duplicate the actual HANDLE, rather return a new fd which at the lowest level still points to the same handle. Something tells me that I should be duplicating the handle as well. I just found some sample code which points to duplicating the actual handle as well - comments please before I "do it right"(tm). Greetings, Jaco

1 0

Re: PATCH: ppc fix 2
by Greg Turner 04 Nov '02

04 Nov '02

On Wednesday 30 October 2002 07:22 am, Marcus Meissner wrote: > Hi, > > Just a bad macro. > > ciao, marcus > > Changelog: > Fixed LITTLE_ENDIAN_32_READ macro to at least compile. > > Index: ndr_marshall.c > =================================================================== > RCS file: /home/wine/wine/dlls/rpcrt4/ndr_marshall.c,v > retrieving revision 1.9 > diff -u -r1.9 ndr_marshall.c > --- ndr_marshall.c 29 Oct 2002 23:07:33 -0000 1.9 > +++ ndr_marshall.c 30 Oct 2002 13:21:15 -0000 > @@ -59,8 +59,8 @@ > > #define LITTLE_ENDIAN_32_READ(pchar) \ > (MAKELONG( \ > - MAKEWORD(*(pchar), *((pchar)+1)) \ > - MAKEWORD(*((pchar)+2), *((pchar)+3))) > + MAKEWORD(*(pchar), *((pchar)+1)), \ > + MAKEWORD(*((pchar)+2), *((pchar)+3)))) > #endif > > /* oops! thanks! strange that this compiles for i386 at all. maybe gcc is automagically fixing the macro for some of us? -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

2 3

Wine 0.8 TODO v0.1
by Dimitrie O. Paun 04 Nov '02

04 Nov '02

This is the initial TODO for Wine 0.8. I know, 0.8 has been released before, but that's ancient history. Whether or not it gets released with this version number is irrelevant. In fact, even if it never becomes a public release, it is an important point to reach toward 0.9, and so if we complete this work, it would have solved its purpose. Now, again, what I mean by 0.8: -- 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.8: -- stable server protocol: no binary compatibility -- DLL separation: ditto That being said, this is my initial list. Comments, flames, suggestions, are appreciated. A. WineHQ work 0. Reorganize a bit the navigational menu 1. Add a screenshot link to the homepage 2. Create some really sexy screenshots 3. Rework the FAQ interface (static HTML, a la http://www.dvddemystified.com/dvdfaq.html, all on one page, with a clickable question list at the top) 4. Enlist some 'official' distribution maintainers (at the minimum RedHat, Suse, UnitedLinux, Debian) 5. Create nice page with apps that run virtually flawless They should not require MS dlls, tricks, etc. to run Small explanation, screeshot, optional link to download page, such as Tucows. B. Documentation work Andy, take it away! :) C. Wine configuration 0. Merge configuration into the registry 1. Write control panel applets for editing it 2. Have decent defaults so we can start control panel without prior configuration 3. Have wizard like app to autoconfigure wine (?) 4. Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg 5. Write .inf script to setup a new Wine installation D. Stabilize utilities 0. Get rid of the init directive from .spec files 1. Make sure the .spec file format is fairly stable 2. Ensure the various utilities' options are stable E. Important fixes Alexandre, what to you see here? -- Dimi.

19 68

lostwages (alpha 1)
by Jeremy Newman 04 Nov '02

04 Nov '02

Alpha 1 of WineHQ is up at http://lostwages.winehq.org The site is very very red. I'm not sure of that idea right now, but tell me what you think anyway. I think it hurts my eyes, but this is a short notice thing, I'll come up with something better. Feel free to submit color ideas. It does not have Francois' latest menu's in yet, but that is easy to change, the menu system reads the menu from an array in the config file. So it's much more dynamic. Anyway it's late, and I imagine you all will tear this to shreads, so have fun doing so. I'm always flame retardant (mostly cause I don't care, and will do what I want anyway >:) nighty night! -- __ _WebGeek/SysAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | / -_) | | / ' \/ _` | ' \ -= jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

5 4

Re: msvcrt-A06: _popen + COMSPEC
by Jaco Greeff 04 Nov '02

04 Nov '02

On Sun, 3 Nov 2002 11:02:02 -0500, "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote : > On November 3, 2002 10:38 am, Jaco Greeff wrote: > > If COMSPEC > > is not set, or not found on disk, _popen makes use of > > c:\windows\system32\cmd.exe binary. > > Why not cmd.exe only, and hope to find it in the PATH? > I think the PATH in Windows contains windows\system32 > in it by default. I have tried this, CreateProcess doesn't find "cmd.exe" if we don't specify the full path. (This happend in the test case with the neccessary changes made to default to "cmd.exe"). But yes, it would be great. Greetings, Jaco

3 3

dialog boxex and DestroyWindow
by Ove Kaaven 04 Nov '02

04 Nov '02

I've found an app which calls DialogBoxParam, but destroys the dialog from inside WM_INITDIALOG, yet expects the dialog to still be alive until WM_INITDIALOG processing is done, i.e. case WM_INITDIALOG: ... initialize and write values to lots of controls ... if (user_dont_want_to_see_this_dialog_today) { DestroyWindow(hDlg); ... mess some more with controls (like reading their current values) ... return; } Does anyone have a good way to deal with this? One way might be to make DestroyWindow map to EndDialog in this case (as EndDialog manages to handle this right), but what would the best way to do that be?

2 2

Re: So lets say we do it
by Dimitrie O. Paun 04 Nov '02

04 Nov '02

On October 31, 2002 04:26 pm, Andreas Mohr wrote: > I wouldn't be 100% against placing a Screenshot link on the main page > - it's a mere 99% only. > But with the current menu infrastructure, I'm about 150% against it. > If we added a separate Screenshots menu item (which, by the way, I don't > think is needed, since we do have that nice About page), > then the whole page would grow overly long. Agreed. I say, let's get some of the content in shape, and worry about the form a wee bit later. BTW, any web-design guys around, that may want to take on this task? -- Dimi.

5 13

Debug messages specific to COM components?
by Mike Hearn 04 Nov '02

04 Nov '02

Hi all, I posted a similar query on Thursday but got no response, and was then away for a few days, so I'll try again a few times before filing something in bugzilla and forgetting about it. Basically my question is whether there is any way of restricting debug messages to one particular COM component: I have some problems with seemingly spurious mouse messages going to the Adobe SVG Viewer plugin in IE6 and would like to cut down on the huge log files wine can generate in these circumstances. In case anybody might know of such an issue, I've found that the ASV triggers onMouseMove events for (0,0) incorrectly, and when dragging with the LMB down bad onMouseUp events are handled. I'm guessing Wine is sending mouse messages to the plugin incorrectly, but I'm not really sure how to start verifying that. thanks -mike

1 0