MFC is a big issue for any claim that we can compile out of the box.
Another issue is wrc. In our experiences, WRC was pretty much unusable for
resources of any size. For the small tools, we used wrc, but we had to use
msvc++ for our application resource.
I think before we make any move towards 1.0 we should reexamine the stub
count. There was some dicsussion a few days ago comparing the number of
stubs to actual implementations. That's important.
Also, we need more font support. Is there any kind of font rasterizer in
wine? We implemented some code to read font data and curve data out of
truetype fonts that we're willing to contribute, but since there's no
rasterizer, it would be mostly useless.
>Jeremy White wrote:
>>
>> Given the amount of progress Wine has made over the past year,
>> it seems (to me anyway) that the time may be appropriate to
>> try for Wine version 1.0.
>>
>> 2. What needs to be done before we can release Wine 1.0?
>
>What about support for MFC ? Most applications are MFC based. And g++
>chokes while compiling MFC.
___________________________________________________________________________
Michael Cardenas Deneba Software
Lead Linux Programmer http://www.deneba.com
___________________________________________________________________________
"Either open source is a net win for both producers and consumers on pure
self-interest grounds or it is not. If it is, you cannot lose; if it is
not, you cannot (and *should* not) win." -Eric S. Raymond
"Imagine someone saying, 'If an uncensored press is not better for
publishers as well as readers, it cannot (and should not) prevail.' This
would show that person does not understand freedom of the press as an issue
of liberty. For people who value civil liberties, such views are ludicrous.
-Richard Stallman
http://www.gnu.org/philosophy/philosophy.html#AboutFreeSoftware
___________________________________________________________________________
