Using folders like 10F,12F,16F,18F will further split the samples, resulting in more directories. For example, the print lib should work on all of these and would be placed in a directory of it's own in each of 10F,12F,16F,18F. Samples should work on all PICs, so I don't see a reason to split based on PIC type.
Lets split based on application the way Rob suggested. Each sample will go into one folder. Generally, the last included library is the lib the user is trying to make a sample for. Many of the samples can be sorted based on this. Of course we can make up categories as needed. We can not have samples duplicated into more then one directory. So I suggest having a related_samples.txt file in each folder that tells the user where other related samples are. This readme.txt file can be checked by a script to ensure samples listed in it actually exist. I'll try to implement this into buildbot. For example, this sample includes fat32 last, so it goes in the filesystem directory: /sample/filesystem/18f67j50_fat32_usb_msd_pata_hard_disk.jal The same sample is related to USB and storage devices, so text files will contain the location of this sample: /sample/usb/related_samples.txt /sample/storage/related_samples.txt Do you think this would help us find our samples? If anyone has the time, we can have a search.py and search.exe to assist with finding samples. Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
