Hello all, There is Dutch saying 'Er is nog nooit een kok gevonden die koken kan naar alle monden'. Which translates (literally) to 'There has never been a cook that can cook for all mouths'.
So it is difficult to find a solution since everybody has its preferences. I did a small test yesterday on my computer to see if I could easly create the solution as proposed by David. It requires two things: 1. All blink sample should be in a blink directory on GitHub. Although there is a way to solve this in a script I thought it was already organized like that on GitHub which was not the case (and it gives less work if it was). So I already implemented this structure on GitHub so that I have a quick overview that when I create new blink samples that I see if the number of samples is the same or more (yesterday I discoverd that I am missing some blink samples using the latest script so still work to do there) 2. It requires a small modification of the Makefile that generates the Jallib package. I managed to create it, see below. This does not mean that there will never be any change if a proposal is made that everybody likes or we find another way to get a good overview of everything that JAL has to offer. The blink folder contains about 1800 samples and sample folder contains about 1000 samples. [cid:96f50068-3bba-426d-83de-3419a1323d46] Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens vsurducan <[email protected]> Verzonden: maandag 20 oktober 2025 06:07 Aan: [email protected] <[email protected]> Onderwerp: Re: [jallib] Re: Proposal to restructure sample files. Yep, true, but newbies should anyway browse everything to understans things, so actually the folder structure does not count too much. For the guys who are modifying things should also be easy... On Sun, Oct 19, 2025, 23:43 Zet Weeh <[email protected]<mailto:[email protected]>> wrote: Hi I follow the discussions, but usually don't respond. I find version B the most logical. Newbies don't know what is meant by 'blink a led'. Version B is much clearer because you immediately see that it is a type of sample. For me, the other options miss their purpose: it becomes more complicated instead of clearer. Kind regards ZetPee Op zaterdag 18 oktober 2025 om 10:47:06 UTC+2 schreef [email protected]<mailto:[email protected]>: Hello, This is posted both on the Jallib as well as the Jallist Google Group. Matt and I had a short discussion about the directory structure of Jallib, related to sample files. At this moment all sample files are in the 'sample' directory. At this moment these are almost 3000 files, most of them blink samples. In order to find samples more easily we could organize this differently. Below some proposals. Proposal 0: ---------- Keep it as it is. Proposal 1: ---------- sample/blink <-- For all blink samples sample/other <-- For all other samples Propsal 2: ---------- sample/blink <-- For all blink samples sample/jal <-- For all jal samples (e.g. print, large_array, etc.) sample/device <-- For all samples of device files Propsal 3: ---------- sample/blink <-- For all blink samples sample/jal <-- For all jal samples (e.g. print, large_array, etc.) sample/ssd1306 <-- For all samples of the ssd_1306 device, one directory per device sample/ws2812b <-- For all samples of the ws2812b device, one directory per device .... <-- You do get a lot of directories, 1 for each device. Proposal 4: ----------- sample/blink <-- For all blink samples sample/16f1823 <-- For all 16f1823 samples sample/18f46q83 <-- For all 18f46q83samples .... <-- You do get a lot of directories, 1 for each PIC type for which there are samples My preference is proposal 1 with the second proposal 2 where proposal 1 is the easiest to implement since blink samples are already in a separate directory on GitHub. Can you let me know your thoughts about it? Thanks. Kind regards, Rob -- 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]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/jallib/da9325e6-6e6f-462f-9c20-60e1ba4547a8n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/da9325e6-6e6f-462f-9c20-60e1ba4547a8n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/jallib/CAM%2Bj4qsS%3DresboRP2WVBH3OVd5FVcth%2BuWkD-TyLu1NXmOqBXQ%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CAM%2Bj4qsS%3DresboRP2WVBH3OVd5FVcth%2BuWkD-TyLu1NXmOqBXQ%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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 view this discussion visit https://groups.google.com/d/msgid/jallib/AM7PR02MB6098FA54A3E76F50260B176AE6F5A%40AM7PR02MB6098.eurprd02.prod.outlook.com.
