Re: [Pharo-dev] Color yzw

>> anyone an idea? >> > I'm trying to think. > Looks like it would be good to be able to make a distinction between symbols > and selectors (selectors installed > in method dictionaries) > yes, this would improve code completion a bit, too, as there are more symbols than symbols that are

Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

problem is that *all other tools* have accept/cancel in context menu. if you change one, you need to change all… otherwise you are breaking muscular/visual memory for no gain. So… I propose to put them in same place all other tools have it: in the contextual menu. cheers, Esteban ps: in

Re: [Pharo-dev] Growl setting name

There are A TON of things named Morphs inside Bloc. Bloc has no choice because it wants to be 100% compatible with Morphic. That means it has to offer a 100% Morphic API . What Bloc does is rework the ugly internals of Morphic offering a better implementation and of course adds a lot of new

Re: [Pharo-dev] Contributing to Pharo

Le 16/1/16 00:15, Henrik Sperre Johansen a écrit : Or, try a stable release. Whenever I try developing on the latest version, I end up getting disrupted by bugs in the core tools 70-80% of the time. For released versions, in 1.4 it was maybe 5%, in 2.0 40%, in 3.0 20%, in 4.0 10% So at least

Re: [Pharo-dev] Contributing to Pharo

On Sat, Jan 16, 2016 at 7:25 PM, David Allouche wrote: > >> On 16 Jan 2016, at 12:14, stepharo wrote: >> >> Le 16/1/16 09:59, David Allouche a écrit : >>> >>> But, really, this "list of dirty packages" should really only list dirty >>> packages. What is the

Re: [Pharo-dev] How do you normally merge Git branches with Metadata-less GitFileTree?

Le 16/01/2016 03:23, Mariano Martinez Peck a écrit : Hi guys, First, let me say that I found very cool that I can do a "git checkout X" from command line, and from Pharo, opening the MC browser detects I am in another branch and everything seems to work. So I guess that's the way I manage

Re: [Pharo-dev] Contributing to Pharo

> On 16 Jan 2016, at 02:42, Ben Coman wrote: > > So if occasionally if everything seems against you, after trying a > fresh Image as you already did, slide back to the last build that > worked for you (I don't think the issues you experience are Spur > related, but 50496

Re: [Pharo-dev] How do you normally merge Git branches with Metadata-less GitFileTree?

On Sat, Jan 16, 2016 at 5:15 AM, Thierry Goubier wrote: > Le 16/01/2016 03:23, Mariano Martinez Peck a écrit : > >> Hi guys, >> >> First, let me say that I found very cool that I can do a "git checkout >> X" from command line, and from Pharo, opening the MC browser

Re: [Pharo-dev] Contributing to Pharo

> On 16 Jan 2016, at 02:15, Ben Coman wrote: > On Sat, Jan 16, 2016 at 3:45 AM, David Allouche > wrote: > it shows a bunch of packages I have not touched > it does not show the package that contains my fix (Spec-Tools) > > I

Re: [Pharo-dev] Contributing to Pharo

It really depend, when I was using pharo 4 back when it was the "unstable/alpha" version it was rock solid, same story with pharo 3. Pharo 5 is the first seriously problematic unstable pharo version. The reason is that Pharo 5 has a ton of core changes , new vm, new debugger, new guis api , new

Re: [Pharo-dev] [Vm-dev] Unable to read Utf8 ?

Le 16/01/2016 11:39, Esteban Lorenzano a écrit : On 16 Jan 2016, at 10:45, Eliot Miranda wrote: Hi Thierry, up until a few hours ago the latest VM sources were indeed broken by work I was doing on 64 bits. My sources are AFAIA now correct and I suppose you're

Re: [Pharo-dev] Contributing to Pharo

Hi david On 16 Jan 2016, at 02:42, Ben Coman wrote: So if occasionally if everything seems against you, after trying a fresh Image as you already did, slide back to the last build that worked for you (I don't think the issues you experience are Spur related, but 50496

Re: [Pharo-dev] Color yzw

> On 16 Jan 2016, at 13:26, Nicolai Hess wrote: > > > > 2016-01-16 10:11 GMT+01:00 Marcus Denker >: > >>> anyone an idea? >>> >> I'm trying to think. >> Looks like it would be good to be able to make a

[Pharo-dev] Unable to read Utf8 ?

Hi Guys, has something changed in string handling? I'm unable to get the latest Pharo to read files containing utf8 data. I tracked it down to a primitive (at:put:) in WideString and to the latest vm for Pharo 5, so, maybe there is something wrong in the latest vm. Thierry

Re: [Pharo-dev] Unable to read Utf8 ?

Le 16/01/2016 10:45, Eliot Miranda a écrit : Hi Thierry, up until a few hours ago the latest VM sources were indeed broken by work I was doing on 64 bits. My sources are AFAIA now correct and I suppose you're waiting on Esteban doing a merge. But I'm responding since there seems to be a

Re: [Pharo-dev] Contributing to Pharo

> On 16 Jan 2016, at 12:14, stepharo wrote: > > Le 16/1/16 09:59, David Allouche a écrit : >> >> But, really, this "list of dirty packages" should really only list dirty >> packages. What is the use case for selecting a non-dirty package? > > because you never know >

Re: [Pharo-dev] Growl setting name

Le 16/01/2016 09:18, Dimitris Chloupis a écrit : > Personally I dont see the point of a rename, we got like 30% of people > coming from macos that will be familiar with the name Growl, 0% that > will be familiar with any other name. So you take a name that is very > popular and change it to

Re: [Pharo-dev] How do you normally merge Git branches with Metadata-less GitFileTree?

Le 16/01/2016 15:06, Mariano Martinez Peck a écrit : On Sat, Jan 16, 2016 at 5:15 AM, Thierry Goubier > wrote: Le 16/01/2016 03:23, Mariano Martinez Peck a écrit : Hi guys, First, let me say that I found very

Re: [Pharo-dev] Growl setting name

> On 16 Jan 2016, at 09:18, Dimitris Chloupis wrote: > > Personally I dont see the point of a rename, we got like 30% of people coming > from macos that will be familiar with the name Growl, 0% that will be > familiar with any other name. So you take a name that is very

Re: [Pharo-dev] Growl setting name

Le 16/01/2016 09:12, stepharo a écrit : > Finally > > "Growl is a global notification system and pop-up notification > implementation for the Mac OS X and Windows[1] operating systems. " > > So? > Growl can be downloaded on Windows but almost no Windows user know this name and can understand

Re: [Pharo-dev] Growl setting name

but notificationPopup is misleading because this is not a Notification (Exception). Stef Le 15/1/16 23:36, Ferlicot D. Cyril a écrit : Le 15/01/2016 22:51, Mariano Martinez Peck a écrit : I clearly would use Notification as part of the name, and not Growl. NotificationPopup? I love this

Re: [Pharo-dev] Contributing to Pharo

Le 16/1/16 09:59, David Allouche a écrit : On 16 Jan 2016, at 02:15, Ben Coman > wrote: On Sat, Jan 16, 2016 at 3:45 AM, David Allouche>wrote: 1. it shows a bunch of packages I have not

Re: [Pharo-dev] Contributing to Pharo

On 16-01-16 12:25, David Allouche wrote: That does not make sense to me. I guess it will, when I understand Monticello better. Ideally, you start with the fresh, latest clean Pharo image to start working on an issue and make the changes in one go to create a slice. Then you only have to

Re: [Pharo-dev] [Vm-dev] Unable to read Utf8 ?

> On 16 Jan 2016, at 11:59, Thierry Goubier wrote: > > Le 16/01/2016 11:39, Esteban Lorenzano a écrit : >> >>> On 16 Jan 2016, at 10:45, Eliot Miranda >>> wrote: >>> >>> >>> Hi Thierry, >>> >>> up until a few hours ago the latest VM

Re: [Pharo-dev] Contributing to Pharo

> On 16 Jan 2016, at 12:12, stepharo wrote: >>> On 16 Jan 2016, at 02:42, Ben Coman wrote: >>> >>> So if occasionally if everything seems against you, after trying a >>> fresh Image as you already did, slide back to the last build that >>> worked for you

Re: [Pharo-dev] Color yzw

and so is auto completion ;) On Sat, Jan 16, 2016 at 1:03 PM stepharo wrote: > How can we proceed? > Because this coloring functionality is really important. > > Stef > > > anyone an idea? > > I'm trying to think. > Looks like it would be good to be able to make a distinction

Re: [Pharo-dev] Color yzw

2016-01-16 10:11 GMT+01:00 Marcus Denker : > > anyone an idea? > > I'm trying to think. > Looks like it would be good to be able to make a distinction between > symbols and selectors (selectors installed > in method dictionaries) > > > yes, this would improve code

Re: [Pharo-dev] How do you normally merge Git branches with Metadata-less GitFileTree?

OK, thanks Thierry. BTW, thanks for all the help you have been giving me in the last weeks and for your great GitFileTree :) On Sat, Jan 16, 2016 at 11:14 AM, Thierry Goubier wrote: > Le 16/01/2016 15:06, Mariano Martinez Peck a écrit : > >> >> >> On Sat, Jan 16,

Re: [Pharo-dev] gtdebugger in pharo 5.0

Le 09/01/2016 10:32, Tudor Girba a écrit : > Hi, > > Could you be specific? What exactly do you find less intuitive? To be able to > react, it is useful to get concrete points. > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "Value is always contextual." > > Hi, After

Re: [Pharo-dev] [Pharo-project] [Vm-dev] Re: Can OSProcess functionality be implemented using FFI instead of plugin?

On Sat, Jan 16, 2016 at 4:37 PM, Levente Uzonyi wrote: > > On Sat, 16 Jan 2016, Mariano Martinez Peck wrote: > > (Still no quote.) > > How will you read the output of the process without having your image's > process blocked in the FFI callout? > How will you make sure that

Re: [Pharo-dev] Growl setting name

So if you want to change (and some tools should not hardcode access to GrowlMorph) a better name would be NotifierPopup Le 16/1/16 09:03, stepharo a écrit : but notificationPopup is misleading because this is not a Notification (Exception). Stef Le 15/1/16 23:36, Ferlicot D. Cyril a écrit :

Re: [Pharo-dev] Growl setting name

Finally "Growl is a global notification system and pop-up notification implementation for the Mac OS X and Windows[1] operating systems. " So?

Re: [Pharo-dev] Growl setting name

Personally I dont see the point of a rename, we got like 30% of people coming from macos that will be familiar with the name Growl, 0% that will be familiar with any other name. So you take a name that is very popular and change it to something none knows, how is that an improvement ? What

Re: [Pharo-dev] Git repository and branch for spur enable pharo-vm

Hi, > On 15 Jan 2016, at 18:29, Holger Freyther wrote: > > Hi, > > what is the official pharo-vm git repository? It looks like > github.com/pharo-project/pharo-vm is not being updated right now. It looks > like esteban's fork is currently being used and the spur64 branch.

Re: [Pharo-dev] Color yzw

How can we proceed? Because this coloring functionality is really important. Stef anyone an idea? I'm trying to think. Looks like it would be good to be able to make a distinction between symbols and selectors (selectors installed in method dictionaries) yes, this would improve code

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

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

[Pharo-dev] [pharo-project/pharo-core] 233d1c: 50529

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 233d1c603f211e85b5f990a062f4977faad8a57d https://github.com/pharo-project/pharo-core/commit/233d1c603f211e85b5f990a062f4977faad8a57d Author: Jenkins Build Server Date:

Re: [Pharo-dev] Contributing to Pharo

> On 16 Jan 2016, at 14:44, Ben Coman wrote: > > On Sat, Jan 16, 2016 at 7:25 PM, David Allouche wrote: >> >>> On 16 Jan 2016, at 12:14, stepharo wrote: >>> >>> Le 16/1/16 09:59, David Allouche a écrit : But, really,

Re: [Pharo-dev] Git repository and branch for spur enable pharo-vm

Hi, Today I was also needed to compile Spur VM and just by chance by this email I found out I should be using Esteban fork. So maybe at least a sentence in the original repo saying that for Spur / Pharo 5.0 you should use Esteban fork would help. At least until you merge. Cheers, On Fri, Jan

Re: [Pharo-dev] Color yzw

2016-01-16 13:46 GMT+01:00 Marcus Denker : > > On 16 Jan 2016, at 13:26, Nicolai Hess wrote: > > > > 2016-01-16 10:11 GMT+01:00 Marcus Denker : > >> >> anyone an idea? >> >> I'm trying to think. >> Looks like it would be good

Re: [Pharo-dev] Running processes at startup vs startUpList, which one first?

On Sat, Jan 16, 2016 at 6:43 AM, Mariano Martinez Peck < marianop...@gmail.com> wrote: > Hi, > > I have a funny question. Let's say I did: > > [ > something > > ] fork. > > and `something` never finishes and does not get GC. And I have a class > that I registered in startup list. > > Which gets

Re: [Pharo-dev] gtdebugger in pharo 5.0

On Sun, Jan 17, 2016 at 9:48 AM, Cyril Ferlicot D. wrote: > > And more, it make the debugger "ventilated" (I don't know if the term > work in English too). I mean that with more space between the classes > and the methods it's better for the eye of the user. Never heard

[Pharo-dev] Running processes at startup vs startUpList, which one first?

Hi, I have a funny question. Let's say I did: [ something ] fork. and `something` never finishes and does not get GC. And I have a class that I registered in startup list. Which gets done first? the resume of the above process of the processing of the startup list? Thanks! -- Mariano