On Tue, Oct 19, 2004 at 10:54:21AM +0100, Gustavo J. A. M. Carneiro wrote: > And a shared data structure is good. You can even use that to build > the option menu. And you'll have anyways most of the times if you value > gui / main code separation in your program.
For the record: IMO not necessarily. It may depend on what that data structure contains; in my case, it is often whole domain objects, which means they can't be module-global, and in consequence that I need to shift this data structure around over parts of the application through APIs that really could live without an extra parameter. If it's just static content like integers or strings, maybe, but I suspect there is indeed lower coupling resulting from using set/get_data() on the menuitems, just because it reduces the amount of information that needs to be explicited in the pipe between who creates the menu and who consumes its items. Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331 _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
