Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

+1 for pinInMemory It explains what it does. On 9/14/17, Eliot Miranda wrote: > Hi Norbert, > >> On Sep 13, 2017, at 3:18 PM, Norbert Hartl wrote: >> >> >>> Am 14.09.2017 um 00:09 schrieb Eliot Miranda : >>> >>> Hi Denis,

Re: [Pharo-dev] [Pharo 7.0-dev] Build #125: SUCCESS

the build is red, not success -- Pavel 2017-09-14 11:18 GMT+02:00 : > There is a new Pharo build available! > > The status of the build #125 was: SUCCESS. > > Could not extract further issue information from commit message: Merge > pull request #278 from

[Pharo-dev] Author name in version Iceberg?

What is needed to make sure the author/committer name is shown in a method version instead of 'GitHub' when using Iceberg? Stephan

Re: [Pharo-dev] Directory structure on files.pharo.org

On 11-09-17 11:18, Guillermo Polito wrote: On Mon, Sep 11, 2017 at 10:55 AM, stephan > wrote: This looks like it is missing directories. On the other hand, perhaps exposing the build steps as directories might not be the best idea, as

Re: [Pharo-dev] Author name in version Iceberg?

> On 14 Sep 2017, at 10:53, Pavel Krivanek wrote: > > AFAIK Esteban is planning to support blame in future at least for Tonel (the > FileTree replacement), however we are not yet there. this ^ (but we will support it for both: filetree AND tonel, if

[Pharo-dev] [Pharo 7.0-dev] Build #125: SUCCESS

There is a new Pharo build available! The status of the build #125 was: SUCCESS. Could not extract further issue information from commit message: Merge pull request #278 from guillep/20421-Email-should-run-in-a-node-and-separate-stage-to-be-sent Case 20421: make email run in a unix

Re: [Pharo-dev] [Calypso] Toolbar and Statusbar Look - voting time

Thank's guys for comments. And thank's Torsten for this initiative. I will merge your changes soon. 2017-09-14 7:09 GMT+02:00 Max Leske : > Right > > > On 13 September 2017 at 18:08:26, Torsten Bergmann (asta...@gmx.de) wrote: > > Hi all, > > as you know Denis Kudriashov does

Re: [Pharo-dev] Author name in version Iceberg?

AFAIK Esteban is planning to support blame in future at least for Tonel (the FileTree replacement), however we are not yet there. -- Pavel 2017-09-14 10:50 GMT+02:00 stephan : > On 14-09-17 10:06, Pavel Krivanek wrote: > >> Iceberg currently uses metadata-less format that does

Re: [Pharo-dev] Directory structure on files.pharo.org

On Thu, Sep 14, 2017 at 9:36 AM, stephan wrote: > On 11-09-17 11:18, Guillermo Polito wrote: > >> >> On Mon, Sep 11, 2017 at 10:55 AM, stephan step...@stack.nl>> wrote: >> >> This looks like it is missing directories. >> On the other hand, perhaps

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hello. I guess we are agree to rename. I will prepare pull request for Pharo. And Squeak is up to you. Here is the new messages: - pinInMemory - unpinInMemory - isPinnedInMemory - setPinnedInMemory: What was decision about #pinInMemoryDuring: ? Do we need it? 2017-09-14 9:28 GMT+02:00 H.

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

On 25-08-17 16:42, Stephane Ducasse wrote: I'm writing a doc of the process so that other people can do it for their private projects. I know how to copy and rename an existing project, and put that on github. What else do I need to do? Register with bintray, register with travis, generate

Re: [Pharo-dev] Bintray for Pharo7 images?

On Thu, Sep 14, 2017 at 8:56 AM, Holger Freyther wrote: > Hey, > > I keep on clicking on the "bintray" badges to get to a recent Pharo7 image > but after looking at the Jenkinsfile I don't see the script being invoked > and given the timestamp of "201706" it seems no

Re: [Pharo-dev] Author name in version Iceberg?

Iceberg currently uses metadata-less format that does not store method timestamp because of the merging conflicts. You cannot do anything now, sorry. -- Pavel 2017-09-14 9:23 GMT+02:00 stephan : > What is needed to make sure the author/committer name is shown in a method >

Re: [Pharo-dev] Author name in version Iceberg?

On 14-09-17 10:06, Pavel Krivanek wrote: Iceberg currently uses metadata-less format that does not store method timestamp because of the merging conflicts. You cannot do anything now, sorry. No support for blame? Stephan

Re: [Pharo-dev] Sources location and name, PharoLauncher

On 14-09-17 14:52, Peter Uhnák wrote: That's not related to Pharo Launcher. Pharo 7 sources (for alpha images) are now shipped with the image, not the VM. That's an issue. I have hundreds of images, and definitely don't need so many different sources. Stephan

Re: [Pharo-dev] Sources location and name, PharoLauncher

That's not related to Pharo Launcher. Pharo 7 sources (for alpha images) are now shipped with the image, not the VM. Peter On Thu, Sep 14, 2017 at 2:45 PM, stephan wrote: > After Peter's tweet about the automatic downloading of a vm I decided to > try the improved

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

> Am 14.09.2017 um 10:17 schrieb Denis Kudriashov : > > Hello. > > I guess we are agree to rename. I will prepare pull request for Pharo. And > Squeak is up to you. > > Here is the new messages: > - pinInMemory > - unpinInMemory > - isPinnedInMemory > -

[Pharo-dev] Sources location and name, PharoLauncher

After Peter's tweet about the automatic downloading of a vm I decided to try the improved PharoLauncher myself. I like the automatic downloading of a vm. When trying it, I noticed that the sources dependency changed to a very unusable one: each image needs its own specific sources file.

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

> On Sep 14, 2017, at 7:07 AM, Norbert Hartl wrote: > > > >> Am 14.09.2017 um 10:17 schrieb Denis Kudriashov : >> >> Hello. >> >> I guess we are agree to rename. I will prepare pull request for Pharo. And >> Squeak is up to you. >> >> Here is the

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

!! How to render automatically your pillar file as pdf We will use bintray to store the latest pdf and we will use github the released pdf. !!! Create an account in bintray Create an account on bintray at https://bintray.com/ You may link it or not to your github account !!! Obtain an encoded

Re: [Pharo-dev] [Calypso] Toolbar and Statusbar Look - voting time

On 14 September 2017 at 09:24, Denis Kudriashov wrote: > Thank's guys for comments. And thank's Torsten for this initiative. I will > merge your changes soon. RIGHT. A bit late to the party, but I agree that the right version is much easier to read. Thanks, Alistair >

Re: [Pharo-dev] Author name in version Iceberg?

For FileTree using log should be enough to get the authorship. For tonel you need blame. On Thu, Sep 14, 2017 at 8:47 PM, Stephane Ducasse wrote: > a > ok but still we need help because our todo list is long. > > > On Thu, Sep 14, 2017 at 8:37 PM, stephan

Re: [Pharo-dev] [Calypso] Toolbar and Statusbar Look - voting time

Thanks Denis for your positive mindset and constant willingness to improve. On Thu, Sep 14, 2017 at 3:05 PM, Alistair Grant wrote: > On 14 September 2017 at 09:24, Denis Kudriashov wrote: >> Thank's guys for comments. And thank's Torsten for this

Re: [Pharo-dev] Sources location and name, PharoLauncher

Kill some images :). We did that for good reasons I do not remember why but this is due to the bootstrap. Stefan we will never be perfect day one. This is not possible for us. Stef On Thu, Sep 14, 2017 at 3:10 PM, stephan wrote: > On 14-09-17 14:52, Peter Uhnák wrote: >> >>

[Pharo-dev] Are assignment to block variables is prohibited?

Hi I know that method arg are read only and you cannot assign to them. Now what is the status of block arguments? Because some old code of plotmorph is breaking. Stef

Re: [Pharo-dev] Sources location and name, PharoLauncher

2017-09-14 15:10 GMT+02:00 stephan : > On 14-09-17 14:52, Peter Uhnák wrote: > >> That's not related to Pharo Launcher. Pharo 7 sources (for alpha images) >> are now shipped with the image, not the VM. >> > > That's an issue. I have hundreds of images, and definitely don't need

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

On 14-09-17 19:10, Stephane Ducasse wrote: I added a pillar file into PharoInProgress https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Bintray Feel free to edit it and improve it. I will make sure that it compiles after lunch. Super! Stephan

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

here is a first pdf On Thu, Sep 14, 2017 at 7:10 PM, Stephane Ducasse wrote: > I added a pillar file into PharoInProgress > > https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Bintray > > Feel free to edit it and improve it. > I will make sure that

Re: [Pharo-dev] Author name in version Iceberg?

Hi guys We worked during years without blame. If you tell me I have a long list of more important items for esteban: - Freetype plugin killing - retina support - Idle Vm - signed mac VM - cleaning host logic in C VM logic - using SDL2 In fact our list is huge and I do not see blame. On Thu,

Re: [Pharo-dev] Author name in version Iceberg?

On 14-09-17 20:05, Stephane Ducasse wrote: We worked during years without blame. If you tell me I have a long list of more important items for esteban: ... In fact our list is huge and I do not see blame. The thing is just to use blame to extract the author information. I guess it is the

Re: [Pharo-dev] Author name in version Iceberg?

a ok but still we need help because our todo list is long. On Thu, Sep 14, 2017 at 8:37 PM, stephan wrote: > On 14-09-17 20:05, Stephane Ducasse wrote: >> >> We worked during years without blame. If you tell me I have a long >> list of more important items for esteban: > >

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

I added a pillar file into PharoInProgress https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Bintray Feel free to edit it and improve it. I will make sure that it compiles after lunch. Stef On Thu, Sep 14, 2017 at 6:49 PM, Stephane Ducasse wrote:

Re: [Pharo-dev] Pharo 6.1 32bit/64bit on CentOS 7 with Iceberg

I used it but not enough to help you with this issue. Phil On Thu, Sep 14, 2017 at 12:22 AM, Andrei Chis wrote: > Hi, > > Does anybody use Pharo 6.1 (32 or 64 bit) on CentOS 7? > I am getting randomly the following crash when trying to clone a > repository from

Re: [Pharo-dev] Sources location and name, PharoLauncher

On 14-09-17 20:00, Stephane Ducasse wrote: Kill some images :). We did that for good reasons I do not remember why but this is due to the bootstrap. Stefan we will never be perfect day one. This is not possible for us. Don't worry. Break it to improve it. I have to change my workflow, so I am

Re: [Pharo-dev] [Calypso] Toolbar and Statusbar Look - voting time

"Denis Kudriashov" wrote >Thank's guys for comments. And thank's Torsten for this initiative. I will >merge your changes soon. No - we have to thank you. For Calypso, for accepting the community decision and (in advance) for merging the first Calypso pull request. I'm pretty sure the next

Re: [Pharo-dev] Are assignment to block variables is prohibited?

Yes. But there is a setting for the compiler to load/compile code with errors. 2017-09-14 20:46 GMT+02:00 Stephane Ducasse : > Hi > > I know that method arg are read only and you cannot assign to them. > Now what is the status of block arguments? > Because some old code

Re: [Pharo-dev] Are assignment to block variables is prohibited?

2017-09-14 21:43 GMT+02:00 Nicolai Hess : > Yes. But there is a setting for the compiler to load/compile code with > errors. > > > 2017-09-14 20:46 GMT+02:00 Stephane Ducasse : > >> Hi >> >> I know that method arg are read only and you cannot assign

[Pharo-dev] Bintray for Pharo7 images?

Hey, I keep on clicking on the "bintray" badges to get to a recent Pharo7 image but after looking at the Jenkinsfile I don't see the script being invoked and given the timestamp of "201706" it seems no images were uploaded for a while? Should we remove the bintray badge or upload them