This will probably get renamed to Wine 0.9 TODO, after Alexandre's clarification, but I haven't changed the name just yet, to avoid confusion.
Once 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 (Beta at: http://lostwages.winehq.org) 0. Website redesign Jeremy Newman jnewman@codeweavers.com 1. Reorganize the navigational menu There is a proposal being discussed on the list 2. Create some really sexy screenshots -- one app per screenshot, avoid cluttered desktop -- minimize size, if possible by using 'Positioned Color Dithering' 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) Agreed on the list. Should be written in SGML, so we can output all sorts of formats. Which means we need layouts, etc. Any takers? 4. Enlist some 'official' distribution maintainers (at the minimum RedHat, Suse, Mandrake, 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. Carlos clozano@andago.com is running with it.
B. Documentation work Andy, take it away! :) 0. We need to figure first _what_ is out of date.
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 WineSetupTk proposed by Jeremy White jwhite@codeweavers.com 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 6. Have a wineboot script for RunOnce stuff
D. Stabilize utilities 0. Get rid of the init directive from .spec files Alexandre Julliard julliard@winehq.com volunteered 1. Make sure the .spec file format is fairly stable Any other things that may need changing here? 2. Ensure the various utilities' options are stable Anything here?
E. Important fixes 0. Window management rewrite, so we can install apps in managed mode.
In the reactos rosapps source tree we have started on a front-end for regedit.exe that uses the regedit from wine/programs. Would you guys like this for 0.9/1.0? If so, I am sure RobD would relicense as his work is based on the LGPL work.
Thanks Steven
--- "Dimitrie O. Paun" dpaun@rogers.com wrote:
C. Wine configuration 0. Merge configuration into the registry
- Write control panel applets for editing it
- Have decent defaults so we can start control panel without prior configuration
- Have wizard like app to autoconfigure wine
WineSetupTk proposed by Jeremy White jwhite@codeweavers.com 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 6. Have a wineboot script for RunOnce stuff
D. Stabilize utilities 0. Get rid of the init directive from .spec files Alexandre Julliard julliard@winehq.com volunteered
- Make sure the .spec file format is fairly stable
Any other things that may need changing here? 2. Ensure the various utilities' options are stable Anything here?
__________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
On November 1, 2002 09:17 pm, Steven Edwards wrote:
In the reactos rosapps source tree we have started on a front-end for regedit.exe that uses the regedit from wine/programs. Would you guys like this for 0.9/1.0? If so, I am sure RobD would relicense as his work is based on the LGPL work.
I think Wine would welcome such a contribution, sure. It would be nice to have it available for 0.9, but I'm not sure it's mandatory. What's its current status?
At the moment I think it will let you browse the registry but not edit it from the GUI. Rob has agreed to relicense his work but atm he and I are short on time and working on other things. I can do a code drop to you guys if someone on the WINE side has the time to adopt it and merge. If not it will be a week or two before I can try and merge it in my local cvs.
Thanks Steven
I think Wine would welcome such a contribution, sure. It would be nice to have it available for 0.9, but I'm not sure it's mandatory. What's its current status?
-- Dimi.
__________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
On November 2, 2002 03:17 pm, Steven Edwards wrote:
At the moment I think it will let you browse the registry but not edit it from the GUI. Rob has agreed to relicense his work but atm he and I are short on time and working on other things. I can do a code drop to you guys if someone on the WINE side has the time to adopt it and merge. If not it will be a week or two before I can try and merge it in my local cvs.
Thanks cool I guess -- there's no huge rush. Not to say that someone on the Wine side should not pick it up...
What about reboot.so or similar support? Andreas said he was deffering sending in an official patch. I was willing to take ownership over that (whether from scratch, or based on work done so far) is Andreas isn't interested any more.
Shachar
Dimitrie O. Paun wrote:
This will probably get renamed to Wine 0.9 TODO, after Alexandre's clarification, but I haven't changed the name just yet, to avoid confusion.
Once 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 (Beta at: http://lostwages.winehq.org) 0. Website redesign Jeremy Newman jnewman@codeweavers.com
- Reorganize the navigational menu
There is a proposal being discussed on the list 2. Create some really sexy screenshots -- one app per screenshot, avoid cluttered desktop -- minimize size, if possible by using 'Positioned Color Dithering' 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) Agreed on the list. Should be written in SGML, so we can output all sorts of formats. Which means we need layouts, etc. Any takers? 4. Enlist some 'official' distribution maintainers (at the minimum RedHat, Suse, Mandrake, 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. Carlos clozano@andago.com is running with it.
B. Documentation work Andy, take it away! :) 0. We need to figure first _what_ is out of date.
C. Wine configuration 0. Merge configuration into the registry
- Write control panel applets for editing it
- Have decent defaults so we can start control panel without prior configuration
- Have wizard like app to autoconfigure wine
WineSetupTk proposed by Jeremy White jwhite@codeweavers.com 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 6. Have a wineboot script for RunOnce stuff
D. Stabilize utilities 0. Get rid of the init directive from .spec files Alexandre Julliard julliard@winehq.com volunteered
- Make sure the .spec file format is fairly stable
Any other things that may need changing here? 2. Ensure the various utilities' options are stable Anything here?
E. Important fixes 0. Window management rewrite, so we can install apps in managed mode.
On November 2, 2002 11:23 am, Shachar Shemesh wrote:
What about reboot.so or similar support?
I've added it as item C6.
Andreas said he was deffering sending in an official patch. I was willing to take ownership over that (whether from scratch, or based on work done so far) is Andreas isn't interested any more.
I don't know, that's between you and Andy. But I would like to know if someone takes ownership of that, so I can add their name there. If both of you work on it, I can add you both, not a problem, but I'd appreciate it if you guys let me know.
-
Dimitrie O. Paun -
Shachar Shemesh -
Steven Edwards