Hi Peter and ,
I would if I could. I am pretty new to (wx)Python so I am not aware of
it's possibilities and built in solutions. sigslot appealed to me
because I strongly believe in data model / GUI seperation. My previous
apps became monsters because the GUI did more with the objects then
plain behavioral code.
My new vision is this:
Controller - that can take actions like "create new project"
Data - The project info itself
GUI - As minimalistic as possible, should only respond to the data
events or initialize new ones. I give a new "project" to the
controller like;
__controller.AddProject(new Project('my name'))
It should emit events to the GUI where the "dumb" combobox simply adds
the new project, the status bar shows this project if the
ProjectManager object tells me that the new object added is also the
selected on, etc.
The problem with traditional GUI programming is that too much
dependencies can exist, things can be forgotten to be updated, etc.
This new approach can also allow Undo / Redo much easier as the Add
signal can be replaced by a remove, which will hide the object from
the GUI's again.
To come back to the example, I am not knowledgeable enough to see how
it works, nor can I see if it allows me to specify an argument list
for every signal that I can create.
By the way I tried PyDispatcher but there is almost no example to be
found showing how it works. Anybody have a good example?
- Jorgen
To unsubscribe, e-mail: wxPython-users-unsubscribe (AT) lists (DOT) wxwidgets.org
For additional commands, e-mail: wxPython-users-help (AT) lists (DOT) wxwidgets.org