Hi Sunish, I think the way it's done right now is because we wanted samples to be as simple as possible, but also as clear and accurate as possible. When you want to blink a LED, you don't set all pins as outputs, you selectectively set one as output, the your LED will be tied to. It's sometime very surprising how code from "naive" copy/paste can be found in situation where it shouldn't... (like register settings...)
That said, I understand what you mean. Either we can set them all as outputs, despite what said, either we could provide another type sample, something like blink_all.jal and check_output.jal, which set all possible pins as outputs so user can check what she wants. Guys ? Cheers, Seb Le Monday 29 December 2008 04:36:56 Sunish Issac, vous avez écrit : > Having samples in one directory is more convenient from the user > perspective. Or may be we should have different directories for different > PIC types like mid range. > > Also for the blink led sample, how about having all pins as output, its > easier as you can check the output on any pin, except for the input only > pin. quite convenient when you are checking out stuff on a bread board, > also we can easily check if an output pin is conked. > > > Sunish > > > > On Sat, Dec 27, 2008 at 8:02 PM, Sebastien Lelong < > > [email protected]> wrote: > > Hi Joep, > > > >> > Let's also wait for more feedback from others to see their point of > >> > >> this. > >> I would like a unique name, nice since I use include a lot. And adding > >> the pic name would make most filenames unique. > >> We should choose the test-name carfully and then there is no problem. > > > > OK, I'll modify the jallib.py script to remove the prefix (or optionally > > specify one) > > > >> And off-topic (not related to naming conventions): > >> > >> - I created two blogs and am happy to create an other one. But I can't > >> keep that alive on my own. Do you (all) think the blog is usefull and > >> will you add a blog within the next few days (weeks)? > > > > Yes, I plan to (about internal osc for example, and i2c echo) but I need > > time... > > > >> - Similar question about test files: they are a way to create many > >> examples for many pics. This means we have to create well documented > >> test files (yes, I am aware that they should be well-documented ;) and > >> we need board files for more different pic's. If someone has > >> pic-specific samples, I'm happy to help converting them to test-files. > >> But there must be a board around somewhere to test them with different > >> pic's. Anybody with a testboard with a new pic (that is, not 16f877, > >> 16f88 or 16f648) with serial coms, led or lcd display running? > > > > I also plant to add a 16f88 board (sorry, already exist, but not the same > > pin layout). And then convert some of my samples, such as pwm and adc > > ones. > > > > > > Cheers, > > Seb > > -- > > Sébastien Lelong > > http://www.sirloon.net > > http://sirbot.org > > -- 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 -~----------~----~----~----~------~----~------~--~---
