that is pretty new, so we didn't fix this issue then :/ (or more probably, we
didn't fix all users).
=> can you open an issue with a description on how to reproduce it?
On 2013-08-26, at 22:52, Igor Stasenko wrote:
> (oops.. pressed send before finishing mail)
>
> Pharo3.0
> Latest update: #3
(oops.. pressed send before finishing mail)
Pharo3.0
Latest update: #30335
.. so it just 10 days old
On 26 August 2013 22:51, Igor Stasenko wrote:
> ah, ok.. maybe i use outdated image?
>
>
>
> On 26 August 2013 22:41, Camillo Bruni wrote:
>
>> I think we agreed that
>> - #inspect: returns t
ah, ok.. maybe i use outdated image?
On 26 August 2013 22:41, Camillo Bruni wrote:
> I think we agreed that
> - #inspect: returns the inspected value
> - #inspector: returns the inspector for the given value
>
> I thought we fixed exactly the bug you experience since Ben complained a
> lot abo
NewValueHolder>>contents: anObject
| oldValue |
lock ifTrue: [ ^ self ].
lock := true.
oldValue := contents.
contents := anObject.
[ self contentsChanged: oldValue ] ensure: [ lock := false ].
^ contents
it is really interesting.. it appears you cannot change the cont
I think we agreed that
- #inspect: returns the inspected value
- #inspector: returns the inspector for the given value
I thought we fixed exactly the bug you experience since Ben complained a lot
about it ;)
On 2013-08-26, at 22:32, Igor Stasenko wrote:
> ... or another reason to answer the in
As a side note: In Dolphin it returns the inspector :)
Esteban A. Maringolo
2013/8/26 Igor Stasenko :
>
>
>
> On 26 August 2013 22:32, Igor Stasenko wrote:
>>
>> ... or another reason to answer the inspector window..
>> because right now it is badly broken:
>>
>> EyeInspector class>>inspect: an
... or another reason to answer the inspector window..
because right now it is badly broken:
EyeInspector class>>inspect: anObject
InspectorWrapper openInspector: (self inspector: anObject).
^ anObject
but:
Morph>>inspectInMorphic: evt
evt hand attachMorph: ((Smalltalk tools inspect:
On 26 August 2013 22:32, Igor Stasenko wrote:
> ... or another reason to answer the inspector window..
> because right now it is badly broken:
>
> EyeInspector class>>inspect: anObject
> InspectorWrapper openInspector: (self inspector: anObject).
> ^ anObject
>
> but:
>
> Morph>>inspectIn
### Here's what I've been up to since the last WhatsUp:
- Made a working web app stack and started an application that uses it.
Kind of works.
- Asked around for the Pharo advantage
- Pushed Pharo technology for a project and associated funding. So far, so
good
- Got DBXTalk working with MySQL on
On 19 Aug 2013, at 07:00, seas...@rmod.lille.inria.fr wrote:
> Hi! We're sending this automatic email twice a month, to give the community
> an opportunity to easily know what's happening and to coordinate efforts.
> Just answer informally, and feel free to spawn discussions thereafter!
>
> #
A workaround could be that when a tab is selected, it set an instance variable
with the correct value.
This way , you can always do something like
myCanvas generates.
where myCanvas is set by the tab.
And in addition, you do not have to use a switch case :)
Ben
On Aug 26, 2013, at 3:58 PM, Er
On Mon, Aug 26, 2013 at 4:14 PM, Camillo Bruni wrote:
> I'll do a pass, since I burnt my fingers already on that code right before
> the 2.0 release :)
I saw you just reviewed the code. Thank you. Now, this code is ready
for inclusion.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"
On 26 août 2013, at 15:04, Igor Stasenko wrote:
>
>
>
> On 26 August 2013 14:34, Camille Teruel wrote:
>
> On 26 août 2013, at 13:31, Igor Stasenko wrote:
>
>> the intent was to replace
>> Smalltalk at:
>> Smalltalk globals at:
>>
>> idioms with shorter one, and get rid of referencing Smal
I'll do a pass, since I burnt my fingers already on that code right before the
2.0 release :)
On 2013-08-26, at 16:12, Damien Cassou wrote:
> Could someone please review this change?
>
> Extract the logic that opens the .sources and .changes files
>
> This logic is currently in the SmalltalkI
Could someone please review this change?
Extract the logic that opens the .sources and .changes files
This logic is currently in the SmalltalkImage class. The code is hard
to read and enhance. Extracting the logic to its own class will fix
these issues.
https://pharo.fogbugz.com/default.asp?1142
On 26 August 2013 13:34, Camille Teruel wrote:
>
> On 26 août 2013, at 13:31, Igor Stasenko wrote:
>
> the intent was to replace
> Smalltalk at:
> Smalltalk globals at:
>
> idioms with shorter one, and get rid of referencing Smalltalk global.
>
> The are not for solving future problems with introd
30344
-
6821 Inconsistent String>>asDate behaviour
https://pharo.fogbugz.com/f/cases/6821
11446 recategorize compareWith:ifLesser:ifEqual:ifGreater:
https://pharo.fogbugz.com/f/cases/11446
11431 #sorted: is broken for some collections
https://pharo.fog
On Aug 26, 2013, at 3:54 PM, p...@highoctane.be wrote:
> ... and Smalltalk should be renamed into Pharo anyway.
>
> :-p
:)
Camillo already wants systems.
Stef
https://pharo.fogbugz.com/f/cases/10583/Use-System-instead-of-Smalltalk-to-access-globals
On 2013-08-26, at 15:54, "p...@highoctane.be" wrote:
> ... and Smalltalk should be renamed into Pharo anyway.
>
> :-p
>
> Phil
>
>
>
> On Monday, August 26, 2013, Igor Stasenko wrote:
>>
>>
>>
>> O
Hi,
I'm using TabManager and i would like to know which tab is active. I didn't
found any methods for that.
Any clue ?
In UIPainter, i will use it to know which tab canvas i have to generate.
Thanks :)
--
Best regards,
Douaille Erwan
... and Smalltalk should be renamed into Pharo anyway.
:-p
Phil
On Monday, August 26, 2013, Igor Stasenko wrote:
>
>
>
> On 26 August 2013 14:34, Camille Teruel wrote:
>>
>> On 26 août 2013, at 13:31, Igor Stasenko wrote:
>>
>> the intent was to replace
>> Smalltalk at:
>> Smalltalk globals
On 26 August 2013 14:34, Camille Teruel wrote:
>
> On 26 août 2013, at 13:31, Igor Stasenko wrote:
>
> the intent was to replace
> Smalltalk at:
> Smalltalk globals at:
>
> idioms with shorter one, and get rid of referencing Smalltalk global.
>
> The are not for solving future problems with intro
On 26 août 2013, at 13:31, Igor Stasenko wrote:
> the intent was to replace
> Smalltalk at:
> Smalltalk globals at:
>
> idioms with shorter one, and get rid of referencing Smalltalk global.
> The are not for solving future problems with introduction of environments.
We want to get rid of Smallt
thanks :)
On 2013-08-26, at 13:42, Marcus Denker wrote:
> 30343
> -
>
> 11447 Improve Chronology
> https://pharo.fogbugz.com/f/cases/11447
>
> 11456 RBLiteralValueNode does not Understand shortPrintOn:
> https://pharo.fogbugz.com/f/cases/11456
>
>
> Diff information:
>
30343
-
11447 Improve Chronology
https://pharo.fogbugz.com/f/cases/11447
11456 RBLiteralValueNode does not Understand shortPrintOn:
https://pharo.fogbugz.com/f/cases/11456
Diff information:
http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1219.diff
ht
the intent was to replace
Smalltalk at:
Smalltalk globals at:
idioms with shorter one, and get rid of referencing Smalltalk global.
The are not for solving future problems with introduction of environments.
And even if you introduce them, i still think you need a way to refer to
globals (they are
On 26 août 2013, at 10:56, Esteban Lorenzano wrote:
>
> On Aug 25, 2013, at 9:40 AM, Camille Teruel wrote:
>
>>
>> On 24 août 2013, at 19:20, Camillo Bruni wrote:
>>
>>> We have now:
>>>
>>> String >> #asClass
>>> String >> #asClassIfAbsent:
>>> String >> #asClassIfPresent:
>>
>> I don't u
>
>
> It works the same way as the dictionary protocol with #at:
> `#adsfasdf asClass` will signal an error, hence for compatibility you have
> the *IfAbsent: protocols. Otherwise you simply cannot replace all the users
> of `Smalltalk at:` and `Smalltalk globals at:` which is the long term goa
On 2013-08-26, at 11:46, Norbert Hartl wrote:
>
> Am 26.08.2013 um 10:56 schrieb Esteban Lorenzano :
>
>>
>> On Aug 25, 2013, at 9:40 AM, Camille Teruel wrote:
>>
>>>
>>> On 24 août 2013, at 19:20, Camillo Bruni wrote:
>>>
We have now:
String >> #asClass
String >> #as
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/435/
1 regressions found.
Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/435/
1 regressions found.
Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/435/
1 regressions found.
Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits
Am 26.08.2013 um 10:56 schrieb Esteban Lorenzano :
>
> On Aug 25, 2013, at 9:40 AM, Camille Teruel wrote:
>
>>
>> On 24 août 2013, at 19:20, Camillo Bruni wrote:
>>
>>> We have now:
>>>
>>> String >> #asClass
>>> String >> #asClassIfAbsent:
>>> String >> #asClassIfPresent:
>>
>> I don't un
On Mon, Aug 26, 2013 at 11:26 AM, Esteban Lorenzano wrote:
> I do not see why
because it means we can override #asClass: in each class and do
whatever we want.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthu
I do not see why
On Aug 26, 2013, at 11:14 AM, Damien Cassou wrote:
> On Mon, Aug 26, 2013 at 10:56 AM, Esteban Lorenzano
> wrote:
>> this was already discussed. With #asClass and relatives what you have is a
>> better abstraction jut because you are decoupled of "Smalltalk globals", it
>> i
30342
-
11421 Update Athens from config
https://pharo.fogbugz.com/f/cases/11421
Diff information:
http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-Text-MarcusDenker.7.diff
http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-Morphic-MarcusDenker.21.diff
http://smalltalkhub.com/m
On Mon, Aug 26, 2013 at 10:56 AM, Esteban Lorenzano wrote:
> this was already discussed. With #asClass and relatives what you have is a
> better abstraction jut because you are decoupled of "Smalltalk globals", it
> is not a big win now, but it open doors to better designs with environments,
>
On Aug 25, 2013, at 9:40 AM, Camille Teruel wrote:
>
> On 24 août 2013, at 19:20, Camillo Bruni wrote:
>
>> We have now:
>>
>> String >> #asClass
>> String >> #asClassIfAbsent:
>> String >> #asClassIfPresent:
>
> I don't understand why we need this new way.
> Is it just to avoid calling 'Sma
30341
-
11425 Improve assert description of
#testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses
https://pharo.fogbugz.com/f/cases/11425
11424 Add #methods accessor to RBBrowserEnvironment
https://pharo.fogbugz.com/f/cases/11424
10481 Cleanup method cat
39 matches
Mail list logo
