As a longtime user of QC and building User Interface's to drive QC graphical displays suitable (user friendly) for anyone to use I found QC quite cumbersome. Even with Quartz builder the replication of Input Inspector and resorting to building your own QC buttons, sliders etc was a pain and the results were unimpressive most of the time.

When I started using Mirek's Web-socket plugin it opened a whole new world of web based Custom UIs for QC. It also allows remote operation a possibility from iOS devices etc. Great for a client of mine doing large screen twitter feeds at International sporting events. OSC is the closest current existing tool to do this but it requires using a pre-determined iOS App of some kind and often that's just not what you want to give to your client, just not relevant. Also Websocket has packet security and I've had issues with OSC dropping messages in the past.

http://www.youtube.com/watch?v=L8GQgSHecNk https://github.com/mirek/quartzcomposer-websocket

HTML/CSS/JS is so quick to build compeling UI/UX with and Vuo/QC are not so I recommend this node to Vuo users to vote for.

Component: 

Tags: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●●○○ — A few weeks of work

Potential: 

●○○ — Appeals to current community

Comments

Alastair,

jmcc's picture
Submitted by
Feature status:
Chosen to be implemented
»
Open for community voting

Alastair,

Our plan has changed, so we are proposing:

  • Make a basic HTTP server node that would send integers, reals, and text from a web browser into Vuo. With that, a user could use/create various form elements: buttons, text fields, select lists, radio buttons, checkboxes. The node or nodes would be similar to "Receive OSC Messages" and "Get Message Values."

I don't really mind what

useful design's picture
Submitted by

I don't really mind what underlying methods are used but two-way flow of data and low-latency are usually determining factors of UI/UX success.

For my needs Mirek's Websocket was easier to use and more powerful than Kineme's web server and client patches. So I guess that's where my preference is. Seeing as you already are using ZMQ library for the Vuo Editor maybe you can leverage that?

I really wanted to use the Kineme patches in preference to Websocket in QC to build my UI but in the end I had no choice. If it's going to be like the QC patches, then I'm less than overjoyed. Maybe if I'd done IP networking 101 I could have got more out of server/client patches – dunno.

@jmcc I don't really

Bodysoulspirit's picture
Submitted by

@Jean Marie I don't really understand what Websocket is, but I was seeking through the feature requests to see if a simple URL/HTML node set request already existed.

Something like the Kineme Network tools, especially the XML Parser patch that was so useful to retrieve some website data into a composition.

Will this feature request handle such things or should I make a seperate one ?

This would be extraordinarily

Project26's picture
Submitted by

This would be extraordinarily helpful to allow back-end services to maintain a constant connection to Vuo and pass data bidirectionally.

For those totally out-of-the-know, think about it as "enabling Vuo to bidirectionally talk to another application over the network, using a magical, long-lived telnet-type or ssh-type session."

This is one of many network-level improvements that would greatly increase our ability to use Vuo in our environments. You could do some very cool things here.

Feature status

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for. Vote your favorite features to the top! (How do Vuo feature requests work?)

  • Submitted to vuo.org
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released

Votes

27 votes so far!

Who voted?

pyramus's picture
gabe's picture
Project26's picture
zzkj's picture