Hi Andreas, Thanks for your feedback. On the jallist Google group the following was suggested, a variant on proposal 1) that it to put blink as well as sample in the rood directory, as follows: jallib/blink jallib/compiler jallib/doc jallib/lib jallib/sample
Would that also work for you? Kind regards, Rob ________________________________ Van: 'Andreas Schlögl' via jallib <[email protected]> Verzonden: zaterdag 18 oktober 2025 18:12 Aan: [email protected] <[email protected]> Onderwerp: Re: [jallib] Proposal to restructure sample files. I vote for Proposal 2, as this brings an easy to understand structure! Thanks Rob, -- Ing. Andreas Schlögl Softwarelösungen & Consulting Metternichstrasse 9 A-2151 Asparn an der Zaya Handy: +4369910402441 + Signal for secure communication Am 18.10.25 um 10:47 schrieb [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/e985f243-8f06-4532-a148-7ef8bff01d4cn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/e985f243-8f06-4532-a148-7ef8bff01d4cn%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/7ccc12e1-993b-412f-8853-380ca3e20366%40schloegl-software.at<https://groups.google.com/d/msgid/jallib/7ccc12e1-993b-412f-8853-380ca3e20366%40schloegl-software.at?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/AM7PR02MB6098862B7A6F1A98745D7AA5E6F7A%40AM7PR02MB6098.eurprd02.prod.outlook.com.
