[Pharo-project] Status of ToolBuilder
I was kind of surprised that ToolBuilder is still part of Pharo. Are there any users? Are there any plans to update it to match the version of Squeak? Is it encouraged to build UIs with ToolBuilder? Lukas -- Lukas Renggli www.lukas-renggli.ch
On Nov 15, 2011, at 8:47 PM, Lukas Renggli wrote:
I was kind of surprised that ToolBuilder is still part of Pharo.
where? Because we removed it.
Are there any users? Are there any plans to update it to match the version of Squeak? Is it encouraged to build UIs with ToolBuilder?
no :) We were brainstorming on valueHolder, Spec and UIBuilder a la VW with Benjamin and we got the conclusions: Specs are cool because the same application Model can propose multiple spec valueHolder are the building brick to be able to reuse the application model UI logic (and not just the UI widgets). placing widgets on the screen is just a part of the story but the least interesting one because point 2 is more important. Now This is a brainstorming
Lukas
-- Lukas Renggli www.lukas-renggli.ch
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.
Are there any users? Are there any plans to update it to match the version of Squeak? Is it encouraged to build UIs with ToolBuilder?
no  :) We were brainstorming on valueHolder, Spec and UIBuilder a la VW with Benjamin and we got the conclusions:     Specs are cool because the same application Model can propose multiple spec
That has nothing to do with specs though, there are many other ways of how multiple views can work with or provided by the same model. In my experience specs often lack the necessary dynamics to build useful UIs. So a lot of glue code is necessary to assemble the different parts. In the end I find it more convenient to just use the glue code (like in Seaside or ToolBuilder).
    valueHolder are the building brick to be able to reuse the application model UI logic (and not just the UI widgets).
I do not understand that point. Lukas -- Lukas Renggli www.lukas-renggli.ch
Just to summarize it.ToolBuilder did not support the widgets of Polymorph like tab, drop boxes and others. We removed it (it was discussed at ESUG in Barcelona). We discussed with esteban which was one of the few users. Now there is no tool builder in pharo. Toolbuilder was nice to get a minimal support for a limited set of widgets but it hampered new UI construction. We need to have better way to build and reuse widget logic. Lukas about the glue (and the spec) we will see. Right now we are trying to understand what we want. Ben will clean his 5 classes code so that we can think together. Stef
I was kind of surprised that ToolBuilder is still part of Pharo.
Are there any users? Are there any plans to update it to match the version of Squeak? Is it encouraged to build UIs with ToolBuilder?
Lukas
-- Lukas Renggli www.lukas-renggli.ch
participants (2)
-
Lukas Renggli -
Stéphane Ducasse