Re: [Pharo-dev] Process>>restart

[Ben Coman]

On Thu, Feb 25, 2016 at 3:06 AM, Eliot Miranda  wrote:
>
>
> On Wed, Feb 24, 2016 at 7:23 AM, Ben Coman  wrote:
>>
>> Just sharing a passing thought so I don't forget it before I have time
>> to think more deeply on it.
>>
>> Several parts of Pharo (like SHTextStyler) are designed to have a
>> background process running, and when new input arrives that process is
>> killed so another can be immediately started - and sometimes we seem
>> to end up with large amounts of zombie processes.
>>
>> As I poke around Process>>terminate, I wonder if a different approach
>> would be to have a Process>>restart.  I see there is Context>>restart.
>>
>> The starting the background process might look like...
>>
>> stylingProcess := [ [ "do stuff with nextData". self suspend ]
>> repeat ] forkAt: 30.
>>
>> and the code in the main morphic priority 40 thread might look like...
>>
>>sylingProcess suspend.
>>nextData := 'blah'.
>>sylingProcess restart.
>
>
> Hi Ben, so I'm assuming restart differs from resume.  Am I right in thinking
> it cuts back the process to the "start"?  Is the start the block from which
> the process was spawned, the argument to fork or forkAt:?

Thats right.  Essentially like Exception>>retry, to do something like this...

restart := false.
workAvailable := Semaphore new.
process :=
[   [  Transcript crShow: 'At the start'.
work := 0.
[   work := work + 1.
Transcript crShow: 'working on ' , work printString.
1 second wait.
work>8 ifTrue:
[   [Transcript crShow: 'Work complete.'] fork.
workAvailable wait.
restart := true.
].
restart ifTrue: [self error].
work
] repeat.
] on: Error do: [:err| restart := false. err retry].
] newProcess name:'My Restartable Worker'.
process resume.

"later do..."
restart := true.
"or after work complete..."
workAvailable signal.

"later still do..."
process terminate

...except being able to interrupt the process anytime,
i.e. not needing to wait to get to "restart ifTrue: [self error]."


btw, The requirement for the fork in "[Transcript crShow: 'Work
complete.'] fork"
is strange. Without it the semaphore does not wait, which seems a bug.

btw2, I needed to hack OCUndeclaredVariableWarning>>defaultAction to
stop the transcript being polluted by unknown playground variables. No
warranty on whether this is suitable to be permanent...
className = 'UndefinedObject' ifFalse: [
 self methodNode selector ifNotNil: [self crTrace: className,
'>>', selector, ' ']
 ifNil: [self traceCr:''].
 self traceCr: '(' , varName , ' is Undeclared1) '.
 ].




On Thu, Feb 25, 2016 at 2:56 AM, Max Leske  wrote:
> Fast spawning processes are very hard to debug (e.g. in the process browser).

This is exactly the use case I was thinking of.  Often they've been
and gone before you even know they are there.  Having a permanent
process aids discoverability of system background functionality.

cheers -ben

[Pharo-dev] Spotter - shortcut display on categories

[Ben Coman]

I see in 50601 that Spotter categories show their shortcut.  I like it
a lot!  Just *maybe* could the "#Implementors" text added to the
search field be appended rather than prepended.  Then it would feel
just like typing.

I say *maybe* because I'd like to use-test the idea before I'm sure of
myself.  Could you point me to where I could make that change to try
it out locally?

cheers -ben

Re: [Pharo-dev] [Moose-dev] Re: short spotter demos

[Yuriy Tymchuk]

Thank you very much. Does it dynamically update the result on each #value: 
send? Also I’ve spotted one behavior which is maybe not always expected. 
Usually when you are defining a processor, you can specify #actLogic:. But when 
you press enter on the history item it only runs the #spotterActDefault method. 
So when you are pressing enter on a catalog project you are prompted if you 
want to load it. If you press enter or a catalog project from history, the 
project is inspected.

Uko

> On 24 Feb 2016, at 22:22, Tudor Girba  wrote:
> 
> Hi,
> 
> Ok, this is more tricky, but it is supported :). Actually this is one of the 
> really cool things about Spotter.
> 
> For this we have #filter:item:. Look at the senders to find examples in the 
> image.
> 
> For example:
> PragmaType>>spotterSendersFor: aStep
>   
>   ^ aStep listProcessor
>   title: 'Senders';
>   filter: GTFilterSubstring item: [ :filter :context | 
>   self keyword senders do: [ :sender | 
>   filter value: sender compiledMethod ] ]
> 
> or:
> GTSpotter>>spotterForReferencesFor: aStep
>   
>   aStep listProcessor
>   title: 'References';
>   filter: GTNullFilter item: [ :filter :context | 
>   context textTrimmed asClassIfPresent: [ :class |
>   SystemNavigation default allReferencesTo: class 
> binding do: filter ] ];
>   keyBinding: $n shift meta;
>   itemName: [ :method | method gtDisplayString ]
> 
> so, the block is being passed a filter which actually behaves like a block 
> :). So, you can pass it to whatever traversal you have, and this will stream 
> the results back to Spotter. I find this so cool that I cannot describe it :).
> 
> Let me know if this helps.
> 
> Cheers,
> Doru
> 
> 
> 
>> On Feb 24, 2016, at 10:14 PM, Yuriy Tymchuk  wrote:
>> 
>> Also in your case you have `allCandidates`. I don’t have this as I’m going 
>> to query a remote service base on input and I want to display all that I 
>> will get :)
>> 
>> Uko
>> 
>>> On 24 Feb 2016, at 21:52, Sven Van Caekenberghe  wrote:
>>> 
 
 On 24 Feb 2016, at 21:41, Yuriy Tymchuk  wrote:
 
 This is super cool! But now I need to lookup: “How to make your own 
 Spotter engine(whatever you call the thing)” ;)
>>> 
>>> That is actually surprisingly simple.
>>> 
>>> To look up known Unicode Characters by partial name:
>>> 
>>> GTSpotter>>#spotterForUnicodeCharacterFor: aStep
>>> 
>>> aStep listProcessor
>>> title: 'Unicode Character';
>>> allCandidates: [ UnicodeCharacterData database values ];
>>> itemName: [ :each | each name ];
>>> filter: GTFilterSubstring;
>>> wantsToDisplayOnEmptyQuery: false
>>> 
>>> And if you want a preview:
>>> 
>>> UnicodeCharacterData>>#spotterPreviewIn: aComposite
>>> 
>>> 
>>> ... same as GT inspector ...
>>> 
 Cheers!
 Uko
 
> On 24 Feb 2016, at 21:38, Tudor Girba  wrote:
> 
> Hi,
> 
> The recent debates around Spotter, showed that some of its features are 
> not well understood. In an effort to document it more thoroughly I 
> created a couple of (very short) videos. They have no sound. Please take 
> a look and let us know what you think.
> 
> 
> Spotting a class with GTSpotter 
> https://www.youtube.com/watch?v=_wIh4fekcD8
> 
> Scoping a search to a specific category in GTSpotter 
> https://www.youtube.com/watch?v=9-fY4mN6Isc
> 
> Using category shortcuts in GTSpotter 
> https://www.youtube.com/watch?v=USNZ7_6gLDA
> 
> Using preview in GTSpotter 
> https://www.youtube.com/watch?v=FSm5xylmTqM
> 
> Using the dive-in action in GTSpotter 
> https://www.youtube.com/watch?v=C7mJBX3Oblw
> 
> Loading a public playground with GTSpotter 
> https://www.youtube.com/watch?v=xeDDLLdA1v8
> 
> Navigating through files with GTSpotter 
> https://www.youtube.com/watch?v=dHQqXcS0vDI
> 
> Refining a search through the dive-in-category action with GTSpotter 
> https://www.youtube.com/watch?v=IclLett0d6c
> 
> Opening a cached playground page with GTSpotter 
> https://www.youtube.com/watch?v=V_yndTSsj8c
> 
> 
> Cheers,
> Doru
> 
> 
> --
> www.tudorgirba.com
> www.feenk.com
> 
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
> 
> 
> 
> 
> ___
> Moose-dev mailing list
> moose-...@list.inf.unibe.ch
> https://www.list.inf.unibe.ch/listinfo/moose-dev
 
 ___
 Moose-dev mailing list
 moose-...@list.inf.unibe.ch
 https://www.list.inf.unibe.ch/listinfo/moose-dev
>>> 
>>> ___
>>> Moose-dev mailing 

Re: [Pharo-dev] Spotter changes broke CodePanel

[Stephan Eggermont]

On 24/02/16 20:14, Tudor Girba wrote:

I took a brief look. It looks like a strange problem. If I add the
wantsToDisplayOnEmptyQuery to false, it seems to work, but I do not
understand the real problem. At least not yet. Could you live with it
for now?


I'll take a better look tomorrow. Thanks for looking into it.

Stephan

Re: [Pharo-dev] [Moose-dev] Re: short spotter demos

[Tudor Girba]

Hi,

Ok, this is more tricky, but it is supported :). Actually this is one of the 
really cool things about Spotter.

For this we have #filter:item:. Look at the senders to find examples in the 
image.

For example:
PragmaType>>spotterSendersFor: aStep

^ aStep listProcessor
title: 'Senders';
filter: GTFilterSubstring item: [ :filter :context | 
self keyword senders do: [ :sender | 
filter value: sender compiledMethod ] ]

or:
GTSpotter>>spotterForReferencesFor: aStep

aStep listProcessor
title: 'References';
filter: GTNullFilter item: [ :filter :context | 
context textTrimmed asClassIfPresent: [ :class |
SystemNavigation default allReferencesTo: class 
binding do: filter ] ];
keyBinding: $n shift meta;
itemName: [ :method | method gtDisplayString ]

so, the block is being passed a filter which actually behaves like a block :). 
So, you can pass it to whatever traversal you have, and this will stream the 
results back to Spotter. I find this so cool that I cannot describe it :).

Let me know if this helps.

Cheers,
Doru



> On Feb 24, 2016, at 10:14 PM, Yuriy Tymchuk  wrote:
> 
> Also in your case you have `allCandidates`. I don’t have this as I’m going to 
> query a remote service base on input and I want to display all that I will 
> get :)
> 
> Uko
> 
>> On 24 Feb 2016, at 21:52, Sven Van Caekenberghe  wrote:
>> 
>>> 
>>> On 24 Feb 2016, at 21:41, Yuriy Tymchuk  wrote:
>>> 
>>> This is super cool! But now I need to lookup: “How to make your own Spotter 
>>> engine(whatever you call the thing)” ;)
>> 
>> That is actually surprisingly simple.
>> 
>> To look up known Unicode Characters by partial name:
>> 
>> GTSpotter>>#spotterForUnicodeCharacterFor: aStep
>>  
>>  aStep listProcessor
>>  title: 'Unicode Character';
>>  allCandidates: [ UnicodeCharacterData database values ];
>>  itemName: [ :each | each name ];
>>  filter: GTFilterSubstring;
>>  wantsToDisplayOnEmptyQuery: false
>> 
>> And if you want a preview:
>> 
>> UnicodeCharacterData>>#spotterPreviewIn: aComposite
>>  
>> 
>>  ... same as GT inspector ...
>> 
>>> Cheers!
>>> Uko
>>> 
 On 24 Feb 2016, at 21:38, Tudor Girba  wrote:
 
 Hi,
 
 The recent debates around Spotter, showed that some of its features are 
 not well understood. In an effort to document it more thoroughly I created 
 a couple of (very short) videos. They have no sound. Please take a look 
 and let us know what you think.
 
 
 Spotting a class with GTSpotter 
 https://www.youtube.com/watch?v=_wIh4fekcD8
 
 Scoping a search to a specific category in GTSpotter 
 https://www.youtube.com/watch?v=9-fY4mN6Isc
 
 Using category shortcuts in GTSpotter 
 https://www.youtube.com/watch?v=USNZ7_6gLDA
 
 Using preview in GTSpotter 
 https://www.youtube.com/watch?v=FSm5xylmTqM
 
 Using the dive-in action in GTSpotter 
 https://www.youtube.com/watch?v=C7mJBX3Oblw
 
 Loading a public playground with GTSpotter 
 https://www.youtube.com/watch?v=xeDDLLdA1v8
 
 Navigating through files with GTSpotter 
 https://www.youtube.com/watch?v=dHQqXcS0vDI
 
 Refining a search through the dive-in-category action with GTSpotter 
 https://www.youtube.com/watch?v=IclLett0d6c
 
 Opening a cached playground page with GTSpotter 
 https://www.youtube.com/watch?v=V_yndTSsj8c
 
 
 Cheers,
 Doru
 
 
 --
 www.tudorgirba.com
 www.feenk.com
 
 "Yesterday is a fact.
 Tomorrow is a possibility.
 Today is a challenge."
 
 
 
 
 ___
 Moose-dev mailing list
 moose-...@list.inf.unibe.ch
 https://www.list.inf.unibe.ch/listinfo/moose-dev
>>> 
>>> ___
>>> Moose-dev mailing list
>>> moose-...@list.inf.unibe.ch
>>> https://www.list.inf.unibe.ch/listinfo/moose-dev
>> 
>> ___
>> Moose-dev mailing list
>> moose-...@list.inf.unibe.ch
>> https://www.list.inf.unibe.ch/listinfo/moose-dev
> 
> ___
> Moose-dev mailing list
> moose-...@list.inf.unibe.ch
> https://www.list.inf.unibe.ch/listinfo/moose-dev

--
www.tudorgirba.com
www.feenk.com

"Every thing has its own flow."

[Pharo-dev] short spotter demos

[Tudor Girba]

Hi,

The recent debates around Spotter, showed that some of its features are not 
well understood. In an effort to document it more thoroughly I created a couple 
of (very short) videos. They have no sound. Please take a look and let us know 
what you think.


Spotting a class with GTSpotter 
https://www.youtube.com/watch?v=_wIh4fekcD8

Scoping a search to a specific category in GTSpotter 
https://www.youtube.com/watch?v=9-fY4mN6Isc

Using category shortcuts in GTSpotter 
https://www.youtube.com/watch?v=USNZ7_6gLDA

Using preview in GTSpotter 
https://www.youtube.com/watch?v=FSm5xylmTqM

Using the dive-in action in GTSpotter 
https://www.youtube.com/watch?v=C7mJBX3Oblw

Loading a public playground with GTSpotter 
https://www.youtube.com/watch?v=xeDDLLdA1v8

Navigating through files with GTSpotter 
https://www.youtube.com/watch?v=dHQqXcS0vDI

Refining a search through the dive-in-category action with GTSpotter 
https://www.youtube.com/watch?v=IclLett0d6c

Opening a cached playground page with GTSpotter 
https://www.youtube.com/watch?v=V_yndTSsj8c


Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Yesterday is a fact.
 Tomorrow is a possibility.
 Today is a challenge."

Re: [Pharo-dev] Help with PrStef with Fonts

[Nicolai Hess]

2016-02-24 17:45 GMT+01:00 stepharo :

> this is what I started to suspect!!!
> Ok I saw that you already commit the code you were faster than me :)
>

No, thats not from me. I'll check.


>
> Stef
>
> Le 24/2/16 17:29, Nicolai Hess a écrit :
>
>
> Am 24.02.2016 5:26 nachm. schrieb "stepharo" < 
> steph...@free.fr>:
> >
> >
> >>>
> >>> may be
> >>>
> >>> showLesson: aLesson withTitle: aString
> >>> self window setLabel: aString.
> >>> self sourceTextModel setText: aLesson lesson.
> >>> self isOpenInWindow ifFalse: [ self open ]
> >>>
> >>>
> >>> but I do not know :(
> >>>
> >>> Stef
> >>>
> >>
> >> Maybe both,
> >> beForSmalltalkCode and beForSmalltalkScripting in
> >> RubScrolledTextMorph should use
> >> self textArea font: StandardFonts codeFont
> >>
> >> At the moment, only beForSmalltalkCode sets this font.
> >
> >
> > Yes I did the same as you, I tried to add
> >
> > beForSmalltalkScripting
> > self textArea beForSmalltalkScripting.
> >
> > self textArea font: StandardFonts codeFont
> >
> > But without success. I'm puzzled.
> > Stef
> >
>
> And you need to reset the tutorial, it reuses the existing lesson view.
>
>
>

Re: [Pharo-dev] Spotter changes broke CodePanel

[Tudor Girba]

Hi,

I took a brief look. It looks like a strange problem. If I add the 
wantsToDisplayOnEmptyQuery to false, it seems to work, but I do not understand 
the real problem. At least not yet. Could you live with it for now?


GTSpotterMorph new
extent: (World width / 3.25 @ (World height / 2.25)) 
asIntegerPoint;
spotterModel: ((GTSpotter new)
processorsFilter: (CodePanelProcessorFilter new 
configuredWith: [ :aProcessor | aProcessor
actLogic: [ :aMethod :step | 
step exit.
aMethod ifNil: [ self new 
openInWindowLabeled: 'Code panel'  ]
ifNotNil: [
|panel|
panel := self new.
panel 
openInWindowLabeled: 'Code panel'.
panel newCardFor: 
aMethod.]];
candidatesLimit: 50;
wantsToDisplayOnEmptyQuery: false ]));
openCenteredInWorld

Cheers,
Doru

> On Feb 24, 2016, at 7:46 PM, Stephan Eggermont  wrote:
> 
> On 24-02-16 19:37, Tudor Girba wrote:
>> Hi,
>> 
>> Could you provide a fully loadable sample to look at this?
> 
> Just load NewUI from the configuration browser.
> 
> Stephan
> 
> 
> 

--
www.tudorgirba.com
www.feenk.com

"Quality cannot be an afterthought."

Re: [Pharo-dev] Process>>restart

[Eliot Miranda]

On Wed, Feb 24, 2016 at 7:23 AM, Ben Coman  wrote:

> Just sharing a passing thought so I don't forget it before I have time
> to think more deeply on it.
>
> Several parts of Pharo (like SHTextStyler) are designed to have a
> background process running, and when new input arrives that process is
> killed so another can be immediately started - and sometimes we seem
> to end up with large amounts of zombie processes.
>
> As I poke around Process>>terminate, I wonder if a different approach
> would be to have a Process>>restart.  I see there is Context>>restart.
>
> The starting the background process might look like...
>
> stylingProcess := [ [ "do stuff with nextData". self suspend ]
> repeat ] forkAt: 30.
>
> and the code in the main morphic priority 40 thread might look like...
>
>sylingProcess suspend.
>nextData := 'blah'.
>sylingProcess restart.
>

Hi Ben, so I'm assuming restart differs from resume.  Am I right in
thinking it cuts back the process to the "start"?  Is the start the block
from which the process was spawned, the argument to fork or forkAt:?


> anyway, back to the grind for me,
> cheers -ben
>

_,,,^..^,,,_
best, Eliot

Re: [Pharo-dev] About contents of Pharo by Example updated

[Tudor Girba]

Hi,

I think this is a good idea.

Another idea would be to point people to the help and then institute a help 
page per-tool policy. We can just create empty items and fill them over time. 
What do you think?

Cheers,
Doru


> On Feb 24, 2016, at 8:02 PM, stepharo  wrote:
> 
> Hi
> 
> I'm looking at some chapters of Pharo by Example like environment that 
> presents many tools
> and I think that I cannot spend time updating this chapter.
> What I will do is to have one tool per page with a small description and key 
> points.
> Else the book will again get obsolete.
> 
> I do not know what you think but I do not have the cycles for all the tiny 
> details.
> 
> Stef
> 

--
www.tudorgirba.com
www.feenk.com

"It's not how it is, it is how we see it."

[Pharo-dev] About contents of Pharo by Example updated

[stepharo]

Hi

I'm looking at some chapters of Pharo by Example like environment that 
presents many tools

and I think that I cannot spend time updating this chapter.
What I will do is to have one tool per page with a small description and 
key points.

Else the book will again get obsolete.

I do not know what you think but I do not have the cycles for all the 
tiny details.


Stef

Re: [Pharo-dev] Process>>restart

[Max Leske]

I like the idea. I implemented something similar recently and one of the real 
advantages is that you can kill (suspend, inspect, etc.) such a process. Fast 
spawning processes are very hard to debug (e.g. in the process browser).

Max

> On 24 Feb 2016, at 16:23, Ben Coman  wrote:
> 
> Just sharing a passing thought so I don't forget it before I have time
> to think more deeply on it.
> 
> Several parts of Pharo (like SHTextStyler) are designed to have a
> background process running, and when new input arrives that process is
> killed so another can be immediately started - and sometimes we seem
> to end up with large amounts of zombie processes.
> 
> As I poke around Process>>terminate, I wonder if a different approach
> would be to have a Process>>restart.  I see there is Context>>restart.
> 
> The starting the background process might look like...
> 
>stylingProcess := [ [ "do stuff with nextData". self suspend ]
> repeat ] forkAt: 30.
> 
> and the code in the main morphic priority 40 thread might look like...
> 
>   sylingProcess suspend.
>   nextData := 'blah'.
>   sylingProcess restart.
> 
> anyway, back to the grind for me,
> cheers -ben
> 

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

[Esteban Lorenzano]

right now feels a lot better than before. 
also the explicit (visible) keybingins to filter are a great addition :)

Esteban

> On 24 Feb 2016, at 19:34, Tudor Girba  wrote:
> 
> Hi,
> 
> Thanks. Indeed, I agree with you. In fact, this is what we did, and then I 
> was told that people would rather want to discuss beforehand :). So, 
> actually, this was a little experiment.
> 
> The thing is that we do not want to disturb people, but we need the feedback 
> to improve fast. So, right now it looks like the only real way to get 
> feedback is to push the changes. This has the tendency to create some 
> annoyance, but we are trying to react as fast as we can to limit it. I hope 
> this will be Ok with everyone.
> 
> Cheers,
> Doru
> 
> 
>> On Feb 24, 2016, at 7:29 PM, Christophe Demarey 
>>  wrote:
>> 
>> Hi Doru,
>> 
>> I don't see a better way to have beta-testers than having your code on the 
>> pharo alpha image ;)
>> You will have very soon feedback and then you can iterate.
>> 
>> Cheers,
>> Christophe
>> 
> 
> --
> www.tudorgirba.com
> www.feenk.com
> 
> "Speaking louder won't make the point worthier."
> 
> 

Re: [Pharo-dev] search query?

[Tudor Girba]

Hi,

Indeed, the ghost text is wrong. It is a plain wildcard type of search. E.g.:
- prefix*
- *postfix
- *middle*

I already fixed it in the latest Glamour and GT.

Cheers,
Doru



> On Feb 24, 2016, at 6:59 PM, stepharo  wrote:
> 
> Hi 
> 
> in the debugger we get a search and I wonder what it is.
> I type true, each 
> and nothing happens (well I do not get the methods list). 
> I think that the ghost text is misleading since we should/can only type
> selectors.
> 
> 
> 

--
www.tudorgirba.com
www.feenk.com

"Value is always contextual."

Re: [Pharo-dev] Spotter changes broke CodePanel

[Stephan Eggermont]

On 24-02-16 19:37, Tudor Girba wrote:

Hi,

Could you provide a fully loadable sample to look at this?


Just load NewUI from the configuration browser.

Stephan

Re: [Pharo-dev] Spotter changes broke CodePanel

[Tudor Girba]

Hi,

Could you provide a fully loadable sample to look at this?

Cheers,
Doru


> On Feb 24, 2016, at 11:52 AM, Stephan Eggermont  wrote:
> 
> I used to do
> 
> CodePanel class>>spot
>  GTSpotterMorph new
>extent: (World width / 3.25 @ (World height / 2.25)) asIntegerPoint;
>spotterModel: ((GTSpotter new)
>processorsFilter: (CodePanelProcessorFilter new
>  configuredWith: [ :aProcessor | aProcessor
>actLogic: [ :aMethod :step |
>  step exit.
>  aMethod ifNil: [ self new openInWindowLabeled: 'Code panel'  ]
>ifNotNil: [ |panel|
>  panel := self new.
>  panel openInWindowLabeled: 'Code panel'.
>  panel newCardFor: aMethod.]];
>candidatesLimit: 50 ]));
>openCenteredInWorld
> 
> That now (since at least 50596) an interesting Brick error.
> Do I need to change my code?
> 
> Stephan
> 
> 
> 

--
www.tudorgirba.com
www.feenk.com

"Being happy is a matter of choice."

[Pharo-dev] Re : Re: [Pharo-users] help needed for testing the order in spotter

[Christophe Demarey]

Hi Doru,

I don't see a better way to have beta-testers than having your code on the 
pharo alpha image ;)
You will have very soon feedback and then you can iterate.

Cheers,
Christophe

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

[Tudor Girba]

Hi,

Thanks. Indeed, I agree with you. In fact, this is what we did, and then I was 
told that people would rather want to discuss beforehand :). So, actually, this 
was a little experiment.

The thing is that we do not want to disturb people, but we need the feedback to 
improve fast. So, right now it looks like the only real way to get feedback is 
to push the changes. This has the tendency to create some annoyance, but we are 
trying to react as fast as we can to limit it. I hope this will be Ok with 
everyone.

Cheers,
Doru


> On Feb 24, 2016, at 7:29 PM, Christophe Demarey  
> wrote:
> 
> Hi Doru,
> 
> I don't see a better way to have beta-testers than having your code on the 
> pharo alpha image ;)
> You will have very soon feedback and then you can iterate.
> 
> Cheers,
> Christophe
> 

--
www.tudorgirba.com
www.feenk.com

"Speaking louder won't make the point worthier."

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50610
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 4a36b4: 50610

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 4a36b431071a12a261972903db068263009cf5a9
  
https://github.com/pharo-project/pharo-core/commit/4a36b431071a12a261972903db068263009cf5a9
  Author: Jenkins Build Server 
  Date:   2016-02-24 (Wed, 24 Feb 2016)

  Changed paths:
M Refactoring-Critics.package/RBSentNotImplementedRule.class/definition.st
R 
Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/accessing/implementorsCache.st
M 
Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/accessing/implementorsExists_.st
R 
Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/private/resetImplementorsCache.st
R 
Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/running/checkClass_.st
A 
Rubric.package/RubEditingArea.class/instance/initialize-release/beForSmalltalkCodeInClass_.st
A 
Rubric.package/RubScrolledTextMorph.class/instance/initialize-release/beForSmalltalkCodeInClass_.st
M Rubric.package/RubSmalltalkCodeMode.class/definition.st
M 
Rubric.package/RubSmalltalkCodeMode.class/instance/shout/classOrMetaClass_.st
A Rubric.package/RubSmalltalkCodeMode.class/instance/shout/updateStyler.st
M 
Rubric.package/RubSmalltalkCodeMode.class/instance/shout/withShoutStyler.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50609.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50610.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50609.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50610.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
A SmartSuggestions.package/SugsProcessBrowserContext.class/README.md
A SmartSuggestions.package/SugsProcessBrowserContext.class/definition.st
A 
SmartSuggestions.package/SugsProcessBrowserContext.class/instance/refactoring/sourceTextArea.st
A 
SmartSuggestions.package/SugsProcessBrowserContext.class/instance/selection/selectedClass.st
A 
SmartSuggestions.package/SugsProcessBrowserContext.class/instance/selection/selectedMethod.st
A SmartSuggestions.package/SugsTranscriptContext.class/README.md
A SmartSuggestions.package/SugsTranscriptContext.class/definition.st
A 
SmartSuggestions.package/SugsTranscriptContext.class/instance/refactoring/selectedClass.st
A 
SmartSuggestions.package/SugsTranscriptContext.class/instance/refactoring/selectedMethod.st
A 
SmartSuggestions.package/SugsTranscriptContext.class/instance/refactoring/sourceTextArea.st
M SmartSuggestions.package/extension/DiffMorph/instance/sugsContext.st
A SmartSuggestions.package/extension/ProcessBrowser/instance/sugsContext.st
A 
SmartSuggestions.package/extension/ThreadSafeTranscript/instance/sugsContext.st
M 
Spec-MorphicAdapters.package/MorphicTextAdapter.class/instance/private/setEditingModeFor_withBehavior_.st
M Spec-MorphicAdapters.package/MorphicTextAdapter.class/instance/spec 
protocol/classOrMetaClass_.st
A 
Tool-ProcessBrowser.package/ProcessBrowser.class/instance/accessing/methodText.st
M 
Tool-ProcessBrowser.package/ProcessBrowser.class/instance/accessing/selectedMethod.st
M 
Tool-ProcessBrowser.package/ProcessBrowser.class/instance/accessing/stackListIndex_.st
M Tool-ProcessBrowser.package/ProcessBrowser.class/instance/stack 
list/changeStackListTo_.st
M Tool-ProcessBrowser.package/ProcessBrowser.class/instance/views/build.st

  Log Message:
  ---
  50610
17683 but right button (menu) is broken in process browser
https://pharo.fogbugz.com/f/cases/17683

17688 speedup RBSentNotImplementedRule
https://pharo.fogbugz.com/f/cases/17688

17065 Transcript has no context menu
https://pharo.fogbugz.com/f/cases/17065

17684  highlighting broken in message list (senders off / implementors of)
https://pharo.fogbugz.com/f/cases/17684

http://files.pharo.org/image/50/50610.zip

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

[Tudor Girba]

Hi,


> On Feb 24, 2016, at 11:24 AM, Damien Cassou  wrote:
> 
> Tudor Girba  writes:
> 
>> Hi,
>> 
>> We need a bit of help with testing the order in Spotter. We do not have a 
>> real solution yet, but the current one should improve the situation.
>> 
>> We need a bit of feedback for this one:
>> https://pharo.fogbugz.com/f/cases/17656/Spotter-should-sort-search-results
>> 
>> Essentially, you would need to load the latest GT-Spotter and 
>> GT-SpotterExtensions-Core and let us know if it works better for spotting 
>> implementors or classes.
> 
> I have the impression this is already in the image. It seems to be
> working fine. Next time, it might help if you could just give us a Pharo
> expression that loads the patch.

Indeed, it is now in the image.

Unfortunately, there was no feedback :(. I will do it better next time. I just 
thought that given the urgency with which issues were reported, people would 
have been more eager to test, so I hurried up :).

Cheers,
Doru



> -- 
> Damien Cassou
> http://damiencassou.seasidehosting.st
> 
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill

--
www.tudorgirba.com
www.feenk.com

"Quality cannot be an afterthought."

Re: [Pharo-dev] GTSpotter displayed shortcut glitch

[Tudor Girba]

Hi,

> On Feb 24, 2016, at 6:00 PM, stepharo  wrote:
> 
> Hi doru and andrei
> 
> I saw that you are displaying the shortcuts that can be used and this is good.
> Now may be I got it wrong but
>Cmd + M is not for implementors everywhere else it is Cmd + m
>Same for senders
> So I checked and Cmd + n is senders but displayed Cmd+N
> Cmd+N shows references and this is cool.

We used the same logic of displaying the keybindings as it is used in the menu. 
There if you have Shift, it appears explicitly. For example, for references, we 
have Shif+Cmd+N. I also think that we should have the letters in smallcaps, but 
at least now it is uniform. We can decide to change it everywhere, and I would 
be fine with that.

Cheers,
Doru

> Stef
> 

--
www.tudorgirba.com
www.feenk.com

"Every thing has its own flow."

[Pharo-dev] search query?

[stepharo]

Hi

in the debugger we get a search and I wonder what it is.
I type true, each
and nothing happens (well I do not get the methods list).
I think that the ghost text is misleading since we should/can only type
selectors.

Re: [Pharo-dev] [pharo-project/pharo-core] 4ade51: 50609

[stepharo]

thanks this one is also important :)


Le 24/2/16 18:02, GitHub a écrit :

   50609
17687 fix: changing class comments does not work
https://pharo.fogbugz.com/f/cases/17687

Re: [Pharo-dev] Git written entirely in Smalltalk?

[Richard Sargent]

Ben Coman wrote
> Max,
> 
> The other say I was contemplating having a git implementation written
> entirely in Pharo, and today I bumped into something from your history
> (~2011?) [1]  indicating this might have been attempted.   I'm curious
> why this was abandoned in favour of libgit bindings.

I have seen a lot of "not invented here" work in the Smalltalk world over
the last 25 years. That in itself is enough reason to not reimplement
everything in native Smalltalk.

There are whole communities out there who specialize in one esoteric piece
of technology. You can stand on their shoulders or you can copy their work.
One of those appeals a lot more to me than the other.

When we bind to someone else's work, their updates are almost free to us.
Otherwise, we tie up a lot of our own resources replicating their work and
not advancing our own.


> [1] http://scg.unibe.ch/wiki/students/maxleske
> 
> cheers -ben





--
View this message in context: 
http://forum.world.st/Git-written-entirely-in-Smalltalk-tp4880274p4880430.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50609
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 4ade51: 50609

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 4ade51dbf2af66d85f356a52898d15c32b602ed1
  
https://github.com/pharo-project/pharo-core/commit/4ade51dbf2af66d85f356a52898d15c32b602ed1
  Author: Jenkins Build Server 
  Date:   2016-02-24 (Wed, 24 Feb 2016)

  Changed paths:
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50608.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50609.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50608.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50609.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
M Slot.package/SlotClassBuilder.class/instance/initialize-release/build.st

  Log Message:
  ---
  50609
17687 fix: changing class comments does not work
https://pharo.fogbugz.com/f/cases/17687

http://files.pharo.org/image/50/50609.zip

[Pharo-dev] GTSpotter displayed shortcut glitch

[stepharo]

Hi doru and andrei

I saw that you are displaying the shortcuts that can be used and this is 
good.

Now may be I got it wrong but
Cmd + M is not for implementors everywhere else it is Cmd + m
Same for senders
So I checked and Cmd + n is senders but displayed Cmd+N
Cmd+N shows references and this is cool.

Stef

Re: [Pharo-dev] Help with PrStef with Fonts

[stepharo]

this is what I started to suspect!!!
Ok I saw that you already commit the code you were faster than me :)

Stef

Le 24/2/16 17:29, Nicolai Hess a écrit :



Am 24.02.2016 5:26 nachm. schrieb "stepharo" >:

>
>
>>>
>>> may be
>>>
>>> showLesson: aLesson withTitle: aString
>>> self window setLabel: aString.
>>> self sourceTextModel setText: aLesson lesson.
>>> self isOpenInWindow ifFalse: [ self open ]
>>>
>>>
>>> but I do not know :(
>>>
>>> Stef
>>>
>>
>> Maybe both,
>> beForSmalltalkCode and beForSmalltalkScripting in
>> RubScrolledTextMorph should use
>> self textArea font: StandardFonts codeFont
>>
>> At the moment, only beForSmalltalkCode sets this font.
>
>
> Yes I did the same as you, I tried to add
>
> beForSmalltalkScripting
> self textArea beForSmalltalkScripting.
>
> self textArea font: StandardFonts codeFont
>
> But without success. I'm puzzled.
> Stef
>

And you need to reset the tutorial, it reuses the existing lesson view.

Re: [Pharo-dev] Help with PrStef with Fonts

[stepharo]

can you add a bug entry I will fix the other and publish it.

Le 24/2/16 17:31, Nicolai Hess a écrit :



Am 24.02.2016 5:29 nachm. schrieb "Nicolai Hess" 
mailto:nicolaih...@gmail.com>>:

>
>
> Am 24.02.2016 5:26 nachm. schrieb "stepharo" >:

> >
> >
> >>>
> >>> may be
> >>>
> >>> showLesson: aLesson withTitle: aString
> >>> self window setLabel: aString.
> >>> self sourceTextModel setText: aLesson lesson.
> >>> self isOpenInWindow ifFalse: [ self open ]
> >>>
> >>>
> >>> but I do not know :(
> >>>
> >>> Stef
> >>>
> >>
> >> Maybe both,
> >> beForSmalltalkCode and beForSmalltalkScripting in
> >> RubScrolledTextMorph should use
> >> self textArea font: StandardFonts codeFont
> >>
> >> At the moment, only beForSmalltalkCode sets this font.
> >
> >
> > Yes I did the same as you, I tried to add
> >
> > beForSmalltalkScripting
> > self textArea beForSmalltalkScripting.
> >
> > self textArea font: StandardFonts codeFont
> >
> > But without success. I'm puzzled.
> > Stef
> >
>
> And you need to reset the tutorial, it reuses the existing lesson view.

And maybe we should use beForSmalltalkScripting in the helpbrowser as 
well, because right now, you can not use "printIt"

Re: [Pharo-dev] Starting to add class comment and test on BlElements

[stepharo]

Oh excellent
I think that I forgot to jump into a bloc world.
So this means that I can now turn some examples into tests.



Le 24/2/16 10:21, Glenn Cavarlé a écrit :

Hi Stef,

Yes, BlElement is the starting point, i think so.
All examples in BlElement run for me, do you have some errors ?
On my side, i'm starting to write examples using layouts.

We can talk about the performances issue later (if asserts really have an
impact on) , when the first stable version will be released.
But for now, i think using asserts is a good choice to make things clear and
to help the understanding and the documentation (same for the 
pragma).


Yes this is my feeling too.



Glenn.



-
Glenn Cavarlé
--
View this message in context: 
http://forum.world.st/Starting-to-add-class-comment-and-test-on-BlElements-tp4879800p4880193.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] cannot use shortcut in text pane of MC

[stepharo]

excellent!


Le 24/2/16 08:57, Marcus Denker a écrit :

fix in since 50597


On 22 Feb 2016, at 08:41, Marcus Denker  wrote:

https://pharo.fogbugz.com/f/cases/17570/Shortcuts-to-browse-code-are-not-available-any-more-in-some-tools

There are *lots* of fixes in the queue to be integrated… progress is slow 
sometimes (e.g. this was done 12 days
ago but we have just yesterday found someone to review to the fix).

Marcus


On 21 Feb 2016, at 18:52, stepharo  wrote:

Hi guillermo

I do not know if this is the one you fixed but in
Pharo5.0
Latest update: #50596

I cannot type the name of class and browse it in a MC textpane.

Stef

Re: [Pharo-dev] [pharo-project/pharo-core] 9d9b04: 50606

[stepharo]

Le 24/2/16 12:13, Marcus Denker a écrit :

On 24 Feb 2016, at 11:02, GitHub  wrote:



  Log Message:
  ---
  50606
16893 Update STON
https://pharo.fogbugz.com/f/cases/16893


this includes:

17651 SettingsStonWriter>>#store should use #asciiOnly: option
https://pharo.fogbugz.com/f/cases/17651


Cases closed last 7 days: 125. Not bad!


No quite good!


Marcus

Re: [Pharo-dev] Why implementors are getting all the text red?

[stepharo]

Tx guille

Stef


Le 24/2/16 12:40, Guille Polito a écrit :
I put a slice in the inbox with a patch that seems to solve this. I 
duplicated some methods, so it should be reviewed/enhanced. But right 
not I have a meeting and I cannot continue to work on this until tomorrow.


On 02/24/2016 12:20 PM, Marcus Denker wrote:

It is a bug.

The alternative would be to continue to have the build failing on the CI often 
and the check of new submissions
8 out of 10 times… honestly it was not possible to continue with a broken setup 
like that.


https://pharo.fogbugz.com/f/cases/17684/highlighting-broken-in-message-list-senders-off-implementors-of

We need to fix this next.

Marcus


On 24 Feb 2016, at 12:12, stepharo  wrote:

hi

May be this is a well known bug but now all the implementors are showed in red.
So I cannot film that.

Stef

Re: [Pharo-dev] Help with PrStef with Fonts

[Nicolai Hess]

Am 24.02.2016 5:29 nachm. schrieb "Nicolai Hess" :
>
>
> Am 24.02.2016 5:26 nachm. schrieb "stepharo" :
> >
> >
> >>>
> >>> may be
> >>>
> >>> showLesson: aLesson withTitle: aString
> >>> self window setLabel: aString.
> >>> self sourceTextModel setText: aLesson lesson.
> >>> self isOpenInWindow ifFalse: [ self open ]
> >>>
> >>>
> >>> but I do not know :(
> >>>
> >>> Stef
> >>>
> >>
> >> Maybe both,
> >> beForSmalltalkCode and beForSmalltalkScripting in
> >> RubScrolledTextMorph should use
> >> self textArea font: StandardFonts codeFont
> >>
> >> At the moment, only beForSmalltalkCode sets this font.
> >
> >
> > Yes I did the same as you, I tried to add
> >
> > beForSmalltalkScripting
> > self textArea beForSmalltalkScripting.
> >
> > self textArea font: StandardFonts codeFont
> >
> > But without success. I'm puzzled.
> > Stef
> >
>
> And you need to reset the tutorial, it reuses the existing lesson view.

And maybe we should use beForSmalltalkScripting in the helpbrowser as well,
because right now, you can not use "printIt"

Re: [Pharo-dev] Help with PrStef with Fonts

[Nicolai Hess]

Am 24.02.2016 5:26 nachm. schrieb "stepharo" :
>
>
>>>
>>> may be
>>>
>>> showLesson: aLesson withTitle: aString
>>> self window setLabel: aString.
>>> self sourceTextModel setText: aLesson lesson.
>>> self isOpenInWindow ifFalse: [ self open ]
>>>
>>>
>>> but I do not know :(
>>>
>>> Stef
>>>
>>
>> Maybe both,
>> beForSmalltalkCode and beForSmalltalkScripting in
>> RubScrolledTextMorph should use
>> self textArea font: StandardFonts codeFont
>>
>> At the moment, only beForSmalltalkCode sets this font.
>
>
> Yes I did the same as you, I tried to add
>
> beForSmalltalkScripting
> self textArea beForSmalltalkScripting.
>
> self textArea font: StandardFonts codeFont
>
> But without success. I'm puzzled.
> Stef
>

And you need to reset the tutorial, it reuses the existing lesson view.

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

[stepharo]

Anne

did you publish the code you did with guillaume on reimplementing graphViz?

Stef


Le 24/2/16 10:28, Anne Etien a écrit :

Hi Alexandre,

In a wonderful world, I would like:
- a real graph layout (like in graphviz) that can take into account around 
hundred nodes and several hundred of edges and place the nodes in order to see 
something. Currently, I have to use the circle layout and it looks strange.
- the possibility to place hangout of the edges on nodes (as box) more 
flexible. Indeed, I am reverse engineering a database containing around 80 
tables and lot of foreign keys and the result is not readable since the edge 
are orthogonal starting from the top or the bottom of the box corresponding to 
the column name. I would like a real entity-relation diagram.

For the remainder, I use only Telescope since I have just to specify my data 
and not to script the visualization taking into account the order of the 
instructions… So don’t change the interface of the existing API in order we can 
continue to use Telescope on top on Roassal.

  If you want, I can show you the current stage of the visu (once again done in 
Telescope on top of Roassal) in order that you see on real data how uggly it is.

Cheers,
Anne


Le 24 févr. 2016 à 09:51, Alexandre Bergel  a écrit :

Dear community,

As you may have seen, Roassal has entered a stabilization phase. The book 
AgileVisualization.com will soon be released. After its release, Roassal will 
go over a new development phase. In order to prepare it, I am asking this 
question:

What are the 3 aspects you would like to see improved in Roassal?

You can answer publicly or by sending private messages.

Kind regards,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



___
Moose-dev mailing list
moose-...@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev

Re: [Pharo-dev] Help with PrStef with Fonts

[stepharo]

may be

showLesson: aLesson withTitle: aString
self window setLabel: aString.
self sourceTextModel setText: aLesson lesson.
self isOpenInWindow ifFalse: [ self open ]


but I do not know :(

Stef


Maybe both,
beForSmalltalkCode and beForSmalltalkScripting in
RubScrolledTextMorph should use
self textArea font: StandardFonts codeFont

At the moment, only beForSmalltalkCode sets this font.


Yes I did the same as you, I tried to add

beForSmalltalkScripting
self textArea beForSmalltalkScripting.
self textArea font: StandardFonts codeFont

But without success. I'm puzzled.
Stef

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

[stepharo]

I do not know.
May be.

Le 23/2/16 10:30, Denis Kudriashov a écrit :

Hi

2016-02-23 9:13 GMT+01:00 stepharo >:


May be we should have some Palette

And we could have (brainstorming)

(ColorBuilder from: MDLPalette)
-> aColorBuilder
  aColorBuilder red
-> 


What the difference between red colors from different palettes? And 
why it is not just "MDLPalette red"?

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

[stepharo]

tx for the pointer


Le 24/2/16 10:34, Glenn Cavarlé a écrit :

Hi,
In my memories, a first implementation of material colors was also made by
Alex in Brick packages.
This can be a inspiration source, too.



-
Glenn Cavarlé
--
View this message in context: 
http://forum.world.st/Bloc-MDLColor-and-new-gradient-tp4879795p4880198.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

[Pharo-dev] Process>>restart

[Ben Coman]

Just sharing a passing thought so I don't forget it before I have time
to think more deeply on it.

Several parts of Pharo (like SHTextStyler) are designed to have a
background process running, and when new input arrives that process is
killed so another can be immediately started - and sometimes we seem
to end up with large amounts of zombie processes.

As I poke around Process>>terminate, I wonder if a different approach
would be to have a Process>>restart.  I see there is Context>>restart.

The starting the background process might look like...

stylingProcess := [ [ "do stuff with nextData". self suspend ]
repeat ] forkAt: 30.

and the code in the main morphic priority 40 thread might look like...

   sylingProcess suspend.
   nextData := 'blah'.
   sylingProcess restart.

anyway, back to the grind for me,
cheers -ben

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50608
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 14f6ba: 50608

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 14f6bab879eb513900b9dd6b01726ffd66291c80
  
https://github.com/pharo-project/pharo-core/commit/14f6bab879eb513900b9dd6b01726ffd66291c80
  Author: Jenkins Build Server 
  Date:   2016-02-24 (Wed, 24 Feb 2016)

  Changed paths:
M 
FreeType.package/FT2Face.class/instance/initialize-release/newFaceFromExternalMemory_index_.st
M 
FreeType.package/FT2Face.class/instance/initialize-release/newFaceFromFile_index_.st
A 
FreeType.package/FT2Face.class/instance/private-primitives/primNewFaceFromExternalMemory_size_index_.st
M FreeType.package/FT2Face.class/instance/private/loadFields.st
R FreeType.package/FT2Handle.class/instance/printing/isValid.st
A FreeType.package/FT2Handle.class/instance/testing/isValid.st
M FreeType.package/FreeTypeFace.class/definition.st
R FreeType.package/FreeTypeFace.class/instance/initialize-release/beNull.st
R FreeType.package/FreeTypeFace.class/instance/testing/isValid.st
M FreeType.package/FreeTypeFace.class/instance/validation/create.st
R 
FreeType.package/FreeTypeFace.class/instance/validation/newFaceFromExternalMemory_index_.st
R 
FreeType.package/FreeTypeFace.class/instance/validation/newFaceFromFile_index_.st
R 
FreeType.package/FreeTypeFace.class/instance/validation/primNewFaceFromExternalMemory_size_index_.st
M FreeType.package/FreeTypeFace.class/instance/validation/validate.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50607.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50608.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50607.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50608.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  50608
17392 FreeType numCharMaps nil causes Array>>basicNew: to fail
https://pharo.fogbugz.com/f/cases/17392

http://files.pharo.org/image/50/50608.zip

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

[Peter Uhnák]

On Wed, Feb 24, 2016 at 3:11 PM, p...@highoctane.be 
wrote:

> Make it working with all graphviz tools and it will be wonderful already.
> BTW, there is already a tool generating graphviz things as this is what
> was used to document seaside dependencies.
>

Yes, this is what I used to generate the GraphViz .dot file.
http://smalltalkhub.com/#!/~hernan/GraphViz

But I had to parse the results myself from SVG, because the default one had
some precision issues (this was most likely GraphViz problems).

Peter

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

[p...@highoctane.be]

Make it working with all graphviz tools and it will be wonderful already.
BTW, there is already a tool generating graphviz things as this is what was
used to document seaside dependencies.

Here us thread:
http://forum.world.st/GraphViz-renggli-repo-down-td4722561.html

Seems that Roassal 1 had such a thing already.

Phil

On Wed, Feb 24, 2016 at 10:44 AM, Anne Etien 
wrote:

>
> Le 24 févr. 2016 à 10:35, Peter Uhnák  a écrit :
>
>
>
> On Wed, Feb 24, 2016 at 10:28 AM, Anne Etien 
> wrote:
>
>> Hi Alexandre,
>>
>> In a wonderful world, I would like:
>> - a real graph layout (like in graphviz) that can take into account
>> around hundred nodes and several hundred of edges and place the nodes in
>> order to see something. Currently, I have to use the circle layout and it
>> looks strange.
>>
>
> Unfortunately making real graph layouts is really hard issue… I've wrote
> my bachelor thesis about this and didn't get very far; it's bit of a
> nightmare if you don't have good foundations. :’(
>
>
> I know. I tried but my mathematical background and my time were not
> enough. I got the research paper explaining the algorithm of Graphviz but
> even with that, it was very complex. However, since some tools (as
> graphviz) do it, we should have it.
>
> Anne
>
>
> In any case, I wrote a simpler layout delegator in Roassal that delegates
> the layouting to graphviz and it works reasonably well, so I could probably
> add it to Roassal (you however need graphviz installed and it would add
> another dependency to Roassal, which I'm not so keen on).
>
> Maybe also OGDF (http://ogdf.net/doku.php) could be used if you are ok
> with GPL… they have their own graph format so there could be some
> interaction.
>
> Peter
> ___
> Moose-dev mailing list
> moose-...@list.inf.unibe.ch
> https://www.list.inf.unibe.ch/listinfo/moose-dev
>
>
>

[Pharo-dev] reviews needed: Cleanup of RubParagraphDecorator drawing

[Marcus Denker]

Hi,

It would be nice if we could review and integrate this:

Cleanup of RubParagraphDecorator drawing
https://pharo.fogbugz.com/f/cases/17062

Re: [Pharo-dev] Git written entirely in Smalltalk?

[Damien Cassou]

Ben Coman  writes:

> The other say I was contemplating having a git implementation written
> entirely in Pharo, and today I bumped into something from your history
> (~2011?) [1]  indicating this might have been attempted.   I'm curious
> why this was abandoned in favour of libgit bindings.

Max did most of the work IIRC. Then Camillo and I tried to help. But
this is difficult to do because the git protocol is complex and we had
not much time to dive into it. We also didn't find good documentation.

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Re: [Pharo-dev] Git written entirely in Smalltalk?

[Max Leske]

:)

It wasn’t a complete implementation but entirely written in Pharo, yes. The 
reason I decided to go for bindings is that Git is quite big. There are many 
things to implement and there’s a lot of mystery when it comes to 
implementation details. Using bindings reduces the cost of maintenance a lot, 
since the burden of updating and fixing stuff is no longer on me.

Additionally, performance was never really good with my solution, partly due to 
the VM of course (FFI wasn’t really an option for me back then, so all the 
calculations were done in the image). And finally, Git has a rather 
unconventional way of handling memory: allocate until it breaks. Since we’re 
quite constrained memory wise in Pharo, I would run into out of memory 
situations pretty quickly. Handing the memory management off to the library 
makes things a lot easier.

BTW, I based my project on the work of Tony Garnock-Jones (from NZ) who started 
work on a Git implementation for Squeak (but then gave up the project).

Cheers,
Max

> On 24 Feb 2016, at 12:30, Ben Coman  wrote:
> 
> Max,
> 
> The other say I was contemplating having a git implementation written
> entirely in Pharo, and today I bumped into something from your history
> (~2011?) [1]  indicating this might have been attempted.   I'm curious
> why this was abandoned in favour of libgit bindings.
> 
> [1] http://scg.unibe.ch/wiki/students/maxleske
> 
> cheers -ben
> 

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

[Alexandre Bergel]

>> Dear community,
>>  What are the 3 aspects you would like to see improved in Roassal?
> 
> My favorite improvement would not really be a Roassal feature
> but would save me a lot of time:
> I would like the configuration versions to stop depending on numbered 
> versions of outside dependencies (Glamour, Neo-JSON-Core)

Hi!

I do not get this. Relying on the baseline is not enough?

Roassal is very simply packaged. Only 4 packages: Roassal, Trachel, 
Roassal2Spec, Roassal2GT. It is very unlikely that this list of package will 
grow (not until we have a Git integration at least). You can make your 
configuration directly point to these packages no? 

Cheers,
Alexandre

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

[Pharo-dev] [Bloc] stroke width and layout measure

[Glenn Cavarlé]

Hi,

The stroke width of an element's shape is not taken into account when the
child elements are measured.
In fact, a child element that matches parent extent hides the left and top
borders of its parent.
Will it mandatory to use a padding to fix that ? Or is it just part of the
work that still to be done ?

Regards,



-
Glenn Cavarlé
--
View this message in context: 
http://forum.world.st/Bloc-stroke-width-and-layout-measure-tp4880292.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Help with PrStef with Fonts

[Nicolai Hess]

2016-02-24 12:18 GMT+01:00 stepharo :

> Hi
>
> I'm trying to understand why PrStef does not use the fonts I defined for
> shooting the videos
>
> StandardFonts codeFont:
>  (LogicalFont familyName: 'Source Code Pro' pointSize: 15).
> StandardFonts defaultFont:
>  (LogicalFont familyName: 'Source Code Sans' pointSize: 13).
> StandardFonts listFont:
>  (LogicalFont familyName: 'Source Code Sans' pointSize: 18).
> StandardFonts menuFont:
>  (LogicalFont familyName: 'Source Code Sans' pointSize: 18).
> StandardFonts buttonFont:
>  (LogicalFont familyName: 'Source Code Sans' pointSize: 12).
>
> I tried to avoid to convert a text into a string...
>
> may be
>
> showLesson: aLesson withTitle: aString
> self window setLabel: aString.
> self sourceTextModel setText: aLesson lesson.
> self isOpenInWindow ifFalse: [ self open ]
>
>
> but I do not know :(
>
> Stef
>
>
Maybe both,
beForSmalltalkCode and beForSmalltalkScripting in
RubScrolledTextMorph should use
self textArea font: StandardFonts codeFont

At the moment, only beForSmalltalkCode sets this font.

Re: [Pharo-dev] Why implementors are getting all the text red?

[Marcus Denker]

Very nice! I will check.


> On 24 Feb 2016, at 12:40, Guille Polito  wrote:
> 
> I put a slice in the inbox with a patch that seems to solve this. I 
> duplicated some methods, so it should be reviewed/enhanced. But right not I 
> have a meeting and I cannot continue to work on this until tomorrow.
> 
> On 02/24/2016 12:20 PM, Marcus Denker wrote:
>> It is a bug. 
>> 
>> The alternative would be to continue to have the build failing on the CI 
>> often and the check of new submissions
>> 8 out of 10 times… honestly it was not possible to continue with a broken 
>> setup like that.
>> 
>>  
>> https://pharo.fogbugz.com/f/cases/17684/highlighting-broken-in-message-list-senders-off-implementors-of
>>  
>> 
>> 
>> We need to fix this next.
>> 
>>  Marcus
>> 
>>> On 24 Feb 2016, at 12:12, stepharo  
>>>  wrote:
>>> 
>>> hi 
>>> 
>>> May be this is a well known bug but now all the implementors are showed in 
>>> red. 
>>> So I cannot film that.
>>> 
>>> Stef
>>> 
>>> 
>> 
> 

Re: [Pharo-dev] Why implementors are getting all the text red?

[Marcus Denker]

Ah, of course there is a workaround to get back the old behaviour:


RubShoutStylerDecorator>>style: 

remove the 

aText size < 1000
ifTrue: [ ^ self styler style: aText ].

after that it again styles everything in the background, which hides the bug.

Marcus

> On 24 Feb 2016, at 12:20, Marcus Denker  wrote:
> 
> It is a bug. 
> 
> The alternative would be to continue to have the build failing on the CI 
> often and the check of new submissions
> 8 out of 10 times… honestly it was not possible to continue with a broken 
> setup like that.
> 
>   
> https://pharo.fogbugz.com/f/cases/17684/highlighting-broken-in-message-list-senders-off-implementors-of
> 
> We need to fix this next.
> 
>   Marcus
> 
>> On 24 Feb 2016, at 12:12, stepharo  wrote:
>> 
>> hi 
>> 
>> May be this is a well known bug but now all the implementors are showed in 
>> red. 
>> So I cannot film that.
>> 
>> Stef
>> 
>> 
> 

Re: [Pharo-dev] Why implementors are getting all the text red?

[Guille Polito]

I put a slice in the inbox with a patch that seems to solve this. I 
duplicated some methods, so it should be reviewed/enhanced. But right 
not I have a meeting and I cannot continue to work on this until tomorrow.


On 02/24/2016 12:20 PM, Marcus Denker wrote:

It is a bug.

The alternative would be to continue to have the build failing on the CI often 
and the check of new submissions
8 out of 10 times… honestly it was not possible to continue with a broken setup 
like that.


https://pharo.fogbugz.com/f/cases/17684/highlighting-broken-in-message-list-senders-off-implementors-of

We need to fix this next.

Marcus


On 24 Feb 2016, at 12:12, stepharo  wrote:

hi

May be this is a well known bug but now all the implementors are showed in red.
So I cannot film that.

Stef

[Pharo-dev] Git written entirely in Smalltalk?

[Ben Coman]

Max,

The other say I was contemplating having a git implementation written
entirely in Pharo, and today I bumped into something from your history
(~2011?) [1]  indicating this might have been attempted.   I'm curious
why this was abandoned in favour of libgit bindings.

[1] http://scg.unibe.ch/wiki/students/maxleske

cheers -ben

Re: [Pharo-dev] [regression reporter]regression occurred

[Cyril Ferlicot Delbecque]

On 24/02/2016 09:07, Sven Van Caekenberghe wrote:
> The following test seems to be failing a lot lately on the CI infrastructure, 
> yet it always succeeds for me on my machine. Is there anybody who sees this 
> fail on their machines ?
> 
>> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
>>
>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
>>
>> 1 regressions found.
>>  Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
> 
> 

It does not fail all the time but on my Mac with a stable connection with:

20 timesRepeat: [
Transcript show: Time now asString, ': '.
Transcript show: (ZnHTTPSTests new setTestSelector: #testAmazonAWS; 
run);
cr
]

I got:


12:19:52.230023 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:19:53.028736 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:19:53.92617 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:19:55.23689 pm: 1 run, 0 passes, 0 skipped, 0 expected failures, 0
failures, 1 errors, 0 unexpected passes
12:20:35.851549 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:36.991826 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:37.955399 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:38.930401 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:39.81128 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:40.775596 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:42.524211 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:43.326577 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:44.291269 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:45.313826 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:46.949006 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:48.581509 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:49.546702 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:50.435629 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:51.403718 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes
12:20:53.225974 pm: 1 run, 1 passes, 0 skipped, 0 expected failures, 0
failures, 0 errors, 0 unexpected passes


So there was one test that failed.

-- 
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France



signature.asc
Description: OpenPGP digital signature

Re: [Pharo-dev] Why implementors are getting all the text red?

[Cyril Ferlicot Delbecque]

See
https://pharo.fogbugz.com/f/cases/17684/highlighting-broken-in-message-list-senders-off-implementors-of

On 24/02/2016 12:12, stepharo wrote:
> hi
> 
> May be this is a well known bug but now all the implementors are showed
> in red.
> So I cannot film that.
> 
> Stef
> 

-- 
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France



signature.asc
Description: OpenPGP digital signature

Re: [Pharo-dev] Why implementors are getting all the text red?

[Marcus Denker]

It is a bug. 

The alternative would be to continue to have the build failing on the CI often 
and the check of new submissions
8 out of 10 times… honestly it was not possible to continue with a broken setup 
like that.


https://pharo.fogbugz.com/f/cases/17684/highlighting-broken-in-message-list-senders-off-implementors-of

We need to fix this next.

Marcus

> On 24 Feb 2016, at 12:12, stepharo  wrote:
> 
> hi 
> 
> May be this is a well known bug but now all the implementors are showed in 
> red. 
> So I cannot film that.
> 
> Stef
> 
> 

[Pharo-dev] Help with PrStef with Fonts

[stepharo]

Hi

I'm trying to understand why PrStef does not use the fonts I defined for 
shooting the videos


StandardFonts codeFont:
 (LogicalFont familyName: 'Source Code Pro' pointSize: 15).
StandardFonts defaultFont:
 (LogicalFont familyName: 'Source Code Sans' pointSize: 13).
StandardFonts listFont:
 (LogicalFont familyName: 'Source Code Sans' pointSize: 18).
StandardFonts menuFont:
 (LogicalFont familyName: 'Source Code Sans' pointSize: 18).
StandardFonts buttonFont:
 (LogicalFont familyName: 'Source Code Sans' pointSize: 12).

I tried to avoid to convert a text into a string...

may be

showLesson: aLesson withTitle: aString
self window setLabel: aString.
self sourceTextModel setText: aLesson lesson.
self isOpenInWindow ifFalse: [ self open ]


but I do not know :(

Stef

Re: [Pharo-dev] [pharo-project/pharo-core] 9d9b04: 50606

[Marcus Denker]

> On 24 Feb 2016, at 11:02, GitHub  wrote:
> 
> 
> 
>  Log Message:
>  ---
>  50606
> 16893 Update STON
>   https://pharo.fogbugz.com/f/cases/16893


this includes:

17651 SettingsStonWriter>>#store should use #asciiOnly: option
https://pharo.fogbugz.com/f/cases/17651


Cases closed last 7 days: 125. Not bad!

Marcus

[Pharo-dev] Why implementors are getting all the text red?

[stepharo]

hi

May be this is a well known bug but now all the implementors are showed 
in red.

So I cannot film that.

Stef

Re: [Pharo-dev] [pharo-project/pharo-core] b98668: 50607

[Marcus Denker]

This recompiles the whole image.

Sadly it means that it allocated some more memory regions while doing so and
the resulting image is now 47MB saved, but that does not mean it really is 47MB…
it just is saved with more free space...

Marcus

> On 24 Feb 2016, at 11:58, GitHub  wrote:
> 
>  Branch: refs/heads/5.0
>  Home:   https://github.com/pharo-project/pharo-core
>  Commit: b98668b7af70223826b1fcc4de3b4b3cb7916779
>  
> https://github.com/pharo-project/pharo-core/commit/b98668b7af70223826b1fcc4de3b4b3cb7916779
>  Author: Jenkins Build Server 
>  Date:   2016-02-24 (Wed, 24 Feb 2016)
> 
>  Changed paths:
>M Collections-Tests.package/ArrayTest.class/instance/tests - 
> fixture/test0FixtureIncludeTest.st
>M Collections-Tests.package/ArrayTest.class/instance/tests - 
> fixture/test0FixtureTConvertAsSetForMultiplinessTest.st
>M Collections-Tests.package/OrderedCollectionTest.class/instance/tests - 
> fixture/test0FixtureTConvertAsSetForMultiplinessTest.st
>M Collections-Tests.package/SortedCollectionTest.class/instance/tests - 
> fixture/test0FixtureTConvertAsSetForMultiplinessTest.st
>M Kernel-Tests.package/IntegerTest.class/instance/tests - mathematical 
> functions/testBigReceiverInexactNthRoot.st
>M Kernel-Tests.package/IntegerTest.class/instance/tests - mathematical 
> functions/testBigReceiverInexactSqrt.st
>M 
> Kernel-Tests.package/ScaledDecimalTest.class/instance/tests/testInexactNthRoot.st
>M 
> Kernel-Tests.package/ScaledDecimalTest.class/instance/tests/testInexactSqrt.st
>R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
> scripts/script50606.st
>A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
> scripts/script50607.st
>R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
> updates/update50606.st
>A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
> updates/update50607.st
>M 
> ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
> 
>  Log Message:
>  ---
>  50607
> 17638 Browsing calls on BoxedFloat64 shows methods with reference to Float in 
> the code
>   https://pharo.fogbugz.com/f/cases/17638
> 
> http://files.pharo.org/image/50/50607.zip
> 
> 

[Pharo-dev] I need some help for the menu inside ProfStef

[stepharo]

Hi guys

I wanted to shoot a video about ProfStef and the menus have been 
rubricixed :)

I need your help.

Stef

[Pharo-dev] [pharo-project/pharo-core] b98668: 50607

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: b98668b7af70223826b1fcc4de3b4b3cb7916779
  
https://github.com/pharo-project/pharo-core/commit/b98668b7af70223826b1fcc4de3b4b3cb7916779
  Author: Jenkins Build Server 
  Date:   2016-02-24 (Wed, 24 Feb 2016)

  Changed paths:
M Collections-Tests.package/ArrayTest.class/instance/tests - 
fixture/test0FixtureIncludeTest.st
M Collections-Tests.package/ArrayTest.class/instance/tests - 
fixture/test0FixtureTConvertAsSetForMultiplinessTest.st
M Collections-Tests.package/OrderedCollectionTest.class/instance/tests - 
fixture/test0FixtureTConvertAsSetForMultiplinessTest.st
M Collections-Tests.package/SortedCollectionTest.class/instance/tests - 
fixture/test0FixtureTConvertAsSetForMultiplinessTest.st
M Kernel-Tests.package/IntegerTest.class/instance/tests - mathematical 
functions/testBigReceiverInexactNthRoot.st
M Kernel-Tests.package/IntegerTest.class/instance/tests - mathematical 
functions/testBigReceiverInexactSqrt.st
M 
Kernel-Tests.package/ScaledDecimalTest.class/instance/tests/testInexactNthRoot.st
M 
Kernel-Tests.package/ScaledDecimalTest.class/instance/tests/testInexactSqrt.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50606.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50607.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50606.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50607.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  50607
17638 Browsing calls on BoxedFloat64 shows methods with reference to Float in 
the code
https://pharo.fogbugz.com/f/cases/17638

http://files.pharo.org/image/50/50607.zip

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50607
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] Spotter changes broke CodePanel

[Stephan Eggermont]

I used to do

CodePanel class>>spot
  GTSpotterMorph new
extent: (World width / 3.25 @ (World height / 2.25)) asIntegerPoint;
spotterModel: ((GTSpotter new)
processorsFilter: (CodePanelProcessorFilter new
  configuredWith: [ :aProcessor | aProcessor
actLogic: [ :aMethod :step |
  step exit.
  aMethod ifNil: [ self new openInWindowLabeled: 'Code panel'  ]
ifNotNil: [ |panel|
  panel := self new.
  panel openInWindowLabeled: 'Code panel'.
  panel newCardFor: aMethod.]];
candidatesLimit: 50 ]));
openCenteredInWorld

That now (since at least 50596) an interesting Brick error.
Do I need to change my code?

Stephan


THERE_BE_DRAGONS_HERE
SubscriptOutOfBounds: 0
24 February 2016 11:43:28.663692 am

VM: unix - i686 - linux-gnu - CoInterpreter VMMaker.oscog-eem.1664 uuid: 9e676eea-f638-4da0-bd70-920a096bda28 Jan 23 2016
StackToRegisterMappingCogit VMMaker.oscog-eem.1664 uuid: 9e676eea-f638-4da0-bd70-920a096bda28 Jan 23 2016
https://github.com/estebanlm/pharo-vm.git Commit: 8872c82ba7e8a56d06a95fb473501bde1b6ec807 Date: 2016-01-23 03:23:40 +0100 By: Esteban Lorenzano  Jenkins build #533

Image: Pharo5.0 [Latest update: #50596]

OrderedCollection(Object)>>errorSubscriptBounds:
	Receiver: an OrderedCollection()
	Arguments and temporary variables: 
		index: 	0
	Receiver's instance variables: 
		array: 	#(nil nil nil nil nil nil nil nil nil nil)
		firstIndex: 	1
		lastIndex: 	0


OrderedCollection>>at:
	Receiver: an OrderedCollection()
	Arguments and temporary variables: 
		anInteger: 	0
		index: 	nil
	Receiver's instance variables: 
		array: 	#(nil nil nil nil nil nil nil nil nil nil)
		firstIndex: 	1
		lastIndex: 	0


OrderedCollection(SequenceableCollection)>>last
	Receiver: an OrderedCollection()
	Arguments and temporary variables: 

	Receiver's instance variables: 
		array: 	#(nil nil nil nil nil nil nil nil nil nil)
		firstIndex: 	1
		lastIndex: 	0


GLMScrollPaneBandBrick(GLMBrick)>>lastSubbrick
	Receiver: a GLMScrollPaneBandBrick(318759936)
	Arguments and temporary variables: 

	Receiver's instance variables: 
		bounds: 	(506.0@291.0) corner: (556.0@331.0)
		owner: 	a GTSpotterResultsBrick(282528768)
		submorphs: 	an OrderedCollection(a GTSpotterCategoryTitleBrick(376809216) a GTSp...etc...
		fullBounds: 	nil
		color: 	Color transparent
		extension: 	a MorphExtension (105366528) [other:  (brickRenderer -> a GLMBrickRe...etc...
		brickBounds: 	a GLMBrickBounds
		brickApi: 	a GLMBrickWrapper
		asyncTask: 	nil
		scrollpane: 	a GTSpotterResultsBrick(282528768)
		shouldLayoutMorphs: 	false


GTSpotterResultsBrick(GLMScrollPaneBrick)>>isBottomOverscrolled
	Receiver: a GTSpotterResultsBrick(282528768)
	Arguments and temporary variables: 

	Receiver's instance variables: 
		bounds: 	(506.0@291.0) corner: (556.0@331.0)
		owner: 	a GLMScrollPaneBandBrick(418434816)
		submorphs: 	an OrderedCollection(a GLMScrollPaneBandBrick(318759936) a GLMScroll...etc...
		fullBounds: 	nil
		color: 	Color transparent
		extension: 	a MorphExtension (700898304) [other:  (brickRenderer -> a GLMBrickRe...etc...
		brickBounds: 	a GLMBrickBounds
		brickApi: 	a GLMBrickWrapper
		band: 	a GLMScrollPaneBandBrick(318759936)
		lastScrollTimeStamp: 	0
		scrollPosition: 	0
		verticalScrollbar: 	a GLMScrollbarBrick(1052137216)
		velocity: 	nil
		allowedBounds: 	(510.0@378.0) corner: (934.0@663.0)
		stepModel: 	a GTSpotterStep
		categories: 	a Dictionary(a GTSpotterCandidatesListProcessor->a GTSpotterCategor...etc...


GTSpotterResultsBrick(GLMScrollPaneBrick)>>scrollTo:
	Receiver: a GTSpotterResultsBrick(282528768)
	Arguments and temporary variables: 
		aBrick: 	a GTSpotterItemBrick(701435648)
		delta: 	378.0
	Receiver's instance variables: 
		bounds: 	(506.0@291.0) corner: (556.0@331.0)
		owner: 	a GLMScrollPaneBandBrick(418434816)
		submorphs: 	an OrderedCollection(a GLMScrollPaneBandBrick(318759936) a GLMScroll...etc...
		fullBounds: 	nil
		color: 	Color transparent
		extension: 	a MorphExtension (700898304) [other:  (brickRenderer -> a GLMBrickRe...etc...
		brickBounds: 	a GLMBrickBounds
		brickApi: 	a GLMBrickWrapper
		band: 	a GLMScrollPaneBandBrick(318759936)
		lastScrollTimeStamp: 	0
		scrollPosition: 	0
		verticalScrollbar: 	a GLMScrollbarBrick(1052137216)
		velocity: 	nil
		allowedBounds: 	(510.0@378.0) corner: (934.0@663.0)
		stepModel: 	a GTSpotterStep
		categories: 	a Dictionary(a GTSpotterCandidatesListProcessor->a GTSpotterCategor...etc...


GTSpotterResultsBrick>>onCandidateSelected:
	Receiver: a GTSpotterResultsBrick(282528768)
	Arguments and temporary variables: 
		ann: 	a GTSpotterCandidateSelected
		categoryBrick: 	a GTSpotterCategoryBrick(377964288)
		titleBrick: 	a GTSpotterCategoryTitleBrick(376809216)
		processor: 	a GTSpotterCandidatesListProcessor
	Receiver's instance variables: 
		bounds: 	(506.0@291.0) corner: (556.0@331.0)
		owner: 	a GLMScrollPaneBandBrick(418434816)
		submorphs: 	an OrderedCollection(a GLMScrollPaneBandB

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Re: Call for action for Roassal

[Alexandre Bergel]

> In any case, I wrote a simpler layout delegator in Roassal that delegates the 
> layouting to graphviz and it works reasonably well, so I could probably add 
> it to Roassal (you however need graphviz installed and it would add another 
> dependency to Roassal, which I'm not so keen on).

Where can we have it please?

Alexandre

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] [regression reporter]regression occurred

[Max Leske]

> On 24 Feb 2016, at 11:21, Sven Van Caekenberghe  wrote:
> 
> 
>> On 24 Feb 2016, at 11:09, Max Leske  wrote:
>> 
>> Here’s an idea:
>> 
>> 1. exclude Zinc tests from the validation tests
>> 2. after the build, trigger a Travis build on Github via API (I just set 
>> that up for Fuel, so I can provide help there)
>> 3. the Travis build only runs the Zinc tests
>> 4. read build results from Travis
>> 
>> Very ugly, I know. But it’s done rather quickly and should solve all the 
>> network problems.
> 
> I don't think the current problem is severe enough to put much work in it, 
> right now.
> 
> But would it not be much better to run everything (all tests) on Travis ? 
> 
> At first, maybe just as a limited experiment ? I would love to see that.

Sure. That wouldn’t be hard (although I think support for Windows is missing 
for the Smalltalk language, but I’m sure Fabio Niephaus would help us out 
there). We could use the Jenkins job as a trigger (or create a second job for 
experimenting first). In the long run, we probably would want to use the push / 
pull request hook to trigger the build but for quickly hacking things together 
I suggest using the API trigger.

I don’t have enough permissions on Github and Jenkins to pull this off alone 
but I’d be happy to help setting up the Travis stuff and providing the trigger 
script.

> 
>> Max
>> 
>>> On 24 Feb 2016, at 11:01, Marcus Denker  wrote:
>>> 
>>> The problem is that managing a CI server for a project like Pharo would be
>>> one full time engineer in a company, we do not have the manpower.
>>> 
>>> So we need to find solutions that are cheap to do.
>>> 
 On 24 Feb 2016, at 10:50, Ben Coman  wrote:
 
 Maybe there can be a pre-test run at the shell level to flag that the
 required network connectivity is available to run that test inside the
 image. Pharo startup could read them in while starting.
 cheers -ben
 
 On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker  
 wrote:
> one idea could be to add this to the filter of the CI runner.
> 
> It seems it fails due to network setup problems that are specific to the 
> CI server...
> 
>> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe  wrote:
>> 
>> The following test seems to be failing a lot lately on the CI 
>> infrastructure, yet it always succeeds for me on my machine. Is there 
>> anybody who sees this fail on their machines ?
>> 
>>> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
>>> 
>>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
>>> 
>>> 1 regressions found.
>>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
>> 
>> 
> 
> 
 
>>> 
>>> 
>> 
>> 
> 
> 

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

[Sven Van Caekenberghe]

> On 24 Feb 2016, at 11:24, Damien Cassou  wrote:
> 
> Tudor Girba  writes:
> 
>> Hi,
>> 
>> We need a bit of help with testing the order in Spotter. We do not have a 
>> real solution yet, but the current one should improve the situation.
>> 
>> We need a bit of feedback for this one:
>> https://pharo.fogbugz.com/f/cases/17656/Spotter-should-sort-search-results
>> 
>> Essentially, you would need to load the latest GT-Spotter and 
>> GT-SpotterExtensions-Core and let us know if it works better for spotting 
>> implementors or classes.
> 
> I have the impression this is already in the image. It seems to be
> working fine.

Yes, it works very well !

> Next time, it might help if you could just give us a Pharo
> expression that loads the patch.
> 
> -- 
> Damien Cassou
> http://damiencassou.seasidehosting.st
> 
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

[Damien Cassou]

Tudor Girba  writes:

> Hi,
>
> We need a bit of help with testing the order in Spotter. We do not have a 
> real solution yet, but the current one should improve the situation.
>
> We need a bit of feedback for this one:
> https://pharo.fogbugz.com/f/cases/17656/Spotter-should-sort-search-results
>
> Essentially, you would need to load the latest GT-Spotter and 
> GT-SpotterExtensions-Core and let us know if it works better for spotting 
> implementors or classes.

I have the impression this is already in the image. It seems to be
working fine. Next time, it might help if you could just give us a Pharo
expression that loads the patch.

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Re: [Pharo-dev] [regression reporter]regression occurred

[Sven Van Caekenberghe]

> On 24 Feb 2016, at 11:09, Max Leske  wrote:
> 
> Here’s an idea:
> 
> 1. exclude Zinc tests from the validation tests
> 2. after the build, trigger a Travis build on Github via API (I just set that 
> up for Fuel, so I can provide help there)
> 3. the Travis build only runs the Zinc tests
> 4. read build results from Travis
> 
> Very ugly, I know. But it’s done rather quickly and should solve all the 
> network problems.

I don't think the current problem is severe enough to put much work in it, 
right now.

But would it not be much better to run everything (all tests) on Travis ? 

At first, maybe just as a limited experiment ? I would love to see that.

> Max
> 
>> On 24 Feb 2016, at 11:01, Marcus Denker  wrote:
>> 
>> The problem is that managing a CI server for a project like Pharo would be
>> one full time engineer in a company, we do not have the manpower.
>> 
>> So we need to find solutions that are cheap to do.
>> 
>>> On 24 Feb 2016, at 10:50, Ben Coman  wrote:
>>> 
>>> Maybe there can be a pre-test run at the shell level to flag that the
>>> required network connectivity is available to run that test inside the
>>> image. Pharo startup could read them in while starting.
>>> cheers -ben
>>> 
>>> On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker  
>>> wrote:
 one idea could be to add this to the filter of the CI runner.
 
 It seems it fails due to network setup problems that are specific to the 
 CI server...
 
> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe  wrote:
> 
> The following test seems to be failing a lot lately on the CI 
> infrastructure, yet it always succeeds for me on my machine. Is there 
> anybody who sees this fail on their machines ?
> 
>> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
>> 
>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
>> 
>> 1 regressions found.
>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
> 
> 
 
 
>>> 
>> 
>> 
> 
> 

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Re: Call for action for Roassal

[Peter Uhnák]

On Wed, Feb 24, 2016 at 11:03 AM, Martin Bähr <
mba...@email.archlab.tuwien.ac.at> wrote:

> Excerpts from Peter Uhnák's message of 2016-02-24 10:35:05 +0100:
> > In any case, I wrote a simpler layout delegator in Roassal that delegates
> > the layouting to graphviz and it works reasonably well, so I could
> probably
> > add it to Roassal (you however need graphviz installed and it would add
> > another dependency to Roassal, which I'm not so keen on).
>
> how does that work? does it ask graphviz for the position of the nodes and
> then
> recreate that in roassal?
>

Yes, I generate .dot file that describes the nodes I want the layout for
(that includes the dimensions of it), and then the .dot file is passed to
GraphViz… from there I parse the generated SVG file (they can also output
other formats like txt, or xml) and move the Roassal nodes.


>
> > Maybe also OGDF (http://ogdf.net/doku.php) could be used if you are ok
> with
> > GPL… they have their own graph format so there could be some interaction.
>
> this would work the same as with graphviz as an additional dependency on
> ogdf, right?
>

GraphViz is good enough for generic graphs, but OGDF is well-founded and
much more powerful layouting library. However C++ coding is required if one
wants to use it.

Peter

Re: [Pharo-dev] [regression reporter]regression occurred

[Max Leske]

Here’s an idea:

1. exclude Zinc tests from the validation tests
2. after the build, trigger a Travis build on Github via API (I just set that 
up for Fuel, so I can provide help there)
3. the Travis build only runs the Zinc tests
4. read build results from Travis

Very ugly, I know. But it’s done rather quickly and should solve all the 
network problems.

Max

> On 24 Feb 2016, at 11:01, Marcus Denker  wrote:
> 
> The problem is that managing a CI server for a project like Pharo would be
> one full time engineer in a company, we do not have the manpower.
> 
> So we need to find solutions that are cheap to do.
> 
>> On 24 Feb 2016, at 10:50, Ben Coman  wrote:
>> 
>> Maybe there can be a pre-test run at the shell level to flag that the
>> required network connectivity is available to run that test inside the
>> image. Pharo startup could read them in while starting.
>> cheers -ben
>> 
>> On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker  
>> wrote:
>>> one idea could be to add this to the filter of the CI runner.
>>> 
>>> It seems it fails due to network setup problems that are specific to the CI 
>>> server...
>>> 
 On 24 Feb 2016, at 09:07, Sven Van Caekenberghe  wrote:
 
 The following test seems to be failing a lot lately on the CI 
 infrastructure, yet it always succeeds for me on my machine. Is there 
 anybody who sees this fail on their machines ?
 
> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
> 
> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
> 
> 1 regressions found.
> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
 
 
>>> 
>>> 
>> 
> 
> 

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

[Guillaume Larcheveque]

You can try it with:
Metacello new
   smalltalkhubUser: 'KevinLanvin' project: 'MaterialDesignLite';
   configuration: 'MaterialDesignLite';
   version: #development;
   load: #(#colors)

2016-02-23 9:13 GMT+01:00 stepharo :

> Hi
>
> Guillaume Larcheveque in Telescope added support for MDLColor
> http://www.materialui.co/colors
>
> and nice gradient building.
>
> I asked him if we could extract this functionality and move it into Pharo
> because
> it will be usefull for Pharo, Bloc, and Roassal.
>
> A first step could be to have MDLColor subclass as it is now
> but the second step would be to rethink Color and palette.
>
> May be we should have some Palette
>
> And we could have (brainstorming)
>
> (ColorBuilder from: MDLPalette)
> -> aColorBuilder
>   aColorBuilder red
> -> 
>
> Stef
>
>
>


-- 
*Guillaume Larcheveque*

[Pharo-dev] [pharo-project/pharo-core] 9d9b04: 50606

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 9d9b040d8c8f350adaddfa76e695fb04908b7442
  
https://github.com/pharo-project/pharo-core/commit/9d9b040d8c8f350adaddfa76e695fb04908b7442
  Author: Jenkins Build Server 
  Date:   2016-02-24 (Wed, 24 Feb 2016)

  Changed paths:
A 
ConfigurationOfSton.package/ConfigurationOfSton.class/class/accessing/catalogContactInfo.st
A 
ConfigurationOfSton.package/ConfigurationOfSton.class/class/accessing/catalogDescription.st
A 
ConfigurationOfSton.package/ConfigurationOfSton.class/class/accessing/catalogKeywords.st
M ConfigurationOfSton.package/ConfigurationOfSton.class/instance/symbolic 
versions/stable_.st
A 
ConfigurationOfSton.package/ConfigurationOfSton.class/instance/versions/version15_.st
A 
ConfigurationOfSton.package/ConfigurationOfSton.class/instance/versions/version16_.st
A 
ConfigurationOfSton.package/ConfigurationOfSton.class/instance/versions/version17_.st
A STON-Core.package/STON.class/class/accessing/associationClass.st
A STON-Core.package/STON.class/class/convencience/fromStreamWithComments_.st
A STON-Core.package/STON.class/class/convencience/fromStringWithComments_.st
A STON-Core.package/STONCStyleCommentsSkipStream.class/README.md
A STON-Core.package/STONCStyleCommentsSkipStream.class/class/instance 
creation/on_.st
A STON-Core.package/STONCStyleCommentsSkipStream.class/definition.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/collectionSpecies.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/next.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/nextLine.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/next_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/next_into_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/next_into_startingAt_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/peek.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/peekFor_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/position.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/readInto_startingAt_count_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/skip_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/upToEnd.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/upTo_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/accessing/wrappedStream.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/initialize-release/close.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/initialize-release/on_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/consumeComment.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/consumeToCommentEnd.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/consumeToEOL.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/escape.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/handleStringDelimiter_.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/insideString.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/private/nextNonCommentChar.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/testing/atEnd.st
A 
STON-Core.package/STONCStyleCommentsSkipStream.class/instance/testing/isBinary.st
M STON-Core.package/STONReader.class/instance/parsing/parseValue.st
M STON-Core.package/STONWriter.class/class/class 
initialization/initializeSTONCharacters.st
M STON-Core.package/STONWriter.class/definition.st
A 
STON-Core.package/STONWriter.class/instance/initialize-release/asciiOnly_.st
M 
STON-Core.package/STONWriter.class/instance/initialize-release/initialize.st
M STON-Core.package/STONWriter.class/instance/private/encodeCharacter_.st
M STON-Core.package/extension/Association/instance/stonOn_.st
A STON-Core.package/extension/Class/class/fromSton_.st
A STON-Core.package/extension/Class/instance/stonOn_.st
A 
STON-Core.package/extension/ClassDescription/instance/stonContainSubObjects.st
A STON-Core.package/extension/Metaclass/class/fromSton_.st
A STON-Core.package/extension/TApplyingOnClassSide/instance/stonName.st
A STON-Core.package/extension/TApplyingOnClassSide/instance/stonOn_.st
A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/README.md
A STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/definition.st
A 
STON-Tests.package/STONCStyleCommentsSkipStreamTests.class/instance/testing/testCommen

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50606
  Home:   https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [regression reporter]regression occurred

[Marcus Denker]

The problem is that managing a CI server for a project like Pharo would be
one full time engineer in a company, we do not have the manpower.

So we need to find solutions that are cheap to do.

> On 24 Feb 2016, at 10:50, Ben Coman  wrote:
> 
> Maybe there can be a pre-test run at the shell level to flag that the
> required network connectivity is available to run that test inside the
> image. Pharo startup could read them in while starting.
> cheers -ben
> 
> On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker  wrote:
>> one idea could be to add this to the filter of the CI runner.
>> 
>> It seems it fails due to network setup problems that are specific to the CI 
>> server...
>> 
>>> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe  wrote:
>>> 
>>> The following test seems to be failing a lot lately on the CI 
>>> infrastructure, yet it always succeeds for me on my machine. Is there 
>>> anybody who sees this fail on their machines ?
>>> 
 On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
 
 https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
 
 1 regressions found.
 Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
>>> 
>>> 
>> 
>> 
> 

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

[Glenn Cavarlé]

Hi,
In my memories, a first implementation of material colors was also made by
Alex in Brick packages.
This can be a inspiration source, too.



-
Glenn Cavarlé
--
View this message in context: 
http://forum.world.st/Bloc-MDLColor-and-new-gradient-tp4879795p4880198.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] [regression reporter]regression occurred

[Sven Van Caekenberghe]

> On 24 Feb 2016, at 10:50, Ben Coman  wrote:
> 
> Maybe there can be a pre-test run at the shell level to flag that the
> required network connectivity is available to run that test inside the
> image. Pharo startup could read them in while starting.

These networking problems are issues specific to the CI infrastructure. But 
these are real bugs: we don't know why they happen, we have no idea. It is not 
that there is no network, else almost everything would fail immediately. It 
should not be too much asked in the 21st century for a server to be able to 
access any website, right ?

> cheers -ben
> 
> On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker  wrote:
>> one idea could be to add this to the filter of the CI runner.
>> 
>> It seems it fails due to network setup problems that are specific to the CI 
>> server...
>> 
>>> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe  wrote:
>>> 
>>> The following test seems to be failing a lot lately on the CI 
>>> infrastructure, yet it always succeeds for me on my machine. Is there 
>>> anybody who sees this fail on their machines ?
>>> 
 On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
 
 https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
 
 1 regressions found.
 Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
>>> 
>>> 
>> 
>> 
> 

Re: [Pharo-dev] [regression reporter]regression occurred

[Ben Coman]

Maybe there can be a pre-test run at the shell level to flag that the
required network connectivity is available to run that test inside the
image. Pharo startup could read them in while starting.
cheers -ben

On Wed, Feb 24, 2016 at 5:38 PM, Marcus Denker  wrote:
> one idea could be to add this to the filter of the CI runner.
>
> It seems it fails due to network setup problems that are specific to the CI 
> server...
>
>> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe  wrote:
>>
>> The following test seems to be failing a lot lately on the CI 
>> infrastructure, yet it always succeeds for me on my machine. Is there 
>> anybody who sees this fail on their machines ?
>>
>>> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
>>>
>>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
>>>
>>> 1 regressions found.
>>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
>>
>>
>
>

Re: [Pharo-dev] Starting to add class comment and test on BlElements

[Glenn Cavarlé]

Hi Stef,

Yes, BlElement is the starting point, i think so.
All examples in BlElement run for me, do you have some errors ?
On my side, i'm starting to write examples using layouts.

We can talk about the performances issue later (if asserts really have an
impact on) , when the first stable version will be released.
But for now, i think using asserts is a good choice to make things clear and
to help the understanding and the documentation (same for the 
pragma).

Glenn.



-
Glenn Cavarlé
--
View this message in context: 
http://forum.world.st/Starting-to-add-class-comment-and-test-on-BlElements-tp4879800p4880193.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

[Anne Etien]

> Le 24 févr. 2016 à 10:35, Peter Uhnák  a écrit :
> 
> 
> 
> On Wed, Feb 24, 2016 at 10:28 AM, Anne Etien  > wrote:
> Hi Alexandre,
> 
> In a wonderful world, I would like:
> - a real graph layout (like in graphviz) that can take into account around 
> hundred nodes and several hundred of edges and place the nodes in order to 
> see something. Currently, I have to use the circle layout and it looks 
> strange.
> 
> Unfortunately making real graph layouts is really hard issue… I've wrote my 
> bachelor thesis about this and didn't get very far; it's bit of a nightmare 
> if you don't have good foundations. :’(

I know. I tried but my mathematical background and my time were not enough. I 
got the research paper explaining the algorithm of Graphviz but even with that, 
it was very complex. However, since some tools (as graphviz) do it, we should 
have it.

Anne
> 
> In any case, I wrote a simpler layout delegator in Roassal that delegates the 
> layouting to graphviz and it works reasonably well, so I could probably add 
> it to Roassal (you however need graphviz installed and it would add another 
> dependency to Roassal, which I'm not so keen on).
> 
> Maybe also OGDF (http://ogdf.net/doku.php ) could 
> be used if you are ok with GPL… they have their own graph format so there 
> could be some interaction.
> 
> Peter
> ___
> Moose-dev mailing list
> moose-...@list.inf.unibe.ch
> https://www.list.inf.unibe.ch/listinfo/moose-dev

Re: [Pharo-dev] [regression reporter]regression occurred

[Ben Coman]

On Wed, Feb 24, 2016 at 4:07 PM, Sven Van Caekenberghe  wrote:
> The following test seems to be failing a lot lately on the CI infrastructure,

On a related topic, its hard for an individual person to notice when
this sort of commonly failing test occurs.  All they see is the one
issue they are working on. Having a daily email of the top 5 failing
tests would help  quicker squash such cases. But probably just an idea
for the back burner.
cheers -ben

> yet it always succeeds for me on my machine. Is there anybody who sees this 
> fail on their machines ?
>
>> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
>>
>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
>>
>> 1 regressions found.
>>  Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
>
>

Re: [Pharo-dev] [regression reporter]regression occurred

[Marcus Denker]

one idea could be to add this to the filter of the CI runner.

It seems it fails due to network setup problems that are specific to the CI 
server...

> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe  wrote:
> 
> The following test seems to be failing a lot lately on the CI infrastructure, 
> yet it always succeeds for me on my machine. Is there anybody who sees this 
> fail on their machines ?
> 
>> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
>> 
>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
>> 
>> 1 regressions found.
>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
> 
> 

Re: [Pharo-dev] [Moose-dev] Re: Call for action for Roassal

[Peter Uhnák]

On Wed, Feb 24, 2016 at 10:28 AM, Anne Etien 
wrote:

> Hi Alexandre,
>
> In a wonderful world, I would like:
> - a real graph layout (like in graphviz) that can take into account around
> hundred nodes and several hundred of edges and place the nodes in order to
> see something. Currently, I have to use the circle layout and it looks
> strange.
>

Unfortunately making real graph layouts is really hard issue… I've wrote my
bachelor thesis about this and didn't get very far; it's bit of a nightmare
if you don't have good foundations. :'(

In any case, I wrote a simpler layout delegator in Roassal that delegates
the layouting to graphviz and it works reasonably well, so I could probably
add it to Roassal (you however need graphviz installed and it would add
another dependency to Roassal, which I'm not so keen on).

Maybe also OGDF (http://ogdf.net/doku.php) could be used if you are ok with
GPL… they have their own graph format so there could be some interaction.

Peter

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

[Alexandre Bergel]

> - the possibility to place hangout of the edges on nodes (as box) more 
> flexible. Indeed, I am reverse engineering a database containing around 80 
> tables and lot of foreign keys and the result is not readable since the edge 
> are orthogonal starting from the top or the bottom of the box corresponding 
> to the column name. I would like a real entity-relation diagram. 

Do you have a screenshot showing the issue?

> If you want, I can show you the current stage of the visu (once again done in 
> Telescope on top of Roassal) in order that you see on real data how uggly it 
> is.

Yes please, some screenshots would help

Alexandre

> 
> Cheers,
> Anne
> 
>> Le 24 févr. 2016 à 09:51, Alexandre Bergel  a écrit 
>> :
>> 
>> Dear community,
>> 
>> As you may have seen, Roassal has entered a stabilization phase. The book 
>> AgileVisualization.com will soon be released. After its release, Roassal 
>> will go over a new development phase. In order to prepare it, I am asking 
>> this question:
>> 
>>  What are the 3 aspects you would like to see improved in Roassal?
>> 
>> You can answer publicly or by sending private messages.
>> 
>> Kind regards,
>> Alexandre
>> -- 
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> 
>> 
>> 
>> ___
>> Moose-dev mailing list
>> moose-...@list.inf.unibe.ch
>> https://www.list.inf.unibe.ch/listinfo/moose-dev
> 
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

[Anne Etien]

Hi Alexandre,

In a wonderful world, I would like:
- a real graph layout (like in graphviz) that can take into account around 
hundred nodes and several hundred of edges and place the nodes in order to see 
something. Currently, I have to use the circle layout and it looks strange. 
- the possibility to place hangout of the edges on nodes (as box) more 
flexible. Indeed, I am reverse engineering a database containing around 80 
tables and lot of foreign keys and the result is not readable since the edge 
are orthogonal starting from the top or the bottom of the box corresponding to 
the column name. I would like a real entity-relation diagram. 

For the remainder, I use only Telescope since I have just to specify my data 
and not to script the visualization taking into account the order of the 
instructions… So don’t change the interface of the existing API in order we can 
continue to use Telescope on top on Roassal.

 If you want, I can show you the current stage of the visu (once again done in 
Telescope on top of Roassal) in order that you see on real data how uggly it is.

Cheers,
Anne

> Le 24 févr. 2016 à 09:51, Alexandre Bergel  a écrit :
> 
> Dear community,
> 
> As you may have seen, Roassal has entered a stabilization phase. The book 
> AgileVisualization.com will soon be released. After its release, Roassal will 
> go over a new development phase. In order to prepare it, I am asking this 
> question:
> 
>   What are the 3 aspects you would like to see improved in Roassal?
> 
> You can answer publicly or by sending private messages.
> 
> Kind regards,
> Alexandre
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
> ___
> Moose-dev mailing list
> moose-...@list.inf.unibe.ch
> https://www.list.inf.unibe.ch/listinfo/moose-dev

Re: [Pharo-dev] [pharo-project/pharo-core] 91c994: 50605

[Marcus Denker]

> 
>  Log Message:
>  ---
>  50605
> Moose
> 
> http://files.pharo.org/image/50/50605.zip
> 
> 
this is

17659 GTPlayground does not highlight defined implicit variables
https://pharo.fogbugz.com/f/cases/17659/

17656 Spotter should sort search results
https://pharo.fogbugz.com/f/cases/17656/

17668 Spotter should allow filtering categories that have space
https://pharo.fogbugz.com/f/cases/17668/


Marcus

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50605
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 91c994: 50605

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 91c994b57d1070c33831a3dc85cbeee58f77d06e
  
https://github.com/pharo-project/pharo-core/commit/91c994b57d1070c33831a3dc85cbeee58f77d06e
  Author: Jenkins Build Server 
  Date:   2016-02-24 (Wed, 24 Feb 2016)

  Changed paths:
M 
ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic
 versions/stable_.st
A 
ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version32_.st
M 
ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic
 versions/stable_.st
A 
ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version32_.st
M 
ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic
 versions/stable_.st
A 
ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version22_.st
M 
ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic
 versions/stable_.st
A 
ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version313_.st
M 
ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic
 versions/stable_.st
A 
ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version43_.st
M 
GT-Spotter.package/GTFilterSubstring.class/instance/private/applyFilterWithQuery.st
A 
GT-Spotter.package/GTFilterSubstring.class/instance/private/indexForItemName_andQuery_.st
R 
GT-Spotter.package/GTFilterSubstring.class/instance/private/indexForItem_.st
M GT-Spotter.package/GTSpotterCandidatesListProcessor.class/definition.st
A 
GT-Spotter.package/GTSpotterCandidatesListProcessor.class/instance/accessing/sort.st
A 
GT-Spotter.package/GTSpotterCandidatesListProcessor.class/instance/scripting/sort_.st
A 
GT-Spotter.package/GTSpotterCategoryBrick.class/instance/adding/addItem_.st
A 
GT-Spotter.package/GTSpotterCategoryBrick.class/instance/adding/addItems_.st
R GT-Spotter.package/GTSpotterCategoryBrick.class/instance/as yet 
unclassified/addItem_.st
M GT-Spotter.package/GTSpotterHelp.class/class/accessing/pages.st
A 
GT-Spotter.package/GTSpotterHelp.class/class/documentation/basicExamples.st
A 
GT-Spotter.package/GTSpotterHelp.class/class/documentation/categoryFilterExamples.st
A 
GT-Spotter.package/GTSpotterHelp.class/class/documentation/diveInCategoryExamples.st
A 
GT-Spotter.package/GTSpotterHelp.class/class/documentation/diveInExamples.st
A 
GT-Spotter.package/GTSpotterHelp.class/class/documentation/extensionExamples.st
M GT-Spotter.package/GTSpotterHelp.class/class/documentation/extensions.st
M 
GT-Spotter.package/GTSpotterHelp.class/class/documentation/extensionsString.st
A 
GT-Spotter.package/GTSpotterResultsBrick.class/instance/adding/addItems_to_.st
M GT-Spotter.package/GTSpotterResultsBrick.class/instance/event 
handling/onAllCandidatesAdded_.st
M 
GT-Spotter.package/GTSpotterStep.class/instance/private/basicRelevantProcessorsProcess_do_.st
A 
GT-Spotter.package/GTSpotterStep.class/instance/private/processor_isRelevantForQuery_.st
M 
Glamour-Morphic-Renderer.package/GLMMorphicPharoScriptRenderer.class/instance/rendering/morph.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50604.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50605.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50604.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50605.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  50605
Moose

http://files.pharo.org/image/50/50605.zip

[Pharo-dev] Call for action for Roassal

[Alexandre Bergel]

Dear community,

As you may have seen, Roassal has entered a stabilization phase. The book 
AgileVisualization.com will soon be released. After its release, Roassal will 
go over a new development phase. In order to prepare it, I am asking this 
question:

What are the 3 aspects you would like to see improved in Roassal?

You can answer publicly or by sending private messages.

Kind regards,
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] [regression reporter]regression occurred

[Max Leske]

OS X 10.11.3

./pharo Pharo.image test --junit-xml-output 
'^(?!Metacello)(?!NativeBoost)[M-Z].*'

4146 run, 4122 passes, 17 failures, 7 errors.


Output from the CI build:

4146 run, 4121 passes, 17 failures, 8 errors.

> On 24 Feb 2016, at 09:07, Sven Van Caekenberghe  wrote:
> 
> The following test seems to be failing a lot lately on the CI infrastructure, 
> yet it always succeeds for me on my machine. Is there anybody who sees this 
> fail on their machines ?
> 
>> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
>> 
>> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
>> 
>> 1 regressions found.
>> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS
> 
> 

Re: [Pharo-dev] [regression reporter]regression occurred

[Sven Van Caekenberghe]

The following test seems to be failing a lot lately on the CI infrastructure, 
yet it always succeeds for me on my machine. Is there anybody who sees this 
fail on their machines ?

> On 24 Feb 2016, at 08:36, no-re...@ci.inria.fr wrote:
> 
> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=mac/755/
> 
> 1 regressions found.
>  Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS