Eric POUECH wrote:
Here is the status of what I have so far on the ToDo's. I am not sure what section to put alot of this in so I just made Tools , Instructions & Aspect or Component for now. As much feedback as possiable is welcomed .
here's some feedback:
Sound drivers
- Alsa driver (on final 0.9 interface)
Video:
- implement native codecs (RLE...)
DDE:
- enhance memory management issues (interprocess sending)
wineconsole:
- add a (n)curse backend so that we can run CUI programs without using USER32 (and X11 behind)
file management:
- implement NT file namespace
- UNC support
- allow flexibility in FS "mounting" (for example, SMB shares)
(NB: I think we should make that clearer and not keep it shadowed in the Aspect/component list)
(native) programs:
- winhelp: fix invocation thru WinHelp
- winedbg: make winedbg use dbghelp DLL (and implement it of course)
--8<--------- remove the Multimedia wave audio section SEH support has been lately enhanced, is there still known issues ? IMO, Dwarf2 support should not be added to winedbg. use of gdb proxy should be required instead. (even if it means adding PDB support to gdb, but that'd be a better investment)
we should make clear what the low priority items are (VxD support with dynamic loading for example)
A+
I dont know if any of these are in any of the TODOs but here goes. all of these would go under porting issues for Mingw/Cygwin/MS_VC
- Better seperation of win16/32 code. - remove/rewite win16/9x api dependancy on newer code - remove/rewrite wineisms from code - documentation fixes
I think all of this is high priortity but I am biased =)
Thanks Steven
Am Die, 2002-09-24 um 22.55 schrieb Steven Edwards:
- Better seperation of win16/32 code.
- remove/rewite win16/9x api dependancy on newer code
- remove/rewrite wineisms from code
- documentation fixes
I may be missing something, but there's already enough on that list to keep all of us busy until the release of Windows ZXF 2016.
Are there plans to go through a public voting to determine which of these we need to fix until 0.9/1.0 ?
Don't get me wrong, no specific recjection against Steven's points, just a general question.
Martin
I may be missing something, but there's already enough on that list to keep all of us busy until the release of Windows ZXF 2016.
Are there plans to go through a public voting to determine which of these we need to fix until 0.9/1.0 ?
Don't get me wrong, no specific recjection against Steven's points, just a general question.
Martin
While the stuff I have recommend are not show stoppers for 0.9/1.0 I would like to see a simi-working wine on Cygwin/Windows for 1.x and none of the changes that I am recommending should break binary compatiblity with wine 1.0 so I think it should be on the list. I will work on the documentation part soon and others have already started working on fixing the win16/32 overlap in certain places.
Thanks Steven