[Pharo-project] MVP

Benjamin benjamin.vanryseghem.pharo at gmail.com
Sun Mar 4 18:38:36 EST 2012


I am kind of a middle of something right now, so my advice is really to use the configuration (moreover I have added a lot of packages)


Keep me in touch,

Ben
 
On Mar 5, 2012, at 12:34 AM, Schwab,Wilhelm K wrote:

> Stef,
> 
> I skimmed the documentation and attempted to load Spec-BenjaminVanRyseghem.34.mcz into 1.3, but got an error and backed off.
> 
> Any ideas?
> 
> Bill
> 
> 
> 
> From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse at inria.fr]
> Sent: Sunday, February 05, 2012 2:56 AM
> To: Pharo-project at lists.gforge.inria.fr
> Subject: Re: [Pharo-project] MVP
> 
> if you want to have a look at what we are doing with benjamin you can have a look at
>  Spec
> 
> Yesterday benjamin added inputField support and rewrote the changeSorter.
> 
> Stef
> 
> 
> 
> On Feb 5, 2012, at 3:28 AM, Schwab,Wilhelm K wrote:
> 
> > More:
> > 
> > proportional layouts need to let each view have a proportion (zero makes it fixed size) and splitters should be just another view that is added to a composite, following the horizontal/vertical nature of the layout manager.
> > 
> > 
> > 
> > 
> > From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab at anest.ufl.edu]
> > Sent: Saturday, February 04, 2012 9:25 PM
> > To: Pharo-project at lists.gforge.inria.fr
> > Subject: Re: [Pharo-project] MVP
> > 
> > I'm still a little overwhelmed, but I see attention to layout; this has been a BIG stumbling block for me in my efforts to bring MVP to Pharo.  I recommend using nested composite view/presenter pairs for most layout.  First, it lends itself well to an eventual view editor, and second, can be surprisingly easy to code directly.
> > 
> > Each composite view has a layout manager.  Layouts include constrained table-like elements, but the real workhorses are proportional layouts, which can be set either horizontal or vertical.  By nesting them, very complicate behavior can be achieved.
> > 
> > There, said "nesting," and that has been where I have fallen into trouble.  Pharo/morphic layout works great for children of the top level, but after that, I can't get reliable results.
> > 
> > Sleep calls...
> > 
> > Bill
> > 
> > 
> > 
> > From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab at anest.ufl.edu]
> > Sent: Saturday, February 04, 2012 6:36 PM
> > To: pharo-project at lists.gforge.inria.fr
> > Subject: [Pharo-project] MVP
> > 
> > Hello all,
> > 
> > I have been to busy to read today, but I like seeing any discussion of MVP.   I am **slowly** working on  a framework for it, but would  be glad to be beaten to it.
> > 
> > Default models are key; they must be replaceable, but (sub)triads should work "out of the box."  Models can include value holders, value adapters, converters, and contexts, depending on how they are wired.
> > 
> > I have something of a start on the adapters and converters, which I can try to package and make available.  If nothing else, they will have value in seeding discussion if not be directly usable.   More to come.
> > 
> > Bill
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20120305/ea87cb1c/attachment-0001.html>


More information about the Pharo-dev mailing list