Seb might answer, but my opinion: 2008/9/2, Ritchie <[EMAIL PROTECTED]>: > Are you (still) interested in LCD ST7036 and HD44780 libraries ? > they are both exactly the same, accept off course initialisation and > communication (ST7036 can also communicate serial). We have an lcd.jal, which supports HD44780 (in 4bit mode). It's good to add support for an other display. I wonder how much it takes to add ST7036 support (in 4bit mode) to this lib. And if there is (also) a separate lib for this controller, please keep it similar in the way the connection to the display is defined and the way it is called (API).
> I know there is already a HD44780 and a DS1302 but the one I > downloaded were not working (maybe now they are?). lcd.jal works on a HD44780. A working lib for the RTC is nice too. But... these two libs bring a more fundamental issue to the surface: we're defining validation criteria for validation of libraries, which state it has to be tested on multiple PICs. If we apply these criteria to all external device libs, this would mean that we can not validate libraries for less-frequent devices when the developer himself (M/F) does not do this for any reason (like when he only has one type of PIC available). If this is the case, we need to have an alternative way to supply these libs to potential users. Maybe in an 'untested' directory? 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 -~----------~----~----~----~------~----~------~--~---
