[ros-kernel] WinCE application support for WINE and ReactOS

Thu Mar 4 18:31:13 CET 2004

Hey Guys:

Now that you are talking about WindowsCE why don't you take a look at this. I landed here http://www.microwindows.org/ and remembered you where talking about this. I have not much time and I have to go home so I have not explored this too much but seems they try to implement windows CE api and some sort of microX server.

"Microwindows is an Open Source project aimed at bringing the features of modern graphical windowing environments to smaller devices and platforms.  Microwindows allows applications to be built and tested on the Linux desktop, as well as cross-compiled for the target device.  Microwindows' genesis was with the NanoGUI project, and has now been combined into a single distribution.  The Win32/WinCE API implementation is known as Microwindows, and the Xlib-like API implementation is known as Nano-X. Please read the FAQ for more information.  An extensive Architecture document is also available. Check out the Articles that have been written about Microwindows in the left sidebar.  To get involved, please join the NanoGUI mailing list. <http://www.linuxhacker.org/nanogui/>   There is a full mirror of the mailing list accessible here <http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/0> ."

...

"1.4.1    Microwindows API

The Microwindows API tries to be compliant with the Microsoft Win32 and WinCE GDI standard.  Currently, there is support for most of the graphics drawing and clipping routines, as well as automatic window title bar drawing and dragging windows for movement. The Microwindows API is message-based, and allows programs to be written without regard to the eventual window management policies implemented by the system.  The Microwindows API is not currently client/server, and will be discussed in more detail in section 4.

1.4.2    Nano-X API

The Nano-X API is modeled after the mini-x server written initially by David Bell, which was a reimplementation of X on the MINIX operating system.  It loosely follows the X Window System Xlib API, but the names all being with GrXXX() rather than X...().  Currently, the Nano-X API is client/server, but does not have any provisions for automatic window dressings, title bars, or user window moves.  There are several groups writing widget sets currently, which will provide such things.  Unfortunately, the user programs must also then write only to a specific widget set API, rather than using the Nano-X API directly, which means that only the functionality provided by the widget set will be upwardly available to the applications programmer.  (Although this could be considerable, in the case that, say Gdk was ported.)"

Now I have not idea how is licensed that code.

and I have no idea on how much mature is it.

Just take a look, it could be usefull.

Best Regards
Waldo Alvarez

________________________________

From: ros-kernel-bounces at reactos.com on behalf of Robert Köpferl
Sent: Thu 3/4/2004 6:29 PM
To: ReactOS Kernel List
Subject: Re: [ros-kernel] WinCE application support for WINE and ReactOS

WinCE is a "cleaned up" win32 api. For example just the ....Ex -Calls
remain.
But for the compiler it sounds rather nice. Why not take just the naked
compiler to compile SEH enabled and more optimized binarys.

Steven Edwards schrieb:

> Hello All,
> This is all very experimental. I am working on in the ReactOS tree and
> it might not even work for larger apps but I am happy with the results
> so far.
>
> I was thinking the other day that ReactOS and WINE/Linux might get a
> big boost if we can push support in the embedded enviroment so I
> started taking a look at WinCE and Microsoft Embedded Visual C++ 4.0
> .BTW: Its a free download now.
> http://www.microsoft.com/downloads/details.aspx?FamilyID=1dacdb3d-50d1-41b2-a107-fa75ae960856&DisplayLang=en
>
> I started looking at WinCE and thought it would be nice if we could be
> source compatible with WinCE apps and binary compatbile on x86. Well it
> seems that WinCE apps dont differ much from standard Win32 apps execpt
> the subsystem ID is differnt. If you attempt to run a WinCE application
> on Windows it will say that its not able to run. Ok no problem, we just
> run "editbin /subsystem:windows blah.exe" and check it out. Now the app
> is looking for coredll.dll. No problem there I have created a stub
> coredll.dll that just forwards all calls to the proper Win32 dlls such
> as user32, kernel32, etc.....
>
> .....and check it out. My little messagebox test works on Windows. Ok
> soon then I go and run the same test on ReactOS but this time I run a
> copy of messagebox without changing the subsystem ID...Hey what do you
> know. It works =). I talked with Alexandre about it a bit and he said
> that WINE like ReactOS also shouldnt care about the subsystem ID so if
> someone is interested in testing just drop the messagebox programs and
> coredll.dll in to a directory and give it a shot.
>
> I am having trouble getting more complex apps (hello world) to work atm
> so I think i am just going to take a break and clear my head for a few
> days. Some of the WinCE API and Win32 is not 100% compatible so we cant
> just forward all parts to the Win32 implementation but I think we can
> do it for most of it. If anyone is interested in helping out the source
> is in the ROS CVS tree and attached to this email......
>
> binary.zip
> messagebox.exe - wince messagebox program
> msgbox.exe - wince messagebox program with subsystem id changed to
> Windows.
> wincehel.exe - Hello World WinCE app
> wincehelw.exe - Hello World WinCE app with subsystem id changed to
> Windows.
> coredll.dll - WinCE Win32 API
> commctl.dll - WInCE common controls API.
>
> source.zip
> coredll - dummy forwarder dll
> commctl - dummy stub dll for common controls
>
> Thanks
> Steven
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Search - Find what you're looking for faster
> http://search.yahoo.com
> _______________________________________________
> Ros-kernel mailing list
> Ros-kernel at reactos.com
> http://reactos.com/mailman/listinfo/ros-kernel
_______________________________________________
Ros-kernel mailing list
Ros-kernel at reactos.com
http://reactos.com/mailman/listinfo/ros-kernel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 9024 bytes
Desc: not available
Url : http://reactos.com:8080/pipermail/ros-kernel/attachments/20040304/e9c5c52b/attachment-0001.bin