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

Re: Wine 0.8 TODO v0.1 + help request :)

by Carlos Lozano

Hello everybody :), Could you send me a list of the popular apps what you have been able to install+run more or less flawless (using only builtin dlls)??? o Name of the app. o Version. o URL, if it can be free downloaded. * popular apps: Applications used by a large number of people in * multiples countries :) * install+run flawless Thanks, Regards, Carlos. -- ___ _ \ | / Infraestructuras | . |._ _ _| | ___ ___ ___ http://www.andago.com | || ' |/ . |<_> |/ . |/ . \__ GNU/Linux |_|_||_|_|\___|<___|\_. |\___/ _ \ __|\ \ / Carlos A. Lozano <___'/ | \ -_) __/\__ \ > < -_) [ carlos.lozano(a)andago.com ]\___|_| ____/ _/\_\___| [ calb(a)epsxe.com ] http://www.epsxe.com

Nov. 1, 2002

Re: Wine 0.8 TODO v0.1

by Carlos Lozano

El jue, 31 de oct de 2002, a las 23:56, Dimitrie O. Paun escribio: > On October 31, 2002 06:02 pm, Alexandre Julliard wrote: > > "Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > > > -- Users can start using Wine > > > -- works well for a fair number of apps > > > -- no MS DLLs required (from real Windows) > > > > That alone should take a couple of years <g> > > Oh, what next, Murphy was an optimist?!? :))) > > If we run 20 of the top 50 downloads from Tucows, we're > doing good. I don't think we're that far off. Carlos, > you we were doing some tests, care to look into this one? Oki doki :) Regards, Carlos. -- ___ _ \ | / Infraestructuras | . |._ _ _| | ___ ___ ___ http://www.andago.com | || ' |/ . |<_> |/ . |/ . \__ GNU/Linux |_|_||_|_|\___|<___|\_. |\___/ _ \ __|\ \ / Carlos A. Lozano <___'/ | \ -_) __/\__ \ > < -_) [ carlos.lozano(a)andago.com ]\___|_| ____/ _/\_\___| [ calb(a)epsxe.com ] http://www.epsxe.com

Nov. 1, 2002

Re: Status of libwine MFC and msvcrt compilation

by Francois Gouget

On Fri, 1 Nov 2002, Uwe Bonnes wrote: > Hallo, > > what is the status of winelib compilation of MFC and msvcrt? I don't think compiling msvcrt with Winelib has ever been attempted. Concerning compiling the MFC it has been a long time (>6 months?) since I tried. Shouldn't be must worse than before <g>. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux: Because rebooting is for adding new hardware

Nov. 1, 2002

Status of libwine MFC and msvcrt compilation

by Uwe Bonnes

Hallo, what is the status of winelib compilation of MFC and msvcrt? Thanks -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Nov. 1, 2002

Re: So lets say we do it

by Andreas Mohr

On Thu, Oct 31, 2002 at 11:18:56PM -0800, Francois Gouget wrote: > On Thu, 31 Oct 2002, Dimitrie O. Paun wrote: > > 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). IMHO, the CVS docu should *all* be moved into Wine Users Guide (basic CVS download only ! with pointer to Devel Guide) and Wine Developers Guide (generating patches, applying diffs, ...), and then have only *links* on WineHQ point to the static links in the HTML versions of these documents. I've been planning to do this for quite a while, but, ya know, time and stuff... ;-) There wasn't much to be said about Winehq_com here, but I just wanted to point out that CVS docu in general is very suboptimal. -- The Declaration of Software Freedom: http://freedevelopers.net/freedomdec/index.php

Nov. 1, 2002

Re: Versions & mass-appeal

by Johan Gill

On Thu, 31 Oct 2002, Dimitrie O. Paun wrote: > On October 31, 2002 03:35 am, Johan Gill wrote: > > Even with perfectly working builtin dlls, one needs overrides for the > > native dlls that are proprietary, or the loading will fail. Or is this a > > bug? > > This doesn't sound right. Can you give some examples of that happening? Sure. Sid Meier's Alpha Centauri uses sound.dll, which contains some convenience sound stuff. If I keep the default loadorder, "builtin","native", Wine tries to load sound.dll as builtin and fails, but does not try to treat the file as native. /Johan Gill, johane(a)lysator.liu.se

Nov. 1, 2002

Re: Getting actively involved in the Wine project

by Francois Gouget

On Fri, 1 Nov 2002, Thomas Wickline wrote: [...] > Since were talking about this *great* winehq site > update. What do you people think about a small ... > LUG resources page for people who are interested > in doing presentations ? We might find a place to put it but I am not sure we should: the web site must remain focused otherwise it becomes bloated and harder to navigate for everyone. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ I haven't lost my mind, it's backed up on tape around here somewhere...

Nov. 1, 2002

Re: So lets say we do it

by Francois Gouget

