Portable Function Handles

[GoogleCodeExporter]

dotsDrawableTexture uses a function handle to specify which texture to draw.  
The function may live on the local machine, remote machine, or both.  It might 
even be part of Snow Dots.

Therefore, it's reasonable to specify a function handle as a SetObservable 
property of a dotsDrawableTexture.  Therefore, dotsTheDrawablesManager should 
be able to send a function handle to its counterpart.  Therefore, mxGram should 
be able to pack and unpack function handles.

The logic would be simple: detect function handle as a separate type of mxGram. 
 For packing, convert it to a string and pack the string.  For unpacking, 
unpack the string and convert it back to a function handle.

The current workaround is to use string function names instead of function 
handles.

Original issue reported on code.google.com by Benjamin.Heasly on 3 Aug 2010 at 6:20

[GoogleCodeExporter]

Original comment by Benjamin.Heasly on 4 Aug 2010 at 6:58

• Changed state: New

[GoogleCodeExporter]

For the November2010 milestone, I'm writing dotsComputable classes.  These also 
need to pass function handles between counterparts of the 
dotsTheComputablesManager.

Original comment by Benjamin.Heasly on 27 Sep 2010 at 11:49

• Added labels: Priority-High
• Removed labels: Priority-Low

[GoogleCodeExporter]

As of r398, I've added function handle support to mxGram.  I added unit tests 
and it looks OK...

Original comment by Benjamin.Heasly on 28 Sep 2010 at 1:36

• Changed state: Fixed