Pubblish ports in exported apps

Discussions
1

Is it possible to access published ports in exported apps ?
Or do you have to build interactivity through the render window ?

2

Right now you need to build interactivity with buttons etc.

• Vuo 2.0 is coming with new UI elements that will already make this easier User interface (UI) node set — buttons, sliders, text/number boxes, menus

• What you want is this feature request to vote on : A UI for storing and editing published input port values (my understanding is that these will be stored across app launches)

• And if you want to save even more “preferences”, node states, url’s, etc (not just published nodes) across multiple app launches, right now you have to like use Save Data and Load Data, but there is another request to automate this : A UI for storing and loading the state of running compositions  

1 Like
3

Thanks for those links, the 2nd one is what i was hoping for but without the need to store values. Basically a separate UI window that is automatically generated from the published inputs when you export to an app. This was a feature or QuartzBuilder, the kineme app that built apps from QC comps and i was expecting vuo apps to have the same functionality. It really does add a lot to the usefulness of being able to create separate apps, i guess for now i’ll look using OSC to intract with app.
Cheers Howie

1 Like
4

Yes, looking forward to it too, and in exported screensavers too.

Yes, OSC is a way to go, one can also create a separate Vuo window for the controls by duplicating “Render __ to Window”, but to be able to hide windows or closing them, we’ll need : Nodes for showing/hiding windows, and to enable the window’s close button

With Kineme the team built upon QC, here, they built it from the ground, still pretty young software, so features are added over time, still missing some features, but already totally loving Vuo fro what it offers ;)  

1 Like
5

With Vuo 2.0 around the corner, it will include checkboxes & sliders, so it will be possible to use those as “Input Parameters” for exported apps too.
Right now you can already create your own checkboxes & sliders, but it takes more nodes VS the upcoming stock nodes for them (see joined composition Slider + Checkbox).

For text boxes, they’re still marked as “chosen to be implemented”, but not for the first Vuo 2.x. version.
You can also somehow make your own ones, but they really take quite a big amount of nodes, and need the custom Paradox nodes to be installed (link) (put the custom downloaded node from Github in your User Module Folder you can access from the Vuo editor Menubar > Tools > Open User Modules Folder & Relaunch Vuo) because the current Vuo version needs layer names for layers to be clickable (Vuo 2.0 will fix that if I’m right so it will already lower the amount of nodes needed).
(See joined composition Text Boxes)

And as said, since we cannot yet hide/close windows, right now you can show/hide the UI or parameters using a keyboard key (command key used in bot joined compositions).  

Slider + Checkbox.vuo (11.5 KB)

UI - Text Boxes.vuo (10.3 KB)