Re: [Pharo-dev] Random access to meta repos?

Le 27/10/2015 02:22, Yuriy Tymchuk a écrit : So was this fixed or not? Because if I’m opening a git repo — it checks the meta, I’m saving to git repo — it checks the meta… Hi Uko, I thought I fixed it; but yes it is checking the meta too much. I'll have a look. Thierry Uko On 24 Aug 20

Re: [Pharo-dev] Finding the reason of merge

Le 27/10/2015 03:40, Chris Cunningham a écrit : you could try Merging instead of loading, and then look at the difference between the newly merged in-image package and version 74. Or, you could open the Monticello browser, highlight the package (which you've already done),and click on Changes to

Re: [Pharo-dev] Finding the reason of merge

you could try Merging instead of loading, and then look at the difference between the newly merged in-image package and version 74. Or, you could open the Monticello browser, highlight the package (which you've already done),and click on Changes to see what you've changed since version 73. Or, ma

Re: [Pharo-dev] Loading of Baselines from GitHub in Metacello using pattern matching not working on Windows

Thanks Dale, I can confirm that with the latest version in master this works in Pharo 5. On Mon, Oct 26, 2015 at 9:10 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > Gabriel, > > Are you using the latest version of Metacello from github (these > instructions work for versions 3.0 a

Re: [Pharo-dev] Random access to meta repos?

So was this fixed or not? Because if I’m opening a git repo — it checks the meta, I’m saving to git repo — it checks the meta… Uko > On 24 Aug 2015, at 22:05, Thierry Goubier wrote: > > Hi Paul, > > do you still see some of this in one of the filetree branches when doing > metacello integra

[Pharo-dev] Finding the reason of merge

Ok, I’m completely exhausted, I have no clue what’s the problem. I have version 73 of my package, I load version 74 an then it says: “If you continue, you will loose these changes: “ and there is nothing more, there are no changes that I’m going to loose. Is there any way to identify why the mer

Re: [Pharo-dev] Loading of Baselines from GitHub in Metacello using pattern matching not working on Windows

I'm using the version that comes preloaded with Pharo. This also fails in Pharo 5. I will give it a try with the github version and if it works I can prepare a slice to merge this version in Pharo. Thanks On Oct 26, 2015 9:11 PM, "Dale Henrichs" wrote: > Gabriel, > > Are you using the latest ver

Re: [Pharo-dev] Little Meeting at Pittsburg

I am attending OOPSLA too, It would be a pleasure to be part of the meeting. Juampi 2015-10-25 19:30 GMT-03:00 stepharo : > Hi > > Guillermo, Andrei, Guido and me are attending OOPSLA so we could have a > small > Pharo meeting. > What about wednesday evening? > > Stef > > -- Saludos, Juan Pab

Re: [Pharo-dev] Loading of Baselines from GitHub in Metacello using pattern matching not working on Windows

Gabriel, Are you using the latest version of Metacello from github (these instructions work for versions 3.0 and newer[1])? The pattern matching feature is relatively new so unless you've loaded from github, you are likely not getting the needed support ... I think that Pharo5.0 should be b

[Pharo-dev] Loading of Baselines from GitHub in Metacello using pattern matching not working on Windows

When trying to load a baseline using the Metacello API and version pattern matching, using the gituhb:// scheme produces an error because it's trying to create a directory with a question mark (?). To reproduce try in a Pharo4/5 image: Metacello new baseline: 'RenoirSt'; repository: 'github

Re: [Pharo-dev] feedback from J Brant

Thanks!!! Le 26/10/15 12:07, Nicolai Hess a écrit : 2015-09-02 20:28 GMT+02:00 stepharo >: Hi guys here is some feedback from John. I share it with you. On 02 Sep 2015, at 16:05, John Brant wrote: I've bee

Re: [Pharo-dev] feedback from J Brant

2015-09-02 20:28 GMT+02:00 stepharo : > Hi guys > > here is some feedback from John. I share it with you. > > > On 02 Sep 2015, at 16:05, John Brant > wrote: > > I've been writing some automated scripts to port SmaCC to Pharo. I have it > where I can file in the Dolphin .pac files directly into

[Pharo-dev] [pharo-project/pharo-core] c8e490: 50406

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c8e490ae15abe6d84d84663db416779793a59e76 https://github.com/pharo-project/pharo-core/commit/c8e490ae15abe6d84d84663db416779793a59e76 Author: Jenkins Build Server Date: 2015-10-26 (Mon, 26 Oct 2015

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

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

Re: [Pharo-dev] FastTable question

Le 26/10/2015 14:09, Esteban Lorenzano a écrit : On 26 Oct 2015, at 14:05, Thierry Goubier mailto:thierry.goub...@gmail.com>> wrote: Le 26/10/2015 11:37, Esteban Lorenzano a écrit : On 22 Oct 2015, at 09:13, Cyril Ferlicot mailto:cyril.ferli...@gmail.com>> wrote: For now On Thu, Oct 22, 2

Re: [Pharo-dev] FastTable question

> On 26 Oct 2015, at 14:05, Thierry Goubier wrote: > > Le 26/10/2015 11:37, Esteban Lorenzano a écrit : >> >>> On 22 Oct 2015, at 09:13, Cyril Ferlicot wrote: >>> >>> For now >>> >>> On Thu, Oct 22, 2015 at 8:57 AM, stepharo wrote: Excellent How did you do it? >>> >>>

Re: [Pharo-dev] FastTable question

Le 26/10/2015 11:37, Esteban Lorenzano a écrit : On 22 Oct 2015, at 09:13, Cyril Ferlicot wrote: For now On Thu, Oct 22, 2015 at 8:57 AM, stepharo wrote: Excellent How did you do it? I removed the hardcode value of the default row height in order use the size of the default font. "Stan

[Pharo-dev] [pharo-project/pharo-core] 896641: 40624

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 896641b25860fced7a3c39116a9128a702516d3a https://github.com/pharo-project/pharo-core/commit/896641b25860fced7a3c39116a9128a702516d3a Author: Jenkins Build Server Date: 2015-10-26 (Mon, 26 Oct 2015

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

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

Re: [Pharo-dev] FastTable question

> On 22 Oct 2015, at 09:09, Cyril Ferlicot wrote: > > We will at least keep it for Synectique in order to have a widget with > an action button for now. I do not want it in the main distribution :S As we talked, for me correct way to implement such behaviour is: - Transmit to FTSearchFunction

Re: [Pharo-dev] FastTable question

> On 22 Oct 2015, at 09:13, Cyril Ferlicot wrote: > > For now > > On Thu, Oct 22, 2015 at 8:57 AM, stepharo wrote: >> Excellent >> >> How did you do it? >> > > I removed the hardcode value of the default row height in order use > the size of the default font. "StandardFont defaultfont pixel

Re: [Pharo-dev] Help with a bug fix

I like it, but wonder if it should even appear above "-- all --". Possibly it should also remain in its original sort position in the list for consistency. I tried this out but the second entry cannot be selected, which seems strange. Maybe list selection is by-content rather than by-index - and

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

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

[Pharo-dev] [pharo-project/pharo-core] 1e8833: 50405

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 1e8833e53a5875ab94780dfcd786909f189f35a2 https://github.com/pharo-project/pharo-core/commit/1e8833e53a5875ab94780dfcd786909f189f35a2 Author: Jenkins Build Server Date: 2015-10-26 (Mon, 26 Oct 2015