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

Re: So lets say we do it

by Francois Gouget

On Thu, 31 Oct 2002, Dimitrie O. Paun wrote: > On October 31, 2002 11:47 pm, Jeremy Newman wrote: > > Here's what I will do. I will start a new design, I will put it up at: > > http://lostwages.winehq.org. A very rough draft of the home page alone with > > new nav should be online late (very very late) sunday night, pending real > > life (TM) does not get in the way. > > Excellent. This is what we need, a little bit of experimentation is needed > here. Yep, it can only help :-) > BTW, how can I contribute to the WineHQ CVS? Can I get access to it? See http://www.winehq.com/development/ Check out Winehq_com. Actually you can also get the same info there: http://www.winehq.com/download/ Argh! Duplication, bad, bad, bad (597). -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The software said it requires Win95 or better, so I installed Linux.

Nov. 1, 2002

Re: RFC: msvcrt _popen/_wpopen/_pclose

by Jaco Greeff

Jaco Greeff wrote: > chrismorgan(a)rcn.com wrote: > >> What is wrong with using wcmd and extending it if necessary? > > > Nothing. I must admit that I have looked at the wcmd code, but if I > remember correctly it lacks a "/C" switch. Yes it lack a "/C" switch, but it has the "/c" switch :) I'm in the process testing and playing a bit, but it seems perfectly do-able. Greetings, Jaco

Nov. 1, 2002

Re: So lets say we do it

by Thomas Wickline

Alexandre Julliard wrote: > "Dimitrie O. Paun" writes: > > > >So the 5% left, install wine, install a Win-app, and play around. > >Great, it works! > > > You forgot a few things here: > > First it doesn't even start because they don't have a config file. OK, > they copy one from somewhere, it doesn't work because the drives are > wrong. The config file that you guy's at Codeweavers use works verrrry well. I have not seen anyone cry about drives being wrong on the codeweavers Discuss list !! And if there is someone with a strange set-up they could read a DOC on how to correct the problem. Most people ask about how to set version to win98 .... since --version was removed. > Then they don't have the proper registry (winedefault.reg? > what's that?) You could look at this registry : http://www.franksworld.net/wine/files/wineregistry.tgz I am in no way saying this is 100% correct but it is at least a good start :) Tom > Then they finally manage to run the installer but it > puts stuff in RunOnce that never gets run so the app doesn't > work. Then they finally make the app run but can't print anything. And > when they ask for help they get told to fight the FAQ-O-Matic crap to > maybe finally find an answer telling them they are an idiot. > > So no, I'm not going to make a general public release just yet... >

Nov. 1, 2002

Re: Wine 0.8 TODO v0.1

by Dimitrie O. Paun

On November 1, 2002 12:52 am, Ender wrote: > Almost. It's on a 100% no-windows install, the only naitve DLL's I use are > installed by IE6 itself - I think I'm using native crypt32/secur32 to get > SSL working, and native wininet. I don't care what the app installs. I care what you do _before_ the app installs. That is, you should have no native DLLs in your fake windows. > It did take some registry hacking to get working, and I didn't note down > what :/ Too bad, these are nice apps to showcase. Maybe you can rediscover? ;) -- Dimi.

Nov. 1, 2002

Re: So lets say we do it

by Dimitrie O. Paun

On October 31, 2002 07:00 pm, Francois Gouget wrote: This is a good start. Here are my comments, based on the following principles: -- while I appreciate (as a geek) the logical nesting of topics, I think they should be organized more around usage patterns. A common topic should be accessible with one click, a obscure one, with two. -- keep things simple, for areas that are of general use (i.e. used frequently by non-developers) > 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?) I think this one should be top-level. I was fascinated for a long while by http://www.gnustep.org/information/progress.html, and I kept visiting the site frequently to monitor their progress. > 1.6. History > 1.7. Alternatives > 1.8. Who's who BTW, this one needs updating *badly*. > 1.9. Wine companies > 1.10. Community > 1.11. Contacts > 1.12. Legal This menu should show as "About" on top level, and when clicked, should expand to the above structure. This is because it's long, and the items here (apart from Status) don't merit front-page status. > 2. News > 2.1. Latest Wine release > 2.2. Latest WWN > 2.3. WWN back issues > 2.4. Press Hopefully we can fit all this in one page, with a clever 1,2 box layout, and we can drop the submenus. > 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 maintenance > 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 This should expand as "About" on click only. The 5.4.x items are a bit too deeply buried, considering that they are high visibility. Maybe we can link to 5.4 from the Status page. Or even better, maybe we can make 5.4 a top-level item, and rename it "Todo". > 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) Too complex. I think only 6.1, and 6.2 belong here, and not as submenus, but part of the page. The rest should be moved under 7. > 7. Development > 7.1. Mostly references to the Wine Developers Guide which is where > most of the information should be. > The distinction between this and the Wine Developers 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 developers. > > 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) What about this: 8. Support 8.1 FAQ 8.2 Howto 8.3 Bugzilla 8.4 Commercial support 9. Documentation 9.1 User Guide 9.2 Developer Guide 9.3 Packager Guide 9.4 API Docs > 10. Forums > 10.1. Mailing lists > 10.2. Newsgroup > 10.3. IRC channel -- Dimi.

Nov. 1, 2002

Re: Wine 0.8 TODO v0.1

by Ender

> On October 31, 2002 10:52 pm, Ender wrote: > > ICQ and IE6 both install and work fine, over here. > > Without any native DLLs? Almost. It's on a 100% no-windows install, the only naitve DLL's I use are installed by IE6 itself - I think I'm using native crypt32/secur32 to get SSL working, and native wininet. It did take some registry hacking to get working, and I didn't note down what :/ - Ender

Nov. 1, 2002

Re: Treeview notifications

by Dimitrie O. Paun

On October 31, 2002 11:32 pm, Dustin Navea wrote: > in TREEVIEW_NotifyFormat shouldnt > (lParam == NF_REQUERY) be (lParam == NF_QUERY) and change the corresponding > line in TREEVIEW_Create since that is the original query? No, the code seems to be OK as it is now. Does this hack fix your problem? Index: dlls/comctl32/treeview.c =================================================================== RCS file: /var/cvs/wine/dlls/comctl32/treeview.c,v retrieving revision 1.108 diff -u -r1.108 treeview.c --- dlls/comctl32/treeview.c 31 Oct 2002 00:54:53 -0000 1.108 +++ dlls/comctl32/treeview.c 1 Nov 2002 05:31:50 -0000 @@ -5045,7 +5045,7 @@ i); i = NFR_ANSI; } - infoPtr->bNtfUnicode = (i == NFR_UNICODE) ? 1 : 0; + infoPtr->bNtfUnicode = 0; return (LRESULT)i; } return (LRESULT)((infoPtr->bNtfUnicode) ? NFR_UNICODE : NFR_ANSI); > I have already > searched throughout the sources and the only place that > TREEVIEW_NotifyFormat is called is in treeview.c in TREEVIEW_Create ... Search again, it's called from the WindowProc as well (line 5339). What do you use to search?!? :) -- Dimi.

Nov. 1, 2002

Re: Wine 0.8 TODO v0.1

by Dimitrie O. Paun

On October 31, 2002 10:52 pm, Ender wrote: > ICQ and IE6 both install and work fine, over here. Without any native DLLs? -- Dimi.

Nov. 1, 2002

Re: Wine 0.8 TODO v0.1

by Dimitrie O. Paun

On October 31, 2002 07:12 pm, Francois Gouget wrote: > I suggest that this should be dynamically generated from the Application > database by looking for applications rated 5 in no-windows mode. I don't like automatically generated pages like the above. They don't have the "human touch" that make them nice. We could invent an automatically generated status page, but it will not be as nice as the one we have. The 'automatic' bit is cool geek-wise, but it almost always sucks. What we need is a nicely done page with 10-15 apps ("Cream of the crop") with links, screenshots, etc., and at the end something like: "For a comprehensive list of apps, go here". Same goes for the 0/9 & 1.0 TODOs. Pointing people to a list of Bugzilla bugs sucks big rocks. It's Not Nice (TM). We can not do nice colors as in the status page, etc. And it shows. -- Dimi.

Nov. 1, 2002

Re: RFC: msvcrt _popen/_wpopen/_pclose

by Jaco Greeff

chrismorgan(a)rcn.com wrote: > What is wrong with using wcmd and extending it if necessary? Nothing. I must admit that I have looked at the wcmd code, but if I remember correctly it lacks a "/C" switch. This I assume is the extending part you are speaking about. Then again, I'm not 100% sure that it will be needed, it might just do the job without touching anything. Come to think of it, it is actually the preferred approach, we don't want to rely on "other" executables. I'll dig a bit... Greetings, Jaco

Nov. 1, 2002