Avisynth Editor

[Marc FD]

If s.o. want to use the avisynth Tokenizer in a C++ app or in a Delphi app, just ask me (i don't want s.o. else to loose 10h for that too :) )

( for delphi users i've made an import dll unit with a template TTokenizer class / for C++ users, i can give you the sources of the core-free tokenizer )

Just 4 that.

Cheers

[dividee]

Reusing the Tokenizer from avisynth for an editor is a great idea!
Maybe later you'll want to reuse the Parser too, so you can provide syntax checking :devil:

[sherpya]

This thread is so long.. maybe someone has said same thing than me...
I use Context (http://www.fixedsys.com/context/)
as standard editor in windows... just tell him to highlight
avs script like a c++ program, the syntax is the same (expect for
# in c++ is not a comment but a preprocessor directive..., highlighting looks good even for comments)

[Marc FD]

@sherpa

>This thread is so long.. maybe someone has said same thing than me...

too long ?? have you see the XCD, the ffdshow and the XviD Alt-curve threads ??

>I use Context (http://www.fixedsys.com/context/)
>as standard editor in windows... just tell him to highlight
>avs script like a c++ program, the syntax is the same (expect for
># in c++ is not a comment but a preprocessor directive..., >highlighting looks good even for comments)

syntax highlighting is of course one of the thing i try to implement, but it's not the harder one :)

@dividee
>Reusing the Tokenizer from avisynth for an editor is a great idea!

yeah you're right :)

>Maybe later you'll want to reuse the Parser too, so you can provide syntax checking

I'll try do it too :devil:, but it'll be a bit harder !
The pb is that the tokenizer already discard too much informations, so i'll only use it to help to parse the script, but if i want the comments, i need to code some things after...
But i really like the idea to use the avisynth script parser to make an editor :cool:

[Richard Berg]

If we're smart about this, we'll find a way to export the necessary info from the DLL. Just copying the source as of today into your project is asking for major compatibility issues in the future.

[Marc FD]

I've only make a little env hack :
I've created a dll who gives me direct access to the tokenizer using tokeniser.cpp but i've done a very clean job so i just make minor changes on the original file : 6 new letters !!
I think it's the best way to use the avisynth internal script parser : there is no need to modify avisynth, it's for the editor to adapt. If you radically change the tokeniser, i would simply load the last CVS and recompile my .dll :) It's as simple as that.

Moreover, i don't think the tokeniser was modified since Ben writed it, so i don't await ANY updates (but i'm ready for :D )

[Richard Berg]

I modified it pretty extensively when I first reorganized the source (mostly just structural stuff, but also some functional changes like allowing newlines within quotes); dividee also added a lot of new functions recently.

Still, I agree that it's not something that'll be changed very often -- exactly the kind of benefit I was going for when I split up everything, in fact. If it's easy to for you to keep up to date, more power to ya!

[Marc FD]

I've "hacked" the 2.0.1 , thx :)

[Belgabor]

Hm, this might be a dumb idea, but why don't you just give it (the Tokenizer) an ActiveX interface? Perhaps you could even a WhatVersionAreYou function, so ppl programming stuff could perhaps find out with which AviSynth version they deal (or is there some other possibility already?). And if we go back to first thoughts about this editor, why not include a function that gives an xml on request which includes internal function descriptions (this too might be unnecessary as i admittedly never looked into the avisynth sources to find out what the tokenizer really supports doing on this behalf).

Cheers
Belgabor

[Marc FD]

The pb is i don't think it's a good idea to orient the dll to help any editor. It would make avisynth.dll a LOT bigger, because i entire XML/ActiveX interface must be something quit huge. And this might slow the use of avisynth too ? (dunno)

But the idea isn't bad :)
I tried to use avisynth.dll , but it's really too hard to call a dll from a dll (i don't know how to call dlls in C++, i only make C++ dlls to import them in delphi :cool: )

But i think a big XML or .inf-type file would be enough.
My problem is currently the graphical engine (oo of course :) )

There is not lot of coders who release 2 filters a day...
...Oups, i did it :devil:

[stax76]

I've added all Filters available in the 2.04 Doku to DVX, also I enlarged the Description. This can be seen in the sceenshots of the DVX site

[stax76]

the AviSynth editor of DVX has now a toolbar for comments and deleting comments, copy, cut, paste and undo. It has syntax highlighting, also new is drag and drop support

Regards,
Dolemite

[Richard Berg]

Wow, blast from the past. For reference, some recent threads that discuss the development of smarter & more integrated AVS parsing are here (http://forum.doom9.org/showthread.php?s=&threadid=37756&perpage=40&pagenumber=1) and here (http://forum.doom9.org/showthread.php?s=&threadid=38893).

[ErMaC]

I think it'd be really nice if we could combine these efforts with that of VirtualDubMOD, it already has an interesting AVISynth script editor, and if all of these things were integrated it'd make life much easier.

[Belgabor]

The script editor in vdubmod already has those functions, except for drag & drop. And if you really need a toolbar i could do something about that, too ;)

[LigH]

Originally posted by dividee
We could easily add a function in avisynth IScriptEnvironment (remember, there is a CreateScriptEnvironment function exported by the dll) which would return the list of all available filters and their paramaters. So you could query it directly. For plugins, you would need to call LoadPlugin first which add the filters in the plugin to the list.

Long ago, this proposal... In the official SDK documentation, I still can't find such a technology to query the functions an AviSynth plugin provides.

Are there any hints, 'how' it could be done currently, or even 'if' at all?

[vion11]

AVEditor uses IsFunction() to get available functions from
autoloaded plugins. I would like to see a solution to get
information on parameters as well.