It is a very good solution. A database indexed primary by devices and then by peripherals? When you select a device, then you have a list with "things" (ADC, Timer, ) for which you have samples, then finally the list with the samples. But this "smells" a complete IDE to me... :P
Vasi(funlw65) P.S. Well, I think then every sample must have some keywords in header zone (comments) for the peripheral for which was written... for a scanner first time P.P.S. Another (preliminary) step is to have a folder for each device? It will be very easy for anyone to find samples for his device (if is not using an IDE). You can't see something similar on other distributions because no one provide samples for every device and this is a plus in JAL favor. But we must make it obvious and I think this way is very ... visible also. This way can encourage users to add samples for their favorite device or to complete where samples are missing. On Aug 1, 2:05 am, Sebastien Lelong <[email protected]> wrote: > Hi guys, > > Let samples in one directory, or many, whatever, and build a relational > database from all these samples ? Then allow to query it from the website, > or with jallib.py (it could use SQLite, only one file needed, no server). > > Cheers, > Seb -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
