On 16 November 2011 21:58, Eliot Miranda <eliot.miranda@gmail.com> wrote:
On Wed, Nov 16, 2011 at 1:53 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Nov 16, 2011, at 6:31 PM, Lukas Renggli wrote:
I was kind of surprised that ToolBuilder is still part of Pharo.
where? Because we removed it.
It is contained in the Polymorph packages in Pharo 1.3, but it missing some and has additional other features compared to the version in Squeak.
I was asking because OmniBrowser in Squeak is now using ToolBuilder, the code works with a few changes in Pharo 1.3 too.
Does Toolbuilder make sense? To me it looked like yet another compatibility layer that does not bring anything (other than forcing anyone to use something that has to be compabtible to MVC).
In general it abstracts away the specific UI used to present a tool and I'd say that was generally useful. Â Anyone wanting to experiment with a novel UI could benefit from ToolBuilder. Â In Squeak trunk there's even the ability to test it against Morphic and MVC. Â MVC is still useful for those trying to build minimal images.
It's also really useful for someone who knows just enough about Morphic to not want to know anything more about Morphic to still knock up a half-decent UI. I've found ToolBuilder useful for constructing new UIs, editing existing ones and being able to follow actions without needing to know much about about Morphic. frank
    Marcus
-- Marcus Denker -- http://marcusdenker.de
-- best, Eliot