Hi Rob, I vote for similar #3 but it should be one folder for each sample type. so folders like:
blink serial_print large_array dcf77_decoder_ssd1306 glcd_ssd1306_font gps_neo_6m_ssd1306_clock Remember this has to be generated easily without us manually placing. so I figure if you just take for example 18f4620_fat32_small_sd_card.jal and remove the device 18f4620 and .jal from the end, you have the folder name. You can't put it by library name since the sample I suggested would go into folders fat32, sd_card, print, spi and many others. If we can't agree, just go with #1 for now, it's a good start, but there is no need for the "other" folder. sample/blink <-- For all blink samples sample/ <-- For all other samples leave device files in the lib folder, since it is a library and we would only want to have to include one folder when compiling like jalv2.exe -s lib Matt. On Saturday, October 18, 2025 at 4:47:06 AM UTC-4 [email protected] wrote: > 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/1352a88a-2735-4f6d-99e4-b85e0c35a0ddn%40googlegroups.com.
