This list is the place to ask all the "simple" questions you as a newcomer to Squeak always wanted to ask.

headers Jeff Gonis | 2 Jun 2010 00:11

_______________________________________________
Beginners mailing list
Beginners <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/beginners

On 02.06.2010, at 00:11, Jeff Gonis wrote:

> Hi everyone,
> 
> I am currently experimenting with using futures in squeak as a very convenient method for creating
processes to do background work in, but a problem I am running into is that they run in the Morphic thread it
appears.  This means that if I have a particularly long lived chunk of work I can end up blocking the UI thread
and having an unresponsive GUI.  Ideally what I would like to do is create a future, dispatch it onto a
process running at userBackgroundPriority, and then block the UI only when I try to get the value from the
Promise that is returned.
> 
> I know that I can use a block closure and the forkAt: method to get a process running at the
userBackgroundPriority, but this doesn't give me the nice behaviour of a Promise where I can block until
completion when I actually need the value my process will generate.
> 
> So my question is, am I missing something obvious here, or is dispatching futures to a different thread
something that is being worked on for a "future" squeak release?
> 
> Thanks for your help,
> Jeff G

Future messages by definition are executed in the main thread, just at a later time. But you don't need
futures to create Promises, you can resolve them directly in your background process.

pr := Promise new.
[pr resolveWith: (... some lengthy computation ...)] forkAt: Processor userBackgroundPriority.
... do something else in foreground ...
result := pr wait.

- Bert -

_______________________________________________
Beginners mailing list
Beginners <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/beginners

At Fri, 28 May 2010 10:55:31 -0600,
Clinton Blackmore wrote:
> 
> Very interesting.  It looks like I will probably not get to try any of these methods until next week, but,
what sort of
> adjustments do you think it would need for Scratch images?

  The biggest single issue is that my ImageBrowser depends on
InterpreterSimulator to load the image file and find out the object
pointers in it.  An older version of InterpreterSimulator that is
suitable for the Scratch image can be found somewhere (like in the
Squeak2.4 image) but bringing in it will take some efforts.

-- Yoshiki

_______________________________________________
Beginners mailing list
Beginners <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/beginners

At Wed, 2 Jun 2010 12:03:30 -0600,
Clinton Blackmore wrote:
> 
> Would it be easier to bring Scratch forward to run on a newer version of Squeak?

  Hmm, I think that would be so much more work, compared to for
example bringing in the InterpreterSimulator into the Scratch image.

-- Yoshiki

> On Wed, Jun 2, 2010 at 11:55 AM, Yoshiki Ohshima <yoshiki <at> vpri.org> wrote:
> 
>     At Fri, 28 May 2010 10:55:31 -0600,
>     Clinton Blackmore wrote:
>     >
>     > Very interesting.  It looks like I will probably not get to try any of these methods until next week, but, what
>     sort of
>     > adjustments do you think it would need for Scratch images?
>    
>     The biggest single issue is that my ImageBrowser depends on
>     InterpreterSimulator to load the image file and find out the object
>     pointers in it. An older version of InterpreterSimulator that is
>     suitable for the Scratch image can be found somewhere (like in the
>     Squeak2.4 image) but bringing in it will take some efforts.
>    
>     -- Yoshiki
>     _______________________________________________
>     Beginners mailing list
>     Beginners <at> lists.squeakfoundation.org
>     http://lists.squeakfoundation.org/mailman/listinfo/beginners
> 
> 
> [2  <text/plain; us-ascii (7bit)>]
> _______________________________________________
> Beginners mailing list
> Beginners <at> lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/beginners

_______________________________________________
Beginners mailing list
Beginners <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/beginners

My TextMorph subclass's>>step seems to be getting called before the object is
ready - or at least that's what I pieced together from stepping through the
debugger.

I tried adding the following to initialize :
	self stop.
	self stopStepping.
But step is still called.

Can I prevent the object from being stepped out of the gate, until I turn
stepping on later?

Here is the code:  http://forum.world.st/file/n2242459/MorphicSPD-spd.1.mcz
MorphicSPD-spd.1.mcz 
To cause the error, Doit: GrowableTextMorph new openInWorld.
The specific error is: 'UndefinedObject(Object)>>doesNotUnderstand:
#withIndexDo:'

Thanks.
Sean
--

-- 
View this message in context: http://forum.world.st/How-can-I-prevent-a-new-Morph-from-being-stepped-tp2242459p2242459.html
Sent from the Squeak - Beginners mailing list archive at Nabble.com.

On 04.06.2010, at 00:46, Sean P. DeNigris wrote:

> 
> Can I prevent the object from being stepped out of the gate, until I turn
> stepping on later?

Have wantsSteps return false.

Then you can start stepping later.

- Bert -

Bert Freudenberg wrote:
> 
> Have wantsSteps return false.
> 

Awesome, worked like a charm.  Thanks, Bert.

Sean
--

-- 
View this message in context: http://forum.world.st/How-can-I-prevent-a-new-Morph-from-being-stepped-tp2242459p2242466.html
Sent from the Squeak - Beginners mailing list archive at Nabble.com.

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30

4	April 2013
30	March 2013
11	February 2013
32	January 2013
10	December 2012
15	November 2012
9	October 2012
32	September 2012
36	August 2012
31	July 2012
47	June 2012
11	May 2012
46	April 2012
23	March 2012
21	February 2012
51	January 2012
50	December 2011
56	November 2011
37	October 2011
43	September 2011
24	August 2011
23	July 2011
68	June 2011
35	May 2011
135	April 2011
108	March 2011
35	February 2011
47	January 2011
85	December 2010
38	November 2010
36	October 2010
21	September 2010
27	August 2010
18	July 2010
36	June 2010
102	May 2010
149	April 2010
85	March 2010
90	February 2010
37	January 2010
81	December 2009
127	November 2009
46	October 2009
30	September 2009
77	August 2009
81	July 2009
68	June 2009
45	May 2009
86	April 2009
79	March 2009
91	February 2009
86	January 2009
88	December 2008
149	November 2008
254	October 2008
284	September 2008
179	August 2008
280	July 2008
129	June 2008
179	May 2008
168	April 2008
203	March 2008
220	February 2008
155	January 2008
122	December 2007
126	November 2007
99	October 2007
153	September 2007
203	August 2007
159	July 2007
126	June 2007
161	May 2007
173	April 2007
167	March 2007
144	February 2007
233	January 2007
129	December 2006
191	November 2006
173	October 2006
193	September 2006
280	August 2006
228	July 2006
146	June 2006
292	May 2006

Using Futures in a thread other than the Morphic Thread

Re: Using Futures in a thread other than the Morphic Thread

Re: Using Futures in a thread other than the Morphic Thread

Re: How do I diff two images?

Re: How do I diff two images?

Re: How do I diff two images?

Re: How do I diff two images?

How can I prevent a new Morph from being stepped?

Re: How can I prevent a new Morph from being stepped?

Re: How can I prevent a new Morph from being stepped?