On Jul 25, 2013, at 11:31 PM, Christophe Demarey
wrote:
> Hello,
>
> This release breaks the right click on the mouse. The event is not handled
> anymore.
> I checked #30295 => ok, images >= #30296 ko
>
Yes, I saw that, too. It seems to be side effect of integrating
10448 Smalltalk os shou
Hello,
This release breaks the right click on the mouse. The event is not handled
anymore.
I checked #30295 => ok, images >= #30296 ko
Christophe.
Le 24 juil. 2013 à 14:46, Marcus Denker a écrit :
> 30296
> -
>
> 10448 Smalltalk os should use instance of OSPlatform
> https://pharo.f
Hi pharoers,
I have always the same problem, to reproduce it, you can use the following
script.
If you execute it in a clean image and a clean vm, it returns 0, then rerun the
last line, it returns 1.
If you execute it in a one-click image, it returns 0.
I don't understand this difference.
Jann
On 24 July 2013 18:38, Chris Cunningham wrote:
> Doesn't just #printString do this? It escapes single strings into doubles -
> should do what you want if it is definitely a string.
> -Chris
>
yes, printString does exactly what you want.
>
> On Wed, Jul 24, 2013 at 8:34 AM, Mariano Martinez Peck
Thanks Chris, the #printString was indeed a good idea :)
On Wed, Jul 24, 2013 at 1:38 PM, Chris Cunningham
wrote:
> Doesn't just #printString do this? It escapes single strings into doubles
> - should do what you want if it is definitely a string.
> -Chris
>
>
> On Wed, Jul 24, 2013 at 8:34 AM,
On 25 July 2013 15:32, Stéphane Ducasse wrote:
> Igor
> Laurent will probably want to get you around next week :)
>
Sure, i can help with understanding how to use FFI.
> Stef
>
> I will have one full week dedicated to Pharo, now I must decide what to
> do. One fun thing would be to write
Ah yeah it is due to gmail quote that hid it. sorry.
2013/7/25 Stéphane Ducasse
> :)
>
>
> On Jul 25, 2013, at 1:20 PM, Guillermo Polito
> wrote:
>
>
>
>
> On Thu, Jul 25, 2013 at 1:17 PM, Camille Teruel
> wrote:
>
>>
>> On 25 juil. 2013, at 13:12, Clément Bera wrote:
>>
>> Perhaps you should
Igor
Laurent will probably want to get you around next week :)
Stef
I will have one full week dedicated to Pharo, now I must decide what to
do. One fun thing would be to write a X11 window manager (based on
TilingWindowManager), so I could run Emacs, shells and all stuff in Pharo,
> In Metacello there are more than one way to "visit specs":
>
> - raw specs
> - merged specs
> - specs by section
> - resolved specs
> - there are more
>
> If you are reasoning about the packages visible for a particular combination
> of attributes (#common, #pharo, etc.) then you are inte
:)
On Jul 25, 2013, at 1:20 PM, Guillermo Polito wrote:
>
>
>
> On Thu, Jul 25, 2013 at 1:17 PM, Camille Teruel
> wrote:
>
> On 25 juil. 2013, at 13:12, Clément Bera wrote:
>
>> Perhaps you should add some value message so that the assertions are
>> actually run, shouldn't you ?
>
> I
On 25 July 2013 14:14, laurent laffont wrote:
>
>>>
>>> I will have one full week dedicated to Pharo, now I must decide what to
>>> do. One fun thing would be to write a X11 window manager (based on
>>> TilingWindowManager), so I could run Emacs, shells and all stuff in Pharo,
>>> even Pharo in Ph
Stef,
In Metacello there are more than one way to "visit specs":
- raw specs
- merged specs
- specs by section
- resolved specs
- there are more
If you are reasoning about the packages visible for a particular combination of
attributes (#common, #pharo, etc.) then you are interested i
>
>> I will have one full week dedicated to Pharo, now I must decide what to
>> do. One fun thing would be to write a X11 window manager (based on
>> TilingWindowManager), so I could run Emacs, shells and all stuff in Pharo,
>> even Pharo in Pharo :)
>>
>
> You mean implementing a native interface
That's going to make working out Metacello details a bit difficult:(
Dale
- Original Message -
| From: "Tudor Girba"
| To: "Pharo Development List"
| Sent: Thursday, July 25, 2013 1:08:30 AM
| Subject: Re: [Pharo-dev] [Pharo-users] [Moose-dev] Re: Re: [ann]
| snapshotcello
| Unfortu
On Thu, Jul 25, 2013 at 1:54 PM, laurent laffont
wrote:
> Hi,
>
> I will have one full week dedicated to Pharo, now I must decide what to
> do. One fun thing would be to write a X11 window manager (based on
> TilingWindowManager), so I could run Emacs, shells and all stuff in Pharo,
> even Pharo i
Hi,
I will have one full week dedicated to Pharo, now I must decide what to do.
One fun thing would be to write a X11 window manager (based on
TilingWindowManager), so I could run Emacs, shells and all stuff in Pharo,
even Pharo in Pharo :)
I've tried some months ago to translate this example
htt
On Thu, Jul 25, 2013 at 1:17 PM, Camille Teruel wrote:
>
> On 25 juil. 2013, at 13:12, Clément Bera wrote:
>
> Perhaps you should add some value message so that the assertions are
> actually run, shouldn't you ?
>
>
> I always felt that e-mails lack an unsend command :D
>
Or gmail quotes should w
On 25 juil. 2013, at 13:12, Clément Bera wrote:
> Perhaps you should add some value message so that the assertions are actually
> run, shouldn't you ?
I always felt that e-mails lack an unsend command :D
> 2013/7/25 Stéphane Ducasse
> For the people following I added a test to show the homeCo
Perhaps you should add some value message so that the assertions are
actually run, shouldn't you ?
2013/7/25 Stéphane Ducasse
> For the people following I added a test to show the homeContext of a block
>
>
> | homeContext b1 |
> homeContext := thisContext.
> b1 := [| b2 |
> self asse
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 332e8c4ead04b4a592097e915c355841cc6a9023
https://github.com/pharo-project/pharo-core/commit/332e8c4ead04b4a592097e915c355841cc6a9023
Author: Jenkins Build Server
Date: 2013-07-25 (Thu, 25 Jul 2013
Branch: refs/tags/30298
Home: https://github.com/pharo-project/pharo-core
Branch: refs/tags/30299
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: e8dc17cb1e2f94c6f9802d25be5f5d539505777f
https://github.com/pharo-project/pharo-core/commit/e8dc17cb1e2f94c6f9802d25be5f5d539505777f
Author: Jenkins Build Server
Date: 2013-07-25 (Thu, 25 Jul 2013
30299
-
11239 ContextPart>>errorReportOn: uses deprecated methods
https://pharo.fogbugz.com/f/cases/11239
11232 Fuel out stack menu entry is missing
https://pharo.fogbugz.com/f/cases/11232
Diff information:
http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger
For the people following I added a test to show the homeContext of a block
| homeContext b1 |
homeContext := thisContext.
b1 := [| b2 |
self assert: thisContext closure == b1.
self assert: b1 outerContext == homeContext.
self assert: b1 home = homeContext.
This would be so cool :).
Doru
On Thu, Jul 25, 2013 at 8:47 AM, Stéphane Ducasse wrote:
> Hi dale
>
> do you plan to write a visitor on metacello spec?
>
> Stef
>
> On Jul 24, 2013, at 9:38 PM, Dale K. Henrichs <
> dale.henri...@gemtalksystems.com> wrote:
>
> > Doru,
> >
> > Are you going to b
Unfortunately, I will not be able to join :(
Doru
On Wed, Jul 24, 2013 at 9:38 PM, Dale K. Henrichs <
dale.henri...@gemtalksystems.com> wrote:
> Doru,
>
> Are you going to be at ESUG this year?
>
> I think there are some features of the Metacello Preview that can be of a
> great help to your Mo
30298
-
11236 Proceed action does not close the refresh processes
https://pharo.fogbugz.com/f/cases/11236
11235 The new debugger is missing some utilities methods
https://pharo.fogbugz.com/f/cases/11235
11231 Predebugger window too small & not skipped to full
I wrote some class comments, but somehow it cannot be merged in Pharo in a
normal way.
Warning: 'You should not change blockclosure' or something like that
I will check with Marcus later.
2013/7/25 Stéphane Ducasse
> Thanks.
> Ok This is clear now - the outerContext is like my scheme environm
We should add a test and fix that issue.
> From: "Pharo Issue Tracker"
> Subject: [Pharo-bugtracker] FogBugz (Case [Issue]11237) Collection - #sorted
> no longer copies Arrays
> Date: July 25, 2013 12:14:23 AM GMT+02:00
> To: "pharo-bugtrac...@lists.gforge.inria.fr"
>
>
> A FogBugz case was
30 matches
Mail list logo
