I disagree with putting samples in device name folders. I do a lot of work on 18f67j50, so many of my samples will be on that PIC. If you name folders like this, nobody will use my samples. I agree with Seb that samples will get hidden from users.
Our libs are meant to work on many different PICs, the device used should not matter for most samples. If we do go with device named folders, I'll need to generate 300+ samples for each sample type, like the blink samples. That's would be a lot of work. I think putting them in sample named directories will be the best for users. So the dir name would be the same as the sample without the device id. In addition, if you want to you can supply a .txt file in the package that orders samples by device id and another by sample name Matt. On Apr 23, 2:14 pm, Sunish Issac <[email protected]> wrote: > Separating the samples based on PIC type would be the simplest for the > user, I divided the samples to 10f,12f,16f,18f in the jaledit pack. It > broke the docs html but still better than have all samples in one folder. > > Also for the blink samples, better to use internal oscillator configuration > whenever possible. > > Sunish -- 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.
