[Pharo-project] MVP

Schwab,Wilhelm K bschwab at anest.ufl.edu
Mon Mar 5 13:24:57 EST 2012


At least in the 1.4 seaside image, I do not get color highlighting the browser - debugger and workspaces do show 
coloring.  I just grabbed the latest seaside image to verify.


________________________________________
From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo at gmail.com]
Sent: Monday, March 05, 2012 12:47 PM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] MVP

Shout works in 1.4 ...


Ben

On Mar 5, 2012, at 6:44 PM, Schwab,Wilhelm K wrote:

> I can use 1.4 to look at the code.  Once shout works in the browsers, I might make the switch anyway.
>
>
>
> ________________________________________
> From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo at gmail.com]
> Sent: Monday, March 05, 2012 11:46 AM
> To: Pharo-project at lists.gforge.inria.fr
> Subject: Re: [Pharo-project] MVP
>
> The problem is that we improved a lot he morphic layout in 1.4, and Spec is based on that. So most probably it doesn't work in 1.3 (and I didn't put effort in this direction, and will probably not)
>
>
> Try Nautilus instead of OB ^^
> Again, we improved the system, but we are not maintaining OB, so it could be not up to date.
>
>
> Have fun with Spec,
>
> Ben
>
> On Mar 5, 2012, at 1:41 PM, Stéphane Ducasse wrote:
>
>> spec is not made to work on 1.3
>>
>> Stef
>>
>> On Mar 5, 2012, at 10:03 AM, Schwab,Wilhelm K wrote:
>>
>>> Stef,
>>>
>>> Thanks for the code!  #stable does some things on 1.4, but I still got nowhere with 1.3.  The big thing keeping me off of 1.4 is shout in the browsers - I *really* like syntax highlighting.  In fairness, I have not looked at 1.4 in a week or so, so maybe that's been fixed.  However, I can certainly run it to play around with spec.
>>>
>>> Even on 1.4, I got a DNU over groups; this time I had to add the noop to OB, which is apparently the default in 1.4??
>>>
>>> More fiddling to come.
>>>
>>> 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: Monday, March 05, 2012 3:26 AM
>>> To: Pharo-project at lists.gforge.inria.fr
>>> Subject: Re: [Pharo-project] MVP
>>>
>>> bill
>>>
>>> thanks for the catch. I updated the document.
>>>
>>>
>>> Gofer new
>>>      url: 'http://ss3.gemstone.com/ss/Spec';
>>>      package: 'ConfigurationOfSpec';
>>>      load
>>>
>>> ConfigurationOfSpec project load: #stable
>>>
>>>
>>> Stef
>>>
>>>
>>> On Mar 5, 2012, at 1:24 AM, Schwab,Wilhelm K wrote:
>>>
>>>> Ben,
>>>>
>>>> Great, but I'm still getting nipped by a DNU of #addGroupForPackage:.  I found that no-oped in 1.4 so added it to 1.3 and was able to loadFull.  It looks like great work, but I can't get anything to run in 1.3 or 1.4.  Any ideas?
>>>>
>>>> Bill
>>>>
>>>>
>>>>
>>>>
>>>> From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo at gmail.com]
>>>> Sent: Sunday, March 04, 2012 6:53 PM
>>>> To: Pharo-project at lists.gforge.inria.fr
>>>> Subject: Re: [Pharo-project] MVP
>>>>
>>>> Everything has been moved in ss3.gemstone.com/ss/Spec :)
>>>>
>>>>
>>>> Ben
>>>>
>>>> On Mar 5, 2012, at 12:47 AM, Schwab,Wilhelm K wrote:
>>>>
>>>>> Ben,
>>>>>
>>>>> Ok, but I don't see it in either dirty experiments or the mc repository.  Am I missing a ConfigurationOfSpec?
>>>>>
>>>>> Bill
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo at gmail.com]
>>>>> Sent: Sunday, March 04, 2012 6:38 PM
>>>>> To: Pharo-project at lists.gforge.inria.fr
>>>>> Subject: Re: [Pharo-project] MVP
>>>>>
>>>>> 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
>>>
>>>
>>>
>>
>>
>
>
>






More information about the Pharo-dev mailing list