-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
[UX] Integrate and update example files to serve as practical references #1560
Comments
@HugoGenillier could you go through the examples and mark the one that fails ? I'll fix them first :) |
Here is the list (tested on score 3.2.4, windows) :
But some other crashed during interviews like video-colorizing.score on a mac. Also there are some files .pd, .frag of .device that works when you drag them in ossia but some users will find it unclear and won't really know how to load the example. |
thanks ! the lygia ones require an additional library installed through the package manager, maybe that's something to add a detection step for. |
Example files can be very powerfull to guide new users, unfortunately they are currently hard to access and some of them are outdated.
It would be great to provide other ways to access these example files (they are only available from the start screen, on a GitHub repository). The GitHub repository slows down users and can dissuade them to fetch these files, it's worth considering integrating them into score. These example files should also be mentioned in the documentation, in the get started part for instance.
Some files are not compatible anymore with latests versions and cannot longer be used. The already a strong basis of examples needs to be updated and commented. Having an example file for each use case is the way to go. We want users to be able to quickly and easily find an example of what they want to do, and build their score around it.
This recommandation was judged as very impactfull.
The "osc" example files is a great one with comments and reusable elements.
The text was updated successfully, but these errors were encountered: