November 2002 - Wine-Devel - list.winehq.org

Re: wine/dlls/rpcrt4 ndr_marshall.c

by Greg Turner

On Thursday 31 October 2002 07:47 pm, Alexandre Julliard wrote: > Fix stupid clone of broken macro, found by Marcus. On Thursday 31 October 2002 07:17 pm, I wrote: > - fix stupid clone of broken macro, found by Alexandre. sheesh! I can't even get the fixer's fixed. oh well :( Like I said in the patch subject, I suck... -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

Nov. 1, 2002

Name, life-cycle, directory structure, autoconf, temporary kludges for wine rpcss subtitute?

by Greg Turner

Sorry, in advance, for this barrage of questions... but I'm getting anxious to proceed with this thing. Naming: This guy needs a name if I'm ever going to start coding it. How about: Wine Remote Procedure Call System Server aka wrpcss.exe.so? A little misleading with the "ss" thing, but this name will look familiar to windows users, and is more accurate than my previous idea of wine-epmap, since it will eventually need to do more than just endpoint mapping. I pretend this is the right name below, but if there's a better one, just substitute that in everywhere you see "wrpcss" in the following discussion. Life Cycle: Some scenarios will require wrpcss to run all the time as a daemon-type-thingy; most wont -- the majority of scenarios require dynamic on-demand invocation and auto-termination upon unmapping of all registered endpoints, as Ove suggested. Are command line arguments an appropriate way to differentiate between these modes? This ends up going back to the open question of how to implement services in wine; but, of course, I don't want to wait for this to be resolved before proceeding. Whatever solution wine implements for services, adapting wrpcss to it won't be insurmountable (assuming it's a good solution). Also: if run as a service, how do I get "detached" without using "fork()"? Is there some existing example of this I ought to emulate? Directory Structure: dlls/rpcrt4/wrpcss/ ? programs/wrpcss/ ? Autoconf: I can try to implment the necessary infrastructure myself, but if history is any guide, I will screw it up. If anyone is feeling generous with their time, they could give me a skeleton to fill in. Temporary Kludges: DCE does, indeed, provide the necessary idl to implement the endpoint mapper. Unfortunately, although the IDL is reasonably simple, there are just too many types in there to "do it right" from the beginning. Meanwhile, I am getting sick of dragging along the unmerged server parts (it isn't that hard, but I'm lazy). So, as discussed earlier, I propose the named-pipes hack until a full implementation is possible. I would, of course, take some care to keep the kludge-based parts separate from meaningful, potentially permanent parts of the code... howsabout I just listen at \\.\pipe\wrpcss for the time being? thanks for your input, -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

Nov. 1, 2002

Re: SIGSEGV in IDirectDrawImpl_EnumDisplayModes

by Matthew Bloch

On Thursday 31 October 2002 18:41, Lionel Ulmer wrote: > > Sorry, that was the method I posted, I happened to paste the wrong > > function name; this is the entire function with line 852 marked: > > Care to give me the actual data type of 'mp_directDraw' ? It seems that as > you supposed, it does not use the correct function pointer when you use > 'mp_directDraw->CreateSurface' and call instead 'EnumDisplayModes' thus, of > course, leading to a crash as the callback function is not filled in > properly. Declared in the header as: IDirectDraw* mp_directDraw; I'm working from the position of not knowing much about DirectDraw, so this is all new territory. > The only thing I find strange is that you call CreateSurface with the 3rd > argument being NULL and we should see that in the trace for > 'EnumDisplayModes'... Yes, to my eye it looks like a linking problem but I'm not sure how to tell. Maybe if I whittle it down to a single .c file which I can post to the list it'll make it easier to diagnose. -- Matthew Bloch Bytemark Computer Consulting Limited http://www.bytemark.co.uk/ tel. +44 (0) 8707 455026

Nov. 1, 2002

Re: I suck...

by Alexandre Julliard

Greg Turner <gmturner007(a)ameritech.net> writes: > Thanks for catching the first, Alexandre, or > I wouldn't have caught this second... Actually I didn't catch anything, the first one was fixed by Marcus. -- Alexandre Julliard julliard(a)winehq.com

