Laurent,
I don't have a fix yet. ��In fact, I am so impressed with what you have done that I am thinking of abandoning, or least strongly altering, my GUI efforts based on what you are doing.
Having some basic Dolphin-like classes for presenters (text, list, tree, image) could be very useful. ��But another approach I am considering is to try to approach it more like Seaside code which has some advantages.
Bill
________________________________________
From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of laurent laffont [laurent.laffont@gmail.com]
Sent: Thursday, June 17, 2010 10:34 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Prof Stef browser
Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr>
On Thu, Jun 17, 2010 at 4:20 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote:
For fun, open two Prof Stef browsers and see what happens when you click on the tree in one of them. ��Then close the second one, and click on the tree in the first. ��They should act independently. ��Beyond just a nice system for newbies, this is a potentially important example to get people started building GUIs in Pharo, so the details are important.
I agree. I'll try to have a look (repository is public write, if you have a fix just commit it).
Cheers,
Laurent Laffont
http://pharocasts.blogspot.com/
http://magaloma.blogspot.com/
_______________________________________________
Pharo-project mailing list
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project