How to separate p5 from non-p5 examples? #1
Comments
|
Dare we say: Another option is rather than have two versions of Some other ideas: |
|
Since the repo is already called ml5-examples, what about having something like this: And then we could have ML5 examples with other frameworks too: maybe its too much? |
…0.5. It also introduces some changes to a couple of the examples to better handle images and text with p5. The Neural Network example has been removed until the method is ready on the library. The stucture of the folders also has changes, reflecting #1
|
Going through this for the first time, I think having the folder be called p5js is confusing. I like Darius and Dan's idea of having 'examples' in the folder names as well. I don't think it's a bad idea to separate out the examples by framework/language, though. |
|
Closing this because it seems resolved. We decided to go with this for now: |
|
Love it! Looking forward to three.js examples! Say hi to @mrdoob at Eyeo this week! (Was such an honor to meet IRL!) |
|
@shiffman same! 😊 |
…0.5. It also introduces some changes to a couple of the examples to better handle images and text with p5. The Neural Network example has been removed until the method is ready on the library. The stucture of the folders also has changes, reflecting ml5js#1
Should we create a directory structure like this?
I'm actually at a loss for what to call the "plain JavaScript" examples. Plain? Vanilla? ES2017? JavaScript? The problem of course being that p5 is also JavaScript.
The text was updated successfully, but these errors were encountered: