Re: [Pharo-users] Depending on MetaRepo instead of the target repo

2017-02-12 Thread Dale Henrichs
Very good to hear ... I have to try to be a bit more patient :) On 2/12/17 9:37 AM, stepharong wrote: On Sun, 12 Feb 2017 16:36:42 +0100, Dale Henrichs wrote: Peter, In the long term the the MetaRepo should be replaced by a repository of project

Re: [Pharo-users] About asSymbol message , some questions in my mind

2017-02-12 Thread john pfersich
BUT There are not compliant below 1.' ' asSymbol no meaning 2. '$%%&' asSymbol no meaning 3. 'sign' asSymbol = 'sign ' asSymbol >>> false because of space. 3. ' one two three ' asSymbol >>>I think It should become three symbols = #one, #two,

Re: [Pharo-users] Citezen bug MessageNotUnderstood: Metaclass>>allMethodsInCategory:

2017-02-12 Thread stepharong
Ok I will have a look. Ping me if I forget. Hi, On 12/02/17 09:19, stepharong wrote: Hi offray I generate all my web page and cv with Citezen. Can you tell which version of citezen? The one provided by ConfigurationOfCitezen (StephaneDucasse.137) how you load it? From the

Re: [Pharo-users] Unable to find the compiler

2017-02-12 Thread Cyril Ferlicot D.
Le 11/02/2017 à 10:38, Mark Neagu a écrit : > Hi, > > Thank you for your answer. > > I first tried to find the code panel but I can't see it in my Pharo: no > panel is titled "code panel" ans nothing looks like > "https://puu.sh/tXu99/f11df69e74.png;. > > I then tried CMD + S or CTRL + S but it

Re: [Pharo-users] Something wrong with my installation of Pharo

2017-02-12 Thread p...@highoctane.be
Hi, What is the problem? Screenshot? Am on Windows and Pharo is working nicely. Win8.1 and Win10. Used to be fine on Win7. Phil On Sun, Feb 12, 2017 at 6:34 PM, stepharong wrote: > tx nicole > Mark I feel sorry. > I only have macs and I do not know windows. > > Stef > >

Re: [Pharo-users] Depending on MetaRepo instead of the target repo

2017-02-12 Thread stepharong
On Sun, 12 Feb 2017 16:36:42 +0100, Dale Henrichs wrote: Peter, In the long term the the MetaRepo should be replaced by a repository of project specification objects (like this [1]). Each project specification would contain the meta data for a project

Re: [Pharo-users] Something wrong with my installation of Pharo

2017-02-12 Thread stepharong
tx nicole Mark I feel sorry. I only have macs and I do not know windows. Stef On Sun, 12 Feb 2017 18:04:15 +0100, Nicole de Graaf wrote: Hi Mark, I can try to help you .. It is possible that I can not find the solution directly but than we can ask other people more

Re: [Pharo-users] getting real changes from RB refactoring

2017-02-12 Thread stepharong
Hi peter is there some filter that will reject RB changes that actually do not do anything? I.e. applying them would have no effect (same method code, class, inst var exists, ...). I do not know. Do you have an example of when such changes are created? For methods I can do reject: [

[Pharo-users] getting real changes from RB refactoring

2017-02-12 Thread Peter Uhnak
Hi, is there some filter that will reject RB changes that actually do not do anything? I.e. applying them would have no effect (same method code, class, inst var exists, ...). For methods I can do reject: [ :each | each oldVersionTextToDisplay = each textToDisplay ] for adding classes I had

Re: [Pharo-users] Something wrong with my installation of Pharo

2017-02-12 Thread Nicole de Graaf
Hi Mark, I can try to help you .. It is possible that I can not find the solution directly but than we can ask other people more concrete questions. For sure team viewer and Skype is the fastest way .. Regards, Nic > On 12 Feb 2017, at 15:56, Mark Neagu wrote: > > Hi,

Re: [Pharo-users] Depending on MetaRepo instead of the target repo

2017-02-12 Thread Ben Coman
On Sun, Feb 12, 2017 at 11:36 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > Peter, > > > > In the long term the the MetaRepo should be replaced by a repository of > project specification objects (like this [1]). Each project specification > would contain the meta data for a

Re: [Pharo-users] Depending on MetaRepo instead of the target repo

2017-02-12 Thread Dale Henrichs
Peter, In the long term the the MetaRepo should be replaced by a repository of project specification objects (like this [1]). Each project specification would contain the meta data for a project (like this[2]) instead of a copy of a ConfigurationOf that is almost always out-of-date.

Re: [Pharo-users] Citezen bug MessageNotUnderstood: Metaclass>>allMethodsInCategory:

2017-02-12 Thread Offray Vladimir Luna Cárdenas
Hi, On 12/02/17 09:19, stepharong wrote: Hi offray I generate all my web page and cv with Citezen. Can you tell which version of citezen? The one provided by ConfigurationOfCitezen (StephaneDucasse.137) how you load it? From the spotter, so I imagine is reading the Pharo

Re: [Pharo-users] Citezen bug MessageNotUnderstood: Metaclass>>allMethodsInCategory:

2017-02-12 Thread Offray Vladimir Luna Cárdenas
My user account is Offray ( http://smalltalkhub.com/#!/~Offray ). I'm using the Citizen version provided by ConfigurationOfCitezen (StephaneDucasse.137). Thanks, Offray On 12/02/17 09:30, stepharong wrote: what is your account on smalltalkhub? On Sun, 12 Feb 2017 00:52:10 +0100, Offray

Re: [Pharo-users] Citezen bug MessageNotUnderstood: Metaclass>>allMethodsInCategory:

2017-02-12 Thread stepharong
what is your account on smalltalkhub? On Sun, 12 Feb 2017 00:52:10 +0100, Offray Vladimir Luna Cárdenas wrote: Thanks to Cyril I have fixed the bug. Now is called #allSelectorsInProtocol. How can I propose a bug fix for the citezen package? Is good to have a

Re: [Pharo-users] Citezen bug MessageNotUnderstood: Metaclass>>allMethodsInCategory:

2017-02-12 Thread stepharong
On which version are you working? I should add an inbox to citezen (waiting to migrate to github). Thanks to Cyril I have fixed the bug. Now is called #allSelectorsInProtocol. How can I propose a bug fix for the citezen package? Is good to have a chat channel for this knowledge... it's a

Re: [Pharo-users] Depending on MetaRepo instead of the target repo

2017-02-12 Thread stepharong
Hi, would it make sense to take configurations from metarepos instead directly from the source? I do not think so but if people show me otherwise I could follow that. Usually I have a conf in my repo referencing other repo and not the meta one Then I push in the meta just to config.

Re: [Pharo-users] Citezen bug MessageNotUnderstood: Metaclass>>allMethodsInCategory:

2017-02-12 Thread stepharong
Hi offray I generate all my web page and cv with Citezen. Can you tell which version of citezen? how you load it? which version of Pharo the expressions you executed? Stef Hi, I'm adding some Zotero[1] integration for my Grafoscopio project, now that I'm

Re: [Pharo-users] Depending on MetaRepo instead of the target repo

2017-02-12 Thread Stephan Eggermont
On 12/02/17 13:03, Peter Uhnak wrote: would it make sense to take configurations from metarepos instead directly from the source? Not really. They are not kept exactly up-to-date in practice, and having one for each Pharo version is also kind of a bad practice. What is missing is some

[Pharo-users] Depending on MetaRepo instead of the target repo

2017-02-12 Thread Peter Uhnak
Hi, would it make sense to take configurations from metarepos instead directly from the source? And more imporantly: would be considered bad practice for users to do it right now? E.g. spec project: 'Magritte' with: [ spec className: #ConfigurationOfMagritte3;

Re: [Pharo-users] About asSymbol message , some questions in my mind

2017-02-12 Thread Ben Coman
On Sun, Feb 12, 2017 at 10:54 AM, lb wrote: > Hi Ben, > Thank you very much, your answer make me clear like water. > My question aimed on where, which type errors occur when perform a message. > My usecase. > when perform: aMessage(with a space), get DNU error , cannot find