Will wine get to 1.0 before the win32 APIs are obsolete?

[Ivan Leo Murray-Smith]

Some interesting stuff about the longhorn APIs, will the wine GDI be complete they are also obsolete?
The good news is that if the windows APIs go from 76.000 to 8-10.000 then the longhorn APIs should be implemented in wine much faster.

A: In the technology generations leading up to Longhorn, Microsoft has been moving to a .NET-based managed code environment, and the Longhorn generation will finally mark a clean split with the Win32 APIs of the past. That is, Win32 will be in maintenance mode, and all new development will occur with managed .NET APIs. One such API, Avalon, forms the basis for the new Desktop Compositing Engine (DCE) in Longhorn that replaces GDI and GDI+. Another, called Aero, provides APIs for the new user interface. All of the new Longhorn APIs will utilize the XML Application markup language (XAML) to make Longhorn more accessible to developers than ever before. The idea is to significantly reduce the number of APIs and make the APIs more standardized. Today, there are over 76,000 Win32 APIs, and countless wrappers. With Longhorn, Microsoft hopes to reduce the API set to 8,000 to 10,000.

Complete text
http://www.winsupersite.com/faq/longhorn.asp

[Jakob Eriksson]

Ivan Leo Murray-Smith wrote:
> Some interesting stuff about the longhorn APIs, will the wine GDI be complete they are also obsolete?

<little tale>
The other week I received a little program from a friend.  I tried to 
run it in Wine.
It didn't work at all.  It was a dotNET - compiled EXE.
</little tale>

Jakob

[Mike Hearn]

On Mon, 2003-09-22 at 20:05, Jakob Eriksson wrote:
> <little tale>
> The other week I received a little program from a friend.  I tried to 
> run it in Wine.
> It didn't work at all.  It was a dotNET - compiled EXE.
> </little tale>

What error did you get from Wine? We should patch it to inform users
that this is the case, and that they can use Mono to try and run it.

At some point of course we're going to have to go the whole way and
fully integrate Wine and Mono.
> Today, there are over 76,000 Win32 APIs, and countless wrappers. With
> Longhorn, Microsoft hopes to reduce the API set to 8,000 to 10,000.

76,000! Man, that's a lot of code. I wonder how many we actually
implement (correctly)?

[Jakob Eriksson]

Mike Hearn wrote:
> On Mon, 2003-09-22 at 20:05, Jakob Eriksson wrote:
> > <little tale>
> > The other week I received a little program from a friend.  I tried to 
> > run it in Wine.
> > It didn't work at all.  It was a dotNET - compiled EXE.
> > </little tale>
>
> What error did you get from Wine? We should patch it to inform users
> that this is the case, and that they can use Mono to try and run it.

wine aaa.exe
err:module:import_dll Module (file) mscoree.dll (which is needed
by F:\tmp\aaa.exe) not found
err:process:start_process Main exe initialization failed
> At some point of course we're going to have to go the whole way and
> ully integrate Wine and Mono.
> > Today, there are over 76,000 Win32 APIs, and countless wrappers. With
> > Longhorn, Microsoft hopes to reduce the API set to 8,000 to 10,000.
>
> 76,000! Man, that's a lot of code. I wonder how many we actually
> implement (correctly)?

We will know more about that once the regression tests increase
in number and quality.

regards,
Jakob