OK, sure. What I mean is a servo controller library can have two parts: - one part is responsible for sending and maintaining PWM signals - another part is responsible for providing an interface (serial, i2c,...).
The last part implements a REPL and interacts with the first part (it calls procedures). The second part is what I call the firmware, and storing/restoring servo position, defining max/min values for each servo, or for all, can (should ?) be done at this level. If user doesn't need any repl or firmware features, he can just use the first part. We can also provide more than one firmware, particularly when dealing with "servo dialect" eval (SSC32, MIC800, Pololu, ...). Cheers, Seb A user may not need the second part or could just implement his own. 2010/10/15 Joep Suijs <[email protected]> > Hi Seb, > > > This is mostly related to some firmware implementation, not the library > > itself, isn't it ? > Not sure what you mean... > What I mean is: give the user the option to leave enable/disable the > option at compile time so they don't fill up their flash with > functions they don't need. This way they have space for the stuff they > do need. > > 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]<jallib%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org -- 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.
