Re: [Pharo-dev] [pharo-project/pharo-core] 32b2db: 60455

Just a note, since 60455 the following Athens no longer fails 30 seconds later... | view form1 form2| view := AthensSceneView new. form1 := UIThemeWatery new scrollbarThumbHorizontalMiddleForm. form2 := UIThemeWatery new scrollbarThumbVerticalMiddleForm. view scene: [:canvas | canvas

Re: [Pharo-dev] [pharo-project/pharo-core] 4a89b0: 60443

> On 16 Mar 2017, at 07:45, GitHub wrote: > > > > Log Message: > --- > 60443 > 19837 Epicea: integrate release 8.1.3 > https://pharo.fogbugz.com/f/cases/19837 > > http://files.pharo.org/image/60/60443.zip > > CHANGE LOG: - Log browser: * Display

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

+1 On Tue, 07 Mar 2017 14:58:33 +0100, Sven Van Caekenberghe wrote: Thank you, Andrei, for your continued efforts ! On 7 Mar 2017, at 14:47, denker wrote: Log Message: --- 60436 Moose http://files.pharo.org/image/60/60436.zip This

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

Thank you, Andrei, for your continued efforts ! > On 7 Mar 2017, at 14:47, denker wrote: > > >> Log Message: >> --- >> 60436 >> Moose >> >> http://files.pharo.org/image/60/60436.zip >> > > > This brings changes to the inspector, debugger and fast table

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

> Log Message: > --- > 60436 > Moose > > http://files.pharo.org/image/60/60436.zip > This brings changes to the inspector, debugger and fast table renderer for glamour. Detailed changes: - added support for refresh in the Inspector/Playground. The refresh uses the stepping

Re: [Pharo-dev] [pharo-project/pharo-core] bbbcab: 60434

catalog use a configuration that points to the baseline (with a github tag). so it is the same… and by the way this is the recommended way to release things maintained with git ;) Esteban > On 7 Mar 2017, at 13:02, Sven Van Caekenberghe wrote: > > Hmm, but that is different

Re: [Pharo-dev] [pharo-project/pharo-core] bbbcab: 60434

Hmm, but that is different than the one in the catalog ? Confusing. Best have only one that is really maintained. > On 7 Mar 2017, at 10:16, Pavel Krivanek wrote: > > Metacello new > smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo50'; > configuration:

Re: [Pharo-dev] [pharo-project/pharo-core] bbbcab: 60434

Metacello new smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo50'; configuration: #SublimishTheme; version: '1.0.0'; load 2017-03-07 10:06 GMT+01:00 Sven Van Caekenberghe : > > > On 7 Mar 2017, at 09:51, GitHub wrote: > > > > Log Message: > > ---

Re: [Pharo-dev] [pharo-project/pharo-core] bbbcab: 60434

> On 7 Mar 2017, at 09:51, GitHub wrote: > > Log Message: > --- > 60434 > 19801 Remove SublimishTheme > https://pharo.fogbugz.com/f/cases/19801 So where/how can this theme be loaded again, I really, really liked it.

Re: [Pharo-dev] [pharo-project/pharo-core] 986ba2: 60402

Ping me in the evening when you have time. I might have some time but I'm not 100% sure. Cheers, Andrei On Tue, Feb 21, 2017 at 7:47 AM, p...@highoctane.be wrote: > There are quite a few Themers + hard coded colors in GT. > > Maybe someone from the GT team can pair for an

Re: [Pharo-dev] [pharo-project/pharo-core] 986ba2: 60402

There are quite a few Themers + hard coded colors in GT. Maybe someone from the GT team can pair for an hour or two with me so that we can get this done. I can do this in the evening CET as I am pretty busy this week (managed to have Pharo a large part of my daily work now). Phil On Mon, Feb

Re: [Pharo-dev] [pharo-project/pharo-core] 69aea4: 60403

> > Log Message: > --- > 60403 > Moose > http://files.pharo.org/image/60/60403.zip > > This actually is a merge for GT… with: The version moves the inspector to FastTable. More precisely it moves the Raw presentation and the presentations for collections to FastTable. For that it

Re: [Pharo-dev] [pharo-project/pharo-core] 986ba2: 60402

Thanks. Not that it is a big deal, but the default background does not really match, but that might be taste as well. > On 20 Feb 2017, at 17:41, p...@highoctane.be wrote: > > I have fixed the spotter styling but need to get a 6.0 and move it there. > > > > On Mon, Feb 20, 2017 at 5:25 PM,

Re: [Pharo-dev] [pharo-project/pharo-core] fcd75f: 60386

> On 11 Feb 2017, at 09:48, GitHub wrote: > > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: fcd75f0830aa6925f2fee68011ae20fb30efee81 > >

Re: [Pharo-dev] [pharo-project/pharo-core] 16537e: 60373

> > Log Message: > --- > 60373 > Moose This is: This version addresses some bug fixes and synchronises those packages integrated using slices with the GToolkit repos. Changes: - case 19575 - case 19646 - case 19604 - case 19542 - case 19260 - case 19454 - FastTable/List/Tree

Re: [Pharo-dev] [pharo-project/pharo-core] cfba43: 60350

> > Log Message: > --- > 60350 > 19556 Glamour version 4.31 > https://pharo.fogbugz.com/f/cases/19556 > Changes: - fixes example GLMBasicExamples>>#morphWithCustomInteraction - adds example GLMBasicExamples>>#changingTabsInComposite - case 19505 Setting the selection using

Re: [Pharo-dev] [pharo-project/pharo-core] 458c6c: 60330

VM looks ok BTW. Really seems to be the update itself. > On 19 Dec 2016, at 21:00, Marcus Denker wrote: > > Hmm.. I think I will revert this update. > >> On 19 Dec 2016, at 16:36, Max Leske wrote: >> >> Confirmed on OS X 10.12.3 >> >>> On 19 Dec

Re: [Pharo-dev] [pharo-project/pharo-core] 458c6c: 60330

Hmm.. I think I will revert this update. > On 19 Dec 2016, at 16:36, Max Leske wrote: > > Confirmed on OS X 10.12.3 > >> On 19 Dec 2016, at 19:26, Marcus Denker wrote: >> >> The image seems to come up with a black screen… something went wrong. >>

Re: [Pharo-dev] [pharo-project/pharo-core] 458c6c: 60330

Confirmed on OS X 10.12.3 > On 19 Dec 2016, at 19:26, Marcus Denker wrote: > > The image seems to come up with a black screen… something went wrong. > > Can someone else check? > >> On 19 Dec 2016, at 14:21, GitHub wrote: >> >> Branch:

Re: [Pharo-dev] [pharo-project/pharo-core] 458c6c: 60330

The image seems to come up with a black screen… something went wrong. Can someone else check? > On 19 Dec 2016, at 14:21, GitHub wrote: > > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 458c6cef0678ceeedd886a7e8c952aa72ceddca0 >

Re: [Pharo-dev] [pharo-project/pharo-core] 48592d: 60274

> > Log Message: > --- > 60274 > Moose This is: 18884 Inspecting a large Bag crashes the Image 18224 Scrolling Spotter creates draw damage outside of its bounds

Re: [Pharo-dev] [pharo-project/pharo-core] 93c8ee: 60250

> > Log Message: > --- > 60250 > Moose > > http://files.pharo.org/image/60/60250.zip > > Changes: - case 19032 - case 19127 - fixed #name deprecation in Announcer>>#gtInspectorSubscriptionsIn: - debuggers uses keymaps for specifying shortcuts instead of characters - sync with

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

For those found of annotations I suggest # or since it's destinated to IDE/Tool Good idea. I will keep it in mind. Stef

Re: [Pharo-dev] [pharo-project/pharo-core] d17433: 60238

Ok I was confused and I checked everything has been well integrated. Le 24/9/16 à 18:42, stepharo a écrit : Apparently the changes are not in the image. I'm puzzled. Stef Le 24/9/16 à 18:05, GitHub a écrit : Branch: refs/heads/6.0 Home:

Re: [Pharo-dev] [pharo-project/pharo-core] d17433: 60238

May be there is a cache here. Could someone tell me if in the latest version Object>>yourself has a large method comment? Tx Le 24/9/16 à 18:42, stepharo a écrit : Apparently the changes are not in the image. I'm puzzled. Stef Le 24/9/16 à 18:05, GitHub a écrit : Branch:

Re: [Pharo-dev] [pharo-project/pharo-core] d17433: 60238

Apparently the changes are not in the image. I'm puzzled. Stef Le 24/9/16 à 18:05, GitHub a écrit : Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d174333406cc1ff2973a8ef75ce1cdedd8e89804

Re: [Pharo-dev] [pharo-project/pharo-core] d3c4dd: 60236

On improvements at a time at work! Excellent Le 23/9/16 à 09:25, Marcus Denker a écrit : 19124 enhance Deprecation to log sending method https://pharo.fogbugz.com/f/cases/19124 The result of this is that now the log on the CI now exactly tells us what to fix: (I will add issue

Re: [Pharo-dev] [pharo-project/pharo-core] d3c4dd: 60236

> On 23 Sep 2016, at 08:25, Marcus Denker wrote: > > >> >> 19124 enhance Deprecation to log sending method >> https://pharo.fogbugz.com/f/cases/19124 > > > The result of this is that now the log on the CI now exactly tells us what to > fix: > (I will add issue

Re: [Pharo-dev] [pharo-project/pharo-core] d87de4: 60237

> On 23 Sep 2016, at 11:34, Marcus Denker wrote: > > >> >> Log Message: >> --- >> 60237 >> Moose >> >> http://files.pharo.org/image/60/60237.zip >> >> > > This is: > > - case 19032 > - testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits was failing

Re: [Pharo-dev] [pharo-project/pharo-core] d87de4: 60237

> > Log Message: > --- > 60237 > Moose > > http://files.pharo.org/image/60/60237.zip > > This is: - case 19032 - testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits was failing due to #isLastInOwner - add manifest wit preUnload action in GTDebugger But: => 19032 seems to

Re: [Pharo-dev] [pharo-project/pharo-core] d3c4dd: 60236

Great addition! Doru > On Sep 23, 2016, at 8:25 AM, Marcus Denker wrote: > > >> >> 19124 enhance Deprecation to log sending method >> https://pharo.fogbugz.com/f/cases/19124 > > > The result of this is that now the log on the CI now exactly tells us what to

Re: [Pharo-dev] [pharo-project/pharo-core] d3c4dd: 60236

> > 19124 enhance Deprecation to log sending method > https://pharo.fogbugz.com/f/cases/19124 The result of this is that now the log on the CI now exactly tells us what to fix: (I will add issue tracker entries for each): *** Warning: Deprecation: The method GTSpotter>>isEmpty called

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Tudor Girba-2 wrote > Now, this is something cool, I think. Let’s investigate this further. One > issue is whether the Pragma class should be modified to take into account > the new semantics. > > Cheers, > Doru A major disadvantage is that in other Smalltalks supporting tags, block scoping

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Now, this is something cool, I think. Let’s investigate this further. One issue is whether the Pragma class should be modified to take into account the new semantics. Cheers, Doru > On Sep 20, 2016, at 10:41 PM, Nicolai Hess wrote: > > > > 2016-09-19 16:24

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

2016-09-19 16:24 GMT+02:00 Henrik Johansen : > > On 19 Sep 2016, at 4:03 , Henrik Johansen > wrote: > > > On 17 Sep 2016, at 4:17 , Ben Coman > wrote: > > On Sat, Sep 17, 2016 at 3:45 AM,

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

2016-09-19 19:14 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2016-09-19 17:08 GMT+02:00 Esteban Lorenzano : > >> >> On 19 Sep 2016, at 16:49, Nicolai Hess wrote: >> >> >> Am 19.09.2016 4:14 nachm. schrieb "Esteban Lorenzano"

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

2016-09-19 19:14 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2016-09-19 17:08 GMT+02:00 Esteban Lorenzano : > >> >> On 19 Sep 2016, at 16:49, Nicolai Hess wrote: >> >> >> Am 19.09.2016 4:14 nachm. schrieb "Esteban Lorenzano"

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

2016-09-19 17:08 GMT+02:00 Esteban Lorenzano : > > On 19 Sep 2016, at 16:49, Nicolai Hess wrote: > > > Am 19.09.2016 4:14 nachm. schrieb "Esteban Lorenzano" >: > > > > > >> On 16 Sep 2016, at 21:45, Nicolai Hess

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

> On 19 Sep 2016, at 16:49, Nicolai Hess wrote: > > > Am 19.09.2016 4:14 nachm. schrieb "Esteban Lorenzano" >: > > > > > >> On 16 Sep 2016, at 21:45, Nicolai Hess >>

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Am 19.09.2016 4:14 nachm. schrieb "Esteban Lorenzano" : > > >> On 16 Sep 2016, at 21:45, Nicolai Hess wrote: >> >> >> >> 2016-09-16 18:42 GMT+02:00 Eliot Miranda : >>> >>> Hi All, >>> >>> >>> >>> _,,,^..^,,,_ (phone) >>> > On

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

> On 19 Sep 2016, at 4:03 , Henrik Johansen > wrote: > >> >> On 17 Sep 2016, at 4:17 , Ben Coman > > wrote: >> >> On Sat, Sep 17, 2016 at 3:45 AM, Nicolai Hess >

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

> On 16 Sep 2016, at 21:45, Nicolai Hess wrote: > > > > 2016-09-16 18:42 GMT+02:00 Eliot Miranda >: > Hi All, > > > > _,,,^..^,,,_ (phone) > > On Sep 14, 2016, at 10:50 PM, Marcus Denker

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

> On 17 Sep 2016, at 4:17 , Ben Coman wrote: > > On Sat, Sep 17, 2016 at 3:45 AM, Nicolai Hess > wrote: >> >> >> 2016-09-16 18:42 GMT+02:00 Eliot Miranda : >>> >>> Hi All, >>> >>> >>>

Re: [Pharo-dev] [pharo-project/pharo-core] 4d8aa6: 60226

2016-09-15 22:11 GMT+02:00 stepharo >: This change break the miniimage. I will check with pavel. Stef This is now the second time the method SingleCodeCriticResultList>>#setTextModelForTransformationRule: vanished see case 19079

Re: [Pharo-dev] [pharo-project/pharo-core] 4d8aa6: 60226

2016-09-15 22:11 GMT+02:00 stepharo : > This change break the miniimage. I will check with pavel. > > Stef > > This is now the second time the method SingleCodeCriticResultList>>#setTextModelForTransformationRule: vanished see case 19079

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

On Sat, Sep 17, 2016 at 3:45 AM, Nicolai Hess wrote: > > > 2016-09-16 18:42 GMT+02:00 Eliot Miranda : >> >> Hi All, >> >> >> >> _,,,^..^,,,_ (phone) >> > On Sep 14, 2016, at 10:50 PM, Marcus Denker >> > wrote: >> > >> > >>

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

2016-09-16 18:42 GMT+02:00 Eliot Miranda : > Hi All, > > > > _,,,^..^,,,_ (phone) > > On Sep 14, 2016, at 10:50 PM, Marcus Denker > wrote: > > > > > >>> > >>> We can change it back and maybe add support for the reformatter to not > convert it to

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Hi All, _,,,^..^,,,_ (phone) > On Sep 14, 2016, at 10:50 PM, Marcus Denker wrote: > > >>> >>> We can change it back and maybe add support for the reformatter to not >>> convert it to the literal array #(3 #+ 4) . >> >> I do not know in fact this is why I asked :)

Re: [Pharo-dev] [pharo-project/pharo-core] 4d8aa6: 60226

error not related, build works well after restart -- Pavel 2016-09-15 22:11 GMT+02:00 stepharo : > This change break the miniimage. I will check with pavel. > > Stef > > > Le 15/9/16 à 22:05, GitHub a écrit : > >Branch: refs/heads/6.0 >>Home:

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

2016-09-16 8:54 GMT+02:00 stepharo : > > Furthermore, typical examples require more than one liners, and these >> should be factored out separately. >> > > I really like the one liners that you can find im some method comments, > like in Color class>>#wheel: > if you are new to

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Furthermore, typical examples require more than one liners, and these should be factored out separately. I really like the one liners that you can find im some method comments, like in Color class>>#wheel: if you are new to pharo and start exploring the system, it makes fun to see

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

So, until know, I didn't really know what pythondoctest is about. I first thought the "test" is about unit tests and thought our way how we can generate or jump from methods to the corresponding is better, but know I understand that it is about "perform regression testing by verifying that

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Hi, > On Sep 15, 2016, at 10:16 PM, Nicolai Hess wrote: > > > > 2016-09-15 8:12 GMT+02:00 Tudor Girba : > Hi, > > > On Sep 15, 2016, at 7:50 AM, Marcus Denker wrote: > > > > > >>> > >>> We can change it back and maybe add

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

2016-09-15 8:12 GMT+02:00 Tudor Girba : > Hi, > > > On Sep 15, 2016, at 7:50 AM, Marcus Denker > wrote: > > > > > >>> > >>> We can change it back and maybe add support for the reformatter to not > convert it to the literal array #(3 #+ 4) . > >> > >>

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

2016-09-14 21:24 GMT+02:00 stepharo : > > Hi nicolai >> >> Why we should not accept >> >> foo >> >> ^ self >> >> and be forced to put around '' >> >> foo >> < func: '(3+4)' res: 0 > >> ^ self >> >> I understand that we store literal but why you do not like it

Re: [Pharo-dev] [pharo-project/pharo-core] 4d8aa6: 60226

This change break the miniimage. I will check with pavel. Stef Le 15/9/16 à 22:05, GitHub a écrit : Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4d8aa66f6cb150f6aef66a9d807106bb89404cf5

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Hi, Given the current interest, I am raising the issue of GTExample again. I sent a while ago a thorough description of the current solution: http://gtoolkit.org/doc/Examples/examples.html The goal is to provide documentation for all methods and classes both by allowing simple examples (plain

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Would you highlight all string in all code as if it contained code? Or would you add this just for Pragmas? But even there, strings are string, not code. and then? you try and if it failed then in not code and you do not highlight it. KISS. No? I think we can conclude that pragmas are not a

Re: [Pharo-dev] [pharo-project/pharo-core] 770d9c: 60222

> > Log Message: > --- > 60222 > 19085 Integrate Epicea 8 > https://pharo.fogbugz.com/f/cases/19085 This is a big sync with Epicea, fixing and improving many things. Change log: - Pass on UI + search more consistent names (e.g. session -> log). - Replace "Session Browser" by

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Hi, > On Sep 15, 2016, at 7:50 AM, Marcus Denker wrote: > > >>> >>> We can change it back and maybe add support for the reformatter to not >>> convert it to the literal array #(3 #+ 4) . >> >> I do not know in fact this is why I asked :) >> Now may be my idea to use

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

>> >> We can change it back and maybe add support for the reformatter to not >> convert it to the literal array #(3 #+ 4) . > > I do not know in fact this is why I asked :) > Now may be my idea to use pragma to get something like pythondoctest is a bad > idea > but I really want to have

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Hi nicolai Why we should not accept foo ^ self and be forced to put around '' foo < func: '(3+4)' res: 0 > ^ self I understand that we store literal but why you do not like it :). First of all, the old compiler did not accept this.

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

Hi nicolai Why we should not accept foo ^ self and be forced to put around '' foo < func: '(3+4)' res: 0 > ^ self I understand that we store literal but why you do not like it :). Stef 60220 19086 do not allow expressions as pragma arguments

Re: [Pharo-dev] [pharo-project/pharo-core] d6bfc8: 60219

Hi, This update should fix the “load updates” menu. Thanks to Norbert who helped tracking that down. Marcus > On 13 Sep 2016, at 18:55, GitHub wrote: > > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit:

Re: [Pharo-dev] [pharo-project/pharo-core] e2d5dd: 60213

> > Log Message: > --- > 60213 > 19076 New assert extension to compare floats by closeTo > https://pharo.fogbugz.com/f/cases/19076 > > 19068 SUnit failed tests during command line or monkey run > https://pharo.fogbugz.com/f/cases/19068 > With these, we are down to 9

Re: [Pharo-dev] [pharo-project/pharo-core] 0e42ac: 60212

> On 12 Sep 2016, at 20:11, stepharo wrote: > > tx > > Should I reissue > > 19055 More iconNamed: cleaning >https://pharo.fogbugz.com/f/cases/19055 normally this should have been integrated. Marcus

Re: [Pharo-dev] [pharo-project/pharo-core] 0e42ac: 60212

tx Should I reissue 19055 More iconNamed: cleaning https://pharo.fogbugz.com/f/cases/19055 Stef Le 12/9/16 à 13:17, Marcus Denker a écrit : This should hopefully fix running the test on the slices for the CI (aka “the monkey”). Marcus On 12 Sep 2016, at 13:14, GitHub

Re: [Pharo-dev] [pharo-project/pharo-core] 0e42ac: 60212

This should hopefully fix running the test on the slices for the CI (aka “the monkey”). Marcus > On 12 Sep 2016, at 13:14, GitHub wrote: > > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit:

Re: [Pharo-dev] [pharo-project/pharo-core] c0db47: 60199

