Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample directory might need re-organisation #184

Open
GoogleCodeExporter opened this issue Mar 3, 2016 · 2 comments
Open

Sample directory might need re-organisation #184

GoogleCodeExporter opened this issue Mar 3, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

The growing amount of Jallib samples makes it more and more difficult for a 
user to search a relevant sample.  
The is a need for a better organisation.

Original issue reported on code.google.com by robhamerling on 9 Sep 2012 at 8:23

@GoogleCodeExporter
Copy link
Author

We have now 1079 samples of which 471 blink-a-led. So splitting off the blink 
samples would reduce the sample directory to about 600. This is still quite a 
lot, but spitting it up more - e.g. like the include directory - might not 
improve the search for a relevant sample by a Jallib user (I might be 
underestimating!).
So I suggest to begin with moving the blink samples to a 'blink-a-led' 
sub-directory in the samples directory, both in Jallib as well as in the 
distribution packages. 

Original comment by robhamerling on 9 Sep 2012 at 8:24

@GoogleCodeExporter
Copy link
Author

I already split it in the installer that's provided for jaledit. Followed the 
structure like:
10F - blink
       - rest of samples
12F - blink
       - rest of samples
16F - blink
       - rest of samples
18F - blink
       - rest of samples
After release found that the relative reference in the html files of the 
documentation broke. The samples can't be opened from within the browser.
Sunish

Original comment by robhamerling on 9 Sep 2012 at 8:26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant