Hey,
I like the idea of the pd.tk sourceing from a directory for tcl/tk code. Great idea HC. I've not taken a good look at pd.tk in some time, but I can't recall it being easy to go through. Any counter arguments to doing this?
pd.tk also sounds like it would need to be done eventually. Is anyone working on this? Design ideas?
As for the toolkit thing I'm curious how other toolkits relate in terms of widget types and so on. I know tk can be used by other languages, but can tcl bind with other toolkits?
I'm imagining that tk specific calls could be wrapped by PD functions. If we change the toolkit then one would only need to change the implimentation in these functions but the higher-level stuff would be left intact. That is IF there is enough similarity between toolkits.
Based on IX's posts it seems to me that tk is finally starting to move in the right direction... (the GL acceleration is particularly interesting)
B.
Krzysztof Czaja wrote:
yes, it would make customizing of pd-gui much easier, and it could somewhat improve robustness of gui externals. If the purpose of such a directory is customizing and extending locally (per user or per site), it will never be overwritten with new Pd installs.
Another thing is splitting pd.tk, which is already too big, and it might not survive adding more features by random patching. This is a typical case of a permanently makeshift code... perhaps, time to decide one way or the other about Tk, after all these years?
Krzysztof
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list