[UI] ToolBuilder
Colin Putney
cputney at wiresong.ca
Mon Sep 10 06:13:30 UTC 2007
On Sep 9, 2007, at 10:47 PM, Jason Johnson wrote:
> On 9/10/07, Colin Putney <cputney at wiresong.ca> wrote:
>>
>> 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
>
> Sorry to be a broken record again, but it looks like you're describing
> the pains of having the Model directly connected to the view, instead
> of a flexible framework like MVP. I think if we switch to MVP these
> kinds of problems just go away.
I think it's just that I used ambiguous terminology. Replace "model"
with "presenter" in the above paragraph and see if it gets more
interesting. :-)
Colin
More information about the UI
mailing list