On 9/18/07, Gary Chambers gazzaguru2@btinternet.com wrote:
Well, there is the Model but there has to be a linkage for when the model changes. That's the basics. We need to decide on the way(s) we wish that to happen. I find changed/update rather inefficient. Much prefer when:send:to:.
By "changed/update" you mean "something changed, go reload the whole object"? I prefer the "register for this specific event from this model", but in MVP the Aspects were so fine grained I think even "changed/update" would work because you would be talking about changes to classes like string, number, etc. In other words, a presenter for a given class would have an aspect for each member as I recall.
But that's just the start. Pretty fundamental though.
-----Original Message----- From: ui-bounces@lists.squeakfoundation.org [mailto:ui-bounces@lists.squeakfoundation.org] On Behalf Of Jason Johnson Sent: 18 September 2007 6:07 pm To: Squeak's User Interface Subject: Re: [UI] Well, shall we do something then?
On 9/16/07, Bill Schwab BSchwab@anest.ufl.edu wrote:
I am not sure that we are actually trying to ditch Morphic,
so much as
offer an alternative to it.
With the MVP proposals I don't think we are doing either. I think Morphic could be used for the view if we want.
I hope people don't take my questioning of Morphic as an indication that MVP has to replace it. I think these are two totally different issues.
Perhaps we can offer a choice between Morphic and "The Welch Thing" on a per-use basis.
Personally I see this choice as the power of the MVP model. We can create a domain class, a presenter for it and a view (or a few) for each possible View type (e.g. Tweak, Morphic, OpenGL, Seaside?), which can be selected automatically depending on user preferences. _______________________________________________ UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui