Hi Matt,
On 20.11.14 03:26, Matthew Schinkel wrote:
I'm not sure how the automatically generated docs works. What script
is used, and when is it run? I'm guessing it's part of buildbot.
I think so.
Other options:
1. Maybe 2 scripts can be written and added to the package. One would
sort your samples by type, and one by PIC. The user could then
easily sort their own samples by running one script or the other.
It isn't too difficult to produce any overview of samples.
But in which format(s)? Wiki, html, plain ASCII text, ....
The windows installer I created could have a sort option.
2. Have two copies of each sample in the package with 2 directories
called by_sample and by_device. Maybe not the best option due to
duplication, but it may be one way to keep everyone happy.
I have not the illusion that everyone can be made happy ;-)
With 'by sample' you probably mean 'by_library'? Many samples use more
than one library, which is not always reflected in the filename. Samples
should be scanned for include statements to obtain a complete overview.
The torelease analysis does that already! So someone with some Python
experience (or has interest to learn PYthon) has already some example
code to make these lists.
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/d/optout.
