Re: [Pharo-dev] Reflecting on data (literal) object syntax

2017-06-30 8:28 GMT-03:00 Norbert Hartl : >> Am 30.06.2017 um 12:03 schrieb Stephane Ducasse : >> recently I started to read a book on machine learning and they >> manipulate dictionary of dictionary. (So I started my own >> implementation and I will

Re: [Pharo-dev] Reflecting on data (literal) object syntax

> But what is DataFrame? the new collection done by alesnedr from Lviv. It is really nice but does not solve the problem of the compact syntax. >> >> STON fromString: 'Point[10,20]' >> > Same goes for JSON. > >> We were brainstorming with marcus and we could have a first nice extension: >> >> {

Re: [Pharo-dev] Reviewing of the pull requests

2017-06-30 17:58 GMT+02:00 Ben Coman : > > > On Fri, Jun 30, 2017 at 4:28 PM, Pavel Krivanek > wrote: > >> Hi, >> >> the reviewing of the pull requests is currently not as easy as we would >> like to have. For simple changes it should be enough to

Re: [Pharo-dev] About Fogbugz 20165 Support-segment-path-printing

Thanks! This is cool I'm learning how to PR too :). Stef On Fri, Jun 30, 2017 at 4:55 PM, Pavel Krivanek wrote: > The PR is updated > > -- Pavel > > 2017-06-30 16:44 GMT+02:00 Alistair Grant : >> >> Attached is the changeset as discussed in my

Re: [Pharo-dev] The new implementation of current working directory

On Fri, Jun 30, 2017 at 4:12 PM, Guillermo Polito wrote: > > > On Fri, Jun 30, 2017 at 9:56 AM, Alistair Grant > wrote: > >> Rajula, thanks for your write-up. >> >> As the person who pushed Rajula to send his email I feel I should >> respond.

Re: [Pharo-dev] Reviewing of the pull requests

On Fri, Jun 30, 2017 at 4:28 PM, Pavel Krivanek wrote: > Hi, > > the reviewing of the pull requests is currently not as easy as we would > like to have. For simple changes it should be enough to go to the pull > requests list

Re: [Pharo-dev] About Fogbugz 20165 Support-segment-path-printing

On Fri, Jun 30, 2017 at 04:55:29PM +0200, Pavel Krivanek wrote: > The PR is updated > > -- Pavel Thanks, Pavel! > 2017-06-30 16:44 GMT+02:00 Alistair Grant : > > Attached is the changeset as discussed in my last email. > > Just to be clear, this is just for

Re: [Pharo-dev] About Fogbugz 20165 Support-segment-path-printing

The PR is updated -- Pavel 2017-06-30 16:44 GMT+02:00 Alistair Grant : > Attached is the changeset as discussed in my last email. > > Just to be clear, this is just for reference, I'm happy to redo the PR > if it will save you and/or Pavel some time. > > Cheers, >

Re: [Pharo-dev] About Fogbugz 20165 Support-segment-path-printing

Attached is the changeset as discussed in my last email. Just to be clear, this is just for reference, I'm happy to redo the PR if it will save you and/or Pavel some time. Cheers, Alistair On 30 June 2017 at 16:42, Alistair Grant wrote: > Hi Stef, > > Good pickup. > > I

Re: [Pharo-dev] About Fogbugz 20165 Support-segment-path-printing

Hi Stef, Good pickup. I also can't load SLICE-Issue-20165-Support-segment-path-printing-AlistairGrant.1. Somehow it is dependent on FileSystem-Core-AlistairGrant.223, and I have no idea what that is (I don't remember ever creating it, and I don't have a copy on my machine anywhere, or in any of

[Pharo-dev] About Fogbugz 20165 Support-segment-path-printing

Hi alistair I'm starting to review code that is in the PR pipeline. https://github.com/pharo-project/pharo/pull/126 I noticed that you wrote in the slice Changes since last slice: - Change Path>>fullName to just print the path - Fix absolute path strings - Bug fix Path class>>from:delimiter: -

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

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

[Pharo-dev] [pharo-project/pharo-core] d09696: 60505

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

Re: [Pharo-dev] Recursively downloading Pharo packages / Building images with Nix

I have done some work on packaging up pharo projects for Nix so that images can be created in the sandboxed build environment. I am a bit stuck though. I have a script that takes a project named and creates a specification of all the required mcz files, recursing into dependencies: Here is the

Re: [Pharo-dev] Reflecting on data (literal) object syntax

Hi, > Am 30.06.2017 um 12:03 schrieb Stephane Ducasse : > > Hi > > recently I started to read a book on machine learning and they > manipulate dictionary of dictionary. (So I started my own > implementation and I will switch to DataFrame). > having an abstract

Re: [Pharo-dev] Reflecting on data (literal) object syntax

for fun I implemented asObjectOf: MCSmalltalkhubRepository owner: 'StephaneDucasse' project: 'asObjectOf' user: '' password: '' On Fri, Jun 30, 2017 at 12:03 PM, Stephane Ducasse wrote: > Hi > > recently I started to read a book on machine learning and

Re: [Pharo-dev] about expressions

Ok. Then we can have an ordered expression :) A sequence without a declaration is a bit useless. On Fri, Jun 30, 2017 at 11:56 AM, Damien Pollet wrote: > Surprising that a sequence is not an expression. I'm pretty sure that (1+2. > 2+3) is an expression that returns 5

[Pharo-dev] Reflecting on data (literal) object syntax

Hi recently I started to read a book on machine learning and they manipulate dictionary of dictionary. (So I started my own implementation and I will switch to DataFrame). Now it occurred to me that when we program complex objects we do not need a compact literal syntax for our objects. But when

Re: [Pharo-dev] about expressions

Surprising that a sequence is not an expression. I'm pretty sure that (1+2. 2+3) is an expression that returns 5 (after computing a useless addition). What is currently not an expression is the variable declaration, indeed. But if we make |d| an expression then that means we can declare variables

[Pharo-dev] about expressions

I do not get why (Yes I know it is because it is not in the syntax but it is conceptually not nice). | d | d := Dictionary new. d at: #top at: #below1 put: 1. d at: #top at: #below1 put: 2. d at: #top at: #below1. is not an expression in Pharo. It means that I can manipulate 1 + 3, x + 3

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

I did not take any blame in wht you say. I just wanted to explain that yes comments can be wrong :) I'm super happy to get some brains looking at improving FS. I'm fighting to see how we can start to integrate faster changes in P70. On Fri, Jun 30, 2017 at 10:58 AM, Alistair Grant

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

Hi Stef, On Fri, Jun 30, 2017 at 09:46:44AM +0200, Stephane Ducasse wrote: > Hi alistair > > I do not know if this is me that wrote a wrong path class comment. > You should consider that theere were nearly no comment at all and I > started to try to give more love to this great library. > >

Re: [Pharo-dev] Pharo 7 provisional HOWTO

I did a simlink total 124088 -rw-rw-r-- 1 ducasse admin 381 Jun 30 10:18 Pharo7.0-32bit-70f3b57.changes -rw-rw-r-- 1 ducasse admin 29740016 Jun 29 13:38 Pharo7.0-32bit-70f3b57.image -rw-rw-r-- 1 ducasse admin 33711804 Jun 29 13:37 Pharo7.0-32bit-70f3b57.sources -rw-r--r--@ 1 ducasse

Re: [Pharo-dev] Pharo 7 provisional HOWTO

I do not get why repository := IceRepositoryCreator new location: ('/Users/ducasse/Workspace/FirstCircle/ActiveResearch/Pharo/PharoCodeBase/pharo-core' asFileReference); is not working and repository := IceRepositoryCreator new location: ('pharo-core' asFileReference); + simlink would be

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Ok I try to understand. I already cloned the github repo and I do not want to be forced to download all these small files all the time. I want one place with all the forked code one and only one. I will try to create a simlink and try again. Tx Stef On Fri, Jun 30, 2017 at 10:26 AM, Pavel

Re: [Pharo-dev] The new implementation of current working directory

Hi Guillermo, On Fri, Jun 30, 2017 at 10:12:32AM +0200, Guillermo Polito wrote: > On Fri, Jun 30, 2017 at 9:56 AM, Alistair Grant wrote: > > Rajula, thanks for your write-up. > > As the person who pushed Rajula to send his email I feel I should > respond. >

[Pharo-dev] Reviewing of the pull requests

Hi, the reviewing of the pull requests is currently not as easy as we would like to have. For simple changes it should be enough to go to the pull requests list (https://github.com/pharo-project/pharo/pulls) and review the changes from the GitHub web interface. In case that the PR passes tests

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Unfortunately you cannot share the repository the way you try because it always needs to be in the image working directory in a folder named 'pharo-core'. Without it the Monticello will not be able to see changes int the packages. On one location place Pharo 7 image and execute the first script

Re: [Pharo-dev] The new implementation of current working directory

On Fri, Jun 30, 2017 at 9:56 AM, Alistair Grant wrote: > Rajula, thanks for your write-up. > > As the person who pushed Rajula to send his email I feel I should > respond. > > While I'm in favour of Rajula's proposed changes, scripting in > particular will be much easier,

Re: [Pharo-dev] Pharo 7 provisional HOWTO

DoIt ^ repository remotes detect: [ :remote | self halt. remote remoteName = 'pharo' ] remote remoteName returns 'origin' and not the name of the fork so what is upstream? Pharo on github origin? the one local? Stef On Fri, Jun 30, 2017 at 10:04 AM, Stephane Ducasse

Re: [Pharo-dev] The new implementation of current working directory

Thanks for the detailed explanation Rajula. I think it makes perfect sense to separate working and image directories from each other. What you didn't mention is how the current working directory is resolved when an image is not started from the command line but by using the operating systems

Re: [Pharo-dev] Stable Pharo VM for Linux?

On 29 June 2017 at 18:29, Alistair Grant wrote: > git clone https://github.com/OpenSmalltalk/opensmalltalk-vm.git > cd opensmalltalk-vm > git checkout 6a63f68 > Just in quick happy testing... The 32-bit VM seems to be fine the 64-bit VM is not working

Re: [Pharo-dev] Pharo 7 provisional HOWTO

So I do not understand Now if I do repository := IceRepositoryCreator new location: ('/Users/ducasse/Workspace/FirstCircle/ActiveResearch/Pharo/PharoCodeBase/pharo-core' asFileReference); subdirectory:'src'; createRepository. repository register. it works but doing it twice breaks. How can I

Re: [Pharo-dev] The new implementation of current working directory

> On 30 Jun 2017, at 09:56, Alistair Grant wrote: > > Rajula, thanks for your write-up. > > As the person who pushed Rajula to send his email I feel I should > respond. > > While I'm in favour of Rajula's proposed changes, scripting in > particular will be much easier,

Re: [Pharo-dev] The new implementation of current working directory

Rajula, thanks for your write-up. As the person who pushed Rajula to send his email I feel I should respond. While I'm in favour of Rajula's proposed changes, scripting in particular will be much easier, I think we need to make the change generally known as it will not always be obvious, e.g. at

Re: [Pharo-dev] Pharo 7 provisional HOWTO

No I did it from a freshly donwloaded image. Pharo7.0-32bit-70f3b57.zip On Fri, Jun 30, 2017 at 9:47 AM, Pavel Krivanek wrote: > The script in section "Use already created clone" is supposed to be used by > a fresh Pharo 7 image. Maybe you are trying it on an image that

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

Hi alistair I'm not expert of file system. Now I like your idea to have explicit messages such as canonalize or expand. Stef On Tue, Jun 27, 2017 at 8:56 PM, Alistair Grant wrote: > Hi Sven, > > On Tue, Jun 27, 2017 at 01:31:42PM +0200, Sven Van Caekenberghe wrote: >> Hi

Re: [Pharo-dev] Pharo 7 provisional HOWTO

The script in section "Use already created clone" is supposed to be used by a fresh Pharo 7 image. Maybe you are trying it on an image that already has the repository set? Even if I tried to use the name 'pharo' instead of 'myFork', the scripts work. Cheers, -- Pavel 2017-06-30 9:34 GMT+02:00

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

Hi alistair I do not know if this is me that wrote a wrong path class comment. You should consider that theere were nearly no comment at all and I started to try to give more love to this great library. Stef On Tue, Jun 27, 2017 at 8:56 PM, Alistair Grant wrote: > Hi

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Hi pavel Since I want to reuse my clone. I tried the following. But I have no idea about the name of my fork so I put the one of my fork = pharo and it seems that this is what should be done. Now when I execute this script I get 'You already have an Iceberg repository So hat should I do?

Re: [Pharo-dev] Pharo 7 provisional HOWTO

It is an iceberg plugin. 100% Pharo Code, uses the github.com rest api. On 30 Jun 2017 09:25, "Stephane Ducasse" wrote: > What is the github plugin? an Iceberg Pharo code or a C plugin? > > On Wed, Jun 28, 2017 at 6:25 PM, Esteban Lorenzano >

Re: [Pharo-dev] Pharo 7 provisional HOWTO

What is the github plugin? an Iceberg Pharo code or a C plugin? On Wed, Jun 28, 2017 at 6:25 PM, Esteban Lorenzano wrote: > > On 28 Jun 2017, at 18:21, Nicolai Hess wrote: > > And if I only want to contribute by reviewing a fix. Do I have to go the >