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

Re: Wine 0.8 TODO v0.1

by Carlos Lozano

El jue, 31 de oct de 2002, a las 15:02, Alexandre Julliard escribio: > "Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > > > 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) > > That alone should take a couple of years <g> It depends on the complex of the apps (winmx,icq or ie6,officeXP ;) and what you means by "works well" ;) 70-80% or 95-100% functionality?? A list of apps should be prepared at least several months before of a release, and sometime before of release's time freeze the advance and concentrate in stabilize this applications. It should be good select the apps seeing the DLLs needed. Hmm, surely after of the release the development should be divided in stable/unstable, because it should be a bad thing that 8.0 should run "Ex. ie5" and 8.1 no :/ 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

Oct. 31, 2002

Re: Wine 0.8 TODO v0.1

by Joerg Mayer

On Thu, Oct 31, 2002 at 05:38:10PM -0500, Dimitrie O. Paun wrote: > 4. Enlist some 'official' distribution maintainers > (at the minimum RedHat, Suse, UnitedLinux, Debian) Add Mandrake, remove UnitedLinux: UnitedLinux is a SERVER distro (or, to be more precise: the core of several server distros). Ciao Jörg -- Joerg Mayer <jmayer(a)loplof.de> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.

Oct. 31, 2002

Re: Getting actively involved in the Wine project

by Francois Gouget

Hi Thomas, Thomas Wickline wrote: [...] > Wine users , CodeWeavers & WineX customers could do Previews/Demo's at > there local lug meetings as well.. This is what I did a couple months > back and it was a huge success there were Windows users at the meeting > to see Linux and Win app's being run on Linux ... Also it gives Linux > users a look at wine as well. > So I suggest that we try to encourage wine users to volinteer to show > Wine at there local user groups/Installfest/Computer shows and so on. I agree. Making Wine presentations at local LUGs can only be a good thing. It can dispel some myths and it might even help Wine recruit new developpers :-) CodeWeavers has actually done a few presentations on "CrossOver and Wine" at local LUGs. I did one recently at the Linux User Group Of Davis (LUGOD, a pretty nice LUG) quite recently. You can find the presentation online at the following URL. http://www.lugod.org/presentations/crossover/ 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 <g>). -- Francois Gouget fgouget(a)codeweavers.com

Oct. 31, 2002

Re: So lets say we do it

by Dimitrie O. Paun

On October 31, 2002 05:05 pm, Jeremy Newman wrote: > Oh pick ME ME ME! :-) OK mister, you're on! :) > I don't volunteer my weekends often, so speak now. 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 So here is my suggestion: 1. Have a left-hand navigation menu, as follows: Home About Download Documentation Development Mailing Lists Screenshots Look at http://www.gimp.org. It's not the nicest, but the home page is simple, and has a link to almost all relevant info: Download, Mailing Lists, FAQ, Docs, Screenshots, etc. You need only *one* click. In our site, you need 3-4 clicks, scrolling, etc. Vast majority of people don't have such a long attention span. Look for example at http://mesa3d.sourceforge.net/, it's not pretty, but you can get to most stuff in *one* click. 2. The main area (in the middle) should be "Announcements" We should have there the last 2-3 announcements, and at the end a link to the archives. Each announcement gets a bold title, and a few lines of text. Here we'll have Wine releases (the few lines of text will contain the What's New stuff), WWN releases (for which we can lists the story titles), etc. I'll stop here. What do you think? -- Dimi.

Oct. 31, 2002

