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

ative impact Norbert > 2017-09-14 9:28 GMT+02:00 H. Hirzel <hannes.hir...@gmail.com>: >> +1 for pinInMemory >> >> It explains what it does. >> >> On 9/14/17, Eliot Miranda <eliot.mira...@gmail.com> wrote: >> > Hi Norbert, >> > >> >

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

> Am 14.09.2017 um 00:09 schrieb Eliot Miranda : > > Hi Denis, > > On Tue, Sep 12, 2017 at 9:29 AM, Denis Kudriashov > wrote: > Hi Eliot. > > I know and I only talk about new messages. I am not trying to rethink

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

I don't think we should come up with a new naming scheme every now and then. If I look at the read-only support there the selector is beReadOnlyObject so in this case it should be bePinnedObject I didn't like the extra Object at the end but now I think it makes it clear and still steps aside

Re: [Pharo-dev] poor state of fuel

> Am 11.09.2017 um 09:35 schrieb H. Hirzel <hannes.hir...@gmail.com>: > >> On 9/10/17, Norbert Hartl <norb...@hartl.name> wrote: >> Max, >> >> Just an update. Martin commited a new package that solves the >> encoding/decoding of SmallIntege

Re: [Pharo-dev] poor state of fuel

> Am 10.09.2017 um 15:08 schrieb stephan <step...@stack.nl>: > >> On 10-09-17 09:56, Norbert Hartl wrote: >> Just an update. Martin commited a new package that solves the >> encoding/decoding of SmallInteger and Character. Together with the patch >&

Re: [Pharo-dev] poor state of fuel

l.com> wrote: >> >>> Hi Norbert, >>> >>> We still maintain Fuel. >>> >>> I was not aware of the problem you describe. Could you open an issue on >>> github (https://github.com/theseion/Fuel/issues) with a detailed >>>

Re: [Pharo-dev] About Git support for windows

Hi! > Am 10.09.2017 um 05:44 schrieb Alexandre Bergel : > > Hi! > > I live very very much this idea! > > I am wondering why do we need the timestamp? Git knows about who has > committed each line and by whom. Why should we have some redundant > information? > the

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

> Am 31.08.2017 um 12:52 schrieb Peter Uhnák : > > So you do not put passphrases on your ssh keys? > > Not always. > > Because you don't give the private key away why protect it? So imagine you > have development process that includes a jenkins that needs to build the >

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

> Am 31.08.2017 um 09:30 schrieb Peter Uhnák <i.uh...@gmail.com>: > > > On Thu, Aug 31, 2017 at 8:45 AM, Norbert Hartl <norb...@hartl.name > <mailto:norb...@hartl.name>> wrote: > > > > Am 31.08.2017 um 03:32 schrieb Sean P. DeNigris <s...@cli

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

> Am 31.08.2017 um 03:32 schrieb Sean P. DeNigris : > > https://github.com/pharo-vcs/iceberg/blob/master/README.md suggests to > configure Iceberg with the "Use Custom SSH Keys" setting, part of which > seems to include pasting one's SSH Key Passphrase into Pharo's

[Pharo-dev] poor state of fuel

I'm migrating most of my projects to pharo 6.1 at the moment. I come from pharo 4, I skipped pharo 5. I use 64 bit which removes a lot of stuff that does not need to be installed and makes deployment better. That really feels much better. I use jenkins and there if a test fails a fuel dump is

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Why is that document in the account of guille? Norbert > Am 12.08.2017 um 11:47 schrieb Pavel Krivanek : > > > > 2017-08-12 11:36 GMT+02:00 Holger Freyther : >> >> > On 26. Jun 2017, at 19:14, Pavel Krivanek wrote: >> >

Re: [Pharo-dev] [Pharo-users] TechTalk Dates for the rest of 2017

I would be in, too. It'll be on 17th of october fix? Norbert > Am 21.08.2017 um 18:38 schrieb Alexandre Bergel : > > Hi! > > I am currently giving a lecture on Neural Networks and Genetic > Algorithm/Programming. > Maybe I could turn this into an express 2 hours

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

For the .deb based distributions the adding of the repo is missing. This would be for Ubuntu 16.04 echo "deb http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/xUbuntu_16.04/ ./" > /etc/apt/sources.list.d/pharo.list Ubuntu 14.04 echo "deb

Re: [Pharo-dev] @About posting here

> Am 16.08.2017 um 13:21 schrieb Guillermo Polito : > > Hi Frank, > > I'll just repeat Stef's message: It's not about being straight or having > unpopular opinions. It's about being rude and on the limit of the insult. I > feel myself some harshness in your

Re: [Pharo-dev] PharoJS crashes at first try

> Am 13.08.2017 um 21:19 schrieb Frank-B : > > Stephane, > > thank you for your open words. > > 1) No I am NOT Frank Lesser and I will communicate this even clearer in a > personal email to you. > > 2) I had tried to make very clear that I see the Pharo project

Re: [Pharo-dev] [ANN] Mustache moved to github

alog entry? > > Stef > > On Fri, Jul 28, 2017 at 12:40 PM, Norbert Hartl <norb...@hartl.name> wrote: >> In the spirit of git notification…I moved mustache to github. >> >> https://github.com/noha/mustache >> >> Enjoy! >> >> Norbert >> >>

[Pharo-dev] [ANN] Mustache moved to github

In the spirit of git notification…I moved mustache to github. https://github.com/noha/mustache Enjoy! Norbert

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo 6.1 (summer) released!

Thank you! That is so cool. Norbert > Am 24.07.2017 um 13:56 schrieb Esteban Lorenzano : > > Hi, > > We are releasing Pharo 6.1. > Usually, between each major version we just apply bugfixes changing the build > number and not announcing new versions but this time is

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

Eliot, > Am 18.07.2017 um 22:26 schrieb Eliot Miranda <eliot.mira...@gmail.com>: > > Norbert, > > On Tue, Jul 18, 2017 at 11:05 AM, Norbert Hartl <norb...@hartl.name > <mailto:norb...@hartl.name>> wrote: > Really great! I think we should move the Cr

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

Really great! I think we should move the Cryptography package from smalltalkhub to github, refactor it and add goodies like this. We need a strong crypto foundation. Norbert > Am 18.07.2017 um 19:10 schrieb Esteban A. Maringolo : > > Great! > > I see you continue doing

Re: [Pharo-dev] Beacon moved to github

t;>> And the rest of the github uses a variety of options >>>> >>>> * nothing >>>> - imho disorganized and very messy if you have several packages >>>> * repository >>>> - I've been using it and recommending it for ~2 years; also us

Re: [Pharo-dev] Beacon moved to github

t; * nothing >> >> - imho disorganized and very messy if you have several packages >> >> * repository >> >> - I've been using it and recommending it for ~2 years; also used by >> >> filetree and metacello repos ;) >> >> - Argument could be

Re: [Pharo-dev] Beacon moved to github

gt; in the project settings "Public write access" and then remove all > contributors. > > -- Pavel > > 2017-07-07 16:45 GMT+02:00 Norbert Hartl <norb...@hartl.name > <mailto:norb...@hartl.name>>: > I used the git migration tool of Peter Uhnak to migra

Re: [Pharo-dev] Beacon moved to github

instead "src" like > in other repos. > Uh, I've never seen "src". In Voyage and MongoTalk it is "mc" which I don't like. And I'm not a big friend of "src" either. But if it is the common rule I wouldn't object. Norbert > 2017-07-07 16:45 GMT+02:

[Pharo-dev] Beacon moved to github

I used the git migration tool of Peter Uhnak to migrate Beacon from smalltalkhub to github. It is available now here https://github.com/pharo-project/pharo-beacon I just need to know how I can switch a smalltalkhub project to read-only. FYI,

Re: [Pharo-dev] OSPlatform currentVersion

ent-returns-a-MacOSPlatform-instead-of-a-MacOSXPlatform-on-macOS-Sierra> Norbert > Am 06.07.2017 um 14:29 schrieb Norbert Hartl <norb...@hartl.name>: > > Ok, then it is a regression because I downloaded vm and image freshly before > trying > > thanks, > > Norbert

Re: [Pharo-dev] OSPlatform currentVersion

uration-for-Pharo-6-release-please-tp4952002p4952005.html > > HTH, > Alistair > > > On 6 July 2017 at 14:06, Norbert Hartl <norb...@hartl.name> wrote: >> Does anyone know when the output for >> >> OSPlatform currentVersion >> >> c

[Pharo-dev] OSPlatform currentVersion

Does anyone know when the output for OSPlatform currentVersion changed? In Pharo 4 I get '1095' and in pharo6 I get '10.12.5'. The determination if it is a OSX system or older is done by currentVersion asNumber >= 1000 which changes behaviour because the currentVersion string has been

Re: [Pharo-dev] Simply Happy

Yeah, it is truly great! I think we've crossed a border. In the past a lot of our legacy was compensating the awesomeness. In the meantime I have the feeling that the awesomeness sticks out much more clear. Thank you all for making this community! Norbet > Am 06.07.2017 um 10:57 schrieb

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

Great! All I wanted to hear! Thanks, Norbert > Am 05.07.2017 um 07:56 schrieb Stephane Ducasse <stepharo.s...@gmail.com>: > > 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 <norb...@hartl.nam

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

y be missing? > > HTH, > Christian > > Von: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Im Auftrag von > Norbert Hartl > Gesendet: Dienstag, 4. Juli 2017 08:14 > An: Pharo Development List <pharo-dev@lists.pharo.org> > Betreff: Re

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

Christian > > [1] https://wiki.pdftalk.de/doku.php?id=complexvalues > > Von: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Im Auftrag von > Norbert Hartl > Gesendet: Montag, 3. Juli 2017 10:28 > An: Pharo Dev <pharo-dev@lists.pharo.org> > Betreff: Re:

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

> Am 03.07.2017 um 14:45 schrieb Esteban Lorenzano <esteba...@gmail.com>: > > >> On 3 Jul 2017, at 13:32, Norbert Hartl <norb...@hartl.name >> <mailto:norb...@hartl.name>> wrote: >> >> So it is decided there won't be an official pharo6 sup

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

Eliot, > Am 01.07.2017 um 20:22 schrieb Eliot Miranda <eliot.mira...@gmail.com>: > > Hi Norbert, > > >> On Jul 1, 2017, at 7:36 AM, Norbert Hartl <norb...@hartl.name> wrote: >> >> >>>> Am 30.06.2017 um 21:14 schrieb Stephane Ducasse &l

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

> Am 30.06.2017 um 21:14 schrieb Stephane Ducasse : > >> 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

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] [ANN] P3, a modern, lean and mean PostgreSQL client for Pharo

> Am 28.06.2017 um 12:43 schrieb Sven Van Caekenberghe <s...@stfx.eu>: > >> >> On 28 Jun 2017, at 12:14, Norbert Hartl <norb...@hartl.name> wrote: >> >>> >>> Am 28.06.2017 um 10:42 schrieb Sven Van Caekenberghe <s...@stfx.eu>:

Re: [Pharo-dev] [ANN] P3, a modern, lean and mean PostgreSQL client for Pharo

> Am 28.06.2017 um 10:42 schrieb Sven Van Caekenberghe <s...@stfx.eu>: > > >> On 28 Jun 2017, at 10:07, Norbert Hartl <norb...@hartl.name> wrote: >> >> Great! I assume it is a smalltalk only client? > > Yes, it is written in pure Pharo, us

Re: [Pharo-dev] [ANN] P3, a modern, lean and mean PostgreSQL client for Pharo

Great! I assume it is a smalltalk only client? As we have protocol version 3.0 does it mean that protocol 4.0 will be announced shortly? :) Great work! Although I do not use SQL databases I need to check. Norbert > Am 27.06.2017 um 14:56 schrieb Sven Van Caekenberghe : > > P3

Re: [Pharo-dev] [Pharo-users] vested interest in PharoJS?

> Am 24.06.2017 um 21:37 schrieb Stephane Ducasse <stepharo.s...@gmail.com>: > > Did you contact noury? > About what? I'm on the pharojs slack community and talk with Noury and Dave from time to time. Norbert >> On Thu, Jun 22, 2017 at 3:49 PM, Norbert Hartl &l

Re: [Pharo-dev] [Pharo-users] vested interest in PharoJS?

eck if it is feasible to use. And my trials with PharoJS were only little so I don't have the feeling, yet, if it is a huge benefit using it. But I feel a huge potential in it so it is on my list of things I wanna try but not on top. Norbert > -- Siemen > > On Thu, Jun 22

Re: [Pharo-dev] vested interest in PharoJS?

I thought I responded already. We are interested in pharoJS. We developed stuff with amber but stopped using it. We have one app in the app store with ionic and amber and I'd like to do another one with pharoJS. Additionally I think that combining pharoJS with electron could be a nice thing to

Re: [Pharo-dev] Iceberg diff colours seem reversed?

I didn't look at the iceberg diff right now. But I can say whenever I see a diff view in pharo it is so confusing I never know what I see. In the changes window I alwas switch from diff to source to see at least what I have now. Maybe a general problem how to put chronological change. And maybe

Re: [Pharo-dev] GitHub survey on open source projects

> Am 20.06.2017 um 09:55 schrieb Sven Van Caekenberghe <s...@stfx.eu>: > > >> On 20 Jun 2017, at 09:52, Norbert Hartl <norb...@hartl.name> wrote: >> >> ??? The only thing that fits us is "plagued by poor docs"!!! >> >> Norbert >

Re: [Pharo-dev] GitHub survey on open source projects

??? The only thing that fits us is "plagued by poor docs"!!! Norbert > Am 19.06.2017 um 20:05 schrieb Eliot Miranda : > > Not sure how much this reflects our communities but this is interesting. > > > GitHub Survey: Open Source Is Popular, Plagued by Poor Docs and

Re: [Pharo-dev] Esteban's ChangeLog week of 12 June 2017

You totally rock! I'm so eager to have iceberg on 64bits. It is the last block for me to move my projects into the 21st century ;) thanks, Norbert > Am 19.06.2017 um 08:00 schrieb esteba...@gmail.com: > > Hello! > > This is my weekly ChangeLog, from 12 June 2017 to 18 June 2017. > You can

Re: [Pharo-dev] Calypso technology preview.

> Am 20.05.2017 um 09:54 schrieb Stephane Ducasse : > > Hi ben > > It is better to load it because for example I could not load a new version > the last time I tried to update. > We should lower the stress of the releasers. Yes, and release twice as often  Norbert

Re: [Pharo-dev] preparing to release: what do we do with this linux distros?

Me, too. But all the work is done by Holger because I don't find time. So no reason to complain for me  Norbert > Am 09.05.2017 um 17:13 schrieb Esteban Lorenzano <esteba...@gmail.com>: > > yes, we are waiting for that :) > >> On 9 May 2017, at 17:10, Norbert H

Re: [Pharo-dev] preparing to release: what do we do with this linux distros?

> Am 09.05.2017 um 16:46 schrieb Sven Van Caekenberghe : > > >> On 9 May 2017, at 16:10, Esteban Lorenzano wrote: >> >> http://pharo.org/STAGE.gnu-linux-installation >> >> I don’t think they will work. >> We need to update or remove. >> >> Esteban > > It

Re: [Pharo-dev] [ann] bloc & cairo+morphic

Very good work. Thanks for that! Norbert > Am 08.05.2017 um 23:00 schrieb Tudor Girba : > > Hi, > > We are happy to announce that based on the work of Glenn, Alex extended Bloc > (Sparta) to work directly in the Morphic world using Cairo as a backend. > > Cairo is less

Re: [Pharo-dev] changing default theme to DarkTheme

I wonder why voting is considered something good. To me voting is rather a last resort strategy. Voting is taking power without the need for having an opinion nor any reason. To me the sense of voting is to make most people feel empowered/comfortable. And the outcome is often poor or even

Re: [Pharo-dev] changing default theme to DarkTheme

> Am 15.04.2017 um 16:39 schrieb Stephan Eggermont <step...@stack.nl>: > > On 15/04/17 16:02, Norbert Hartl wrote: >> And comparing the capability of building >> contrasts with colors, dark colors win, sorry. At least that were the >> last researches

Re: [Pharo-dev] changing default theme to DarkTheme

> Am 15.04.2017 um 15:35 schrieb webwarrior : > > All major desktop OSes have light theme by default. Most web sites have white > or light background and dark text. Almost all PDF documents have white > background. > > Switching between dark and light themed applications

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

If enough people move and there is a note the others will follow Norbert > Am 07.04.2017 um 14:39 schrieb Alexandre Bergel : > > I would not mind moving to Discord. But, what is the plan to kill Slack? Can > a Slack project be simply removed? > > Alexandre > -- >

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

I'm on discord now. Ready to leave slack Norbert > Am 07.04.2017 um 14:19 schrieb philippe.b...@highoctane.be > : > > My xmpp client works okay now for that use case. Enable the gateway and I'll > be able to pick them up, store them and make them searchable. > >

Re: [Pharo-dev] Pharo7 Inspector feature idea - cherry-pick collection items

Is there a reason why the order is reversed? Norbert > Am 17.03.2017 um 10:02 schrieb Tudor Girba : > > Hi, > > That list is multi-selection. On Mac, you can press Cmd while clicking and > you get the collection to the right. > > > Cheers, > Doru > > >> On Mar 17,

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

+1 Always true, always sad. But most changes for the good do something bad that is recognized after release. Norbert > Am 06.03.2017 um 08:24 schrieb Esteban Lorenzano : > > … and this is why even small additions should not be included in frozen > versions… you never

Re: [Pharo-dev] [ANN] Regex Tester Tool for Pharo

> Am 02.03.2017 um 09:54 schrieb Peter Uhnak : > > On Thu, Mar 02, 2017 at 09:20:12AM +0100, Esteban Lorenzano wrote: >> >>> On 1 Mar 2017, at 22:40, stepharong wrote: >>> >>> >>> And I think that his remark makes sense. I was wondering if we should not

Re: [Pharo-dev] Esteban's ChangeLog week of 6 February 2017

> Am 13.02.2017 um 09:38 schrieb esteba...@gmail.com: > > Hello! > > This is my weekly ChangeLog, from 6 February 2017 to 12 February 2017. > You can see it in a better format by going here: > http://log.smallworks.eu/web/search?from=6/2/2017=12/2/2017 > > ChangeLog > = > > 9

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

> Am 01.02.2017 um 11:56 schrieb Denis Kudriashov <dionisi...@gmail.com>: > > > 2017-02-01 9:41 GMT+01:00 Norbert Hartl <norb...@hartl.name > <mailto:norb...@hartl.name>>: > I think in the future we need to work out how we can inspect a remote object >

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

> Am 01.02.2017 um 13:44 schrieb Torsten Bergmann : > >>> Great job!!! A dream comes true. >>> If there is a working UFFI for ARM then we have a pretty decent stack for >>> IoT times. >> Thank's. UFFI works in my simple tests like "LibC system: 'ls'" > > Did you check out my

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

> Am 30.01.2017 um 13:14 schrieb Norbert Hartl <norb...@hartl.name>: > >> >> Am 30.01.2017 um 11:49 schrieb Sven Van Caekenberghe <s...@stfx.eu >> <mailto:s...@stfx.eu>>: >> >>> >>> On 30 Jan 2017, at 11:43, Norbert

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

> Am 30.01.2017 um 16:21 schrieb Ben Coman <b...@openinworld.com>: > > On Mon, Jan 30, 2017 at 9:32 PM, Norbert Hartl <norb...@hartl.name> wrote: >> >>> Am 30.01.2017 um 14:21 schrieb Ben Coman <b...@openinworld.com>: >>> >>> But I ag

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

eers -ben > > On Mon, Jan 30, 2017 at 9:15 PM, p...@highoctane.be <p...@highoctane.be> > wrote: >> Like it too FWIW. >> >> Phil >> >> On Mon, Jan 30, 2017 at 12:55 PM, Denis Kudriashov <dionisi...@gmail.com> >> wrote: >>> >&

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

> Am 30.01.2017 um 11:49 schrieb Sven Van Caekenberghe <s...@stfx.eu>: > >> >> On 30 Jan 2017, at 11:43, Norbert Hartl <norb...@hartl.name> wrote: >> >>> >>> Am 30.01.2017 um 11:36 schrieb Denis Kudriashov <dionisi...@gmail.com>:

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

Hi, I really enjoy how motivated people get when it is about finding a name :) I don't agree PharmIDE is a bad name. Farming is a well known term when it comes to server installations (server farm) or other distributed stuff. So as it is not your context you get another impression. People that

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

> Am 30.01.2017 um 11:36 schrieb Denis Kudriashov : > > Hi Sean. > > 2017-01-28 19:06 GMT+01:00 Sean P. DeNigris >: > Have you considered security at all yet? Leaving a port open which allows > arbitrary code to be

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

Von meinem iPad gesendet > Am 28.01.2017 um 19:06 schrieb Sean P. DeNigris : > > Denis Kudriashov wrote >> I am glad announce first version of PharmIDE project which is complete >> toolset for remote development of Pharo images. > > Awesome! > > Have you considered

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi Alex, thanks for the detailed mail. I can only share my gut feeling. And that is that you want too much at a time. We are still living in bitblt times and we need to escape from that. That means we need to have a proper vectorial support in our graphics backend. Having this we could use

Re: [Pharo-dev] memoized vs once

> Am 27.01.2017 um 02:45 schrieb Igor Stasenko : > > > > On 27 January 2017 at 02:28, Ben Coman > wrote: > On Fri, Jan 27, 2017 at 7:35 AM, Igor Stasenko > wrote: > > > >

Re: [Pharo-dev] Immutability support

> Am 26.01.2017 um 10:32 schrieb Clément Bera <bera.clem...@gmail.com>: > > > > On Thu, Jan 26, 2017 at 9:54 AM, Norbert Hartl <norb...@hartl.name > <mailto:norb...@hartl.name>> wrote: > >> Am 26.01.2017 um 08:11 schrieb Clément Bera <bera.clem

Re: [Pharo-dev] Immutability support

> Am 26.01.2017 um 08:11 schrieb Clément Bera : > > The "CAN'T REACH" comment is there because execution never reach that part of > the code. If you write code there, it will never be executed. The process > code performs a return without pushing any value on stack. >

Re: [Pharo-dev] Immutability support

Clément, > Am 25.01.2017 um 13:54 schrieb Clément Bera <bera.clem...@gmail.com>: > > > > On Wed, Jan 25, 2017 at 11:35 AM, Norbert Hartl <norb...@hartl.name > <mailto:norb...@hartl.name>> wrote: > Does anyone know the state of immutability su

Re: [Pharo-dev] Immutability support

> Am 25.01.2017 um 12:16 schrieb Esteban Lorenzano : > > >> On 25 Jan 2017, at 12:04, Denis Kudriashov > > wrote: >> >> >> 2017-01-25 12:03 GMT+01:00 Denis Kudriashov >

Re: [Pharo-dev] Immutability support

> Am 25.01.2017 um 11:40 schrieb Denis Kudriashov <dionisi...@gmail.com>: > > > 2017-01-25 11:35 GMT+01:00 Norbert Hartl <norb...@hartl.name > <mailto:norb...@hartl.name>>: > ASUser new > setIsReadOnlyObject: true > > And why so ugly name

[Pharo-dev] Immutability support

Does anyone know the state of immutability support in vm and image? The latest vm downloadable is compiled with IMMUTABILITY=1 (Esteban said that). When I open a pharo6 image with this VM and do: ASUser new setIsReadOnlyObject: true; name: 'foo' with ASUser>>#name: arg1

Re: [Pharo-dev] problem with linux: missing

The reason is that the vm binary is 64bit but the interpreter is for 32bit images. Therefor the plugins are 32bit, too. If there will be a 64bit vm plus image the dependencies would go away. We are close to that but not there. Norbert > Am 12.01.2017 um 15:00 schrieb Nicolas Anquetil

Re: [Pharo-dev] happy and bold new year

> Am 09.01.2017 um 11:11 schrieb philippe.b...@highoctane.be > : > > Doru, > > Wow. > > I have to say that in the face of other technologies there is often the force > that lures me back go them. But they do not have the same feel. This ability > to understand and

Re: [Pharo-dev] :: Separator in class names

> Am 02.01.2017 um 12:57 schrieb Torsten Bergmann : > > First of all: happy new year to all Pharo supporters! > > Not many of you answered this thread in 2016. Maybe > I have more luck in 2017 ;) > > So please tell me about the requested change of #isValidGlobalName > to allow

Re: [Pharo-dev] Epicea user experience report

> Am 27.12.2016 um 10:49 schrieb Martin Dias : > > I do not care a lot. BTW, what about other tools in the same manu such as > Komitter and Versionner? It has a cool name that describes what it does. Putting Epicea in front of it does not add information only confusion.

Re: [Pharo-dev] Berlin 2016-12-19

I don't think this list is the proper place for discussing politics. So can we please not do it? thanks, Norbert > Am 22.12.2016 um 11:20 schrieb Dimitris Chloupis : > > I completely agree with you Phil, the real tragedy is this Berlin tragedy > will be the excuse to

Re: [Pharo-dev] Epicea user experience report

I don't like the extra menu. I think going three levels in a menu should only be done for thing used rarely. Feels awkward very time. Do we have three cases wirh epicea? - this session meaning all changed since start of the image? - last session/aborted session the last session that did not

Re: [Pharo-dev] About traits

> Am 11.12.2016 um 09:05 schrieb stepharong : > > >> >> Dale >> >> I missed your remark about traits. >> I think that traits are nice because they act as a kind of static macro >> expansion and really help to get multiple inheritance into single one. >> >> Now ideally

Re: [Pharo-dev] About traits

> Am 10.12.2016 um 20:48 schrieb stepharong : > > > Dale > > I missed your remark about traits. > I think that traits are nice because they act as a kind of static macro > expansion and really help to get multiple inheritance into single one. > > Now ideally I would

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

> Am 10.11.2016 um 12:27 schrieb Thierry Goubier <thierry.goub...@gmail.com>: > > > > 2016-11-10 12:18 GMT+01:00 Norbert Hartl <norb...@hartl.name > <mailto:norb...@hartl.name>>: > [ ...] > > Be it small chunks of data or not. A statement t

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

> Am 10.11.2016 um 10:42 schrieb Tudor Girba : > > Hi Igor, > > I am happy to see you getting active again. The next step is to commit code > at the rate you reply emails. I’d be even happier :). > +1 > To address your point, of course it certainly would be great to

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

> Am 10.11.2016 um 07:27 schrieb Tudor Girba : > > Hi Igor, > > Please refrain from speaking down on people. +1 > If you have a concrete solution for how to do things, please feel free to > share it with us. We would be happy to learn from it. > +10 Norbert > Cheers,

Re: [Pharo-dev] why RBComment is not called RBCommentNode

> Am 04.11.2016 um 07:53 schrieb Nicolas Cellier > : > > > > 2016-11-04 1:54 GMT+01:00 John Brant >: > > > On Nov 3, 2016, at 4:03 PM, stepharo >

Re: [Pharo-dev] Mocks are missing in Pharo (from thread OSProcess is missing)

The context might be right. Still Denis is talking about integrating Mocks in SUnit. And to have kernel tests using Mocks. I don't see a problem because can be loaded later. I see no reason if there is a small kernel why it cannot load additional stuff just for testing. The kernel would still

Re: [Pharo-dev] Custom Pharo builds from terminal [ it was (Re: [ANN] Sparta v1.1) ]

Isn't that something complementary to pharo. Why have the tools a different name??? I think pharo should be usable as scripting engine. And that means files should begin with #! /usr/bin/env pharo Norbert > Am 22.10.2016 um 13:41 schrieb Esteban Lorenzano : > > >> On

Re: [Pharo-dev] [ANN] Sparta v1.1

Dale, > Am 21.10.2016 um 22:15 schrieb Dale Henrichs > <dale.henri...@gemtalksystems.com>: > > > > On 10/21/2016 07:30 AM, Norbert Hartl wrote: >> Dale, >> >>> Am 21.10.2016 um 16:12 schrieb Dale Henrichs >>> <dale.henri...@gemtalk

Re: [Pharo-dev] [ANN] Sparta v1.1

the tunnel just went off :) Norbert > Dale > > On 10/21/16 6:50 AM, Norbert Hartl wrote: >> Dale, >> >> I was not arguing against evolution. I was refering to the fact that work of >> others is mostly ignored just to come up with a potential weaker soluti

Re: [Pharo-dev] [ANN] Sparta v1.1

e/builds/160382244 > <https://travis-ci.org/SeasideSt/Seaside/builds/160382244> > [3] https://travis-ci.org/pharo-nosql/voyage/builds/167012791 > <https://travis-ci.org/pharo-nosql/voyage/builds/167012791> > [4] https://en.wikipedia.org/wiki/Software_evolution > <ht

Re: [Pharo-dev] [ANN] Sparta v1.1

> Am 21.10.2016 um 04:00 schrieb Sean P. DeNigris : > > Denis Kudriashov wrote >> I look at code and it seems you implemented another one new text model? >> Why >> you not use TxText? > > Argh. I know it's bad form to complain about gifts, but at the rate we > reinvent

Re: [Pharo-dev] [ANN] New release of iceberg

Nico, > Am 13.10.2016 um 14:25 schrieb Nicolas Passerini : > > - Integration with Metacello, i.e. after installing Iceberg you do something > like > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit' ; > load. > > (By default) it will

Re: [Pharo-dev] [ANN] Sparta v1.1

Great! Seems to be the case that we need to take the 64bit border!! Norbert > Am 19.10.2016 um 18:06 schrieb Aliaksei Syrel : > > Hi > > I am happy to announce the release of Sparta v1.1 for Pharo 6. > https://github.com/syrel/Sparta/tree/v1.1 > > It can be bootstrapped

Re: [Pharo-dev] Spur VM Bug for Chinese Characters?

Sean, fuel relies on the fact that the environment for materialization is the same as where it has been serialized. So classes and methods need to be mostly the same. A non-spur to spur change is likely to make it fail. These changes are rare but sonetimes the need to be done. If you want to

Re: [Pharo-dev] [ANN] New "DarkMetalTheme" for Pharo

You should call it Insomnia! Norbert > Am 06.10.2016 um 10:36 schrieb Esteban Lorenzano : > > Hi, > > I took some time to extract the ==MUDDarkTheme== I made for my > *MUDClient>https://github.com/estebanlm/MUDClient* > , >

Re: [Pharo-dev] macOS Sierra support

Sven, > Am 27.09.2016 um 11:15 schrieb Sven Van Caekenberghe : > > PS2: Another really annoying problem is the following: he saved all his > (really important) scripts using Script Manager as a FUEL. Moving between 4.0 > and 5.0 FUEL stops working (version incompatibility) - this

<    1   2   3   4   5   6   7   8   >