Hi guys, I was thinking about adding issues (as todo, not bug) about some external parts & libs I plan to add to jallib. This may be a good idea if everyone here do the same, we'd be able to know who owns what, avoid duplicates, and ultimately tell what will be next integrated in jallib.
I think having a lot of external libs may give an interesting "marketing" view for jallib :), specially when rare. Google for "ST7036 PIC", jallib is here (mail archive). Google for "MIC800 library servo", I'm here :) hopefully jallib will be here in a few weeks or months. I guess this can make people switch to jalv2/jallib (I did it that way). Or at least, people may know we exist, and communicate... More, jallist guys can give feedback by giving their opinion on the next external part to be integrated. GC issue tracker has a nice feature (google account owner onle): "star the issue". By checking, ie. starring the issue, the number of star increase, thus give hints about a kind-of prioriry. http://code.google.com/p/jallib/issues/list?can=2&q=&sort=&colspec=ID+Type+Status+Priority+Component+Milestone+Owner+Summary+Stars So, my next about external part issues ("Component-External") will be about: * a GP2D02 IR ranger * a MIC800 chip, a servo controller chip (quite a crap, but anyway) * a Maxbotic Ultrasonic ranger (a nice beast, can be accessed through serial, pwm and timer IIRC) I'll fill issues for these. Cheers, Seb -- 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 -~----------~----~----~----~------~----~------~--~---