Re: Wine 0.8 TODO v0.1

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > 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) That alone should take a couple of years <g> > -- 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 IMO the goals for 0.9 will be reached before the ones for 0.8 so you might as well put everything together... > D. Stabilize utilities > 0. Get rid of the init directive from .spec files This requires dll separation... > E. Important fixes > Alexandre, what to you see here? I think the window management stuff is important, otherwise you can't install most apps without using desktop mode. But it's already in the 0.9 goals (and I'm working on it). -- Alexandre Julliard julliard(a)winehq.com

Oct. 31, 2002

Wine 0.8 TODO v0.1

by Dimitrie O. Paun

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.

Oct. 31, 2002

Re: So lets say we do it

by Andreas Mohr

On Thu, Oct 31, 2002 at 04:05:21PM -0600, Jeremy Newman wrote: > On Thu, 2002-10-31 at 15:30, Dimitrie O. Paun wrote: > > 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? > > Oh pick ME ME ME! :-) > > Wait a minute, I'm already in charge of that. Must have been slacking > off again. > > Here's my idea. On the front page, add a new box above the WNN box, > below the Latest Wine release box. This box would be a random screenshot > pulled from the AppDB, (or a predefined list of available screenshots). > I can whip up a new page/section/what have you called "Screenshots". > This requires a new button for the front page. It should be linked to on > the About page, and the screenshots page links back to the About page. A > little cross referencing if you will. > > Does this work for anyone. I can probably do this during the weekend in > my "off" hours. Two words: Earth-shattering idea ! :-) (oh wait, there's just been an earthquake in Italy :-\) That's a very good proposal. I guess all that's left for us to do is to make sure About looks terrib^H^Hific :) -- "My attitude is, everybody should try competing with Microsoft once in their life. Once." - Marc Andreessen, former Netscape lead employee, in a "browser wars" interview

Oct. 31, 2002

Re: So lets say we do it

by Jeremy Newman

On Thu, 2002-10-31 at 15:30, Dimitrie O. Paun wrote: > 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? Oh pick ME ME ME! :-) Wait a minute, I'm already in charge of that. Must have been slacking off again. Here's my idea. On the front page, add a new box above the WNN box, below the Latest Wine release box. This box would be a random screenshot pulled from the AppDB, (or a predefined list of available screenshots). I can whip up a new page/section/what have you called "Screenshots". This requires a new button for the front page. It should be linked to on the About page, and the screenshots page links back to the About page. A little cross referencing if you will. Does this work for anyone. I can probably do this during the weekend in my "off" hours. I don't volunteer my weekends often, so speak now. -- __ _WebGeek/SysAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | / -_) | | / ' \/ _` | ' \ -= jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

Oct. 31, 2002

Re: RFC: msvcrt _popen/_wpopen/_pclose

by chrismorgan＠rcn.com

What is wrong with using wcmd and extending it if necessary? Chris > > From: "Jaco Greeff" <jaco(a)puxedo.org> > Date: 2002/10/31 Thu PM 04:27:43 EST > To: wine-devel(a)winehq.com > Subject: RFC: msvcrt _popen/_wpopen/_pclose > > Hi, > > I want some comments on the possibility of a _popen/_wpopen/_pclose > implementation in Wine. Reference available at: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html… > > The open functions basically operate in the same way as the popen function > in Linux, ie. it spawns a process with the command via the command > interpreter. Now, unfortionately we don't have our won cmd.exe available, > but should people really need this functionality it might not be too much to > ask as to copy it from a working Windows installation. > > In my mind, supporting the Win 95/98 command interpreters might be a > nightmare - my gutt feel is that these two rely too much on DOS internals to > be sucessfully launched via Wine. No, I haven't tried it, so I might be > completely wrong. Either way, something like this might be better > implemented via the Win NT/2000/XP cmd.exe. (I'll test my assumptions > tomorrow, I don't have access to the command interpreters tonight.) > > I've hacked (yes, it was quick) a potential implementation of the _popen > family of functions. (Haven't compiled, haven't tested, this is just and RFC > - if it can work, I'll spend some real time on it.) Anyway, here it is, > comments appreciated: > > --[ inline-ish RFC ]---- > > #include "config.h" > #include "wine/port.h" > > #include <stdio.h> > #include <stdlib.h> > #ifdef HAVE_UNISTD_H > # include <unistd.h> > #endif > > #include "winbase.h" > #include "winnls.h" > #include "wine/unicode.h" > #include "msvcrt/stdio.h" > #include "msvcrt/string.h" > > #include "wine/debug.h" > > #define POPEN_FLAG_READ 0x0001 > #define POPEN_FLAG_WRITE 0x0002 > #define POPEN_FLAG_TEXT 0x0004 > #define POPEN_FLAG_BINARY 0x0008 > > inline CHAR *LPCWSTRToLPSTR(const LPCWSTR lpwstrIn, INT nIn) > { > INT nLen = WideCharToMultiByte(CP_ACP, 0, lpwszIn, nIn, NULL, 0, NULL, > NULL); > CHAR *szOut = (CHAR *)malloc((nLen+1)*sizeof(CHAR)); > if (szOut) > { > WideCharToMultiByte(CP_ACP, 0, lpwszIn, nIn, szOut, nLen+1, NULL, NULL); > szOut[nLen] = '\0'; > } > return szOut; > } > > INT POPEN_parseModeFlags(const CHAR *szMode) > { > INT nFlags = 0; > while (szMode && *szMode) > { > switch (*szMode) > { > case 'r': > { > if (nFlags & POPEN_FLAG_WRITE) > WARN(": _popen: Cannot set both read and write open > flags, ignoring read flag\n"); > else > nFlags = nFlags & POPEN_FLAG_READ; > break; > } > case 'w': > { > if (nFlags & POPEN_FLAG_READ) > WARN(": _popen: Cannot set both read and write open > flags, ignoring write flag\n"); > else > nFlags = nFlags & POPEN_FLAG_WRITE; > break; > } > case 'b': > case 't': > { > FIXME(": _popen: %c mode flag not implemented, ignoring\n", > *szMode); > break; > } > default: > { > WARN(": _popen: unknown mode flag %c, ignoring\n", *szMode); > break; > } > } > } > return nFlags; > } > > MSVCRT_FILE *MSVCRT_popen(const CHAR *szCommand, const CHAR *szMode) > { > MSVCRT_FILE *fProcess = NULL; > > if (!szCommand || !szMode) > return NULL; > > INT nFlags = POPEN_parseModeFlags(szMode); > if (!(nFlags & (POPEN_FLAG_READ|POPEN_FLAG_WRITE))) > { > ERR("No open mode flag r or w specified\n"); > return NULL; > } > > /* _popen/_wpopen executes the required command via the command > * processor, either command.com (Win 95/98) or cmd.exe (Win NT/2000/XP). > * Wine does not currently have it's own "cmd.exe" hence we cannot > * really do anything more at this point. However, we try to lauch it > * and hope for the best... > */ > CHAR *szExec = (CHAR *)malloc(strlen("wine -- C:/cmd.exe -C > ")+strlen(szCommand)+1); > if (szExec) > { > sprintf(szExec, "wine -- C:/cmd.exe -C %s", szCommand); > fProcess = popen(szExec, (nFlags & POPEN_FLAG_READ) ? "r" : "w"); > if (!fProcess) > ERR("Execution of C:/cmd.exe via wine failed\n"); > else > WARN("Launch of %s succeeded, no guarentees of success made\n", > debugstr_a(szExec)); > free(szExec); > } > > return fProcess; > } > > MSVCRT_FILE *MSVCRT_wpopen(const WCHAR *wszCommand, const WCHAR *wszMode) > { > MSVCRT_FILE *fProcess = NULL; > > if (!wszCommand || !wszMode) > return NULL; > > CHAR *szCommand = LPCWSTRToLPSTR(wszCommand, strlenW(wszCommand)); > if (szCommand) > { > CHAR *szMode = LPCWSTRToLPSTR(wszMode, strlenW(wszMode)); > if (szMode) > { > fProcess = _popen(szCommand, szMode); > free(szMode); > free(szCommand); > } > free(szCommand); > } > > return fProcess; > } > > int MSVCRT_pclose(MSVCRT_FILE *fProcess) > { > if (!fProcess) > return -1; > return pclose(fProcess); > } > > > >

Oct. 31, 2002

Re: Wine securityflaw.

by Raul Dias

Greg Turner <gmturner007(a)ameritech.net> wrote: >On Thursday 31 October 2002 08:10 am, Raul Dias wrote: >> My $0.02, >> >> A way to make it more secure is to catch key API calls and decide if >> the application is allowed to run it or not. > >not a bad idea. > >> Wine could implement a clean Security Layer: YES > >Clean, perhaps, but secure? That depends on what you are trying to >achieve: since the unix API is available to apps running under wine, >such measures will only secure applications which don't specifically >check for wine and circumvent its api-level security measures. > >So, for example, this could be used to protect a system against security >flaws in Internet Exploder or Outlook... but a malicious virus writer >could work around winapi-based security provisions, as discussed >earlier in this thread. In this case I agree that the OS should provide the security layer, not wine. Wine should provide security only for (or "at least for") WIN32 API flaws. []'s Raul Dias > >-- >gmt > >"The purpose of government is to rein in the rights of the people" > --President Bill Clinton, MTV interview, 1993 >

Oct. 31, 2002