[squeak-dev] Alternatives to inform:

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]]On Behalf Of
> stephane ducasse
> Sent: 03 March 2008 9:59 AM
> To: The general-purpose Squeak developers list
> Subject: [squeak-dev] Alternatives to inform:
>
>
> Hi all
>
> I would like to avoid to use inform: loading or other actions.
> Is there anybody that worked on such an alternative?
> I was thinking that may be something like toothpick or a logger could
> be the
> way to go but I would like to hear about alternatives before going in
> that direction.
>
> Stef
>

>
> On 3-Mar-08, at 1:59 AM, stephane ducasse wrote:
>
>> I would like to avoid to use inform: loading or other actions.
>> Is there anybody that worked on such an alternative?
>> I was thinking that may be something like toothpick or a logger  
>> could be the
>> way to go but I would like to hear about alternatives before going  
>> in that direction.
>
> What are you trying to accomplish?
>
> I've found that Notifications are good ways of handling user  
> interaction from low-level code. The default action can do the  
> conventional thing - open a FillInTheBlank or whatever - but higher  
> level code can intercept them, do something special, and resume with  
> a "user-supplied"  value.
>
> Also... what's a toothpick?
>
> Colin
>
>

>
> On 3-Mar-08, at 1:59 AM, stephane ducasse wrote:
>
>> I would like to avoid to use inform: loading or other actions.
>> Is there anybody that worked on such an alternative?
>> I was thinking that may be something like toothpick or a logger  
>> could be the
>> way to go but I would like to hear about alternatives before going  
>> in that direction.
>
> What are you trying to accomplish?
>
> I've found that Notifications are good ways of handling user  
> interaction from low-level code. The default action can do the  
> conventional thing - open a FillInTheBlank or whatever - but higher  
> level code can intercept them, do something special, and resume with  
> a "user-supplied"  value.

>
> On 3-Mar-08, at 1:59 AM, stephane ducasse wrote:
>
>> I would like to avoid to use inform: loading or other actions.
>> Is there anybody that worked on such an alternative?
>> I was thinking that may be something like toothpick or a logger  
>> could be the
>> way to go but I would like to hear about alternatives before going  
>> in that direction.
>
> What are you trying to accomplish?
>
> I've found that Notifications are good ways of handling user  
> interaction from low-level code. The default action can do the  
> conventional thing - open a FillInTheBlank or whatever - but higher  
> level code can intercept them, do something special, and resume with  
> a "user-supplied"  value.
>
> Also... what's a toothpick?
>
> Colin
>
>

>
> On 4-Mar-08, at 12:46 PM, stephane ducasse wrote:
>
>> My goal is to have a version of squeak (let's call it sapphire)  
>> that does not pop up windows all the time anywhere (especially  
>> annoying if we want to have a
>> server or headless system).
>> So I plan to have a look at all the inform: and other in the  
>> packages of sapphire and I would like to have a way to
>> provide feedback via an UI elements or not. I thought that I should  
>> look at toothpick.
>
> Aha. Then I definitely recommend Notifications. Take a look at  
> subclasses of OBInteractionRequest. OmniBrowser uses them everywhere  
> it needs to initiate interaction with the user - basically for  
> opening a menu or window. As a result, the same core code can work  
> unchanged with Morphic, a web UI via HTTP and a fake UI that's used  
> for testing.
>
> Cleaning up direct use of Morphic in Squeak is a worthy goal -  
> please share the code with us. I can certainly use it even if it  
> doesn't go into the main distribution. Here's a fix to Parser to get  
> you started.
>
> Colin
>
> <Parser.3.cs>
>
>
>