> > Log Message: > --- > 10025 MethodDictionary at:put: and #flushCache > https://pharo.fogbugz.com/f/cases/10025 > For this one we need to carefully check if there are bad side effects. it should work as now at:put: is the fall-back case and flushes by selector. (instead of

Re: [Pharo-dev] [pharo-project/pharo-core] e64121: 60202

Sean this is like that since years. Stef Le 4/9/16 à 20:06, Sean P. DeNigris a écrit : GitHub wrote 19001 Another pass to introduce iconNamed: and avoid Smalltalk ui icons https://pharo.fogbugz.com/f/cases/19001 This one surprised me. I thought we were trying to avoid extensions to

Re: [Pharo-dev] [pharo-project/pharo-core] e64121: 60202

GitHub wrote > 19001 Another pass to introduce iconNamed: and avoid Smalltalk ui icons > https://pharo.fogbugz.com/f/cases/19001 This one surprised me. I thought we were trying to avoid extensions to low-level classes when possible. How is icon retrieval a responsibility of

Re: [Pharo-dev] [pharo-project/pharo-core] 518075: 60194

> On 31 Aug 2016, at 11:29, GitHub wrote: > > > Log Message: > --- > 60194 > Moose > > http://files.pharo.org/image/60/60194.zip > > This update contains: - case 18965 (removed GTExample) - case 18596 Remove references from Glamour to Smalltalk

Re: [Pharo-dev] [pharo-project/pharo-core] e91f1f: 60171

Pay attention that it was on my todo to work on packaging Grid and I need to do a pass on the Spec version because I do not like the design. So I will probably change the Grid package. Then I not sure that the grid should be by default in Pharo. It was a personal project and I should

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

Le 5/8/16 à 05:28, Martin Dias a écrit : Hi Stef, good, I take note. I improved filters in the recent releases and will continue improving. Thanks Martin I have problems with the menu item names :) To me redo looks strange when I get a crash I want to import the changes not redo them. Then

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

Hi Stef, good, I take note. I improved filters in the recent releases and will continue improving. Martin On Wed, Aug 3, 2016 at 5:30 PM, stepharo wrote: > Thanks Martin. > > We missed yesterday: show only the latest version of every entities. :) > > > Setf > > > Le 3/8/16 à

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

Ben Coman wrote > Thanks for the follow up post of this change log Marcus. +1!! - Cheers, Sean -- View this message in context: http://forum.world.st/pharo-project-pharo-core-f57843-60163-tp4909296p4909676.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

Thanks for the follow up post of this change log Marcus. cheers -ben On Wed, Aug 3, 2016 at 5:23 PM, Marcus Denker wrote: > >> On 03 Aug 2016, at 11:07, GitHub wrote: >> >> >> Log Message: >> --- >> 60163 >> 18831 Integrate new Epicea

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

Thanks Martin. We missed yesterday: show only the latest version of every entities. :) Setf Le 3/8/16 à 11:23, Marcus Denker a écrit : On 03 Aug 2016, at 11:07, GitHub wrote: Log Message: --- 60163 18831 Integrate new Epicea version

Re: [Pharo-dev] [pharo-project/pharo-core] 94fcf4: 60165

Thanks for the follow up log message Marcus. cheers -ben On Wed, Aug 3, 2016 at 7:00 PM, Marcus Denker wrote: > >> On 03 Aug 2016, at 12:24, GitHub wrote: >> >> Branch: refs/heads/6.0 >> Home: https://github.com/pharo-project/pharo-core >>

Re: [Pharo-dev] [pharo-project/pharo-core] 94fcf4: 60165

> On 03 Aug 2016, at 12:24, GitHub wrote: > > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 94fcf44742b41d7898726b57a76edc70fb1d9aea > >

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

> On 03 Aug 2016, at 11:07, GitHub wrote: > > > Log Message: > --- > 60163 > 18831 Integrate new Epicea version > https://pharo.fogbugz.com/f/cases/18831 > ChangeLog for this: - Case 18813: Implement redo and undo of protocol addition and removal. -

Re: [Pharo-dev] [pharo-project/pharo-core] ac9f62: 60149

> On 13 Jul 2016, at 10:03, Marcus Denker wrote: > >> >> http://files.pharo.org/image/60/60149.zip >> >> > Strangely it did not build. Wasted already >1 hour on this… > Now it is there. Marcus

Re: [Pharo-dev] [pharo-project/pharo-core] ac9f62: 60149

> > http://files.pharo.org/image/60/60149.zip > > Strangely it did not build. Wasted already >1 hour on this… Marcus

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Do you think professional developers who use Pharo all day like crashes or hangs ? We are all the same here, we want a stable system. It is not certain that the catalog download is the problem. This specific feature that you think should only be enabled by those who want it (you call them

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

> On 08 Jul 2016, at 12:21, stepharo wrote: > > > > Le 8/7/16 à 11:44, Sven Van Caekenberghe a écrit : >> Do you think professional developers who use Pharo all day like crashes or >> hangs ? We are all the same here, we want a stable system. >> >> It is not certain that

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Le 8/7/16 à 11:44, Sven Van Caekenberghe a écrit : Do you think professional developers who use Pharo all day like crashes or hangs ? We are all the same here, we want a stable system. It is not certain that the catalog download is the problem. This specific feature that you think should

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Do you think professional developers who use Pharo all day like crashes or hangs ? We are all the same here, we want a stable system. It is not certain that the catalog download is the problem. This specific feature that you think should only be enabled by those who want it (you call them

Re: [Pharo-dev] [pharo-project/pharo-core] a813b2: 60138

Le 6/7/16 à 18:52, Marcus Denker a écrit : On 06 Jul 2016, at 18:16, stepharo wrote: I always found such kind of changes totally obscure and it would be nice to have a description. Fixes issues: - 18450 GT-Tools: "Do not use #ifNotNilDo:ifNil:, #ifNil:ifNotNilDo:,

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Again again and again: How many times do you see students having Pharo frozen because the internet connection in the classroom is fleaky. Apparently turning off these people is not an issue to you. Perfect but it is one for me. For your productivity boost why can't you click on one setting

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

I have to add here… solution is bad, because now projects are not shown EVEN if I activate it in settings :( > On 06 Jul 2016, at 12:28, Esteban Lorenzano wrote: > > yes, I do not agree either but is true there where problems. > but IMO this would be solved just by

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Hi Ben, On Wed, Jul 6, 2016 at 5:16 PM, Ben Coman wrote: > On Thu, Jul 7, 2016 at 2:19 AM, Sven Van Caekenberghe > wrote: > > I'll try once more to explain. > > > > You like the catalog, don't you ? It was your idea in the first place. > With this feature

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

On Thu, Jul 7, 2016 at 2:19 AM, Sven Van Caekenberghe wrote: > I'll try once more to explain. > > You like the catalog, don't you ? It was your idea in the first place. With > this feature you can just type XML, CSV, JSON or whatever and it will suggest > a couple of catalog

Re: [Pharo-dev] [pharo-project/pharo-core] a813b2: 60138

On Thu, Jul 7, 2016 at 12:52 AM, Marcus Denker wrote: > >> On 06 Jul 2016, at 18:16, stepharo wrote: >> >> I always found such kind of changes totally obscure and it would be nice to >> have a description. >> > > The point I took from Stef's question

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

+1 On Wed, Jul 6, 2016 at 8:19 PM, Sven Van Caekenberghe wrote: > I'll try once more to explain. > > You like the catalog, don't you ? It was your idea in the first place. > With this feature you can just type XML, CSV, JSON or whatever and it will > suggest a couple of catalog

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

I'll try once more to explain. You like the catalog, don't you ? It was your idea in the first place. With this feature you can just type XML, CSV, JSON or whatever and it will suggest a couple of catalog projects that you can install with just one click, no need to open any tool you don't

Re: [Pharo-dev] [pharo-project/pharo-core] a813b2: 60138

> On 06 Jul 2016, at 18:16, stepharo wrote: > > I always found such kind of changes totally obscure and it would be nice to > have a description. > Fixes issues: - 18450 GT-Tools: "Do not use #ifNotNilDo:ifNil:, #ifNil:ifNotNilDo:, #ifNotNilDo:" - 18453 GT-Tools: "do not

Re: [Pharo-dev] [pharo-project/pharo-core] a813b2: 60138

I always found such kind of changes totally obscure and it would be nice to have a description. Stef Le 6/7/16 à 11:29, GitHub a écrit : Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: a813b2cc8d72ea3442e7ab1e9be5856203ea4c3f

  1   2   3   4   5   >