On 4 September 2012 15:41, H. Hirzel <hannes.hirzel at gmail.com> wrote:
> Frank
> I think this is far from being obvious. It could remain in the image.
> Other option is to have a help class with notes with pointers to
> entries like
>
> http://www.lshift.net/blog/2012/08/31/intercession-without-source-changes
>
> Actually without additional explanation as in the web  link given
> above it is difficult to see the need for ObjectsAsMethods.
>
> So to summarize: This is a valuable thing which makes Smalltalk
> outstanding and people should be pointed to this either by having an
> example in the image or a reference in the help system or one of the
> help workspaces.
>
> --Hannes

Fair enough. The ObjectsAsMethodWrappers library (which the post you
mention uses) is a lot more featureful, but then again, you don't
necessarily need all those features, and certainly not in an example.
I withdraw my objection :)

frank

> On 8/31/12, Frank Shearar <frank.shearar at gmail.com> wrote:
>> I note ObjectsAsMethodsExample in the trunk image. Given the much more
>> featureful http://www.squeaksource.com/ObjectsAsMethodsWrap/, should
>> this guy really be in the image? (I guess it's OK, in the sense as
>> being a minimal working example of something not obvious.)
>>
>> Maybe it could go into its own unloadable package?
>>
>> frank
>>
>>
>