Hi to > That's the other way around then Rob suggested. So we have 4 options: > 1- choose the interface-layer (const LCD_CONTROL=4) and then include > the control layer (include hd44780) > 2- choose the control layer and then include the interface layer. > 3- include both > 4- include the combi (inlude hd44780_serial) > > Please vote! >
I vote for 4 because IMHO you only use hd44780 in 4 bit and st7036 in serial ore i2c so you would have only 3 libraries so far. hd44780_4 ( we already have) st7036_serial ( or dogm_serial) and st7036_i2c ( or dogm_i2c) and remove hd44780_8 Why use hd44880 in 8bit or st7036 in 4 bit ore more?, it only cost you IO and you gain nothing. So why create/offer a lib which will not be used. > lcd'put creates a pseudo-var. So the user can do: > lcd = "A" > And this enables to use this lib with print.jal and format.jal can i read some information about this, looks nice. > > I think this are most of the control layer functions - functions that > all (most) LCD's have, but differ in the way they are implemented from > controller to controller. You have to check the datasheet to see if > this list is complete ;) Yes and check if there is a (major) difference between controllers. > The decimal and hex functions are already in print.jal, but without > the leading 0x. Maybe we should add a function to print this 0x (like > print_crlf). why option? 123 could be decimal and in your case hex but 0x123 can never be decimal and is always hex. i think if the value is not decimal it should have its appropriate leading like 0x for hex and 0b for binair. > > > but for lcd_date, lcd_bvalue* and lcd_wvalue*, to put them in > > print.jal without change i don't know, but to change them would be a > > pity. > > Can you explain why we should not put them into print.jal ? And why > would it be a pity to change them? lcd_date should not be a problem the others have options nice for lcd but useless for serial interface. but to remove the option make them less flexible for lcd. i can send you a hd44780 library and test file with all options so you can see what i mean (and maybe you don't like it or have better ideas). > > - If it is worth keeping and can be used on, say, serial ports too, > then we should move it to print.jal > - If it is worth keeping it and it is lcd-specific, we should put it > in lcd_common. > - If it is not worth keeping, we should not put it in a lib ;) i agree > > > please correct me if i am wrong, > > You're not! > We need to discuss these issue's to get it right. > again i agree Richard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
