[En-Nut-Discussion] Nutconf subtree construction

[Ulrich Prinz]

Hi Hans!

The thing is, that I mostly have to design the things now, as the 
prototypes have to be ready fpr HMI in Hannover mid of April. As you 
didn't mention anything about the license terms I think it's better to 
continue my work. Your mail earlyer sounded like there's something 
mostly finished.

Then keep the work going on by times and I hope we'll find a way to 
match things up and put something into nutos under BSD license.

Best regards
Ulrich


-----------------------------------------
Ulrich Prinz, Schmittbachweg 9, 35781 Weilburg


-----Original Message-----
From: Hans Bacher <hans at wack-engineering.de>
To: 'Ethernut User Chat (English)' <en-nut-discussion at egnite.de>
Sent: Tue, 31 Mar 2009 1:45 pm
Subject: Re: [En-Nut-Discussion] Nutconf subtree construction










Hi,

I chose the Microchip Graphics Library as GUI because its features are
comparable to GUIs like Segger's emWin or Micrium's µC/GUI. In contrast 
to
these quite costly solutions, Microchips Graphics library is free and 
comes
along very well documented and with several additional application 
notes. It
is based on a three-layer architecture: Device Driver Layer, Primitives
Layer (lines, text, circles, pics, etc.) and an Graphics Object Layer
(widgets such as buttons, grids, textboxes, charts, etc. but also user
interaction abilities as keyboard and touch screen functionality). The
Device Driver Layer clearly defines a fixed
, well documented interface 
to
higher layers to simplify developing own display drivers.

So far about the lib of Microchip. At the moment this is a private 
project
at a very early stadium. I'm adapting and integrating these layers into
Nut/OS build chain. Until now no further Nut/OS concepts have been 
mapped to
the GUI, such as the Nut/OS device structure.

First at all I'd like to finish the implementation of one single driver 
for
a Densitron 262k color, 128x128 pixels OLED to work with the GUI and to
integrate the whole thing into nutconf. If this step has become stable 
it
might be a good reference for creating further display drivers and a 
good
starting point to develop things further.

Current state is, that all GUI source (originally designed for 
Microchips
native PIC-Compiler) files have been adapted to GCC and integrated into
Nut/OS' source tree. Configuring the GUI and building from out of 
NutConf
works fine, and the device driver for the OLED is almost finished (ca. 
90%).
Unfortunately, the next few weeks are full of Nut/OS-unrelated work...
that's why it will take until end of April until I can finish this first
goal as described above.

Best regards,

Hans

-----Ursprüngliche Nachricht-----
Von: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] Im Auftrag von Thiago A. 
Corrêa
Gesendet: Dienstag, 31. März 2009 09:49
An: Ethernut User Chat (English)
Betreff:
 Re: [En-Nut-Discussion] Nutconf subtree construction

Hi Ulrich,

On Tue, Mar 31, 2009 at 4:17 AM, Ulrich Prinz <uprinz2 at netscape.net> 
wrote:
> Hi!
>
> When will the code be inside repository?

It's not clear if Hans will contribute his changes, he haven't 
mentioned.
Of couse he doesn't have to, but it sure would be nice :)

He does mention that it's ported from Microchip library, so I'm not
sure what the upstream license terms are.

> I am integrating drivers for DD32645C-1A OLED (Mono-Blue) and
> DD160128C-1A (250k RGB) actually. So I can concentrate to the hardware
> layer before doing the API twice. I didn't know that several people 
are
> designing same things, that I am doing over here the same time.

Same here. Anyone else interested in working with the GUI libraries?
We should outline the system archtecture, and when pieces are working,
submit it to the repository.
Release early, release often is a good way to avoid duplicate effort.

> Did someone program a font converter too, before I start doing
> something like that? The usefull converters I know are shareware, had 
a
> timelock or are scrambling parts of the characters until one buys a
> license.
>
> Is there generally a page where one can see who is doing what in the
> code?

I guess the best place would be announcing it here and/or the Wiki, at
the Roadmap.

Kind Regards,
   Thiago A. Correa
_____________________
__________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion