Thanks Ben,
Thierry
2015-01-25 6:41 GMT+01:00 Ben Coman :
>
>
> On Mon, Jan 12, 2015 at 6:10 AM, Thierry Goubier <
> thierry.goub...@gmail.com> wrote:
>
>>
>>
>> 2015-01-11 20:42 GMT+01:00 David T. Lewis :
>>
>>> Thanks Ben,
>>>
>>>
>>> I copied ConfigurationOfOSProcess-ThierryGoubier.33 to the
On Mon, Jan 12, 2015 at 6:10 AM, Thierry Goubier
wrote:
>
>
> 2015-01-11 20:42 GMT+01:00 David T. Lewis :
>
>> Thanks Ben,
>>
>>
>> I copied ConfigurationOfOSProcess-ThierryGoubier.33 to the OSProcess
>> repository. An update to ConfigurationOfOSProcess will be needed to
>> get the latest version
Behavior basicNew basicNew.
Class basicNew basicNew.
No .log is generated
Applies to Pharo4 #40460 and Pharo 3.0 (Windows 8.1)
Cheers,
Hernán
Hi!
It would be great to have a good dark theme. There is a bit of theory behind
about how to choose a nice color schema. It would be _great_ that the crew
behind this effort have a look at it.
Here is a set of colors that works well for the dark theme. The code
highlighter may greatly benefit
Ben Coman wrote
> Anyone see a problem with removing
> that last condition?
Off the top of my head... Yes that doesn't seem like a good idea. You don't
want to find yourself inside Halt. You want to be in your code. Although the
change makes this weird exceptional-sounding case better, it looks li
Le 23/1/15 13:30, Aliaksei Syrel a écrit :
3) Fix spotter theming (currently ignores dark theme)
I added DarkTheme to spotter. Update to check and you can also take a
look how theming mechanism works in GT.
There is UITheme>>spotterWidgetThemer that returns themer object for
Spotter and
It is ok :)
We are concerned by such problems (and also frustrated).
Le 20/1/15 14:57, Pieter Nagel a écrit :
Sorry, wrong mailing list, will take this to pharo-users.
I have this little one physically on my desk :)
Le 21/1/15 17:43, Noury Bouraqadi a écrit :
See the adertisement I received :-)
Noury
Thanks Paul.
Stef
Le 21/1/15 02:36, Paul DeBruicker a écrit :
Stephan Eggermont wrote
Who is dealing with CI? The queue is still growing and nothing seems to
finish.
Stephan
Jenkins tells me there are only 4 jobs using any significant amount of
space:
- FileTree-Pharo30-dev,
- Fuel-Stable
-
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: d22e5ba6338767a899fbdeac270e35d8a1995d12
https://github.com/pharo-project/pharo-core/commit/d22e5ba6338767a899fbdeac270e35d8a1995d12
Author: Jenkins Build Server
Date: 2015-01-24 (Sat, 24 Jan 2015
Branch: refs/tags/40460
Home: https://github.com/pharo-project/pharo-core
I absolutely agree that incremental is the way to go, I am slow doer anyway
;)
On Sat, Jan 24, 2015 at 9:26 PM, stepharo wrote:
>
> Le 19/1/15 22:21, kilon alios a écrit :
>
> Ok then I think the best way to do this is to start this in my own github
> account then give you guys the link , review
Le 19/1/15 22:21, kilon alios a écrit :
Ok then I think the best way to do this is to start this in my own
github account then give you guys the link , review the documentation
and if you find satisfying add it to SquareBracketAssociates via
forking it, if not I can still continue it with my g
I've found a fix for something that has annoyed me for a long time - but I
can't determine what it might break.
1. In Workspace I evaluate the following
Halt enableHaltOnce.
a := 1.
self halt.
b := 2.
self haltOnce.
c := 3.
Transcript show: a + b + c.
2. In the debugg
On Sat, Jan 24, 2015 at 9:47 PM, Ben Coman wrote:
> How about doing it as a post load script like this (tested on my local
> package-cache)...
>
> oldPackageName := 'ShoutTests'.
> newPackageName := 'Shout-Tests'.
> repository := MCRepository allSubInstances detect: [ :repo | repo location
> =
>
How about doing it as a post load script like this (tested on my local
package-cache)...
oldPackageName := 'ShoutTests'.
newPackageName := 'Shout-Tests'.
repository := MCRepository allSubInstances detect: [ :repo | repo location
=
'/Users/ben/Library/Application Support/Pharo/package-cache' ].
" '
> On 24 Jan 2015, at 11:24, Marcus Denker wrote:
>
> Hi,
>
> One of the power of slots is the concept of Virtual Slots that do not have an
> ivar to store their state.
> But of course, some uses fo this concept want to store state in the object.
> (e.g. imagine a property slot, all proper slot
Hi,
One of the power of slots is the concept of Virtual Slots that do not have an
ivar to store their state.
But of course, some uses fo this concept want to store state in the object.
(e.g. imagine a property slot, all proper slots of the object would store into
a property dictionary).
The ide
>>
>> This is now in 40457
>>
>> #isSpecial is fixed, too.
>>
>> This means that you can subclass AbstractInstanceVariableSlot and just
>> override #read and #write:to: and it should work.
>>
> Hmm… maybe IndexedSlot would be a better name…? I do not like
> AbstractSomethings. And it actuall
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 31f0fda864bb103a8d7fd8937b8ae24f927fb035
https://github.com/pharo-project/pharo-core/commit/31f0fda864bb103a8d7fd8937b8ae24f927fb035
Author: Jenkins Build Server
Date: 2015-01-24 (Sat, 24 Jan 2015
Branch: refs/tags/40459
Home: https://github.com/pharo-project/pharo-core
21 matches
Mail list logo
