I have used Tkinter a lot and never had any threading problems. Everything 
always
worked fine, even python callbacks from Csound. Tkinter's canvas object is 
something
I have not seen in WxWidgets, but I must say I don't know that toolkit 
extensively.

Victor
----- Original Message ----- 
From: "Michael Gogins" 
To: 
Sent: Sunday, January 06, 2008 5:02 PM
Subject: [Csnd] Re: Re: Re: a new crossplatform initiative, was Re: Re: 
intel maccsound


> There are threading issues between Tkinter and Csound that do not appear 
> in, at least, wxPython. I recommend wxPython for this reason. As far as I 
> know it has the richest set of widgets and the Boa Constructor IDE can be 
> used to interactively design GUIs. Highly recommended.
>
> Regards,
> Mike
>
> ----- Original Message ----- 
> From: "Russ S" 
> To: 
> Sent: Sunday, January 06, 2008 9:33 AM
> Subject: [Csnd] Re: Re: a new crossplatform initiative, was Re: Re: intel 
> maccsound
>
>
>> Perhaps Python's Tkinter, since there is already an existing
>> relationship between CSound and Python.
>>
>> On Jan 6, 2008 7:21 AM, Andres Cabrera  wrote:
>>> I wouldn't know where to start either, but I guess it would be hard to
>>> get everyone to agree on a particular set of tools. I would propose Qt,
>>> which I've used lately, is cross-platform and is quite easy to use.
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>> csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

I'm afraid this discussion is becoming more about GUI toolkits than Matt's
 suggestion, i.e., creating a mechanism whereby particular GUI toolkits
don't matter! What's important here is, and should always be Csound, not
the front end code that is piled on top of it. Of course this is only my
opinion...

Rory.




> I have used Tkinter a lot and never had any threading problems. Everything
> always
> worked fine, even python callbacks from Csound. Tkinter's canvas object is
> something
> I have not seen in WxWidgets, but I must say I don't know that toolkit
> extensively.
>
> Victor
> ----- Original Message -----
> From: "Michael Gogins" 
> To: 
> Sent: Sunday, January 06, 2008 5:02 PM
> Subject: [Csnd] Re: Re: Re: a new crossplatform initiative, was Re: Re:
> intel maccsound
>
>
>> There are threading issues between Tkinter and Csound that do not appear
>> in, at least, wxPython. I recommend wxPython for this reason. As far as
>> I
>> know it has the richest set of widgets and the Boa Constructor IDE can
>> be
>> used to interactively design GUIs. Highly recommended.
>>
>> Regards,
>> Mike
>>
>> ----- Original Message -----
>> From: "Russ S" 
>> To: 
>> Sent: Sunday, January 06, 2008 9:33 AM
>> Subject: [Csnd] Re: Re: a new crossplatform initiative, was Re: Re:
>> intel
>> maccsound
>>
>>
>>> Perhaps Python's Tkinter, since there is already an existing
>>> relationship between CSound and Python.
>>>
>>> On Jan 6, 2008 7:21 AM, Andres Cabrera  wrote:
>>>> I wouldn't know where to start either, but I guess it would be hard to
>>>> get everyone to agree on a particular set of tools. I would propose
>>>> Qt,
>>>> which I've used lately, is cross-platform and is quite easy to use.
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>> "unsubscribe
>>> csound"
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

> I'm afraid this discussion is becoming more about GUI toolkits than Matt's
> suggestion, i.e., creating a mechanism whereby particular GUI toolkits
> don't matter! What's important here is, and should always be Csound, not

yes - i think we already have that with lettuce/csound~/maccsound/etc - 
but i am also thinking about how we can make something were it would be a 
snap to create frontends for any toolkit -- especially for WYSIWIG 
interface editor tools (there's no way i can get maccsound's gui editor 
better than apple's interfacebuilder app)

plus i was just thinking (outloud) about future possibilities, and in 
the context of migrating maccsound file format to cabbage (and enhancing cabbage to 
make this possible) - and i have to admit all came about because i was 
checking out some of the new features in the new max/msp.
http://www.cycling74.com/story/2007/10/31/135346/29

so all i was proposing (with my first suggestion) was to create a protocol 
where:
  + widget attributes could be (assumed to be) capable of changing
 	dyanamically
  + changing these attributes would occur over a single bus channel


-m