Tudor Girba wrote: 
Hi,

On Thu, Mar 1, 2012 at 3:07 PM, Ben Coman <btc@openinworld.com> wrote:

  
#formatAsWords - what does this have to do with composites protocol?


I do not understand the question. This example simply shows how you can use
format to customize how each item gets displayed.


The third pane of System Browser shows 'protocols.'  GLMBasicExamples has a
'composite' protocol which includes the formatAsWords method, but I don't
see what formatAsWords has to do with composites.
    

Oh, I see now :). It's just a mistake.

  
#magritte - This was one a was I was REALLY interested to see regarding the
update to Magritte 3.  However the code is identical to 4.5.  Both 4.5 and
4.6 produce the same error....
[Save] ==> error MAWriteError: Not supposed to write to something.
[Cancel] ==> no change. Now without knowing anything about Magritte, I would
expect the text box to revert to the original text.
    
What would actually be a fantastic example here would be a small address
book of a few entries that browsed a list in one pane and in another the
magritte detail could be edited.


Thanks. At the moment, I just improved a bit the existing magritte example.
I will try to enhance it a bit if I get some time.


Where do I find this?
Very much looking forward to a further Glamour-Magritte example.
    

It's in the repository. You can also find it in the latest Moose dev
build, although this will be on Pharo 1.4:
http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/artifact/

Thanks Tudor.  I added having a list view and details pane (image attached) and uploaded to http://www.squeaksource.com/Glamour as Glamour-Examples-BenComan.227.  I hope you like it.  Those small number of lines are a testament to the power of both Glamour and Magritte, and a minor achievement in my learning of them.  Things are slowly falling into place.

However I've broken starting it from the examples browser, so use the method comment - and hopefully the fix is obvious to you since I could not work it out.
Also as I mentioned above, the <Cancel> button does not perform as I expect, which would be to revert back to the original data.

cheers, Ben