Re: Well, shall we do something then?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Well, shall we do something then?

Jason Johnson-5
On 9/18/07, Gary Chambers <[hidden email]> 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: [hidden email]
> > [mailto:[hidden email]] 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 <[hidden email]> 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
> > [hidden email]
> > http://lists.squeakfoundation.org/mailman/listinfo/ui
> >
>
> _______________________________________________
> UI mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/ui
>
_______________________________________________
UI mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/ui
Reply | Threaded
Open this post in threaded view
|

Re: Well, shall we do something then?

Jason Johnson-5
Exactly my thoughts, though more fleshed out with your more thorough knowledge.

On 9/19/07, Bill Schwab <[hidden email]> wrote:

> Jason,
>
> Understood/agreed.  In fact I would expect to see a
> MorphicWorldPresenter that would allow one to incorporate morphs into an
> MVP framework.  I probably would start out using Morphic for views, and
> once that was working, start looking for an alternative.  It should be
> possible to coexist so that: (1) there will be a prayer of people
> looking at it let alone using it; (2) who wants to start writing an IDE
> while reworking the GUI =:0
>
> Bill
>
>
>
>
> Wilhelm K. Schwab, Ph.D.
> University of Florida
> Department of Anesthesiology
> PO Box 100254
> Gainesville, FL 32610-0254
>
> Email: [hidden email]
> Tel: (352) 846-1285
> FAX: (352) 392-7029
>
> >>> [hidden email] 09/18/07 1:06 PM >>>
> On 9/16/07, Bill Schwab <[hidden email]> 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
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/ui
>
> _______________________________________________
> UI mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/ui
>
_______________________________________________
UI mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/ui