wine-devel

wine-devel@winehq.org

5 participants
84473 discussions

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

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

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 12:53:15 -0500, "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote : > But the question is whether or not CreateProcess _should_ find it, or not. > If it is, than it's a bug in CreateProcess, and working around it is rather > detrimental. If not, than fine, use the full path. We should always try > to fix the bug at the source, not to invent workarounds. Agreed, if a know bug exists it needs to be fixed. I was in a rush when replying to your initial request for clarification, so I didn't express it properly. I however, did look at what the correct behaviour of CreateProcess should be when I came across this. According to MSDN: "The string can specify the full path and file name of the module to execute or it can specify a partial name. In the case of a partial name, the function uses the current drive and current directory to complete the specification. The function will not use the search path. If the file name does not contain an extension, .exe is assumed. Therefore, if the file name extension is .com, this parameter must include the .com extension." So no, I didn't try to create workarounds. As I've said, it is something that bugged me as well. :) Greetings, Jaco

2 2

A heartfelt thank you!
by Dimitrie O. Paun 04 Nov '02

04 Nov '02

To all our WWN editors (past, and present), a big THANK YOU! for doing the Wine's Weekly News. You guys are doing an excellent (and quite important work). I love them dearly. Keep up the good work! :) -- Dimi. P.S. People may think that I lost my mind. Not really, it's backed up somewhere on tape... :) Seriously, I just felt like saying this. So sue me! :P P.P.S. Monday I'm gonna have a full day of meetings at a large financial company, and I hate it. It's gonna be worse than Friday. So if I return to the list in a bellicose mood, please excuse me: you have to go once to understand... :/ P.P.P.S. I love working on Wine -- and the prospect that I have to go to said company tomorrow makes it so obvious, that I just hate ending this email to go to sleep to wake up very early tomorrow to go there... :)))

1 0

My WineHQ menu structure proposal
by Dimitrie O. Paun 03 Nov '02

03 Nov '02

This is my proposal for the WineHQ menu structure, based on the discussions I had with Francois. The Home Page should just be our news page. Many projects opt for this, and I think it's good: News are 'zero' click items. It should consist of the WNN box to the right (as our current home page), and a bigger central box for announcements. Each box should have a link at the bottom to their respective archive pages. Below, the numbers are for reference only, they should not appear on the site. Top Level --------- 1. About 2. Status 3. Screenshots 4. Download 5. Support 6. Documentation 7. Development 8. Contributing 9. Forums Expanded -------- 1. About 1.1 Intro 1.2 Why Wine 1.3 Myths 1.4 Technology 1.5 History 1.6 Related projects 1.7 Who's Who 1.8 Community 1.9 Companies 1.10 Contacts 1.11 Legal (1.1-1.3 may be collapsed in one page, that is served when you click on About; there are too many subitems like this) 2. Status (our current status page, with links to TODOs, etc) 3. Screenshots (add real sexy shots, as discussed in other mail) 4. Download (link to tarballs, and binary packages) 5. Support 5.1 FAQ 5.2 Howto 5.3 Bugzilla 5.4 Troubleshooting 5.5 Application database 5.6 Commercial support 6. Documentation 6.1 User Guide 6.2 Developer Guide 6.3 Packager Guide 6.4 API Docs 7. Development 7.1 Source (page with explanation of the CVS trees, LXR, cvsweb, etc.) 7.2 Developer Hints 7.3 Submitting Patches 7.4 Outstanding Work (page with the 0.9/1.0 TODOs, Tasklist/bug 395, FIXMEs/bug 455, Tasklets/bug 406, most wanted bugs) 7.2 Tools 7.3 References (Win32 documentation, X doc, etc.) 8. Contributing 8.1 Application maintainer 8.2 Bug triage 8.3 Website maintenance 8.4 Development (short page with links to the development section) 8.5 Support Wine-based products 9. Forums 9.1 Mailing Lists 9.2 Newsgroup 9.3 IRC Channel ----- So we don't forget, some related bugs in Bugzilla: Other relevant Web Site tasks ----------------------------- * 597 - How to get the web site files * 598 - Update the Who's Who * 600 - Add a Site Map * 601 - Add drop-down menus * 605 - Add 'tables of contents' * 607 - Add screenshots * 608 - Reorganize the Web site -- Dimi.

7 37

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