[ENH] MorphicEventDispatcher refactoring ([closed] on Mantis
1594 )
Larry Trutter
ltrutter at onemain.com
Tue Aug 2 12:26:31 UTC 2005
Thank you for your report. I have transferred your report to Squeak's
Mantis Database and you can followup on the issue if desired by going to
http://bugs.impara.de/view.php?id=1594
In the future please report new issues on Squeak's Mantis Database at
http://bugs.impara.de/ .
Please see http://minnow.cc.gatech.edu/squeak/398 for information on
reporting bugs, fixes, or enhancements.
thanks!
Larry Trutter
Eddie Cottongim wrote:
> This is a fairly straightforward refactoring; three methods had an
> essentially identical procedure for handing events to submorphs. [one
> condition had to be flipped in #mouseDown]. This doesn't have any
> performance benefit but it does make it easy to override for fast
> event dispatch for specialized clients.
>
> But I was hoping to get some ideas to make it better. Right now, its
> slightly ugly to use a fast binary search dispatcher, because the fast
> dispatcher has to consider what kind of morph its dealing with and/or
> get itself uninstalled for regular morphs further down the chain. What
> I'm getting at is maybe it would be better to delegate the submorph
> search to Morph; then all the submorph search logic would be in one
> (or at least no more than a few) place for a given Morph, and the
> event dispatcher would stay simple and clean. In trying to accelerate
> things I find its necessary to put the binary search logic in many
> places and it would indicate a good design if this number was minimal.
>
> Any ideas? I'm not totally sure what I want.
>
> Thanks,
> Eddie
>
>
>------------------------------------------------------------------------
>
>
>
>
More information about the Squeak-dev
mailing list
|