Hi all, After some discussion I will go for the proposal of Matt, move the blink samples is a separate folder of the sample directory, so: sample/blink sample (for all other samples)
I did some work on this but before it can be released there is still a Python torelease.py script to be changed since it would not work right with this change. Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens [email protected] <[email protected]> Verzonden: zondag 26 oktober 2025 18:31 Aan: jallib <[email protected]> Onderwerp: Re: [jallib] Re: Proposal to restructure sample files. Hi all, Why not just reconsider the initial goal, which was to simplify things ? Under Linux as under Windows as well, you just type, for example, " dcf77" in the search field of the file explorer, and you get all relevant files, since that "search" works in fact as a filter. That way, you keep the two folders mentioned before: samples blink And the packaging process remains much much simplier. Do not forget that in your proposal, you (Rob) have to modify the packaging script each time you add a sample for a new device. That is not simplification, IMHO.... Just my 2c David Obtenir BlueMail pour mobile<https://bluemail.me/download/> Le 26 octobre 2025, à 18:09, Matthew Schinkel <[email protected]<mailto:[email protected]>> a écrit: Hi Rob, Please take this list of samples, and suggest folders they would be kept in. I see a lot are glcd samples, so would they go in a glcd folder? Then again, there are many decoders, so would those ones use a decoder folder? Do gps samples go in the glcd folder or a gps folder? Does gps_neo_6m_ssd1306_clock go into a gps folder, glcd folder or clock folder? 16f1825_dcf77_decoder_serial.jal 16f1825_dcf77_decoder_ssd1306.jal 16f1825_glcd_ssd1306_font.jal 16f1825_gps_neo_6m_serial.jal 16f1825_gps_neo_6m_ssd1306_clock.jal 16f1825_nec_rc_decoder_ssd1306.jal 16f18857_nec_rc_decoder_serial.jal 16f1825_philips_rc_decoder_ssd1306.jal 16f18857_glcd_ssd1306_font_graphics.jal As a user looking for 16f1825_gps_neo_6m_ssd1306_clock.jal, I'd have to look in 3 folders (gps, glcd, clock) to find the sample. The only folder name that makes sense for that one is gps_neo_6m_ssd1306_clock Matt. On Wednesday, October 22, 2025 at 2:11:46 PM UTC-4 [email protected] wrote: Hi Matt I read your message. If I understand well you mean: sample/large array and sample dcf 77 I think thats okay. Peter Groeten Op 21 okt. 2025 om 23:19 heeft Matthew Schinkel <[email protected]> het volgende geschreven: Hi, yes for now just have directories sample/blink - only blink samples sample - all other samples I get what your saying with this now thanks, but I won't know where i would find a sample. these directory names don't tell me much, and some samples may fit into both, like a sample that uses sd_card and crc. CRC is jal, sd_card is device, so which folder would it go into? Also device is misleading as it makes me think of the device includes. sample/jal sample/device I was suggesting: blink - all blink samples large_array - 12f617_large_array.jal - 16f1825_large_array.jal - 18f14k50_large_array.jal dcf77_decoder_ssd1306 - 16f1825_dcf77_decoder_ssd1306.jal Seems the issue with my solution is that there is only one file in directory dcf77_decoder_ssd1306. But I don't see that it is a problem with the directory structure I suggested, the real problem with the fact that there is only one dcf77_decoder_ssd1306 sample, where there should be at least 2 or more. Seems to me we need to test our samples on more devices. Does anyone disagree here? Thanks, Matt. On Tuesday, October 21, 2025 at 1:01:29 PM UTC-4 [email protected] wrote: Hi Matt, So, you mean? sample/blink sample Then maybe you could also choose for: sample/bllink - around 1800 samples sample/jal - around 42 samples sample/device - around 1000 sampes (I mean not PIC devices but internal PIC like spi and adc and external devices like glcd_ssd1306 and hcsr04, etc.) I do not understand what you mean with the statement you mention. Do you mean if you organize by (PIC) device? There are then indeed a lot of PIC devices with only a blink sample. If you organize by type of device (e.g. wireless, jal, network, adc, spi, etc.) then there would be more than one sample but in some cases it can still be one sample. When you look on GitHub on type of device, you get ground 60 types where there might be overlap with some of them. Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens Matt Schinkel <[email protected]> Verzonden: dinsdag 21 oktober 2025 06:10 Aan: [email protected] <[email protected]> Onderwerp: Re: [jallib] Re: Proposal to restructure sample files. Hi, I would just move the blink folder into the sample folder. Someone said if we organize by sample type, there would be many folders with one sample in it. That statement is true, however there should not be any sample types on only one pic. To me that is a sample that needs to be tested on more devices. Sent from my Android device. ________________________________ From: [email protected] <[email protected]> on behalf of Rob CJ <[email protected]> Sent: Monday, October 20, 2025 12:46:23 PM To: [email protected] <[email protected]> Subject: Re: [jallib] Re: Proposal to restructure sample files. 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. [image.png] 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]> 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]: 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]. 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]. 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<https://groups.google.com/d/msgid/jallib/AM7PR02MB6098FA54A3E76F50260B176AE6F5A%40AM7PR02MB6098.eurprd02.prod.outlook.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to a topic in the Google Groups "jallib" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jallib/dGp_CAqTOlk/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jallib/MW4PR10MB5882BE5DBB9B782519356B0FDEF2A%40MW4PR10MB5882.namprd10.prod.outlook.com<https://groups.google.com/d/msgid/jallib/MW4PR10MB5882BE5DBB9B782519356B0FDEF2A%40MW4PR10MB5882.namprd10.prod.outlook.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/b68f9af0-64a2-4326-a4d1-296b4a8a0855n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/b68f9af0-64a2-4326-a4d1-296b4a8a0855n%40googlegroups.com?utm_medium=email&utm_source=footer>. <image.png> -- 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/9a2ef56d-72e1-46f5-8e13-881c829cd59an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/9a2ef56d-72e1-46f5-8e13-881c829cd59an%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/2f4eeba010f17c.f2891901787f08%40gmail.com<https://groups.google.com/d/msgid/jallib/2f4eeba010f17c.f2891901787f08%40gmail.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/VI1PR02MB6095579D7A6F49C816EF396BE6FCA%40VI1PR02MB6095.eurprd02.prod.outlook.com.
