Page 1 of 2

Different open source apps as widgets?

Posted: Tue Jun 02, 2009 11:31 am
by gooze
Would it be possible to get a more thorough integration with the software on the desk itself if you could install the opensource add-ons as a kind of widgets that are easily available (like in a sidebar on the second monitor).
People I speak to like the things the desk can do, but they don't like so much that it takes (a lot - as they say) of user action to get to all those beautiful add-ons.
Maybe you could make it as simple as the apps on the iPhone. People can develop for the platform and there is a standardised way of putting it on the device and a standardised way of how it looks and how you can interact with the apps. That would help a lot of getting a tighter user experience.

Re: Different open source apps as widgets?

Posted: Tue Jun 02, 2009 11:33 am
by BobbyHarrell
Interesting idea Gooze. Will discuss.

Re: Different open source apps as widgets?

Posted: Tue Jun 02, 2009 12:46 pm
by RobertBell
We have a method of adding widgets to [S5-Display] popup. Would that help if we used that? Also - the the Macro Editor - items are added to the SCRIPT list on the left. Does that help too? (examples right now are the Show Reporter macros).

I had a long talk today with Alan about how the desk could drive the Open Palette apps dynamicallyl. There is a bunch of work do to on that. Please discuss furtgher here (my above questions and anything else). Thanx

Re: Different open source apps as widgets?

Posted: Tue Jun 02, 2009 5:42 pm
by BrianEvans
As a developer of widgets, even I don't like the implementation as Gooze says.
I feel we are becoming to "floaty" like Martin Light Jockey.

We need a clever way of making OpenPalette Aps look like they are a part of the main UI.

Re: Different open source apps as widgets?

Posted: Tue Jun 02, 2009 8:32 pm
by JohnGrimshaw
BrianEvans wrote:As a developer of widgets, even I don't like the implementation as Gooze says.
I feel we are becoming to "floaty" like Martin Light Jockey.

We need a clever way of making OpenPalette Aps look like they are a part of the main UI.
A Folder D:\Widgets
- Any .exe file or .lua file in that folder is presented as a new option in a drop down menu to the right of "Display"
- Any widget can have a CTRL+[something] dynamically allocated by the user to run that script or .exe file.

MAYBE the .exe files need to be "registered" at OpenPalette, and have an "installer" made for them so that they will work on the console (and make sure we don't get "nasties" on the console).

Re: Different open source apps as widgets?

Posted: Tue Jun 02, 2009 10:10 pm
by amoyer
JohnGrimshaw wrote:A Folder D:\Widgets
- Any .exe file or .lua file in that folder is presented as a new option in a drop down menu to the right of "Display"
- Any widget can have a CTRL+[something] dynamically allocated by the user to run that script or .exe file.

MAYBE the .exe files need to be "registered" at OpenPalette, and have an "installer" made for them so that they will work on the console (and make sure we don't get "nasties" on the console).
I definitely agree with a centralized place where all of these widgets get place. D:\Widgets works for me.

And I think that from the side of support on the consoles, having the widgets tested by someone at Horizon (or Strand) and "registered" by OpenPalette is a MUST! It's one thing to test out an application on another computer/laptop on the network but to actually have it run on the console I would like to see a little bit of a stamp from Strand saying this application is good to use (functions without crashing the console). Last thing we need is to find an app that has the HC.ConsoleCrash command in it, as fun as that might be with an operator you want to piss off. :P

Re: Different open source apps as widgets?

Posted: Tue Jun 02, 2009 10:19 pm
by BobbyHarrell
At the same time, there are advantages to running the app on another machine. It offloads processing for one and gives your more options for running the app from a separate location like the LD at the tech table and the stage manager backstage.

Re: Different open source apps as widgets?

Posted: Tue Jun 02, 2009 11:55 pm
by JohnGrimshaw
BobbyHarrell wrote:there are advantages to running the app on another machine
Not withstanding that mapping network drives on the console is a dog to achieve, perhaps there is a function in the drop down menu:
Show Widgets from External Computer...

Maybe this is an IP Address for an instance of Palette, or Remote Palette running elsewhere, and it simply means that you can see and activate widgets/scripts for that processor.

Re: Different open source apps as widgets?

Posted: Wed Jun 03, 2009 12:20 am
by TaineGilliam
Wouldn't an Open GUI framework be a great step towards unifying all of this.

As for letting the console see the external apps - some published standard way for the apps to "advertise" on the network would be cool. The flip side of this would be the console advertising itself. I would tend to prefer more of a standardized ping/respond system rather than a continuous heartbeat (the old SN1xx node UDP heartbeat).

Of course the heartbeat had uses we have already discussed relating to remote consoles and tracking backup...

I'm sure there is a great opportunity for ACN (possibly RMD over ACN for some devices) when it comes to handling nodes, racks, consoles and other hardware "seeing" each other.

Re: Different open source apps as widgets?

Posted: Thu Jun 04, 2009 4:21 am
by gooze
I think the open surce apps shuld be intergrated in the software on the console as well as on separate hardware. So even if you are running let's say the followspot app it should be running from within the Remote or Remote video software.
The only difference should be plug-ins written for other software such as Lightwright.
Under view: plug-ins or with [S5 - View] would be the most logical place to find such a thing as a plug-in. I am not such a fan of scripts and the script editor, because using that I feel like a computer programmer instead of a designer or board-op.
I like Taine's sugestion of having the opensource app's or plug-ins or widgets unified by developing a Open GUI framework.