Re: [Pharo-dev] About better communication in the community

Hi, Thanks Stef for the reply. I completely concur. @Hernán: About the issues with GT: please do get in touch. We have asked for it several times, and we are still here. If you have concrete issues, please raise them but focus on how to improve concretely. At the same time, also keep in mind t

Re: [Pharo-dev] About asClass and friend

Le 25 août 2016 08:53, "Tudor Girba" a écrit : > > Hi, > > There exists already a method for that: > Symbol>>asClassInEnvironment: > > But, what if we introduce: > > Symbol>>asClassFrom: anObject > ^ self asClassInEnvironment: anObject class environment > > ? > > This would allow u

Re: [Pharo-dev] About better communication in the community

Hello, Looking at bugs is really difficult. There are not enough people looking and fixing bugs. just a short note from a Pharo noob...it is, imho, very strange that one cannot even take a look at bugs *without* creating account at tracker. We know. Now the company offered us a professiona

Re: [Pharo-dev] Refactoring HelpTopic (needs review)

2016-08-25 7:13 GMT+02:00 stepharo : > > > Le 24/8/16 à 11:20, Nicolai Hess a écrit : > > > > 2016-08-24 6:49 GMT+02:00 stepharo : > >> Hi nicolai >> >> I remember that I read everything and fix typos. Did you got my review or >> did I suuceed to lose it ;). >> > > No, I think it was lost :-/ > >

Re: [Pharo-dev] About better communication in the community

Let us know because we do not I don't get why we don't have more discussions about end-developer tools : XML, i18n, GIS, simulation & expert systems, big data, reporting... Yes the idea is that we would like to try a process for Pharo and that such process can be used by other projects

Re: [Pharo-dev] About asClass and friend

Le 25/8/16 à 08:34, Yuriy Tymchuk a écrit : Just my 2 cents: instead of #name asClass we have to use self class environment at: #name. Maybe instead of #at: we can have #classNamed:? Why not if it helps people :) Or something similar? Because 1) it’s not obvious that the method will

Re: [Pharo-dev] About asClass and friend

Hi, There exists already a method for that: Symbol>>asClassInEnvironment: But, what if we introduce: Symbol>>asClassFrom: anObject ^ self asClassInEnvironment: anObject class environment ? The problem is asClass unary. All the tools should be parametrized by an environment.

Re: [Pharo-dev] About asClass and friend

Hi, > On Aug 25, 2016, at 9:52 AM, stepharo wrote: > > >> Hi, >> >> There exists already a method for that: >> Symbol>>asClassInEnvironment: >> >> But, what if we introduce: >> >> Symbol>>asClassFrom: anObject >> ^ self asClassInEnvironment: anObject class environment >> >> ? > Th

Re: [Pharo-dev] About asClass and friend

Hi 2016-08-25 8:52 GMT+02:00 Tudor Girba : > Furthermore, as #asClass is meant to be mainly used for convenience, not > performance, I would also propose to make it lookup in thisContext and take > the environment from there. I know that his might sound like magic, but it > would be the default t

[Pharo-dev] [ann] Lam Research evaluates Pharo

Hi, We are very happy to make the following announcement: Lam Research, a leading supplier of wafer fabrication equipment and services to the global semiconductor industry, is an experienced user of the Smalltalk programming language. Smalltalk is a key component in Lam's software control sys

Re: [Pharo-dev] [ann] Lam Research evaluates Pharo

Excellent Keep going guys! You are impacting state of the art of software engineering! Alexandre > On Aug 25, 2016, at 10:50 AM, Tudor Girba wrote: > > Hi, > > We are very happy to make the following announcement: > > > Lam Research, a leading supplier of wafer fabrication equipment an

Re: [Pharo-dev] [ann] Lam Research evaluates Pharo

Wonderful news. That may turn to be a real turning point for our beloved platform. Kudos to you people Phil On Thu, Aug 25, 2016 at 10:50 AM, Tudor Girba wrote: > Hi, > > We are very happy to make the following announcement: > > > Lam Research, a leading supplier of wafer fabrication equi

[Pharo-dev] problem with Epicea and #name

Hi, When trying to load a new version of the GTInspector in the latest Pharo image I get an infinite recursion. It seems that the problem is appears because a class is removed, which at a certain point calls #asEpiceaRingDefinition. This does then 'self superclass name', however, the superclass is

Re: [Pharo-dev] About better communication in the community

Hi! Hola! I would like to help with some of this, so I sorted a bit the ideas in the previous emails to see if we can extract some concrete actions to apply. So I'll make a step back and put some titles to the topics of discussion: !Human/Social/Politics stuff 1) Policies - Deciding about

Re: [Pharo-dev] problem with Epicea and #name

Hi Andrei, there is an open issue that involves #name in category removal whose fix is ready in bleeding edge and only waits that i release the new stable version. But this is about category removal, not class removal. This night I will take a look on the code of class removal... however, could yo

Re: [Pharo-dev] problem with Epicea and #name

Hi Martin, To reproduce the error execute the code below. The first part does some cleanups needed to remove the code. The second part attempts to remove two packages and seems to go into a recursion. If you interrupt the execution with cmd+. you'll see a lot of Context>>#handleSignal:. If you ri

Re: [Pharo-dev] problem with Epicea and #name

Hi Martin, Thanks a lot for the quick response. As Andrei said, please do not feel sorry. Epicea is an important new core component and just because it is a core one every tiny error will appear as a large problem. But, we are all humans here, and it should be expected that we make errors :).

Re: [Pharo-dev] [ann] Lam Research evaluates Pharo

On Thu, Aug 25, 2016 at 4:50 PM, Tudor Girba wrote: > Hi, > > We are very happy to make the following announcement: > > > Lam Research, a leading supplier of wafer fabrication equipment and services > to the global semiconductor industry, is an experienced user of the Smalltalk > programming lan

[Pharo-dev] WideString and commits

Hi! I opened an issue month ago on fogbugs because I could not commit some packages. I didn't get time to investigate it and nobody could. With Guille we found that the problem is that the code contained a special character. It contains a ♥... And we cannot commit specials character anymore on Mo

Re: [Pharo-dev] WideString and commits

Do we now since when? 2016-08-25 16:49 GMT+02:00 Cyril Ferlicot Delbecque < cyril.ferli...@gmail.com>: > Hi! > > I opened an issue month ago on fogbugs because I could not commit some > packages. I didn't get time to investigate it and nobody could. > > With Guille we found that the problem is th

Re: [Pharo-dev] About better communication in the community

On Thu, 25 Aug 2016 09:05:45 +0200 stepharo wrote: > Yes but we cannot do much OK. I got it...do you believe it makes sense for a noob to create acount in case there are some low-hanging fruits to pick? Sincerely, Gour -- From wherever the mind wanders due to its flickering and unsteady natu

Re: [Pharo-dev] [ann] Lam Research evaluates Pharo

Hi Ben, > On Aug 25, 2016, at 3:15 PM, Ben Coman wrote: > >> On Thu, Aug 25, 2016 at 4:50 PM, Tudor Girba wrote: >> Hi, >> >> We are very happy to make the following announcement: >> >> >> Lam Research, a leading supplier of wafer fabrication equipment and services >> to the global semicond

Re: [Pharo-dev] [ann] GTExamples alpha

2016-08-25 8:47 GMT+02:00 Tudor Girba : > Hi, > Hi Doru, some questions and feedback ( I am sorry for my tone or if this sounds negative, it isn't meant to be) > Over the last coupe of years Stefan Reichhart and the rest of the GT team > worked on an implementation of examples. The work is insp

Re: [Pharo-dev] WideString and commits

Le 25/8/16 à 16:55, Nicolas Cellier a écrit : Do we now since when? unfortunately not. @Cyril this is in Pharo50? 2016-08-25 16:49 GMT+02:00 Cyril Ferlicot Delbecque mailto:cyril.ferli...@gmail.com>>: Hi! I opened an issue month ago on fogbugs because I could not commit some

Re: [Pharo-dev] problem with Epicea and #name

thanks martin! I really appreciate that you maintain epicea because this is a great tool. Le 25/8/16 à 13:00, Martin Dias a écrit : Hi Andrei, there is an open issue that involves #name in category removal whose fix is ready in bleeding edge and only waits that i release the new stable ve

Re: [Pharo-dev] problem with Epicea and #name

Le 25/8/16 à 14:10, Tudor Girba a écrit : Hi Martin, Thanks a lot for the quick response. As Andrei said, please do not feel sorry. Epicea is an important new core component and just because it is a core one every tiny error will appear as a large problem. But, we are all humans here, and i

Re: [Pharo-dev] About asClass and friend

Yes this is what I was thinking too :) Hi 2016-08-25 8:52 GMT+02:00 Tudor Girba >: Furthermore, as #asClass is meant to be mainly used for convenience, not performance, I would also propose to make it lookup in thisContext and take the environment fro

Re: [Pharo-dev] About asClass and friend

Hi, There exists already a method for that: Symbol>>asClassInEnvironment: But, what if we introduce: Symbol>>asClassFrom: anObject ^ self asClassInEnvironment: anObject class environment ? The problem is asClass unary. All the tools should be parametrized by an environment.

Re: [Pharo-dev] About asClass and friend

Ah, I am using that a lot to parametrize software. On one hand Pharo is breaking with the past, on the other one it sticks with it as much as possible? #MeConfused asHell. This has nothing to do with complying with the past. Do you think seriously that if we could replace self class env: #f

Re: [Pharo-dev] About better communication in the community

Hi, > On Aug 25, 2016, at 5:31 PM, Gour wrote: > > On Thu, 25 Aug 2016 09:05:45 +0200 > stepharo wrote: > >> Yes but we cannot do much > > OK. I got it...do you believe it makes sense for a noob to create acount > in case there are some low-hanging fruits to pick? It definitely does! We are

Re: [Pharo-dev] About asClass and friend

Hi, > On Aug 25, 2016, at 10:10 PM, stepharo wrote: > Hi, There exists already a method for that: Symbol>>asClassInEnvironment: But, what if we introduce: Symbol>>asClassFrom: anObject ^ self asClassInEnvironment: anObject class environment >

Re: [Pharo-dev] problem with Epicea and #name

Hi, > On Aug 25, 2016, at 10:03 PM, stepharo wrote: > > > > Le 25/8/16 à 14:10, Tudor Girba a écrit : >> Hi Martin, >> >> Thanks a lot for the quick response. >> >> As Andrei said, please do not feel sorry. Epicea is an important new core >> component and just because it is a core one every

Re: [Pharo-dev] [ann] GTExamples alpha

Hi Nicolai, Thanks a lot for the feedback. Please let’s continue. See more inline. > On Aug 25, 2016, at 6:34 PM, Nicolai Hess wrote: > > > > 2016-08-25 8:47 GMT+02:00 Tudor Girba : > Hi, > > Hi Doru, > some questions and feedback ( I am sorry for my tone or if this sounds > negative, it is

Re: [Pharo-dev] [ann] GTExamples alpha

Hi, I just tried again, and the latest GToolkit image does contain FileSystem class >> gtExampleZip: Inspect this: Smalltalk gtExamplesContained select: [ :each | each method methodClass instanceSide = FileSystem ] This is the image: https://ci.inria.fr/moose/job

[Pharo-dev] CI is down

https://ci.inria.fr/pharo

Re: [Pharo-dev] About better communication in the community

Hi Stef, 2016-08-25 3:48 GMT-03:00 stepharo : > Hi hernan > > Could you reply to my mail? Because what is important is how we can make > progres. > Ok, here it is :) > About GT I have some concerns too now I see also a lot of improvements. I > love GTInspector and we should remove EyeInspector

Re: [Pharo-dev] problem with Epicea and #name

ok, ok, thanks ;-) Loading latest ConfigurationOfEpicea from Epicea's repo and load bleedingEdge fixes the #name issue in the script. Tomorrow I can release the new version. Martin On Thu, Aug 25, 2016 at 6:10 PM, Tudor Girba wrote: > Hi, > > > On Aug 25, 2016, at 10:03 PM, stepharo wrote: >

[Pharo-dev] UIprocess around when loading broken code

Hi yesterday I started to port omnibase to pharo and it uses the old API apicall: so it breaks when loading. I got some windows showing errors and after the image was full of new UIProcess. Can someone try to reproduce it and I think that we should fix it? Stef

Re: [Pharo-dev] About asClass and friend

Thanks doru. I do not like when people think that we are complaining just because something changes. It should change for the better and we all agree on that. Stef Hi, There exists already a method for that: Symbol>>asClassInEnvironment: But, what if we introduce: Symbol>>asCla

Re: [Pharo-dev] About asClass and friend

Hi, > On Aug 26, 2016, at 6:37 AM, stepharo wrote: > > Thanks doru. > > I do not like when people think that we are complaining just because > something changes. > > It should change for the better and we all agree on that. Certainly. There are many points of view and many constraints. Thi

Re: [Pharo-dev] About better communication in the community

On Thu, Aug 25, 2016 at 11:31 PM, Gour wrote: > On Thu, 25 Aug 2016 09:05:45 +0200 > stepharo wrote: > >> Yes but we cannot do much > > OK. I got it...do you believe it makes sense for a noob to create account > in case there are some low-hanging fruits to pick? Definitely. And not necessarily

Re: [Pharo-dev] About better communication in the community

On Thu, 25 Aug 2016 23:06:51 +0200 Tudor Girba wrote: > It definitely does! We are all noobs in many parts in our system. Heh, I'm for the whole system. :-) > But, if you take your time and are willing to dig, the system is kind > enough to reveal itself to you :). That is the beauty of this wo

Re: [Pharo-dev] About asClass and friend

Hi, My point of view is: 1) in code/core, we should use (we already said that with Camille in the past ;-)): self environmentAt: #Blah Object>>environmentAt: aSymbol ^ self class environmentAt: aSymbol Object class>>environmentAt: aSymbol ... The idea is that we can then customize name

Re: [Pharo-dev] About better communication in the community

On Fri, 26 Aug 2016 14:27:24 +0800 Ben Coman wrote: > Definitely. And not necessarily that you *solve* an issues, but that > I found a benefit from "goal directed learning". That's a good point! > When I started using Pharo I learned a lot from: * trying to reproduce > issues - which also bene