It is not the only place where on: is used to set the model, I guess it is a
common way to do this kind of things.
Franck
> From: b...@openinworld.com
> Date: Wed, 9 Sep 2015 23:47:52 +0800
> To: pharo-dev@lists.pharo.org
> Subject: [Pharo-dev] AbstractNautilusUI class >> #on: versus onModel:
>
> This is a small point, but maybe one tiny incremental improvement.
> Just thought I'd get some feedback before opening a ticket. While
> debug tracing through...
> Smalltalk tools openClassBrowser
>
> in Nautilus>>open I see...
> (self uiClass on: self)
>
> which calls PackageTreeNautilusUI class(AbstractNautilusUI class)>>on:
> ^ self new model: aNautilus
>
> where PackageTreeNautilusUI(AbstractNautilusUI)>>model:
> model := aNautilusModel.
> ...
>
> and my passing thought was a nicer API would be
> PackageTreeNautilusUI class(AbstractNautilusUI class)>>onModel:
>
> such that Nautilus>>open would be...
> (self uiClass onModel: self)
>
>
> Thoughts?
> cheers -ben
>
