Re: [Anygui-devel] Internal Requests for Comments

[Magnus L. H. <ml...@id...>]

From: "Paolo Invernizzi" <pao...@dm...>


> >but it may be interesting when dealing with the model/view mechanism etc.
> Infact I'm using it for such a job ;)
> One model of my data, 3 views... and the "old" signals.py keeping all the
> circus working...
> Oh well, NP, I'll extend anygui module for my own use ;)

I haven't ruled it out, mind you. If it makes model/view mechanisms
easier/better, we should probably have it. Could you give a simple example
of how you do this sort of thing?

> > Right... Joe didn't like that either. I just thought it was more
> > event-related. What would you like instead? Should we keep send? (Do you
> > really *send* an event?)
>
> To tell the truth, I loved "signal"... It remember me someone who raises
his
> hand asking for teacher's attemption...

Yes... I liked that too. Does it still seem reasonable as part of an event
system (rather than a "signal/slot" system)? E.g.

  signal(source, event, **kwds)

?

Doesn't sound too bad to me... Actually, you might see it like this:

  signal(source, **kwds)

with an optional event argument :)

Joe: Does signal() sound better than dispatch() to you in this context?
(It still shadows the standard lib signal.signal, but that's probably
not too dangerous...)

> > Should perhaps be ALL rather than ANY... Perhaps we could use the string
> "*"?
> Probably ANY is the right choice...

But you think None would be better? (It seemed so from your original
mail.)

> Paolo Invernizzi

--
Magnus Lie Hetland                           The Anygui Project
http://hetland.org                           http://anygui.sf.net