1. I totally agree with you. I try to do that in the Nokia & Samsung
file
2. I think one file will be great if it can be done. It may become too
clustered and difficult
Even though it only should contain non-device code, there are
still big differences between
the displays.
For now I want keep the character and graphics code separated.
There will not
be any dependencies, so its easy to put in one file afterwards.
3. The fonts are superb Mat. Exactly what I was looking for
What naming prefixes do you propose for the generic stuff. I know you
like to see something
with 'write' instead of e.g. 'plot' but it would be best to have a
clear separation between character
or byte writing and drawing.
I'm not at home yet with the jallib housekeeping and exactly what
rights I have.
e.g where to find your code and is it expected that I upload my
'fruits' to jallib env.
and not to my own?.
Paul
On 16 Dec., 02:47, mattschinkel <[email protected]> wrote:
> I'm afraid these GLCD libraries may become a mess if we don't find a
> common way to do things. I seems you wish to help with that.
>
> Personally, this is what I would like to see:
> 1. one library file per GLCD type, holding only GLCD specific stuff.
> 2. one generic file "glcd_common". there is an updated glcd_common on
> SVN
> 3. a generic way of building fonts. last week, just before you posted,
> I created a font library, see it on SVN. glcd_font.jal and
> glcd_font_8x12.jal I have lots of notes in them.
>
> Let me know what you think, and if we can improve on this or change
> it.
>
> I'll have a look at your new code. Just so you know, my LCD writes
> pixels in blocks. I specify start x/y and end x/y then write data
> only. I don't specify x/y address on every pixel write.
>
> Matt.
>
> On Dec 15, 5:20 pm, pdhaene <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hey
>
> > I have started to work on the glcd libraries and as a result will
> > glcd_graphics not be changed/updated anymore
> > The files I'm working on ( names ending with X01 ) can be accessed
> > from today.
>
> > Since I update the file daily there will be a lot of unfinished stuff
> > so please don't look to closely at the details
>
> > I am however interested in feedback, advice, critique, ideas and
> > anything else to make it work
>
> > The file names and names for procedures & functions are, at the
> > moment, not so important and easily changed later, but any advice on
> > how to name them consistent with jallib practice are more than
> > welcome.
>
> > I have the following files: ( all filenames ending on X01 )
>
> > 1. library with device specific code e.g. glcd_Nokia_3310_X01.jal
>
> > 2. library for generic character/byte writing/printing:
> > glcd_common_character_X01.jal
>
> > 3. library for generic graphics (pixel) drawing/printing:
> > glcd_common_graphics_X01.jal
>
> > Thanks
>
> > Paul
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
