Date: 2009-08-05 03:55:59 GMT (4 hours and 2 minutes ago)
Hi All,
in ParseNodeprintCommentOn: there is the most perplexing
destructive modification of a comment on printing:
printCommentOn: aStream indent: indent
| thisComment |
self comment == nil ifTrue: [^ self].
On 05 Aug 2009, at 09:37, Stéphane Ducasse wrote:
Can you open a bug entry report?
I just did that right now. I wanted to drill down in the problem a bit
further before entering the ticket.
The additional info is in the bug report (1038).
It seems the DNU is handled by Seaside code since it
Hi there,
attached is a blinking cursor implementation for Pharo
ported/inspired from/by the Morphic Text improvements done by Andreas [1].
The more general question I have is:
is it legally possible to port and include stuff like this from the
new squeak trunk into pharo? Andreas is not
Thanks Mariano,
The following code works:
UIManager default
chooseFileMatching: #('mse')
label: 'Import model from MSE file.'.
The problem is indeed that you have to pass a valid set of extensions,
so * is not allowed. Anyway, it works for the moment but
I have the impression that in case you want to have to run your vm on
system not having the freeType plugin.
Relying less on C code is a nice option (especially when a guy did all
the work).
Often people are telling us that we should not do everything in
Smalltalk but there this is a nice
On Aug 5, 2009, at 10:24 AM, Torsten Bergmann wrote:
Hi there,
attached is a blinking cursor implementation for Pharo
ported/inspired from/by the Morphic Text improvements done by
Andreas [1].
cool!
The more general question I have is:
is it legally possible to port and include stuff
2009/8/5 Torsten Bergmann asta...@gmx.de:
Hi there,
attached is a blinking cursor implementation for Pharo
ported/inspired from/by the Morphic Text improvements done by Andreas [1].
The more general question I have is:
is it legally possible to port and include stuff like this from the
new
Hi adrian
I got some problems when merging the latest polymorph (_ fixes).
I got conflicts when there should be none. I simply got revision
changed.
Did you already experience that?
Stef
___
Pharo-project mailing list
I managed to trace the problem to the following:
After rendering the stack trace of the DNU in the browser, the
EscapeContinuation terminates the thisContext and unwinds the stack.
After this, the execution resumes in the #withEscapeContinuation:
method, essentially ending up executing
Hi again,
On the same topic, what is the invocation to open a dialogue that
allows for saving files?
Cheers,
Doru
On 5 Aug 2009, at 10:26, Tudor Girba wrote:
Thanks Mariano,
The following code works:
UIManager default
chooseFileMatching: #('mse')
label:
On Wed, Aug 5, 2009 at 11:18 AM, Stéphane
Ducassestephane.duca...@inria.fr wrote:
Hi adrian
I got some problems when merging the latest polymorph (_ fixes).
I got conflicts when there should be none. I simply got revision
changed.
Did you already experience that?
You may want to try
Ok I will try
What I did was to click on all the use incoming version and at the end
(at 5 left items)
it just looped for ever. I had the redo the use incoming version but
the number of conflicts
stayed the same for ever 5.
So far I could merge Polymorph-Widgets-gvc.70 but not Polymorph-
Will do!
Submitted Issue 1041 as a simple case where an (unneccessary)
primitive failure happens.
If a similar slowdown is experienced in f.ex. the fallback bitblt code
used in font rendering, it might be worth investigating what exactly
causes it to fail.
Fallback code isn't always a good
2009/8/5 Torsten Bergmann asta...@gmx.de
Hi there,
attached is a blinking cursor implementation for Pharo
ported/inspired from/by the Morphic Text improvements done by Andreas [1].
Hi! I just tested and seems nice! The only weird thing I found is that the
cursor still blinks when moving it.
10406
---
Issue 1040: Polymorph
- Keybaord navigation improvements to PopupChoiceDialogWindow. Enter
will confirm valid selection and close, left/right arrows will switch
columns (regardless of filter).
- fixing most _ (not for widget because of merging problems)
I tested in latest (pharo1.0beta-10401web09.07.5) and noticed that now pharo
uses the same debugger for breakpoints and for debugits, which is nice.
The bug I mentioned seems to be in OTDebugger, which has been removed from
the image, so it could be said it's fixed.
Now, this debugger has ooother
Hi guys
MethodContext allInstances size seems to loop forever or even to
crash my VM.
Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On 05.08.2009, at 11:30, Stéphane Ducasse wrote:
Hi guys
MethodContext allInstances size seems to loop forever or even to
crash my VM.
This might be because new instances are created while executing the
expression.
Normally contexts are recycled. But the list of contexts available for
Yes stupid me.
Now in Squeak or Cuis the equivalent of MethodContext was not crashing.
So there is something strange.
In any case may be then we should pay attention to
allInstancesDo: and friends
Stef
On Aug 5, 2009, at 5:53 PM, Marcus Denker wrote:
On 05.08.2009, at 11:30,
Yes, see the other mail. The reason is that the allocation of contexts
in case of blocks happens now at #value, whereas it used to be just
done
at the definiton point (#blockCopy).
So nothing to worry about.
still it crashes my image when doing MethodContext allInstances
may be a
Stef and Javier,
I am maintaining the OTDebugger and have been addressing problems as they are
reported. When you originally reported the bug I (mistakenly) thought you had
been using the old debugger since that is the debugger shipped with the 1.0beta.
I'm somewhat hammered at the moment, but
Hi folks. PLEASE a good soul of you update the linux VM from webpage?
http://gforge.inria.fr/frs/download.php/22421/pharo-vm-0.15.1b-linux.zip
Every single day there are folks asking in Pharo IRC channel how to use it.
It is not intuitive and they are lost. No matter what you say, the reality
is
the problem now is that
allInstancesDo: aBlock
Evaluate the argument, aBlock, for each of the current instances of
the
receiver.
Because aBlock might change the class of inst (for example, using
become:),
it is essential to compute next before aBlock
2009/8/5 Marcus Denker den...@acm.org:
On 05.08.2009, at 12:30, Igor Stasenko wrote:
2009/8/5 Marcus Denker den...@acm.org:
On 05.08.2009, at 12:00, Stéphane Ducasse wrote:
I did that in pharo 211 and it worked.
Yes, that was before closures.
MethodContext allInstances size 2309
On 05.08.2009, at 13:18, Igor Stasenko wrote:
Yes, and the real solution of course is to change the VM to allocate
less
contexts and use the C-stack instead...
hmm, doesn't that breaks the smalltalk introspection capabilities,
since then you can't see all the
context objects which is used
On 05.08.2009, at 14:54, Mariano Martinez Peck wrote:
Hi folks. PLEASE a good soul of you update the linux VM from webpage?
http://gforge.inria.fr/frs/download.php/22421/pharo-vm-0.15.1b-linux.zip
Every single day there are folks asking in Pharo IRC channel how to
use it. It is not
+1 to changing this...
On Wed, Aug 5, 2009 at 4:59 AM, Stéphane Ducasse
stephane.duca...@inria.frwrote:
Date: 2009-08-05 03:55:59 GMT (4 hours and 2 minutes ago)
Hi All,
in ParseNodeprintCommentOn: there is the most perplexing
destructive modification of a comment on printing:
Hi,
I have a Morphic newbie question.
I have a list morph:
PluggableListMorph
on: listModel
list: #displayedItems
selected: #selection
changeSelected: #selection:
I now would like it to update when
28 matches
Mail list logo
