Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

2015-09-17 1:18 GMT+02:00 John Brant : > On 9/16/2015 10:34 AM, Ben Coman wrote: > >> On Wed, Sep 16, 2015 at 4:56 PM, Nicolai Hess wrote: >> >>> The following method compiles with Opal: >>> >>> createRedMorph >>> ^ (self new color:Color red); yourself >>> >>> but gives a syntax error with t

Re: [Pharo-dev] Remove rule "References an abstract class"

Hi. First of all: thank you for the feedback Damien! It makes sense, the rule also has higher amount of negative feedback. I will remove it from QA, let it stay in the image, it actually can be useful. Uko > On 17 Sep 2015, at 06:49, Damien Cassou wrote: > > This lint rule pops up all the ti

Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

2015-09-16 15:14 GMT+02:00 Thierry Goubier : > Argh, sent too early: > > self new color: Color red; yourself > > est bien une cascade, non? > Yes, but in (self new color: Color red); yourself the expression in parenthesis looks like "this evalulates first, to 'anObject' ", so we send " ; yoursel

Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

2015-09-17 9:10 GMT+02:00 Nicolai Hess : > > > 2015-09-16 15:14 GMT+02:00 Thierry Goubier : > >> Argh, sent too early: >> >> self new color: Color red; yourself >> >> est bien une cascade, non? >> > > Yes, but in > > (self new color: Color red); yourself > the expression in parenthesis looks like

Re: [Pharo-dev] Remove rule "References an abstract class"

You can probably remove it directly from Pharo instead https://pharo.fogbugz.com/f/cases/15858/review-rule-RBAbstractClassRule Peter On Thu, Sep 17, 2015 at 9:09 AM, Yuriy Tymchuk wrote: > Hi. > > First of all: thank you for the feedback Damien! > It makes sense, the rule also has higher amount

[Pharo-dev] [Reflectivity] Links on Block creation vs. execution

Hi, For blocks, we now have the correct model to destinguish “block creation” from “block execution”: 1) put a link on the block node, it will be called when the block definition (creation) is executed. e.g. when you put a before link on the block in this method, it will be called when you ex

[Pharo-dev] [pharo-project/pharo-core] feb71a: 50329

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: feb71a8705982cbb829e2678703c07d2131e71d8 https://github.com/pharo-project/pharo-core/commit/feb71a8705982cbb829e2678703c07d2131e71d8 Author: Jenkins Build Server Date: 2015-09-17 (Thu, 17 Sep 2015

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

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

Re: [Pharo-dev] SyntaxError: parentheses; cascades and yourself (Opal vs. old compilers parser)

> On 17 Sep 2015, at 09:32, Thierry Goubier wrote: > > > > 2015-09-17 9:10 GMT+02:00 Nicolai Hess : > > > 2015-09-16 15:14 GMT+02:00 Thierry Goubier : > Argh, sent too early: > > self new color: Color red; yourself > > est bien une cascade, non? > > Yes, but in > > (self new color: Colo

Re: [Pharo-dev] Rubric/Event handling issue?

ping On 15-09-15 17:49, Stephan Eggermont wrote: There is an interesting bad interaction between my drag-and-drop code and Rubric. It kills all Rubric editors at the same time, so it looks to me like a problem with the Rubric background thread interacting with mouseMove or mouseEnter/Leave. htt

Re: [Pharo-dev] Remove rule "References an abstract class"

Ok, it can be removed from Pharo… I still find it useful as well as missing yourself, but I can keep track of then individually :) > On 17 Sep 2015, at 09:39, Peter Uhnák wrote: > > You can probably remove it directly from Pharo instead > https://pharo.fogbugz.com/f/cases/15858/review-rule-RBA

Re: [Pharo-dev] Remove rule "References an abstract class"

yes the problem with rules comes when the rule add more noise than is helpful. If you do not want to remove this rule because it is useful in some cases, maybe the rule could check only these specific situations to do not add noise in others. Le 17 sept. 2015 à 10:37, Yuriy Tymchuk a écrit : >

Re: [Pharo-dev] Contribution scheme confusing ...

Yes we know. Now we are full. Sorry I cannot clone ourselves. Else I would do it. Stef Le 16/9/15 22:17, Torsten Bergmann a écrit : We are in a transition to use more and more ConfigurationOf to manage packages included in Pharo 5. But neither the new help topic "How to contribute to Pharo

Re: [Pharo-dev] Rubric/Event handling issue?

I forwarded to alain. Now this is the restart of the university... Stef Le 15/9/15 17:49, Stephan Eggermont a écrit : There is an interesting bad interaction between my drag-and-drop code and Rubric. It kills all Rubric editors at the same time, so it looks to me like a problem with the Rubric

Re: [Pharo-dev] Remove rule "References an abstract class"

Well, what I am saying is that I agree that people should not be bothered with this rule by QualityAssistant. But why we should remove the rule from the image? Uko > On 17 Sep 2015, at 12:11, Christophe Demarey > wrote: > > yes the problem with rules comes when the rule add more noise than

Re: [Pharo-dev] Remove rule "References an abstract class"

> On 17 Sep 2015, at 12:50, Yuriy Tymchuk wrote: > > Well, what I am saying is that I agree that people should not be bothered > with this rule by QualityAssistant. But why we should remove the rule from > the image? > Because it is wrong? If we keep it, people will see it when they use the C

Re: [Pharo-dev] Rubric/Event handling issue?

On Tue, Sep 15, 2015 at 11:49 PM, Stephan Eggermont wrote: > There is an interesting bad interaction between my drag-and-drop code and > Rubric. It kills all Rubric editors at the same time, so it looks > to me like a problem with the Rubric background thread interacting with > mouseMove or mouseE

Re: [Pharo-dev] Pedantic on Random>>nextValue method name

-Original Message- From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Ben Coman Sent: Wednesday, September 16, 2015 6:39 PM To: Pharo Development List Subject: Re: [Pharo-dev] Pedantic on Random>>nextValue method name On Wed, Sep 16, 2015 at 11:22 PM, Henrik Nergaar

Re: [Pharo-dev] Contribution scheme confusing ...

> On 16 Sep 2015, at 22:17, Torsten Bergmann wrote: > > We are in a transition to use more and more ConfigurationOf > to manage packages included in Pharo 5. > Yes, and it is a mess. > But neither the new help topic "How to contribute to Pharo base code" > nor the link it points to http:

Re: [Pharo-dev] Remove rule "References an abstract class"

Because people can choose in critic browser what they want to see. At least this is my opinion. As a sneak peek to the survey results I can say that there are people who find the removed of “missing yourself” rule as a negative change. Of course they are only a few of them, but as you are not ab

Re: [Pharo-dev] Remove rule "References an abstract class"

> On 17 Sep 2015, at 14:08, Yuriy Tymchuk wrote: > > Because people can choose in critic browser what they want to see. At least > this is my opinion. As a sneak peek to the survey results I can say that > there are people who find the removed of “missing yourself” rule as a > negative change

Re: [Pharo-dev] Remove rule "References an abstract class"

Well, for me it’s ok. Then I don’t have to create a new version in conf :). > On 17 Sep 2015, at 14:17, Marcus Denker wrote: > > >> On 17 Sep 2015, at 14:08, Yuriy Tymchuk wrote: >> >> Because people can choose in critic browser what they want to see. At least >> this is my opinion. As a sne

[Pharo-dev] [pharo-project/pharo-core] 7586c2: 50330

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 7586c211f6842acc22a041ac7df29bc8fffbb659 https://github.com/pharo-project/pharo-core/commit/7586c211f6842acc22a041ac7df29bc8fffbb659 Author: Jenkins Build Server Date: 2015-09-17 (Thu, 17 Sep 2015

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

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

Re: [Pharo-dev] Rubric/Event handling issue?

On 17-09-15 13:59, Ben Coman wrote: On Tue, Sep 15, 2015 at 11:49 PM, Stephan Eggermont wrote: There is an interesting bad interaction between my drag-and-drop code and Rubric. It kills all Rubric editors at the same time, so it looks to me like a problem with the Rubric background thread inter

[Pharo-dev] About the Unicode class

Hi, Does anyone know why there are so many class variables in Unicode and what they are used for? Most of them have no sender. EncodedCharSet subclass: #Unicode instanceVariableNames: '' classVariableNames: 'Cc Cf Cn Co Cs DecimalProperty GeneralCategory Ll Lm Lo Lt Lu Mc Me Mn

Re: [Pharo-dev] Contribution scheme confusing ...

>> >> Also: >> I did a simple fix on NautilusGroupAutoBuilder package - there is >> a ConfigurationOfNautilusGroupAutoBuilder. But is it managed internally >> or externally now? >> > Even I can not tell you. > I think the rule we should adopt: if there is a dedicated repository defined in the

Re: [Pharo-dev] Contribution scheme confusing ...

Exactly! This is the cheapest way to document the process. We could even try to automatically remove the inbox if there is another repository associated with a package. What do you think? Cheers, Doru On Thu, Sep 17, 2015 at 3:40 PM, Marcus Denker wrote: > >> > >> Also: > >> I did a simple f

[Pharo-dev] EncodedCharSets

Hi again, Does anyone know the rationale behind this? declareEncodedCharSet: anEncodedCharSetOrLanguageEnvironmentClass atIndex: aNumber EncodedCharSets at: aNumber put: anEncodedCharSetOrLanguageEnvironmentClass "this method is used to modularize the old initi

Re: [Pharo-dev] Contribution scheme confusing ...

Hi Marcus, Could work - but is a fragile rule. We should document it somewhere. What about providing this info directly in the image. Alexandre has already added a help topic on how to contribute (but yet only for the slice process). I changed it so we can have the differences of config manage

Re: [Pharo-dev] EncodedCharSets

> On 17 Sep 2015, at 4:09 , Christophe Demarey > wrote: > > Hi again, > > Does anyone know the rationale behind this? > > declareEncodedCharSet: anEncodedCharSetOrLanguageEnvironmentClass atIndex: > aNumber > > EncodedCharSets at: aNumber put: > anEncodedCharSetOrLanguageEnvironmentC

[Pharo-dev] [Reflectivity] Links on Class Variables

Hi, We can put meta links on AST Nodes. But with Variables being represented by Objects in Pharo, it is easy to allow those to be annotated, too. With the changes from https://pharo.fogbugz.com/f/cases/16596/before-for-Class-Variable

Re: [Pharo-dev] [review needed] speed up RBClassNotReferencedRule

Marcus Denker-4 wrote > Hi, > > Review needed for > > > https://pharo.fogbugz.com/f/cases/16074/Is-RBClassNotReferencedRule-200x-slower-in-Pharo-4-vs-Pharo-3 > > Speedup can be checked with: > > rule:=RBClassNotReferencedRule new. > environment:=RBBrowserEnvironment new forPackageNames: #('Fue

Re: [Pharo-dev] About the Unicode class

> On 17 Sep 2015, at 2:58 , Christophe Demarey > wrote: > > Hi, > > Does anyone know why there are so many class variables in Unicode and what > they are used for? > Most of them have no sender. > > EncodedCharSet subclass: #Unicode > instanceVariableNames: '' > classVariableName

Re: [Pharo-dev] About the Unicode class

There has been some work on Squeak by Levente in this area, maybe it's time to harvest... 2015-09-17 18:22 GMT+02:00 Henrik Johansen : > > On 17 Sep 2015, at 2:58 , Christophe Demarey > wrote: > > Hi, > > Does anyone know why there are so many class variables in Unicode and what > they are used

Re: [Pharo-dev] EncodedCharSets

Hi Christophe, On Thu, Sep 17, 2015 at 7:09 AM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi again, > > Does anyone know the rationale behind this? > > declareEncodedCharSet: anEncodedCharSetOrLanguageEnvironmentClass atIndex: > aNumber > > EncodedCharSets at: aNumber put

Re: [Pharo-dev] Pedantic on Random>>nextValue method name

On Thu, Sep 17, 2015 at 7:56 PM, Henrik Nergaard wrote: > > > -Original Message- > From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Ben > Coman > Sent: Wednesday, September 16, 2015 6:39 PM > To: Pharo Development List > Subject: Re: [Pharo-dev] Pedantic on Random>>

Re: [Pharo-dev] Rubric/Event handling issue?

On Thu, Sep 17, 2015 at 8:47 PM, Stephan Eggermont wrote: > On 17-09-15 13:59, Ben Coman wrote: >> >> On Tue, Sep 15, 2015 at 11:49 PM, Stephan Eggermont >> wrote: >>> >>> There is an interesting bad interaction between my drag-and-drop code and >>> Rubric. It kills all Rubric editors at the same

Re: [Pharo-dev] EncodedCharSets

> On 17 Sep 2015, at 19:26, Eliot Miranda wrote: > > Hi Christophe, > > On Thu, Sep 17, 2015 at 7:09 AM, Christophe Demarey > wrote: > Hi again, > > Does anyone know the rationale behind this? > > declareEncodedCharSet: anEncodedCharSetOrLanguageEnvironmentClass atIndex: > aNumber > >

Re: [Pharo-dev] Contribution scheme confusing ...

On Thu, Sep 17, 2015 at 9:40 PM, Marcus Denker wrote: >>> >>> Also: >>> I did a simple fix on NautilusGroupAutoBuilder package - there is >>> a ConfigurationOfNautilusGroupAutoBuilder. But is it managed internally >>> or externally now? >>> >> Even I can not tell you. >> > > I think the rule we sh

Re: [Pharo-dev] Rubric/Event handling issue?

2015-09-17 10:35 GMT+02:00 Stephan Eggermont : > ping > > > On 15-09-15 17:49, Stephan Eggermont wrote: > >> There is an interesting bad interaction between my drag-and-drop code >> and Rubric. It kills all Rubric editors at the same time, so it looks >> to me like a problem with the Rubric backgr

Re: [Pharo-dev] About the Unicode class

Le 17/9/15 18:27, Nicolas Cellier a écrit : There has been some work on Squeak by Levente in this area, maybe it's time to harvest... Thanks nicolas for the information. It is in the Unicode class? 2015-09-17 18:22 GMT+02:00 Henrik Johansen mailto:henrik.s.johan...@veloxit.no>>: O

Re: [Pharo-dev] PID of VM ?

nativeboost is not maintained and we need a solution that can be maintained by multiple people. Normally with the new FFI esteban is doing you will be able to use the NativeBoost syntax. Bye T.

Re: [Pharo-dev] [review needed] speed up RBClassNotReferencedRule

> Maybe we can hijack that mechanism with a class side method e.g. > > rbNotReferenced > > > > Do your modifications test sends of subclassesDo: and friends? > > OR > > #(#MyClass1 #MyClass2 #MyClass3) collect:[:ea | (Smalltalk at: ea) > doSomething]. > > The reason I ask is I'm pl