Re: [Pharo-project] Status of ToolBuilder
On Nov 16, 2011, at 7:09 PM, Lukas Renggli wrote:
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).
It is quite powerful given that it can run OmniBrowser.
Of course Omnibrowser makes it easy by not allowing anything else than what is in MVC (e.g, Trees).
And the extra layer makes UI building trivially testable. This is not possible when directly using Morphs.
What we need is a seperation between Morph and the Widgets on top of Morphic. This than will likely include some layer, too. But keeping Toolbuilder if you have no MVC and Tweak is not really useful.
For Pharo I will rewrite the OB UI builder to directly generate an optimized Polymorph GUI. This buys more us more flexibility.
.. like trees. -- Marcus Denker -- http://marcusdenker.de
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).
It is quite powerful given that it can run OmniBrowser.
Of course Omnibrowser makes it easy by not allowing anything else than what is in MVC (e.g, Trees).
For sake of correctness: ToolBuilder supports trees since at least Squeak 3.9, but probably earlier. Lukas -- Lukas Renggli www.lukas-renggli.ch
participants (2)
-
Lukas Renggli -
Marcus Denker