Re: [ECOS] Re: MicroWindows, network stack, framebuffer API

[Alexander Neundorf <a dot neundorf-work at gmx dot net>]

On Wednesday 05 November 2008, Gábor Török wrote:
> Hi!
>
> On Tue, Nov 4, 2008 at 2:18 PM, Alexander Neundorf <neundorf@kde.org> wrote:
> > Two years ago or so I was working on this already, you can find the
> > results here:
> > http://www.ecosforge.net/pmwiki/index.php/Projects/EcosMicrowindows
>
> Thanks for the information, I will have a look at it soon. Do you work
> on it now, or have you finished working on it?
> I wiil register on eCosForge and I can help developing it.

That would be nice.

> > I didn't manage to rip the network requirements out of the X API yet, so
> > this still needs to be done.
> > A socket is used for communication with the X server thread, it should be
> > possible to replace this with eCos thread synchronization primitives.
>
> I saw some code fragments in a NanoX source, that linked in the server
> functions directly. I don't remember, it may have been the MW API not
> NanoX, but I will have a look at it.
>
> > Most of my changes are also in the main Microwindows cvs.
>
> What are the differences between main eCos CVS and the eCosForge version of
> MW?

Compared to eCos cvs the version on eCosForge is:
-much newer, i.e. I synced it with Microwindows cvs back then
-modular, i.e.
-it can use an external libjpeg (also on ecosforge)
-an external libpng (also on ecosforge)
-you can build just the graphic primitves library
-you can add input support for that
-you can choose which fonts you want to have
-you can build the mwin API, with different options for threading (which 
doesn't require networking)
-it supports the RTEMS key handling interface

What's not done:
-socket stuff ripped out
-updated to work with the new framebuffer driver of eCos
-synced with now current Microwindows

Alex

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss