Re: [Pharo-dev] Do we kill the catalog?

Just for the record https://pharo.fogbugz.com/f/cases/21825/Improve-Catalog-loading https://github.com/pharo-project/pharo/pull/1292 Feel free to review or to propose other PRs, Guille

Re: [Pharo-dev] self-backporting from P7 to P6.1

Esteban did some work on making a forward compatibility package for spec. github://pharo-contributions/Spec70Compatibility:v1.0.0/src The idea is that people should do the opposite: code for Pharo7, while being in Pharo 6. But that covers only Spec. We have to think if there is some automatic

Re: [Pharo-dev] self-backporting from P7 to P6.1

On Mon, Apr 30, 2018 at 12:19 PM, Peter Uhnák wrote: > > The idea is that people should do the opposite: code for Pharo7, while >> being in Pharo 6. >> > > Exactly. Several times I was put off contributing to P7, because I needed > a solution now, and not in year when P7 comes

[Pharo-dev] Github API on github

Hi guys, I extracted and extended some of the github API from iceberg, so it can be used as a standalone project. Maybe this is useful for somebody. https://github.com/guillep/github-api It should be easy to extend and add new functionalities, so don't hesitate if you need some missing request

Re: [Pharo-dev] CI Build order and strange "latest" Pharo 7 effect

Follow up. We tested with Pablo how these options work on a separate repository/job. I just integrated these changes, and they effectively disable concurrent builds on the development branch. PRs are still being validated concurrently. On Fri, Oct 13, 2017 at 11:37 AM, Guillermo Polito

[Pharo-dev] Updating CI plugins

Hi all, I'm updating CI plugins. *This will require a CI restart. *The corresponding issue is here: https://pharo.fogbugz.com/f/cases/20884/Update-CI-Plugins The installed versions are the following: Workspace Cleanup Plugin 0.34 0.33 SCM API Plugin 2.2.6 2.2.1 Pipeline Utility Steps 1.5.1

Re: [Pharo-dev] Updating CI plugins

Christophe is also taking benefit of this to update jenkins from 2.32.3 LTS to 2.89.2 LTS On Fri, Dec 22, 2017 at 10:06 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi all, > > I'm updating CI plugins. *This will require a CI restart. *The > corresponding issue

Re: [Pharo-dev] Replacement for deprected MultiByteFileStream?

On Tue, Jan 2, 2018 at 1:13 PM, Henrik Sperre Johansen < henrik.s.johan...@veloxit.no> wrote: > Stephane Ducasse-3 wrote > > Hi Bernhard > > > > Have a look at how guille started to implement File package. > > (Guille is actively converting all the image users of the old > > hierarchy but last

Re: [Pharo-dev] How to restore image upgrade? was New Year Wishlist (2018) ?

On Tue, Dec 26, 2017 at 11:36 PM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > > > 2017-12-25 23:54 GMT+01:00 Ben Coman : > >> As a half-way house, consider that "upgrade" scripts could be a good >> mechanism >> post-Release when changes should be

Re: [Pharo-dev] git and author/timestamps, 10000's of files, etc.

On Sun, Jan 14, 2018 at 7:11 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > I've been skimming the ironically named "blame" thread and just want to > clear up some apparent misconceptions. > > git/github is not the reason that the author/timestamps information was > "lost" ...

Re: [Pharo-dev] git workflow (iceberg) and monticello packages

On Sun, Feb 4, 2018 at 11:07 PM, Nicolai Hess wrote: > Hi , > > I am still not sure I understand the git based development workflow. > > I set up my image and repository as described by the guide. > > now, if new commits are in the pharo-project, iceberg shows the list of

Re: [Pharo-dev] Cleaning up... baseClass, instanceSide, theNonMetaclass

In my code I use to use instanceSide and classSide. don't know why. Maybe they are clearer to me? On Sun, Feb 11, 2018 at 8:59 PM, Denis Kudriashov wrote: > 2018-02-11 18:14 GMT+01:00 Stephane Ducasse : > >> Hi >> >> We already got this discussion

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

On Thu, Feb 8, 2018 at 6:28 AM, Ben Coman wrote: > Could the Iceberg gurus try and comment on the following workflow. > > Please familiarise with the first four commits here... > https://github.com/Traadh/cloudflareun/network > > from these actions... > > "first commit" --

Re: [Pharo-dev] VirtualMachine vs. Platform and Bootstrap

On Fri, Feb 16, 2018 at 10:18 AM, Torsten Bergmann wrote: > Hi, > > 1. We can query for the VIRTUAL MACHINE and ask if it is 32 or 64 bit > (internally depending on wordSize): > > Smalltalk vm is32Bit > >Anything OK on that side. > > 2. We can also query for the

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

++999^1000 :) On Fri, Feb 23, 2018 at 7:32 AM, Stephane Ducasse wrote: > Thanks Sven > I thought that suddenly I was an idiot. > > > On Thu, Feb 22, 2018 at 11:47 AM, Sven Van Caekenberghe > wrote: > > > > > >> On 22 Feb 2018, at 10:41, Clément Bera

Re: [Pharo-dev] Monticello file out bug during bootstrap

Hi Alistair, Can you provide some more context on what are you trying to do and how? Generally you should not change anything in the bootstrap, just modify the classes you want to modify and commit them into the repository. The bootstrap will take care of it. The only cases when you need to

Re: [Pharo-dev] Pull Request 20898-MultiByteFileStream-upToAll-does-not-work-correctly-with-UTF-8

Well, It looks like when you read tonel files with your changes there are some "invisible" characters left over in the stream. I think that first you should be able to reproduce the issue locally without bootstrapping by trying to import a tonel file in an image with your changes. Just take any

Re: [Pharo-dev] "curl https://get.pharo.org/64 | bash" does not work (on Mac)

These pages are wrong (at least): http://pharo.org/download https://pharo.org/gnu-linux-installation-64 https://pharo.org/gnu-linux-installation On Sun, Feb 25, 2018 at 9:36 PM, Stephane Ducasse wrote: > which page? > >

Re: [Pharo-dev] [Vm-dev] OSSubprocess 0.2.5 fails in Pharo 6.1 64 bits (macOS)

I'll try making a PR now to fix that. On Mon, Feb 26, 2018 at 10:19 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hmm, wait, I think these are two different issues :) > > I managed to successfully use OSSubprocess in 64bits with some tweaks. The > problem is that

Re: [Pharo-dev] [Vm-dev] OSSubprocess 0.2.5 fails in Pharo 6.1 64 bits (macOS)

Hmm, wait, I think these are two different issues :) I managed to successfully use OSSubprocess in 64bits with some tweaks. The problem is that OSSubprocess does some manual type coertions like assumming 32 bits: collectArgumentPointersInto: aPointer [...] aPointer nbUInt32AtOffset:

Re: [Pharo-dev] Updating CI plugins

Jenkins and slaves are up un running. Let's cross fingers hoping everything is ok :) Keep you updated On Fri, Dec 22, 2017 at 10:14 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Christophe is also taking benefit of this to update jenkins from 2.32.3 > LTS to 2.89.2 LT

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

lle On Mon, Jun 18, 2018 at 9:12 PM Torsten Bergmann wrote: > Great - thank you! Might be a small patch release - but nonetheless > important. > > BTW: the links in your mail are pointing to PR's of Pharo and not Iceberg. > If you used > a template you might want to consid

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

Hi, I don't know the windows situation at all, but I'm wondering. ([ File stdioDescriptorIsATTY not ] on: PrimitiveFailed do: [ :ex | "HACK kept for retrocompatibility" Smalltalk os isWin32 ]) ifTrue: [ ^ self createStdioFileFor: moniker ]. the first thing I would do, just trying to keep the

Re: [Pharo-dev] CI Issue on PR

Just FYI, Pablo has answered in the PR. In short, adding new packages means adding them also in the baselines, otherwise metacello does not load them. On Wed, Aug 1, 2018 at 6:48 AM Eric Gade wrote: > Hello all, > > I'm having a strange issue with CI on my recent pull request. See >

Re: [Pharo-dev] Problem with Iceberg and Working Branches

Hi! On Wed, Aug 1, 2018 at 1:30 PM Eric Gade wrote: > I have already mentioned some of this on Discord so forgive me for being > redundant if you've seen it. > > I'm having problems loading into the latest P7 images from Launcher a > working branch of Pharo that I have forked. I perform the

Re: [Pharo-dev] Problem with Iceberg and Working Branches

Ah, just in case I add to what I say: this particular tricky scenario is specific for Pharo and contributing to Pharo. Any third party project/library will not have the constraints described in my previous email. On Wed, Aug 1, 2018 at 1:48 PM Guillermo Polito wrote: > Hi! > > On W

Re: [Pharo-dev] Problem with Iceberg and Working Branches

o checkout the branch from origin > directly. That did give me a normal error and I do have a fuel dump of the > stack. Unfortunately it is too big to attach to emails to this list. > If you want, send me a dropbox link or something like that personally... > > I will send a follow u

Re: [Pharo-dev] Iceberg: Cannot Clone Pharo Repository

As a workaround, maybe you can try updating your fork before cloning it from Iceberg? $ git clone yourFork $ git pull from-pharo $ git push On Mon, Aug 6, 2018 at 10:26 AM Guillermo Polito wrote: > Hi Eric, > > Thanks for the report. I'm looking into it. > > On Sun, Aug 5, 2018

Re: [Pharo-dev] [rmod] About the infinite debugger

can we get this fixed? > > Tim > > On 2 Aug 2018, at 21:44, Norbert Hartl wrote: > > bump > > Am 04.07.2018 um 02:28 schrieb Martin McClure : > > On 07/03/2018 05:02 PM, Martin McClure wrote: > > On 06/29/2018 07:48 AM, Guillermo Polito wrote: > I know that the e

Re: [Pharo-dev] About the infinite debugger

On 2 Aug 2018, at 21:44, Norbert Hartl wrote: > > bump > > Am 04.07.2018 um 02:28 schrieb Martin McClure : > > On 07/03/2018 05:02 PM, Martin McClure wrote: > > On 06/29/2018 07:48 AM, Guillermo Polito wrote: > I know that the exception handling/debugging has been modifie

Re: [Pharo-dev] Iceberg: Cannot Clone Pharo Repository

Hi Eric, Thanks for the report. I'm looking into it. On Sun, Aug 5, 2018 at 6:20 PM Eric Gade wrote: > I am having (new) issues cloning my forked pharo repository in a fresh P7 > image for development. Git objects are pulled from the repository > successfully, but during the checkout phase the

[Pharo-dev] CI Down

Hi all, Since yesterday evening, CI is down because of Inria network problems at the level of Paris. Inria tells us that they do not have yet an estimation of how much time it will take to fix it. Until then, there will be no CI testing PRs nor new builds. Previous Pharo builds are still

Re: [Pharo-dev] CI Down

e: >> >> The one thing is not be able to run the CI. The bigger problem is that >> pharo is not buildable at all. Can we please move mission critical repos >> like epicea to github? >> >> Norbert >> >> Am 08.08.2018 um 09:55 schrieb Guillermo Polito <

Re: [Pharo-dev] Association hash vs equality

Actually, #= and #hash should be defined so: if (a=b) then a hash = b hash if a != b, it's not important This is required because some collections (like sets, dictionaries) will index their elements by their hash. Then, typically the collection implementation will first ask the hash, access the

Re: [Pharo-dev] Is Jenkins OK?

Nope, the osx slave is down since yesterday. https://ci.inria.fr/pharo-ci-jenkins2/computer/pharo-ci-jenkins2-osx/ I've been trying to restart it but no luck so far... I'll keep you updated. On Tue, Aug 14, 2018 at 7:49 AM Alistair Grant wrote: > I have a PR that has been running for over 13

Re: [Pharo-dev] Is Jenkins OK?

back from the > grave!! > > So we can continue working! > > Cheers. > > On Tue, Aug 14, 2018 at 10:03 AM Alistair Grant > wrote: > >> On Tue, 14 Aug 2018 at 09:59, Guillermo Polito >> wrote: >> > >> > Nope, the osx slave is down si

Re: [Pharo-dev] A new rule to implement in Pharo ?

We had another idea yesterday with Julien. Add a rule to check that in a test `self skip` is only present in the first statement of a test case. On Fri, Aug 17, 2018 at 9:38 AM Marcus Denker wrote: > > > > On 13 Aug 2018, at 14:59, Lionel Akue wrote: > > > > Hello, > > > > Do you have a rule

Re: [Pharo-dev] New Iceberg Version 1.2.1

Hi, I'll write down some of the reasons of the project's design, like that I can afterwards copy paste it in the wiki :). First, this design did not came up from an egg. We worked on it for about two months. And it is thought to be backwards compatible and manage lots of metacello

Re: [Pharo-dev] New Iceberg Version 1.2.1

> > [SNIP] > I think I can see what is the rationale behind it but I’m not sure this > can be the way to go: > > - I don’t think there can be a „standard way“ of defining source > directory. And I don’t think that a tool should enforce this however. I > keep frontend and backend code in some

Re: [Pharo-dev] [Pharo-users] New Iceberg Version 1.2.1

On Thu, Aug 9, 2018 at 11:18 AM Norbert Hartl wrote: > > > Am 08.08.2018 um 14:12 schrieb Herbert Vojčík : > > > > Damien Pollet wrote on 8. 8. 2018 13:53: > > First of all, quick stupid question: I'm currently loading my code with > gitlocal://./src as the repository URL (my workflow starts in

Re: [Pharo-dev] Stdio>>#standardIOStreamNamed:forWrite: bug?

Damien, Could you check that at least the proposed image-side changes fix your problem for *nixes? On Sat, Aug 4, 2018 at 7:13 PM Sean P. DeNigris wrote: > Alistair Grant wrote > >> Tracking issue: > >> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/274 > > The issue above is for the

Re: [Pharo-dev] Iceberg > review pull request & repo name clash

Hi Ben, The github integration has sure problems, since we were not actively working on it. So I really think it needs some love. Please go ahead an open as many issues (or PRs) as you want ^^. On Fri, Sep 7, 2018 at 4:54 AM Ben Coman wrote: > Two concerns from one flow of events... > > I was

Re: [Pharo-dev] Iceberg goodness plus ideas

Hi Ben, I'm really interested on improving on this. Please read below :) On Sun, Sep 9, 2018 at 5:07 PM Ben Coman wrote: > First, kudos to Iceberg team for detecting the mistake I made messing > around at the command line under the feet of an Iceberg managed repo. > I'm interested in some

Re: [Pharo-dev] Release test for unused temps and other

Hi, I don't think that 20 seconds will affect the overall process :). It will only become a problem if we increment the number of these kind of tests by *a lot*... Another solution is to make some tests run in parallel. But for this to run properly we have to increase the number of slaves in

Re: [Pharo-dev] Pharo BOF at ESUG

Ok by me, so tuesday or wednesday? On Mon, Sep 10, 2018 at 2:46 PM Stéphane Ducasse wrote: > Hello > > We would like to have a BOF around Pharo. > Since there are many topics to talk about. > Tuesday after the show us your project? > We can have one at the beach before the social event aroun

[Pharo-dev] Tonel class comments

Hi all, Since people have been asking how to use Tonel, I've took a look at it and have written down two class comments for both the reader and the writer. I'll push them to Tonel and schedule soon a patch release with it. Here are the class comments so people can see them/discusses them. Please,

Re: [Pharo-dev] Loading configuration of spur

Hi, I'll Esteban answer better but I don't know if that VMMaker mirror is up to date. Taking a look at the images/newImage.sh script, it is using Pharo5.0. But I see no reason for it not working on latest versions. Probably some patches are required... What is your error? On Sun, Mar 11, 2018

Re: [Pharo-dev] Loading configuration of spur

ncoder class>>#isExtension: which seems to have been removed from > the image. It is a bit different to typical doesNotUnderstand errors > because it opens an emergency evaluator and leaves the image unusable. > > On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito < > guillermopol...@g

Re: [Pharo-dev] Error opening Zinc MC repository in latest Pharo 7

Ah, that's Iceberg's magic proxies I think :/ On Tue, Mar 13, 2018 at 3:05 PM, Sven Van Caekenberghe wrote: > For some reason I can no longer open Zinc's old school MC repository in > Pharo-7.0+alpha.build.690.sha.ffd58dcc88a0698be21b52b565a86316799cb25d > (32 Bit) > >

Re: [Pharo-dev] Error opening Zinc MC repository in latest Pharo 7

that, is to create a pharo repository. That should "bind" the proxy version infos... On Tue, Mar 13, 2018 at 3:40 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > Well it is so magic that I do not understand what is happening ... > > > On 13 Mar 2018, at 15:32, Gu

Re: [Pharo-dev] cannot write to the changes file

Yes, the changes files were being opened twice, and the second time it failed :). On Tue, Mar 13, 2018 at 11:11 PM, Cyril Ferlicot D. < cyril.ferli...@gmail.com> wrote: > Le 13/01/2018 à 18:03, Ben Coman a écrit : > > > > Great! That was quick work (thanks Pavel.) > > Do you have an issue for me

Re: [Pharo-dev] Epicea changes broken in latest 7

I cannot reproduce it from here... does your file have non-ascii characters? On Wed, Mar 14, 2018 at 10:55 AM, Sven Van Caekenberghe wrote: > World Menu > Tools > Code Changes > > click on any change, boom. > > [ :error | > (OmFileStoreReadingError > readingError: error >

Re: [Pharo-dev] Released versions in Pharo Bootstrap

Hi Dale! On Mon, Mar 5, 2018 at 8:07 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > > > On 03/05/2018 09:07 AM, Guillermo Polito wrote: > >> On the other side, there is the fact that Metacello baselines are so far >> nice to describ

[Pharo-dev] generated webdoc?

Hi all, I know that we had before the generated webdoc from pharo releases in the file server (files.pharo.org). But I cannot see it anymore. Do we still have it hosted somewhere? We were planning to use it as online material for a course. I know that it is mostly not needed, but newby students

Re: [Pharo-dev] MCMczWriter>>#flush breaks

On Tue, Mar 13, 2018 at 8:08 PM, Sven Van Caekenberghe wrote: > Hi, > > I was trying to merge in Zinc changes from the latest Pharo 7 back to the > MC Zinc repos. It seems like MCMczWriter>>#flush breaks [1]. I can save to > the package cache but not to an Http repo, nor copy to

Re: [Pharo-dev] Loading code with iceberg

Hi Javier, you should register your repository, otherwise it will be just garbage collected: [[[ myRepository register. ]]] On Sun, Apr 1, 2018 at 4:57 PM, Javier Pimás wrote: > We are loading some code using Iceberg API in pharo6.1. That works fine, > the problem

Re: [Pharo-dev] help wanted: normalising LF on tonel for Pharo project

Yes, that is the thing. Is libgit reading that properties file or not? I'll do some digging.. On Tue, Apr 10, 2018 at 11:31 PM, Peter Uhnák wrote: > > Git for Windows even asks you if you want to automatically convert CRLF > > to LF during checkin and back to CRLF on

Re: [Pharo-dev] help wanted: normalising LF on tonel for Pharo project

It could be a checkbox in the "create repository dialog". "Use lf as default line ending" (and set it to true by default (?)) On Tue, Apr 10, 2018 at 11:50 PM, Peter Uhnák wrote: > An argument can be made that Pharo would _always_ produce LF. > I don't think I've ever

Re: [Pharo-dev] help wanted: normalising LF on tonel for Pharo project

Both, the checkbox will be used to set the property in disk at some point :). On Tue, Apr 10, 2018 at 11:55 PM, Esteban Lorenzano <esteba...@gmail.com> wrote: > or a .iceberg file? > > Esteban > > ps: yep, we need it… we will have it, why not start now? > > On 10 Ap

Re: [Pharo-dev] help wanted: normalising LF on tonel for Pharo project

I'd say yes? https://github.com/libgit2/libgit2/commit/b83fd07880307106deb0ac7cb0d415d85c27f465 ? On Tue, Apr 10, 2018 at 11:42 PM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Yes, that is the thing. Is libgit reading that properties file or not? > I'll do some digging.

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 7:34 PM, Ben Coman <b...@openinworld.com> wrote: > > > On 14 April 2018 at 01:10, Guillermo Polito <guillermopol...@gmail.com> > wrote: > >> >> >> On Fri, Apr 13, 2018 at 5:57 PM, Ben Coman <b...@openinworld.com> wrote:

Re: [Pharo-dev] Iceberg2.0 crash test passed :)

Is that Pharo 7? On Fri, Apr 13, 2018 at 9:43 PM, Serge Stinckwich < serge.stinckw...@gmail.com> wrote: > Yes I was able to commit also. > Very slick interface :-) > > > But now, every time I want to commit, my image crash and I have: > > Assertion failed: (git_atomic_get(__n_inits) > 0),

Re: [Pharo-dev] Iceberg2.0 crash test passed :)

I want your bug reports! Le ven. 13 avr. 2018 à 21:09, Stephane Ducasse a écrit : > I could commit my first commit with iceberg 2.0 > Well done > > It feels nicer :). > > Stef > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 5:57 PM, Ben Coman <b...@openinworld.com> wrote: > > > On 13 April 2018 at 23:15, Alistair Grant <akgrant0...@gmail.com> wrote: > >> On 13 April 2018 at 17:07, Cyril Ferlicot <cyril.ferli...@gmail.com> >> wrote: >> >

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 5:15 PM, Alistair Grant <akgrant0...@gmail.com> wrote: > On 13 April 2018 at 17:07, Cyril Ferlicot <cyril.ferli...@gmail.com> > wrote: > > > > > > On ven. 13 avr. 2018 at 17:03, Guillermo Polito < > guillermopol...@

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 4:26 PM, Ben Coman wrote: > > > On 13 April 2018 at 21:14, Marcus Denker wrote: > >> >> >> On 13 Apr 2018, at 15:04, Andrei Stebakov wrote: >> >> Can you make the video available online? >> >> >>

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 5:38 PM, Alistair Grant <akgrant0...@gmail.com> wrote: > Hi Guille, > > On 13 April 2018 at 17:29, Guillermo Polito <guillermopol...@gmail.com> > wrote: > > > > > > On Fri, Apr 13, 2018 at 5:15 PM, Alistair Grant <akgrant0..

Re: [Pharo-dev] Images, VMs and 32 vs 64bit

VMs share most of the code. At least the basic interpreter, primitives and garbage collector. But there are some platform specificities such as how some plugins are managed. Also there are different JIT backends, one per platform. I don't know if a VM comes shipped with all of them or just the one

Re: [Pharo-dev] Environment variables encoding ?

Hi, I think this problem is not environment variable exclusive. It also affects file paths and others. So far Pharo does not detect the locale to perform the encoding and it should be nice to do it. On Tue, Apr 17, 2018 at 10:56 AM, Henrik Sperre Johansen < henrik.s.johan...@veloxit.no> wrote:

Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

On Sun, Apr 15, 2018 at 3:19 PM, Ben Coman wrote: > I am doing a pass to cleanup the DelayScheduler hierarchy. > I'll be refactoring of the hierarchy to aid code understanding > and eliminate redundant instance variables from the original code. > The target structure is

Re: [Pharo-dev] Do we kill the catalog?

Hi all, IMHO, the problem is not metacello or gofer but the fact that the catalog uses the old Metacello API: i.e., Gofer new repository: 'zzz'; configurationOf: 'XXX'; load. (ConfigurationOfXXX project version: #YYY) load instead of the *new* Metacello API Metacello new repository:

Re: [Pharo-dev] Do we kill the catalog?

Hi all, I think that we are all aligned. Stef may be "too strong" in his way of talking, but he raised an issue: we should probably do an iteration on the catalog. And I think we all agree on that? So, what would be a list of tasks for it? (I copy past what Stef put before) - Use Metacello API.

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-03-19

Can't we make Extensions first class objects in ring? On Mon, Mar 26, 2018 at 11:02 AM, Pavel Krivanek wrote: > 2018-03-26 10:52 GMT+02:00 Stephane Ducasse : > > Pavel > > > > Why we do not know if this is a class or trait? > > Imagine that you

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

On Fri, Mar 23, 2018 at 7:53 PM, Ben Coman wrote: > > > On 23 March 2018 at 11:31, Ben Coman wrote: > >> >> >> On 23 March 2018 at 05:14, Cédrick Béler wrote: >> >>> Hi, >>> >>> I just saw students and they still have some problem

Re: [Pharo-dev] Build 739 breaks project load initialization order?

I'm checking it. It may be a side effect of: https://github.com/pharo-project/pharo/pull/1130 Short story long: - building Pharo we need to ensure that class initializations are executed in a particular order, so some metacello configurations are disabling monticello initializers during

Re: [Pharo-dev] Build 739 breaks project load initialization order?

PR: https://github.com/pharo-project/pharo/pull/1161 I added a test to avoid this problem in the future. Guille On Thu, Mar 29, 2018 at 9:36 AM, Guillermo Polito <guillermopol...@gmail.com > wrote: > Issue: https://pharo.manuscript.com/f/cases/21658/ > Monticello-initializers-are

Re: [Pharo-dev] Build 739 breaks project load initialization order?

Issue: https://pharo.manuscript.com/f/cases/21658/Monticello-initializers-are-not-enabled-by-default On Thu, Mar 29, 2018 at 9:33 AM, Guillermo Polito <guillermopol...@gmail.com > wrote: > I'm checking it. > > It may be a side effect of: https://github.com/pharo- > proje

Re: [Pharo-dev] [pharo-project/pharo] 21646 AbstractFileReference should use "utilities" protocol name (#1149)

Hi Torsten, I like all this cleanups and recategorizations. But I have two requests, tell me what you think: - first and more important. I'd like that we define a convention document in a wiki page or pillar document for protocols. What are the correct protocols to use and why? This is

Re: [Pharo-dev] Pharo 7 new file stream encoders

That should be fixed now. I proposed also the rename. I can revert it if needed. On Fri, Mar 16, 2018 at 1:04 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > > On 16 Mar 2018, at 11:29, Guillermo Polito <guillermopol...@gmail.com> > wrote: > > >

Re: [Pharo-dev] FileHandle creates a buffered stream on a buffered stream

Nice catch. The write stream is well defined in comparison. https://pharo.fogbugz.com/f/cases/21604/FileHandle-creates-a-buffered-stream-on-a-buffered-stream https://github.com/pharo-project/pharo/pull/1118 Can somebody review please? Tx, Guille On Thu, Mar 15, 2018 at 4:00 PM, Sven Van

Re: [Pharo-dev] Pharo 7 new file stream encoders

Thierry, Sven, Can you review https://github.com/pharo-project/pharo/pull/1116 ? Tx, Guille On Fri, Mar 16, 2018 at 11:29 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi, > > Yes, I'll provide a PR with that functionality soon. Probably in that case > *ZnCrP

Re: [Pharo-dev] Performances of source code search on latest Pharo

Yes, looking at the stack in the profiler, there is a buffered stream missing in there. The thing is that source/changes file reading/writing required special attention in the migration (or the image became unusable :)). I'll fix it tomorrow first thing in the morning, if you can wait a couple of

Re: [Pharo-dev] pharo bootstrap is in inconsistent state

Hi! On Mon, Mar 19, 2018 at 9:17 AM, Alistair Grant wrote: [SNIP] > > https://pharo.fogbugz.com/f/cases/21615/Separate-bootstrap-process-in-to- > distinct-stages > > https://github.com/pharo-project/pharo/pull/1127 > > This does the first step of breaking the bootstrap

Re: [Pharo-dev] pharo bootstrap is in inconsistent state

On Mon, Mar 19, 2018 at 2:13 PM, Alistair Grant <akgrant0...@gmail.com> wrote: > Hi Guille, > > On 19 March 2018 at 13:59, Guillermo Polito <guillermopol...@gmail.com> > wrote: > > Hi! > > > > On Mon, Mar 19, 2018 at 9:17 AM, Alistair Grant <ak

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

If the launcher had a command line interface, I'd use it all the time :) On Tue, Mar 20, 2018 at 10:15 AM, Marcus Denker wrote: > Hi, > > > I'm really glad PharoLauncher has been promoted to the download page, > but it seems some people want to push PharoLauncher to *be*

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

Yes, it would be good to have those kind of methods. But there are some other constraints to have into account :) - introducing these without introducing duplications is right now complicated because streams do not share a hierarchy - having a common hierarchy is maybe complicated: ZnStreams

[Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

Hi all, I've put some minutes summarizing the new APIs provided by the combination of the new File implementation and the Zn encoders. They all basically follow the decorator pattern to stack different responsibilities such as buffering, encoding, line ending convertions. Please, do not hesitate

Re: [Pharo-dev] Pharo 7 new file stream encoders

Hi, Yes, I'll provide a PR with that functionality soon. Probably in that case *ZnCrPortableWriteStream* is not the right name for that class. Sven, do you think renaming it now (before it has lots of users) would be acceptable towards backwards compatibility? Otherwise I would name it

Re: [Pharo-dev] Released versions in Pharo Bootstrap

On Mon, Mar 5, 2018 at 4:45 PM, Cyril Ferlicot <cyril.ferli...@gmail.com> wrote: > > On Mon, Mar 5, 2018 at 4:38 PM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> But, "one single class" does not mean anything. Because it depends from &

Re: [Pharo-dev] Released versions in Pharo Bootstrap

t; 2018-03-05 17:17 GMT+01:00 Denis Kudriashov <dionisi...@gmail.com>: > >> 2018-03-05 17:02 GMT+01:00 Cyril Ferlicot <cyril.ferli...@gmail.com>: >> >>> >>> On Mon, Mar 5, 2018 at 4:51 PM, Guillermo Polito < >>> guillermopol...@gmail.com&

Re: [Pharo-dev] Released versions in Pharo Bootstrap

But, "one single class" does not mean anything. Because it depends from which branch/commitish you are loading it from... Can you explain better what is the problem because I am not getting it... In any case, independently of where is the burden, I want to veto any new integration that may make

Re: [Pharo-dev] Released versions in Pharo Bootstrap

> Commander. And ClassAnnotation will be in Kernel. > So we will need to load them in another time than Calypso. > > Now we can just put them directly into #loadCalypso method. (there are > three dependencies) > It will fix my problem and make Pharo build reproducible. > >

Re: [Pharo-dev] Is Beacon still planned to be added to P7?

On Mon, Apr 23, 2018 at 1:13 PM, Tudor Girba wrote: > I hope so. Beacon is ready to be integrated, but I do not know if there is > enough bandwidth right now due to the Iceberg work. > Well, if people issue a pull request I'll gladly review it. Guille > > Doru > > > On

[Pharo-dev] About the infinite debugger

Hi all, during today's sprint we have been working with lots of people on the infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/). We have checked the emails sent in the latest month. Then, together with Quentin, Pablo, Pavel, Yoan we have been discussing and testing hypothesis

[Pharo-dev] [Call for testers] Pharo Launcher 1.4.5

Hi all, We have been working these last ~two weeks with Christophe on the stability of the launcher. We have prepared version 1.4.5, and we would like to have some feedback. http://files.pharo.org/pharo-launcher/1.4.5 So, we would really LOVE, if somebody can play with this version and send us

Re: [Pharo-dev] STON updates/improvements

Thanks Sven :) On Fri, Oct 12, 2018 at 11:38 AM Sven Van Caekenberghe wrote: > Now, AFTER the changes, the STON serialisation looks as follows: > > { > #datatype : MimeType [ 'application/json' ], > #background : Color [ #red ], > #home : URL [

Re: [Pharo-dev] Streams and FileDialog in Pharo 6 and 7

Ok, so can we agree on deprecating the non compatible methods and redirect the user to the new ones? To me, the problem with returning a stream is that from a user perspective you don't know: - is the file encoded or binary - if it is encoded, in which encoding? - if i receive an open file

Re: [Pharo-dev] Streams and FileDialog in Pharo 6 and 7

o file" UIManager default chooseExistingFileReference: 'title' extensions: nil path: FileSystem workingDirectory / 'PharoDebug.log'. "Get file reference for save (not necessarily existing)" UIManager default chooseForSaveFileReference: 'title' extensions: #('log') path: 'PharoDebuasdg.log'. On Fri, Oct 26,

Re: [Pharo-dev] Streams and FileDialog in Pharo 6 and 7

pect file references because it is what is exposed to users > in pharo file system. Not neccessery to put it in method name. > > пт, 26 окт. 2018 г., 16:32 Guillermo Polito : > >> Hi all, >> >> I've proposed a PR with some cleanups in this respect >> >> https://gi

[Pharo-dev] Better management of encoding of environment variables

Hi all, following the meeting we had here @Inria headquarters, I'll be backporting some of the improvements we did in the launcher this last month regarding the encoding of environment variables. I've opened for this issue https://pharo.fogbugz.com/f/cases/22658/ We have already studied

<    1   2   3   4   5   6   7   8   >