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

Introduce module categorization #307

Open
edwinRNDR opened this issue Apr 27, 2023 · 2 comments
Open

Introduce module categorization #307

edwinRNDR opened this issue Apr 27, 2023 · 2 comments
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@edwinRNDR
Copy link
Member

As the number of ORX modules is steadily increasing it may be helpful to provide a categorization or tagging system to guide users through the process of finding the modules they want/need.

This categorization would be used in the TOC of the orx repository as well as a potential updated version of the guide

@edwinRNDR edwinRNDR added help wanted Extra attention is needed question Further information is requested labels Apr 27, 2023
@Treide1
Copy link

Treide1 commented Jun 4, 2023

Just the top of my head I can think of some categories:

  • Compatability
    -> For Hardware (like pen drawer g-code, midi devices, kinect or similar) or Software (like syphon or chataigne)
  • Data Structure/ Computation
    -> kdtree, compute-graph, animation, easing, interval tree
  • 3D
    -> mesh-generator, camera
  • GLSL
  • Drawing
    -> color-palette, no-clear

Also a "used in the template" would be nice to see what's used by default like orx-color

@Treide1
Copy link

Treide1 commented Jun 4, 2023

I am wondering how the labeling would be presented to newcomers.
I don't see a decent way of doing it with GitHub. Maybe as a separate page in the guide ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants