2009/2/23 Wayne Topa <[email protected]>:
>
> I sure hope you are right!
Trust me (on this one)!

I think you were clear but I was not.
I had (only) a brief look at the command set and noticed that - as one
could expect - there are quite a few functions that are also supported
on an hd44780.
What I intent to achieve is that for a user (an user??) there is as
little as possible difference between the two (and other lcd's).

lcd_hd44780_common current api is:

procedure lcd_writechar(byte in data) is
procedure lcd'put(byte in data) is
procedure lcd_restore_cursor() is
procedure lcd_new_line_cursor_position(byte in line, byte in pos) is
procedure lcd_shift_left(byte in nr) is
procedure lcd_shift_right(byte in nr) is
procedure lcd_cursor_shift_left(byte in nr) is
procedure lcd_cursor_shift_right(byte in nr) is
procedure lcd_clearscreen()  is
procedure lcd_cursor_blink_display(bit in cursor,bit in blink,bit in display) is
procedure lcd_home()  is
procedure lcd_clear_line( byte in line  ) is
procedure lcd_progress(byte in line, byte in amount, byte in pattern) is
procedure lcd_setcursor(byte in row, byte in col)  is
procedure lcd_init() is

When you start on the K107 lib, could you please use the same API
where you can. And obvious, for 'set tab', you need to add a new
procedure. And maybe there are some procedures that are close to the
one's above but not close enough. Please share this with us, so we
have a chance to concider changing the above.

The reason for this is that a clear, consistent, powerfull  and stable
API is just as important for jallib as stable working code.

Joep

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to