On Fri, 1 Nov 2002, Dimitrie O. Paun wrote: > On October 31, 2002 07:00 pm, Francois Gouget wrote: > > This is a good start. Here are my comments, based on > the following principles: [...] > > 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. They don't have screenshots. What the hell is wrong with them? Ah, they hid them carefully like us... Anyway, I'm not sure 'Status' should be top-level and if you look on GNUStep's site it is in fact level 2 (it's a submenu of 'Information'). [...] > > 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. My thinking is that only the top-level items would be visible on the home page and then you can click on an item to expand it and go to its first page. Gimp (http://www.gimp.org) is a good example of that. When you arrive on the home page you don't see the sub-items of the Documentation menu, and if you go to the 'Documentation' page you don't see the sub items of 'The Gimp'. Actually, if we want to reduce the number of top-level menus in my proposal we could make 'Screenshot' a sub item of 'About' as long as About is expanded when you go to the site's home page. Again, see how it works in the Gimp's web site: 1. The Gimp 1.1. About The Gimp 1.2. Screenshots 1.3. About this site ... 2. Documentation 3. Resources 4. Download 5. Gimp Art 6. Important links Once we have the menu hierarchy we can decide how to display them. I see four possible ways: 1. not pre-expanded left-side menus http://www.gimp.org/ 2. pre-expanded left-side menus http://www.gnustep.org/ 3. drop-down menus http://www.ca.com/ 4. two-level horizontal menu http://www.tcl.tk/software/ I vote for 1. > > 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. I don't think these can fit on one page. For instance the back issues cannot be on the same page as the current issue. So I think the most natural way to deal with this is to have sub-menus. > > 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. My thinking was that all 5.x items would be on the same page and that the 5.x menus would just point to the relevant section of that page. The 5.4.x would not actually be visible on the page and just exist as sections in the page. That's subject to that page not being too long of course but that should be ok. > Or even better, maybe we can > make 5.4 a top-level item, and rename it "Todo". No. I don't want to give it priority or separate it from the other extremely important ways to contribute to Wine. > > 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. Yeah, they can be in one or the other. The main thing to avoid is to duplicate them. The reason why I put them there is that they are about downloading or retrieving stuff while the Development page should be more about what to do once you have the source. [...] > > 8. Documentation [...] > > 9. Bugs > > 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 Looks good. I like it. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The nice thing about meditation is that it makes doing nothing quite respectable -- Paul Dean

Nov. 1, 2002

Re: Getting actively involved in the Wine project

by Thomas Wickline

Francois Gouget wrote: > Hi Thomas, > > > > http://www.lugod.org/presentations/crossover/ Hi Francois, Thanks I had a 14 page .ppt slide show. Since were talking about this *great* winehq site update. What do you people think about a small ... LUG resources page for people who are interested in doing presentations ? I am going to take some Vacation day's from my job next week. And catch up on some things.. So I should have some time to put into this :) Thomas > > > Feel free to check it out and use it as inspiration if you want to make > a presentation (credit to CodeWeavers appreciated if you use significant > portions of it ). > >

Nov. 1, 2002

Re: Wine 0.8 TODO v0.1

by Thomas Wickline

Dimitrie O. Paun wrote: > 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. > Hello Dimi, List This is exact same question that I brought up when I did the TODO's update on the status page :) I ask if TODO's should be .9/1.0 ToDo's ??? Or just ToDo's in general. Maybe after all this is hashed out I can go back and re-do the todo's section of the status page..... 0.8.0 ToDo's 0.9.0 ToDo's 1.0.0 ToDo's That is what I wanted to do ... but wanting and doing is two very differant things.. First off I am very new to Wine my self and I just jumped in and and started with status page updates. Why ?? Because I think if a new user comes and looks at the frontpage and then ( what is Wine? ) then ohh shit there is a status page :) :) Then they look and it has not been updated in a YEAR !!! Then they have NO Freaken IDEA about the current status of Wine .... So I ask Alexandre if he would update it :) And I recieved a nice reply .. I would like for someone to volinteer to do this .. And here I am ... Is the Status page up to date ?? @#*% NO ... I need to add in alot of missing parts.. dlls/shlwapi is a good example Marcus Meissner as worker for : ole32, oleaut32. Jukka Heinonen as worker on WineDos I have not made one single change to the Status of any of the Documentation !! Then in the future if ** YOU** make a change to comctl32/listview and if you feel the status has went from say 5% to 10% -- ( the Status page goes in 5% increments.. ) And at the same time you have done some work on the DOC's .. All you need to do is send me a message and say ..... Hey, comctl32 is now --% and the DOC status is now whatever .. And ill update it ! and reflect the change in the Change Log. The way it is now I Search around for who is working on what .. And then PESTER the info out of them ;) I don't like doing it this way. But it is the only way I have at this time. I just want to say thanks to everyone who replied and gave Feed Back ( it really helps ) And since im new here I can't just make %% up off the top of my head and wait for someone to say .. What the HELL that is not 85% its more like 60% then change it to what it really is .. Tho it did think about it a time or two :) Thomas Wickline

Nov. 1, 2002