[UI] ToolBuilder

[Colin Putney]

On Sep 9, 2007, at 6:25 PM, tim Rowledge wrote:

> On 9-Sep-07, at 2:59 PM, Gary Chambers wrote:
>
>> As far as I see, the "Pluggables" seem to extend the flexibility...
> One of the original reasons for plugability of views was so that  
> several views of the same kind could be connected to the same  
> model; without having pluggable selectors (or the alternative  
> pluggable adaptors as proposed by the Tek gang in about 1985) you  
> would have to have a separate subclass of list view for each pane  
> in a browser.

Right. Without pluggability, you're limited to one view per model. By  
making the view-model protocol to be different for each view, the  
model can react differently to different view. In OmniBrowser I found  
that even this level of flexibility wasn't enough. I found I wanted a  
variable number of views, which pluggability couldn't accommodate. So  
I went back to the one-view-per-model pattern, with the main model  
holding a collection of sub-models and communicating through them.  
That worked out quite well... maybe there's a better way to do it, or  
a way to generalize this pattern and build it into the framework.

Colin