Ah ok ToolBuilder is an old abstraction we removed. It was a visitor based way of building a UI using different builder. I was however incomplete and not really documented so we decided to simplify everything.
On Apr 2, 2012, at 7:08 PM, [email protected] wrote: > No, ToolBuilder. > > ToolBuilder-Kernel > ToolBuilder-Morphic > > ToolBuilder cross-refs: > > MCWorkingCopyBrowser > and > ThreadSafeTranscript>>openAsMorphLabel: aString > > openAsMorphLabel: aString > ^ (self buildWith: ToolBuilder default labeled: aString) > openInWorld; > yourself > " ^UIManager default openTranscript: self asMorphLabel: aString it should a bug. Stef > > So? Looks like interesting but... what's meant in the spec? > > Phil > > > 2012/4/2 Stéphane Ducasse <[email protected]> > > > > How is this related to ToolBuilder in the image? > > You mean UIBuilder? > The idea is that this is quite strange that UIBUilder defines the logic of > debugger and other tools building. > Now imagine (as this is done in VW) that a tools has a spec that defines how > to populate and link its widgets, then > we would not need to have UIBuilder concentrating too much of the logic. > > stef > > > > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: [email protected] | > Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges >
