Hans-Christoph Steiner wrote:
Hey Chun, all,
I am thinking that for adding locales to pd-devel, we should leave iemgui out of it. It is very messy code that has a lot of legacy use, so that the iemgui stuff would need to have full backwards
I agree they are very messy.
I am totally for a remake of gui objects, with cleaner code, better functionality, and all the best. I believe much time must be spent on design of this, creating a common codebase for such objects, an API, a set of user requirements, and so on....
which collaborative tool could help in this phase? wiki?
just to throw in some ideas: * powerful sliders which allow to select range (i.e. a second handle comes in) * sliders and radio are basically the same type of object, just that a radio only would allow integer values * a bitmap object is missing (a seqence of bits.... just another representation of an integer) also, that could be 2-dimensional, allowing grid of bits... but that falls out of generality with the radio/slider objects * preferences dialogs as pd patches? (this may be too ambitious)
my 0.02
compatibility. Instead, I think we should build a new GUI library that includes locale support. In the process we could make a locale API for people who want to write their own GUI objects and include
where exactly does the locale applies to those objects? I mean I see really few text around those objects. could you provide a practical example?
btw I see this could apply well in a bigger picture... e.g. when rewriting the pd.tk ui
translations. I have almost the whole framework for such a library finished, its called 'tkwidgets'.
would be nice to see a demo of it! :)