ml5-research-studio update: inpage code editor
alanvww opened this issue · 8 comments
Hi everyone. So as my project proposal for ml5 research studio showed, I am working on adding build-in code editor to the reference page and recently rewrote my previous code using Vite with React to minimize the size so it can easier on bandwidth when it loaded as iframe on each page. I added my in-page code editor to the facemesh example.
Here is the link and the screenshot:
The future plan as for now, is to show it to all of you for review and feedback and if this goes further, I would also like to create a json file to sum up all the example code in one place for easier loading and running.
Any advice and discussion would be greatly appreciated :D
Update:
Changed layout to vertical
Code Repo
Hey @alanvww ! I LOVE this - we will discuss this during our website meeting today and get back to you regarding the feedback :)
Hey @alanvww ! I LOVE this - we will discuss this during our website meeting today and get back to you regarding the feedback :)
Thanks Quinn! I am so glad you like it!
The target scenario for this widget is to show it with other projects like @jackbdu 's tutorials and @XiaozaoWang's interactive learning experience, so that all beginners can have a quick code reference and maybe just preview functionality without jumping to p5 sketch.
Other than that, I am also really open to working on anything else that has higher priority on both Gatsby and Docsify :D
@alanvww I had a quick discussion with @QuinnHe, and we are eager to implement your idea. Can we arrange a remote meeting? I will reach out to you via email.
Sounds awesome! I am available all day Friday except 6-8 PM EST and my NYU email is alan.ren@nyu.edu :)
@alanvww I had a quick discussion with @QuinnHe, and we are eager to implement your idea. Can we arrange a remote meeting? I will reach out to you via email.
Sounds awesome! I am available all day Friday except 6-8 PM EST and my NYU email is alan.ren@nyu.edu :)
Hey @alanvww , sent you an email:)
Alan, Quinn and I have scheduled a meeting to discuss the gradual implementation of the in-page code editor!