Nov. 1, 2002

Re: So lets say we do it

by Duane Clark

Andreas Mohr wrote: > On Thu, Oct 31, 2002 at 03:07:15PM -0500, Dimitrie O. Paun wrote: > >>On October 31, 2002 03:00 pm, Andreas Mohr wrote: >> >>>>Not yet too late for another 'Halloween' release though ;) >>> >>>Yep... >>> >>>...next year ! ;) >> >>I don't want to jinx it, but at the rate we're going, we'd be >>lucky to do a 1.0 'Halloween' release next year :/ > > Why, the current rate is avalanche-like ;) > > I'm growing ever more astonished about the increase in wine-patches per day... > > But of course you're sorta right, we're still quite far off the mark. (Jumping in a little late) I seem to remember someone once posted a graph of the growth in wine source (I think it was a line count). Seems to me it is about time for another one.

Nov. 1, 2002

Re: IDL/header issues

by Alexandre Julliard

Ove Kaaven <ovehk(a)ping.uio.no> writes: > IDL-generated files would also eventually obsolete all the current > wine/obj_*.h files, but those obj_* files seem to be somewhat more > logically structured than MS's own IDL files, should we craft Wine's IDL > files accordingly, and maybe have some top-level .idl files in include/ > and some sub-.idl files under include/wine/, like it's done now in e.g. > objidl.h? No, I think we should follow the Microsoft way. Sure it's a mess, but so is the rest of the API anyway... And every time we tried to do things better than Microsoft we ended up having to revert it. -- Alexandre Julliard julliard(a)winehq.com

Nov. 1, 2002

Re: IDL/header issues

by Greg Turner

On Thursday 31 October 2002 06:08 pm, Ove Kaaven wrote: > Note that I will work on ReWind, not directly on Wine, so I probably > won't be able to submit massive "change all files to include this > instead of that" patches (that apply to Wine) with any new files. I get the ReWind-patches digest. I'd be happy to continue merging your changes back into wine, at least insofar as I know how... but will they all funnel through that list, or do I need to watch cvs? -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

Nov. 1, 2002

Re: Wine 0.8 TODO v0.1

by Francois Gouget

On Thu, 31 Oct 2002, Dimitrie O. Paun wrote: [...] > A. WineHQ work > 0. Reorganize a bit the navigational menu > 1. Add a screenshot link to the homepage See also my other email... > 2. Create some really sexy screenshots Advice on screenshots: - if the screenshot is just about one application then only that application window should be in the screenshot rather than the whole desktop. - do not try to cram 15 different applications in the screenshot. A lot of screenshots I see look like a mess and that's not good. - try to avoid JPGs as they produce artifacts on text. Use PNG instead. Unless you have photos in the screenshot, you can even convert to 256 colors with no loss of quality if you use 'Positioned Color Dithering' in Gimp (reduces image size significantly). > 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) Agreed. > 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. I suggest that this should be dynamically generated from the Application database by looking for applications rated 5 in no-windows mode. And it is the task of application database mantainers and application owners to control these applications and forcefully downgrade applications that incorrectly received a 5 rating. There's still a risk of problem if too many applications receive and deserve 5 rating, but is that the case? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ "Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)" -- Linus Torvalds

Nov. 1, 2002

IDL/header issues

by Ove Kaaven

Now WIDL is good enough to generate a drop-in replacement for Wine's wtypes.h (attached) from a suitably crafted Wine-compatible wtypes.idl (also attached). I've included all the definitions that were already in Wine's wtypes.h (but I was too lazy to do everything that's in Microsoft's wtypes.idl yet). What do you think, is this good enough to go into Wine? Are there some desirable changes to widl or wtypes.idl? And should IDL files go into the main include dir along with the other Win32 headers? IDL-generated files would also eventually obsolete all the current wine/obj_*.h files, but those obj_* files seem to be somewhat more logically structured than MS's own IDL files, should we craft Wine's IDL files accordingly, and maybe have some top-level .idl files in include/ and some sub-.idl files under include/wine/, like it's done now in e.g. objidl.h? Note that I will work on ReWind, not directly on Wine, so I probably won't be able to submit massive "change all files to include this instead of that" patches (that apply to Wine) with any new files.

Nov. 1, 2002

Re: So lets say we do it

by Francois Gouget

On Thu, 31 Oct 2002, Dimitrie O. Paun wrote: [...] > IMO we need to reorganize the front page a bit more than that. > Namely: > -- the big "Navigation" box is wasted space, because > 1. It contains items everybody expects as a left-hand menu > 2. Contains no real content > -- while pretty, the layout is a non-standard, and is a wee bit > too far away from the "least surprise" principle > -- the news/announcements need a bit more space I pretty much agree. I will also add a me too concerning screenshots: this is the first thing I look for and I'm pretty disappointed if I don't see any. > So here is my suggestion: > 1. Have a left-hand navigation menu, as follows: > Home > About > Download > Documentation > Development > Mailing Lists > Screenshots I proposed something similar in task 608 but did not have much feedback (though it was mentioned a couple of times before). Here's my menu tree proposal: Top Level --------- 1. About 2. News 3. Screenshots 4. Application Database 5. How to contribute 6. Download 7. Development 8. Documentation 9. Bugs 10. Forums The goal is to make important items like the Application Database, Screenshots, or How to contribute, more visible, and to make it easier to locate where things are. I would also modify the home page to: - display the introduction to Wine (included from the About section 1.1.) - display a (small) screenshot (worth 10.000 words). Newman's idea is pretty good for that. - the Home page can be accessed by clicking on the WineHQ icon (but I'm not opposed to adding a menu entry) Complete menu tree ------------------ You will note that there are sometimes 3 levels of 'menus'. The third level would most likely not actually be a menu but just sections on the page and an entry in the relevent table of content (task 605). I just included them here to clearly show where each item in the web site goes. 1. About 1.1. Intro 1.2. Why Wine 1.3. Wine myths debunked 1.4. Technical details 1.5. Status (or move this to the How to contribute or Development section?) 1.6. History 1.7. Alternatives 1.8. Who's who 1.9. Wine companies 1.10. Community 1.11. Contacts 1.12. Legal 2. News 2.1. Latest Wine release 2.2. Latest WWN 2.3. WWN back issues 2.4. Press 3. Screenshots General screenshots, typically full desktops. Also point people to the Application Database. 4. Application Database 5. How to contribute 5.1. Application maintainer 5.2. Bug triage 5.3. Web site maintainance 5.4. Development 5.4.1. Wine 0.9.0 task list 5.4.2. The Tasklist (bug 395) 5.4.3. The FIXMEs (bug 455) 5.4.4. The Tasklets (bug 406) 5.4.5. The most wanted bugs (a Bugzilla query returning bugs with the most votes) 5.6. Write regression tests 5.5. Support Wine-based products 6. Download 6.1. Binary Packages 6.2. Source tar files 6.3. Source tars for CVS 6.4. LXR 6.5. CVS 6.6. CVS Web 6.7. Other CVS modules (web site) 7. Development 7.1. Mostly references to the Wine Developpers Guide which is where most of the information should be. The distinction between this and the Wine Developpers Guide is that the guide should be more about general principles and less about which specific web server to connect to (although that's more a download issue anyway). 7.2. References Pointers to online resources (Win32 documentation, X doc, etc.) useful to Wine developpers. 8. Documentation 8.1. User Guide 8.2. Howto 8.3. FAQ 8.4. Developer Guide 8.5. API Documentation 8.6. Packager Guide 8.7. How to get commercial support 9. Bugs (Bugzilla) 10. Forums 10.1. Mailing lists 10.2. Newsgroup 10.3. IRC channel 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 -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ "Utilisateur" (nom commun) : Mot utilisé par les informaticiens en lieu et place d'"idiot".

Nov. 1, 2002