[squeak-dev] OmniBrowser and ToolBuilder

Chris Muller asqueaker at gmail.com
Tue Nov 22 19:37:35 UTC 2011

Have you considered fixing / augmenting the general capabilities of
ToolBuilder with the needs of OB?

Seems like needing to know the selection at any time is something that
any TextMorph widget should be able to provide!  I'm pretty surprised
it doesn't already.

Are there very many more cases where ToolBuilder falls short?

Does your option 4 mean you need to chanse existing base methods?  You
said, "add" the functionality so maybe you mean only add extensions.
If that is the case, I think that's fine.  However, if you meant the
former, then my concern about option 4 would be that it would pretty
much guarantee a continued "dichotomy" between ToolBuilder and OB.  I
like a lot of OB, but wouldn't be able to use it if I had to abandon
the highly-productive windows we have now..

 - Chris

On Sun, Nov 20, 2011 at 12:37 PM, Colin Putney <colin at wiresong.com> wrote:
> On 2011-11-20, at 1:15 AM, Frank Shearar <frank.shearar at gmail.com> wrote:
>> What options are missing from ToolBuilder? Is it just a case of
>> missing specs (+ Morphic backing) for some set of widgets?
> No, the widgets all seem to be there. What's missing is configuration
> options, and in some cases, capability in the Morphic widgets.
> For example, a bunch of refactorings operate on the current selection
> in the text pane. (eg. Extract Method.) Pluggable TextMorphPlus
> doesn't give the model any way to find out what the selection is when
> the building the context menu, so it can't decide what refactorings
> are applicable.
> Colin

More information about the Squeak-dev mailing list