Open technobly opened 10 years ago
Awesome, I’ll check it out!
Do you think there is any way to combine the two efforts or do you think they should just remain separate? Maybe their even two different tabs on one page?
On Dec 27, 2013, at 2:14 AM, Technobly notifications@github.com wrote:
Hi jflasher! Just wanted to let you know of a project I was working on tonight to create a really simplified version of your spark helper for function control with dedicated buttons: https://github.com/technobly/Simple-Spark-Core-Controller
I ended up hacking it up too much to turn it into any kind of pull request, so I just gave you credit as the origin. Hope that's ok.
You might benefit from some of the changes I made, specifically to the success/failure routines, and placement of the alert box. When you have multiple successes, it hides the alert for a bit to give you that positive feedback that it succeeded a second time. The success is keyed off of actual return_values as well, and the error will come through in case of a Time Out.
— Reply to this email directly or view it on GitHub.
What I am envisioning is an easy way to add controls (buttons) and feedback text (variables) on one page. You setup everything in the background, and then you are presented a working page of controls. I started down this path when hacking on your helper, but ultimately for smartphones you need some nice way of saving the setup of that "page" of controls. You could generate a form encoded URL that can be saved and later modified, which would make saving a shortcut to your app easy. That was too much work to get something going last night, so I just whittled everything down into one file index.html, and put all of the setup stuff in the code. It works, but if you don't have a place to host the files, it's not accessible on the road. I also removed the angularJS code just because I felt it wasn't loading fast enough, but then later I didn't even have a need for all of the extra input boxes for things.
I could see two different tabs, like a Playground area, and MyApp area. But you still need a good way to save the setup for smartphones. Currently the local storage doesn't work on iPhones.
It would be really neat to have the buttons auto size to fill a certain area on the screen. I'm sure a little addition to the bootstrap CSS would allow that.
Have you ever checked out the TouchOSC app for the iPhone/iPad? It's relatively easy to setup the controls, and then you just wire everything up in the background. It could actually be easier to just make an interface to OSC on the Core, but sometimes a dedicated interface with a few buttons is the easiest thing for people to understand. https://www.youtube.com/watch?v=wgFINZs6ido
I'm probably going to work on adding back the variable polling that you have in the helper, but make it dynamic like the buttons.
Let me know what ideas you have. I'm willing to help out in whatever way I can.
I ended up making a project that needed variables for feedback, so here's an example of that as well: https://github.com/technobly/Remote-Spark
This looks pretty nice. My original eventual plan was to make it so that both methods and variables would be able to be added/deleted. I also like the idea of having it be hosted somewhere centrally (like it is now on GH) and then be used by anyone.
I wanted to make something for people to test methods/variables with while it looks like your work is aimed more at something a bit more permanent? I just looked at the TouchOSC stuff and it looks pretty nice. It'd be neat to get some sort of interface builder in place, but then I think we might want to bring something like Angular back in?
Hi jflasher! Just wanted to let you know of a project I was working on tonight to create a really simplified version of your spark helper for function control with dedicated buttons: https://github.com/technobly/Simple-Spark-Core-Controller
I ended up hacking it up too much to turn it into any kind of pull request, so I just gave you credit as the origin. Hope that's ok.
You might benefit from some of the changes I made, specifically to the success/failure routines, and placement of the alert box. When you have multiple successes, it hides the alert for a bit to give you that positive feedback that it succeeded a second time. The success is keyed off of actual return_values as well, and the error will come through in case of a Time Out.