-
Notifications
You must be signed in to change notification settings - Fork 52
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
Timeline for support of server-based processing.js? #28
Comments
There's long been interest in a Processing.js port of WordCram, but at the moment, no plans for it. The biggest obstacle is collision detection, which WordCram currently handles with Beyond that, WordCram.js would need to parse its own text, since cue.language is only in java. Once all that's sorted out, I'd still have to port the other parts of the API. |
Thanks Dan, have to figure out a way for my project...keep you posted... |
Awesome, thank you! I'd ❤️ to see wordcram.js in the wild, I just don't have the time to work out the core bits yet. Any help on those will get it closer to possible. |
Further due diligence on the topic left me with this possible solution/approach...only to let you know... 😸 |
Hehehhh n1 I like especially the swapped Ying/Yang...on 🔥 |
Here's another project that could help get a WordCram.js started: https://github.com/nodebox/opentype.js |
Hi Dan,
Thanks for this great project, had lots of fun so far. It's rather a question than an issue. Wondering by when processing.js will be supported within WordCram. Any details to the timeline/implementation as of yet?
Thanks for short response...
Doucor
The text was updated successfully, but these errors were encountered: