[ECOS] RE: New features required on Cortex-M platform

[Andrew Hannam]

As one of the primary developers of uGFX I have been watching the ecos
mail-lists for a long time but have never implemented an ecos system yet
(just due to being caught up on other projects such as uGFX).

I would be happy to work with you to create a port of uGFX for ecos.

As per one of your follow-up Emails relating to uGFX versus Qt:

Some of the advantages of uGFX versus Qt:
 - uGFX is designed for small memory footprint systems (ie. embedded
systems), Qt is not and therefore has a very large footprint.
- uGFX works equally well on systems without a framebuffer. Qt requires a
framebuffer (and the related RAM requirements)
- uGFX is a full multi-threaded GUI, you can draw from any thread regardless
on which thread the object was created. Qt has only limited support for
multi-threaded applications.
- uGFX has support for many LCD controllers and supports custom wiring
connections to your micro. Qt assumes a full graphics/windows layer is
already available (usually X).
- uGFX includes other sub-systems like audio, toggle switch input devices,
analogue dials, ROM based file system etc. Qt does not.

Some disadvantages of uGFX versus Qt:
- uGFX has a different API to Qt. More programmers are familiar with Qt.
- uGFX has only restricted support for overlapping windows (container
windows are however supported).

uGFX is in short designed for embedded systems while Qt has a desktop based
design.

uGFX aims to provide a cross-platform way of writing embedded GUI
applications. For example, most of the uGFX demos can be run on any uGFX
supported operating system without changing a single line of code. This
means you can prototype and debug your application on Windows or Linux and
then very simply move it to your embedded board.

Regards,
Andrew (aka inmarket)

-----Original Message-----
From: Jerzy Dyrda [mailto:jerzdy@gmail.com] 
Sent: Saturday, 14 June 2014 1:15 AM
To: eCos Discussion
Subject: Fwd: New features required on Cortex-M platform

Hello all,

During developing some application on Cortex-M controller I realized that is
missing some vital components in current version of eCos system (from my
point of view)  i.e :

1) HTTP server - AHTTPD doesn't support lwIP stack what causes that it's
useless.
I'm planing to modify it thus any kind of advises are welcome.

2) Small embedded GUI working directly on display. From my side I propose
uGFX -> http://ugfx.org/ License seems to be compatible and due its nature
porting on new platform shouldn't be complicated even for me :) I'm also
planning to add support and again any kind of comments advices or warnings
are expecting.

3) SD bus support. I know that I can use SD card in SPI mode but on some
board like STM32F4DISCOVERY SD card i only available on SD bus.
It's high time to add this miss part of system.

Best regards,
jerzy


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