Once I modified a commercial Smalltalk so that "senders" showed all
methods which referenced the symbol with the same name. It was fairly
trivial to do, though I forget the details of how; it's been so long.

Rather than specifically to get at "performs", I did this because I had
set up an approach of defining resource methods used to connect up
standard GUI form components using literal array expressions like:
  #( "((componentName aspect) (path into domain))"
      ((userName text) (application user nameAsString))
     ... ).

It did occasionally cause confusion when you browsed "senders" -- since
you had to look a little harder to find the reference, since it
sometimes was just coincidentally used as a symbol for other reasons.
But the change really seemed essential to manage these GUI defining
resources. And I grew to like it. Obviously, one could have a
development GUI with options to search for senders in various ways.

Is something similar to such a simple approach to changing how senders
are looked up (to optionally include any symbols or their FONC
equivalents [identifiers, strings, whatever] in the method) possible
here to achieve the goal? Or maybe I don't yet understand the FONC
approach well enough?

--Paul Fernhout

Ted Kaehler wrote:
>       In Coke, let's make "senders" know about the perform calls. 
> Here are two variants of how this could be done:
> 
> 1. The perform primitive only operates on an S-expressions.  The 
> programmer would store the (target selector args) triplet in an 
> S-expression.  S-expression would be the default way to store the 
> data of a button or menu item at all times.  Searching all of them 
> would reveal the "static" performs.  (It is still possible to gin up 
> a selector on the fly and send it... no search can catch that 
> beforehand.)
> 
> 2.  Make some other kind of special object whose purpose is to store 
> the data for a perform.  Strongly encourage all perform data to be 
> stored in this kind of object.
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc

Reply via email to