[Clam-devel] Frontend for automatic generation of plugin code

[Pau Arumí]

On ds, 2008-08-02 at 23:56 +0200, Xavier Amatriain wrote:
> Really cool ++ :-) This has been a long time in the todo list!
> 
> What else would it take to generate a full working processing class this 
> way? Add a text box for the Do() C++ code? The #includes? Anything else?

And then you get the compiler error message and what you do? Hummm...

Code editing (beyond tedious template code) should be done in
editors/IDEs instead of forms, IMO.

*But* it leaves to an interesting point. Why not integrate this
processing generation in NE? 
You specify the metadata, click "create processing" and plop, it appears
in the canvas. Then, as in faust we could launch an editor on user
request (clicking on the box), and even recompile, re-using the console
panel we have for faust.

P


> Hernán Ordiales wrote:
> > On Sat, Aug 2, 2008 at 4:32 PM, Pau Arumí <parumi at iua.upf.edu> wrote:
> >   
> >> On ds, 2008-08-02 at 14:58 -0300, Hernán Ordiales wrote:
> >>     
> >>> Written in pyqt:
> >>> CLAM/scripts/TemplatedPluginsGenerator/PluginCodeGeneratorGUI.py
> >>>
> >>> Screenshot: http://iua-share.upf.edu/wikis/clam/index.php/Image:PluginCodeGenerator.png
> >>>       
> >> very neat addition! :-)
> >>
> >> maybe we should call this "processing code generator" or similar.
> >> else it collides with the other kind of "plugins" we now also generate
> >> (LADSPA, VST in the future...). what do you think?
> >>     
> >
> > I agree. I'll rename it
> >
> >   
> 
> 
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel