Re: [Pharo-dev] [ANN] Iceberg 0.5 released

Yes there will be a nice 6.1 because we care of people. Stef On Mon, Jul 3, 2017 at 4:39 PM, Norbert Hartl wrote: > > Am 03.07.2017 um 14:45 schrieb Esteban Lorenzano : > > > On 3 Jul 2017, at 13:32, Norbert Hartl wrote: > > So it is

Re: [Pharo-dev] Pharo Launcher

yes latency problem. We should improve on that front :( On Mon, Jul 3, 2017 at 12:35 PM, Serge Stinckwich wrote: > > > On Thu, Jun 29, 2017 at 2:32 PM, Stephane Ducasse > wrote: >> >> Hi >> >> where can I find the pharo launcher for the

Re: [Pharo-dev] [ANN] for P7, default VM for linux moved to threaded

What are the implications? Stef On Mon, Jul 3, 2017 at 2:39 PM, Esteban Lorenzano wrote: > Hi, > > I made default vm for linux (for P7) the default VM. > > I also updated zeroconf to add a new type of download for linux: the explicit > iTimer heartbeat download. > > > So,

Re: [Pharo-dev] P6 crashed image

Hi hilaire We should throw away this plugin it is a bug nest. Sorry because it does not solve your problem and this is super annoying for us. Stef On Tue, Jul 4, 2017 at 3:07 AM, David T. Lewis wrote: > Hi Hilaire, > > I do not know if it will help in this case, but

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

Yes I agree with Norbert. I will implement the proposal of eliot because it should be slight variation of what I implemented already. Christian we have immutable objects in Pharo and we plan to clean the system to use them more and more :) I hope that people will join to port your pdf framework

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

JFYI: My conclusion is that there is too much friction when building Pharo images under Nix. Nix and Pharo seem to make opposite trade-offs on the reproducibility-vs-convenience axis. Pharo hackers seem to expect a lot of freedom during builds, like unrestricted internet access, and that doesn't

Re: [Pharo-dev] [ANN] Pharo community addon for world menu

I would also point to the issue tracker. In Roassal, I have a similar menu. And indeed, this is useful. Alexandre > On Jul 4, 2017, at 7:41 PM, Torsten Bergmann wrote: > > Hi, > > I added a small utility called "Community" to the catalog that allows you to > quickly >

[Pharo-dev] [ANN] Pharo community addon for world menu

Hi, I added a small utility called "Community" to the catalog that allows you to quickly access/browse the most prominent Pharo pages (Homepage, Discord, Mailinglist Archive, CI Server, Books page, Association, Consortium, STHub) right from the world menu. Also in Spotter. Example:

[Pharo-dev] Pull requests reviews

I prepared a script that should help you with the reviews of the pull requests on Pharo 7. We will later convert it into a more fancy tool. It does next steps: - sets the basic information: pull request number, path to your pharo repository clone, name of your fork. - registers the repository

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

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

[Pharo-dev] [pharo-project/pharo-core] 9a3d58: 60506

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

Re: [Pharo-dev] Pharo 7 provisional HOWTO

A small update: You are not forced to use a 'pharo-core' repository in your image folder if you provide a path to your own clone to the working copies of the bootstrapped packages. This way you can more easily share one local clone of the pharo-project/pharo repository. For the registration of

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

Yes, Value (the superclass) is used for – äh :) - values, i.e. immutable literal objects, which aid me with a more functional programming style. The literal printing of Objects is possible for all objects, since the facilities are defined in Object (#asSource). And yes, it is the same as

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

Hi Christian, thanks for the explanation. I see that Values serve a different purpose. We are looking for a compact form of object literal, the is not bound to the external interface and does not need to be subclassed. I'm interested how the printing of Values is different to #storeString.

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

Hi Norbert, yes, that is the point: it is a normal Smalltalk expression. It is trivial and every Smalltalk understands it. No need for special parsers; you just have class names and constructor methods. I believe this is a very compact and simple representation of Smalltalk objects. The

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

Hi Christian, > Am 03.07.2017 um 11:06 schrieb Christian Haider > : > > I solved this with Values[1] for VW and I am very happy with it (using it > intensively/routinely). > Your example would look like: > > (PointCollection points: (Array >