The perfect AviSynth GUI ...

[vion11]

There are some rumors AviSynth 3.0 will have
a better programming interface for GUIs.

But it is hard to implement unknown features.

So if you ever had a thought of something
more convenient or powerful
than notepad or Ctrl+E in vdubmod,
this is the right place to drop a line.

To enhance your workflow and to progress productivity -
what do you need?

And if you want your dreams come true,
forget about Freud, use this thread
as your anonymous oneirocritic and
don't resist excessive loquacity.

Though some imaginable features will appear
soonest with AviSynth XII...

[Doom9]

@vion11: I understand your intentions are just the best, but don't think think "perfect AviSynth GUI" is a bit provocative? Even if you create something awsome, not everybody will necessarily agree with that assessment ;)

[Guest]

Well, it needs to support dialog boxes for filters, with dynamic preview, as in VirtualDub.

[stax76]

it would have a full blown parser for the AviSynth scripting language which is a essential component to any modern IDE to offer advanced code editor features for direct code editing and GUI features that need information or about the code or need to modify the code. DVX and AVSEdit have limited parsing facilities for features like displaying and comparing filter stages but it ain't really a full parser. In any case it would have both code editing and GUI representation that can comunicate bidirectional, after all AviSynth is a scripting language and most people want to use it that way

[Bidoche]

@neuron2

It can be done (clumsily) by having sliders to adjust digital function input and reparsing the script at each mod.

A better way would be to have filters to provide hooks to modify them in place.
With the help of a ClipEditor class, maybe...


@Dolemite

Can you be more specific about what you want, I am not following you anywhere.

[stax76]

@Bidoche

you mean the parser? Modern development environments have code parsers, code generators etc. for features like IntelliSense, designers (forms etc.), in the best case these components are part of the platform of the development environments and not in the development environments self, in .NET for instance it's the System.CodeDom namespace but there is no parser yet, only generators, language providers, compiler services etc. (the parsers are therefor in the IDE's until they become part of the platform)

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemcodedom.asp

[vion11]

@all
I have impression things getting weird in this forum.

Intention of this thread was to collect ideas about
a perfect GUI, and then in a second step to look what kind
of interface is needed to *enable* that sort of GUI.

That's what I call working future compatible.
I've never said, anybody is actually going to
develope that dream GUI.

I've choosed this topic (usage) and *not* development
to encourage user of avisynth to tell their needs.
To achieve that I've choosed a level of language
*everybody* can understand and makes clear it is not
adressed to developper.

And to get response a bit of provocation is needed.

Now the top developer are throwing around with terms
normal user can't understand and prevent their participation.

What is Avisynth ? A tool from developer to developer only?
Or is a wonderful flexible system to fullfil all aspects of
video creation, worth to play a major role in this domain?

If any developer feels forced to participate on Avisynth 3.0,
subscribe to this newsgroup and get active there:
news://news.gmane.org/gmane.comp.video.avisynth3.devel

@doom9
please close this thread it is useless now.

[t_2]

Well, if anyone doesn't qualify as a developer it is me, so here goes.

I would like a full fledged gui like Premire complete with timeline, and filter preview as was mentioned above, BUT without compromising the scripting nature of AviSynth. Let me explain. In my mind AviSynth is somewhat like a webpage, which can be viewed on two levels, i.e., the actual page and the source code. Couldn't Avisynth be made with 3 levels, with a 3rd lever, a GUI between the script and the video. So that the script could be opened up as an avi, a txt and an html, or maybe just as an avi and html, where the actual page would be an interactive gui and the source code would be our tried and true script. Maybe something like saving an html file with the "avs" extention. Give it to a player and it's a video, feed it to a browser and it's an interactive GUI and look at the source code in that browser and it's a script!!! Wow!!!

Of course anytime you have a script like:
A=B+C where A,B and C are clips you have a timeline, here A. It would be nice if this timeline would indicate the length of the clip so that dragging the right end of B with the mouse in the Web Page would change the paramaters of Trim in the underlying script, and would grow no further when we reached "B.Trim(0,0)". BlankClip on the other hand could grow endlessly as the arg "length" became greater and greater. This Gui would have as many timelines as there are clip equations in the script. Highlighting any one of the timelines would make this the return clip in the script. Thus the script and Gui would be somewhat interactive since changing either one would automatically change the other. Of course there may be things that can't be implemented in the GUI.


I have no idea if any of this is possible, but then again, the real neat thing about AviSynth is that it is transparently present in your PC. This html idea would preserve this exciting feature while allowing for a gui. Or is this just science fiction???

[vion11]

@T_2
Many thanks for your input. The analogy to browsers is
quite smart and intelligible. And it is a challenge to
turn science fiction into past :)