Hi 2008/10/2, Sebastien LELONG <[EMAIL PROTECTED]>: > > Hi all, >
> About 3.: this is not the case. Should we still try to standardize our libs > with one interface ? Is it too much work ? Is it too early for now to > consider this ? Will we never have more than one lcd attached to a PIC ? Maybe not the same, but I think it is a good idea to keep interfaces within jallib as similar as possible. Some libraries have an 'initialize' function which the user should call, other call this function on startup or have init code outside a procedure/function. Retreiving chars from a device can be done by using a function or a procedure. Success can be returned as 0 or non-zero. So: keep it the same unless you have a very good reason not to. And if this is the case, keep it similar, so users can easly adapt their code and maybe even predict the interface. And always include a pseudo-var interface to an output device library! > > About 4.: please advise ! Richard's lib has nice high-level procedures > (lcd_time, lcd_date,lcd_progress, ...). Maybe we could extract them to > another lcd lib, so people can decide to include it or not. It should be extracted! Take a look at print.jal or format.jal how this can be done. And since I can't imagine what's lcd-specific from lcd_time, maybe it should be part of a generic library, so it can be used on other output devices too. 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 -~----------~----~----~----~------~----~------~--~---
