[Clam-devel] Re: faust status

Tue Jul 15 01:26:00 PDT 2008

The same, but without using StatusBarDumper class (anyway, it didn't 
work, I removed a line that makes an error), just a temporal 
QStatusBar::showMessage when compiling.

El 07/15/2008 05:02 AM, Natanael Olaiz escribió:
> Hi!
>
> Here is an adaption of the Annotator TaskRunner with queue commands 
> support.
> MainWindow compiles the faust plugins as the actual SVN version (one 
> by one), or if you uncomment the line 515 uses the makefiles (need 
> faust installed).
>
> What do you think to use just the standard output for the messages?
>
>
> Regards,
> Natanael.
>
> El 07/09/2008 05:20 PM, David García Garzón escribió:
>> Indeed we had a version of such a widget that implemented a queue of 
>> commands. I'll take a look to my 'borrame' folder, but if i don't 
>> find it, it is not that difficult to adapt the existing one. The nice 
>> think of that is that it is a component that can be reused. For 
>> example with the ladspa export i am about to implement.
>>
>>
>> On Wednesday 09 July 2008 22:00:19 Natanael Olaiz wrote:
>>  
>>> El 07/09/2008 03:42 PM, David García Garzón escribió:
>>>    
>>>> Take a look at the code we are using in Annotator to lauch the
>>>> Extractors. We are using a widget that displays the output and the
>>>> interface doesn't block. The missing thing is a signal to notify 
>>>> the end
>>>> in order to reload the faust plugins.
>>>>       
>>> Nice!
>>> Anyway, do you think to use in that way for every single compile
>>> command? The finished() slot can wait until the last .dsp is 
>>> compiled to
>>> emit "taskDone" signal... but we can use just one external script
>>> instead (using 'make' with original makefiles doesn't work if you don't
>>> have faust installed on /usr/...). What do you prefer?
>>>
>>>    
>>>> On Wednesday 09 July 2008 20:46:42 Natanael Olaiz wrote:
>>>>      
>>>>> El 07/09/2008 10:14 AM, David García Garzón escribió:
>>>>>        
>>>>>> Wow. Dump such many screenshots to the Development screenshots wiki.
>>>>>>           
>>>>> Added some, except the warning messages (maybe an animated gif 
>>>>> could be
>>>>> better for that). BTW, if we use just one script to compile the faust
>>>>> files we could use QProcess.startDetached
>>>>> (http://doc.trolltech.com/4.3/qprocess.html#startDetached) instead
>>>>> QProcess.start (http://doc.trolltech.com/4.3/qprocess.html#start) and
>>>>> manage it as background process, so the NE will not be 'frozen' when
>>>>> compiling.
>>>>>
>>>>> And thanks for improving the ugly format of the article and 
>>>>> screenshots!
>>>>>
>>>>>        
>>>>>> On Dimecres 09 Juliol 2008, Natanael Olaiz wrote:
>>>>>>          
>>>>>>> A simple overview of the actual Faust support:
>>>>>>> http://iua-share.upf.edu/wikis/clam/index.php/Devel/Faust_support
>>>>>>>
>>>>>>> I think so many of those how-to steps could be managed by a faust
>>>>>>> install/configuration script. What do you think?
>>>>>>>
>>>>>>> El 07/08/2008 09:50 PM, Natanael Olaiz escribió:
>>>>>>>            
>>>>>>>> Commited in two steps, and changed some names on MainWindow and
>>>>>>>> NetworkCanvas. Now those names are a little bit large, but I think
>>>>>>>> now them refers better to its uses.
>>>>>>>>
>>>>>>>> Commit 11582:
>>>>>>>> * RunTimeLibraryLoader: Load() changed to virtual, added some
>>>>>>>> commented debug messages, and minor changes on CompletePathFor()
>>>>>>>> * RunTimeFaustLibraryLoader:
>>>>>>>>    - implemented virtual Load() to search first for the examples
>>>>>>>> faust dir
>>>>>>>>    - added std::map GetCompilePluginCommands(std::string
>>>>>>>> pluginSourceFullName) to get required faust compilation 
>>>>>>>> commands with
>>>>>>>> the propers paths
>>>>>>>>    - if plugin exists in factory, use ReplaceCreator instead
>>>>>>>> AddCreatorWarningRepetitions
>>>>>>>>    - added helpers: faustBinCommand() and faustLibIncludeFile()
>>>>>>>>
>>>>>>>> Commit 11583:
>>>>>>>>
>>>>>>>> * ClamNetworkCanvas:
>>>>>>>>    - added signal: openFileWithExternalApplicationRequest
>>>>>>>>    - added QString _fileNameToOpen (used when catching the 
>>>>>>>> previous
>>>>>>>> signal on MainWindow), onOpenFileWithExternalApplication to set it
>>>>>>>> and getFileNameToOpenWithExternalApplication() to get it
>>>>>>>>    - added slot onOpenFileWithExternalApplication
>>>>>>>>    - added "Open diagram with browser" item on processings context
>>>>>>>> menu which have svg_diagram attribute
>>>>>>>>    - added "Open source with editor" item on processings 
>>>>>>>> context menu
>>>>>>>> which have dsp_source attribute
>>>>>>>> * NewtorkEditor MainWindow:
>>>>>>>>    - added slot on_action_Launch_Browser_triggered
>>>>>>>>    - on_action_Online_tutorial_triggered() calls
>>>>>>>> on_action_Launch_Browser_triggered
>>>>>>>>    - added slot
>>>>>>>> on_action_Processing_Open_File_With_External_Application_triggered, 
>>>>>>>>
>>>>>>>> connected to
>>>>>>>> ClamNetworkCanvas::openFileWithExternalApplicationRequest signal
>>>>>>>>    - added messages on slot on_action_Compile_Faust_triggered, and
>>>>>>>> changed to search the .dsp files on faust examples directory and
>>>>>>>> compile them one by one directly (doesn't need to have Faust
>>>>>>>> installed or makefiles)
>>>>>>>>               
>>>>>>> _______________________________________________
>>>>>>> Clam-devel mailing list
>>>>>>> Clam-devel at llistes.projectes.lafarga.org
>>>>>>> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-de 
>>>>>>>
>>>>>>> ve l
>>>>>>>             
>>
>>
>>
>>   
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: queuedFaustCompilation.patch
Type: text/x-diff
Size: 10413 bytes
Desc: not available
URL: <http://lists.clam-project.org/pipermail/clam-devel-clam-project.org/attachments/20080715/2a54df59/attachment-0003.patch>