New V8 scripting features - Non-modal?

Cheesehole wrote on 9/12/2007, 10:56 AM
Hi all,

Could one of the scripting experts give us a run down of what the new scripting features really mean? Can we script "plugin" style dialogs that stay active while all the editing features of Vegas are accessible? This sounds cool, but is the workflow for creating such things documented somewhere? And I wonder what tools we would need...

I realize I'm asking a lot, but the answers to these questions would give me a huge jumpstart.

Thanks...
Ben

Comments

jetdv wrote on 9/12/2007, 12:02 PM
Can we script "plugin" style dialogs that stay active while all the editing features of Vegas are accessible?

Yes. You can now make scripts that create docable windows that dock with the Explorer/Trimmer/Project Media/... area (or can be docked with other Vegas windows). These "Custom Commands" will remain running while Vegas is running.

Look for some example soon! :-)
jwcarney wrote on 9/13/2007, 12:18 PM
I read the changes.txt of the new scripting interface. It appears that .net 3 isn't just a scripting interface, but the official plug-in api, since Vegas is exposing more for developers.

Is that a correct assumption?
jetdv wrote on 9/13/2007, 12:28 PM
You use the .NET languages to access the Vegas API. Through .NET, though, the scripts can access all the standard Windows API as well.

I'll post a sample Custom Command in a new post here.
ForumAdmin wrote on 9/13/2007, 1:51 PM
Also note that .net 3 is really just .net 2 plus a few new assemblies.

The managed scripting/extension API in Vegas does not currently use .net 3 specific classes but the ProType titler does use a couple of .net 3 classes (WPF specifically)... so that's really why Vegas requires .net 3.

Another important thing to note is that scripts and extensions can not use WPF because there are problems using it outside the Default AppDomain... neither scripts or extensions run in the Default domain.

Hopefully Microsoft will fix that problem soon.
jwcarney wrote on 9/17/2007, 10:47 AM
Thanks for the info. They didn't fix it in 3.5 either? bummer.