Ok what I suggest is to 
        - build the smallest case so that others can understand the forces in 
presence (this is what we did with Spec)
                in fact we started with one button and a list.

        - have a look at spec (the code is small) and how we could integrate 
your ideas to it. 

On Feb 5, 2012, at 12:42 PM, Schwab,Wilhelm K wrote:

> Stef,
> 
> It sounds great, and I will indeed help where I can.   I also have some code 
> (see separate plea for help re gofer or any non-mc way to upload files) that 
> might help.  If you have past me in some areas, WONDERFUL.
> 
> I'm on the mend from a bug last week, so I'm not 100% just yet (feeling much 
> better though).  More to come.
> 
> Again, one thing that I would really like to see is the ability to deeply 
> nest MVP triads.  Layout has been the hardest part of getting that to work.  
> You seem to be on good ground in terms of connecting models.  MVP is tough on 
> newbies (we never understood why that is), but very much worth the effort.
> 
> My goal has been to create an MVP infrastructure with "just a little Seaside" 
> feel to coding.  Don't ask why, but I think that would be a nice fit with 
> Pharo, and would allow us to defer what should be a long-term goal of making 
> a view editor.   With very good coding idioms, we can defer the editor w/o 
> losing much (I think).
> 
> Bill
> 
> 
> 
> 
> ________________________________________
> From: [email protected] 
> [[email protected]] on behalf of Stéphane Ducasse 
> [[email protected]]
> Sent: Sunday, February 05, 2012 6:27 AM
> To: [email protected]
> Subject: Re: [Pharo-project] Pharo Morphic View Application Framework
> 
> On Feb 5, 2012, at 12:19 PM, Schwab,Wilhelm K wrote:
> 
>> Stef,
>> 
>> Dumb/lazy question with good intentions; what is spec?  Too many code names 
>> :)  I should be able to at least offer guidance on MVP; I've used it to 
>> great effect for years, and know the good and weak points.
> 
> 
> I would love that :)
> 
> Spec so far:
>        Models based on valueHolder
>        to reuse widgets configuration AND logic
> 
>        declarative specification of UI
> 
> Next steps
>        - Support more widgets:
>                - combox
>                - drop box
> 
>        - start to rewrite most of the UI with Spec
>                - file list
>                - changesorter
> 
>        - boostrap a UI Builder
>                - first steps a spec presenter
>                - then a click and place
> 
>        - add present like prototype idea propagation
>        - Get more people helping/using/...
> 
> Stef
> 


Reply via email to