[Clam-devel] Improving Faust usability

[Natanael Olaiz]

r11641:
 * TaskRunner: added 'TODO: make a slot which first properly terminate 
the running process, if exists' on _closeButton->clicked()

I'll do it tomorrow.


El 07/19/2008 06:33 AM, Natanael Olaiz escribió:
> El 07/19/2008 05:18 AM, Pau Arumí escribió:
>> On ds, 2008-07-19 at 02:30 -0300, Natanael Olaiz wrote:
>>  
>>> El 07/18/2008 07:16 PM, Pau Arumí escribió:
>>>    
>>>> I'm thinking in some changes that could make faust a bit more usable.
>>>>
>>>>       * Change the "gear" icon for the command shortcut, which is
>>>>         repeated from the prototyper one. One idea is composing the
>>>>         faust logo with a gear (i.e. the logo on the back)
>>>>         
>>> Commited. I don't like it... but is something for now... Here is the 
>>> original svg attached (48x48px gear.png in front, faustlogo.svg in 
>>> the middle and a transparent square frame behind)
>>>
>>>    
>>>>       * Change the compilation workflow. Now you press "compile"->
>>>>         window pops up asking if you want to continue -> do stuff 
>>>> in the
>>>>         bottom panel -> window pops up saying "finished"
>>>>                 Why not: press compile -> the progress panel have a 
>>>> "cancel"
>>>>         button -> finishes and the "cancel" button turns into a 
>>>> "close"
>>>>         button.
>>>>                 Also with a close button we could disable the timed 
>>>> panel exit.
>>>>         Users may want to examine the console output.         
>>> I like the idea.
>>>    
>>>> What do you think? Maybe dynamically adding buttons is hard? An
>>>> alternative would be to have both buttons all the time but only one is
>>>> enabled at a time.
>>>>         
>>> I'll try it.
>>>
>>> BTW, I tried to dinamically add visual objects with the todo: 
>>> 'search bar' on the processings tree... but the automatically 
>>> generated layout is really ugly. In that cases, do you think is 
>>> better to deal with that managing the layout by the code, or use an 
>>> externally defined widget?
>>>     
>>
>> I'd do it by code, using layouts. Here goes an example with a similar
>> layout. It's pyqt4 but the qt usage is the same.
>>
>>         self.ok = QPushButton('Choose and Close')
>>         self.cancel = QPushButton('Cancel')
>>         buttonbox = QHBoxLayout()
>>         buttonbox.addStretch(1)
>>         buttonbox.addWidget( self.cancel )
>>         buttonbox.addWidget( self.ok )
>>
>>         mainbox = QVBoxLayout()
>>         mainbox.addLayout( consolewidget )
>>         mainbox.addLayout(buttonbox)
>>         self.setLayout(mainbox)
>>   
> Great, thanks!
>
> I commited it (r11640):
>
>     * TaskRunner: created a widget with a cancel/close buttons. Cancel
>    terminate the actual processs, clear the queue list and returns an
>    error.
>     * origin.txt: added UbuntuStudio reload.svg
>
>
> It uses an intermediate widget because I didn't found (yet) how to 
> pass the layout size.
>
>> Probably the hardest thing to do will be stopping the running process...
>>   
> Cancel clears the queue, set the error flag and do a 
> QProcess::terminate(). The finished signal calls finishedCommand, that 
> found an empty queue, to it finish the overall process.
>
>> P
>>
>>
>>  
>>>> Natanael, take the task if you feel like it (or discuss the idea, of
>>>> course). The functionality is already there, so no need to hurry.
>>>>  
>>>>       
>>> No problem. But I want to, it's really annoying the timer when you 
>>> want to see what happened :)
>>>    
>>>> P
>>>>
>>>>
>