Re: [Pharo-dev] Segmentation fault while installing Scale

Are you on 64-bit using 32-bit Pharo? Can you use ldd to check the pharo binary is linking to these 32-bit libraries? http://pharo.org/gnu-linux-installation When you get it working can you provide a recipe for the download page. Alternatively you might try either (pre-release) 64-bit VM from...

Re: [Pharo-dev] Slack, fragmentation and design information

I fail to see the problem here On Sat, Feb 11, 2017 at 1:52 AM p...@highoctane.be wrote: > Am still finding useful stuff on Squeak wiki, sorry. > The point of a Wiki is to capture discussions over a given topic and make > it grow into something more structured over time.

Re: [Pharo-dev] Slack, fragmentation and design information

Am still finding useful stuff on Squeak wiki, sorry. The point of a Wiki is to capture discussions over a given topic and make it grow into something more structured over time. Like original c2 wiki. Phil On Fri, Feb 10, 2017 at 9:30 PM, Dimitris Chloupis wrote: > If you

Re: [Pharo-dev] Segmentation fault while installing Scale

Hi all, > and which VM do you use (there is a System report browser where you can find the information. I've somehow managed to get the information from System report browser: Image - /home/demi/mess/2017/06/tmp2/Pharo.image Pharo5.0 Latest update: #50768 Unnamed Virtual Machine

Re: [Pharo-dev] Slack, fragmentation and design information

If you miss it so much we have something much better Github wikis, we never use Each of our books is hosted in a Github repo and each repo always comes with its own wiki using very simple markdown as everything else in Github You do not have content but only a snippet of code to offer ? No

Re: [Pharo-dev] Slack, fragmentation and design information

I miss the Squeak wiki Pharo style. Phil Le 10 févr. 2017 19:06, "Esteban A. Maringolo" a écrit : > 2017-02-10 14:59 GMT-03:00 p...@highoctane.be : > > Mass adoption and hyper reduced friction to get people on board. > > > > For me: I have 10+ slack

Re: [Pharo-dev] Pharo 60 need help on When-coding-in-the-debugger-I-get-an-error-sourceNodeExecuted

super tx denis. Stef Fixed 2017-02-06 17:55 GMT+01:00 Stephane Ducasse : https://pharo.fogbugz.com/f/cases/19661/When-coding-in-the-debugger-I-get-an-error-sourceNodeExecuted Then I got a really strange problem when I was doing the counterexecise using the

Re: [Pharo-dev] Segmentation fault while installing Scale

Hello, > Hi, > We are looking at it with Santi. I see in the log that you're using an ubuntu 12? No, this is Gentoo Linux. > I tried in a debian jessie and Santi in an ubuntu 14 and we could not > reproduce it. Also the travis ci of scale uses ubuntu 12 and the > installation works in there...

Re: [Pharo-dev] Segmentation fault while installing Scale

Hi Clement, > Hi Andrey, > Thanks for providing both a way to reproduce and the log so we can have you > machine details. I see that the VM was compiled from build #589 on jenkins > with VMMaker.oscog-eem.1855 and you're on Linux using x86 back-end. > Scale works only on Linux and when I try

Re: [Pharo-dev] [Pharo-users] Slack, fragmentation and design information

Actually your numbers are pretty low #blendercoders indeed has 187 , but those are the actual C coders working on the blender source (which I do not do), so its an equivalent of our phraro-dev, the equivalent of pharo-users is #blender with 360 members and the #blenderpython with 70 members which

Re: [Pharo-dev] Slack, fragmentation and design information

2017-02-10 14:59 GMT-03:00 p...@highoctane.be : > Mass adoption and hyper reduced friction to get people on board. > > For me: I have 10+ slack teams in my slack client and there is really no > point in having more clients on the desktop. +1 to this. This is key. Maybe what

Re: [Pharo-dev] Slack, fragmentation and design information

Mass adoption and hyper reduced friction to get people on board. For me: I have 10+ slack teams in my slack client and there is really no point in having more clients on the desktop. Phil On Fri, Feb 10, 2017 at 5:30 PM, Hilaire wrote: > Please excuse my ignorance but what

Re: [Pharo-dev] [Pharo-users] Slack, fragmentation and design information

I just saw Blender developers seems to use IRC (#blendercoders @ irc.freenode.net), 187 users. Ruby too at #ruby 917 users Le 10/02/2017 à 12:29, Dimitris Chloupis a écrit : > e) for personal reason all my favorite software (Blender, Unreal > etc) is using it -- Dr. Geo http://drgeo.eu

Re: [Pharo-dev] Slack, fragmentation and design information

Please excuse my ignorance but what are the advantages of Slack over other instant messaging system like IRC or Jabber? Hilaire Le 10/02/2017 à 10:27, Stephan Eggermont a écrit : > The past year we have started using Slack to communicate in real-time > about Pharo. It has nice (mobile) clients

Re: [Pharo-dev] [Pharo-users] Slack, fragmentation and design information

There is a special price for non-profits organization: > The Slack for Nonprofits program offers eligible organizations a *free upgrade* to our Standard plan for teams of up to 250 members. For eligible teams above that size, we offer an 85% discount on the Standard plan. With 322 users it means

Re: [Pharo-dev] [Pharo-users] Slack, fragmentation and design information

> >> I share many of what you say… but in the other point of view, Slack as >> really worked and there is a lot more happening now in Slack + mailing list >> than what was before just in mailing list. >> But most of that is lost because of Slack policies (also Slack pricing model >> is

Re: [Pharo-dev] [Pharo-users] Slack, fragmentation and design information

I have been pushing for Discord because a) There is no need to host and maintain as Esteban said b) There a ton of communities already using it and its by far the second most mature chat client after Slack c) It has a very powerful Python API yes I know I know its no Pharo but still it

[Pharo-dev] GSOC Pharo application done

Dear all, thanks to the efforts of Jigyasa Grover, Yuriy Tymchuk and Alexandre Bergel, , we were able to have a GSOC 2017 application for the Pharo Consortium. This is only the first phase. If we are selected by Google, they will give some slots for students. We have a list of projects for GSOC

Re: [Pharo-dev] [Pharo-users] Slack, fragmentation and design information

I am frustated by this too and indeed we need a way to keep the messages. I am about done with my wrapping of LibStrophe in Pharo with , which provides a XMPP/Jabber client to Pharo. So, if someone can activate the XMPP gateway on our Slack instance, we will have a way to archive the contents

Re: [Pharo-dev] [Pharo-users] Final rush for submitting GSOC proposal - Need your help

On Thu, Feb 9, 2017 at 5:28 PM, Stephan Eggermont wrote: > On 09/02/17 17:05, Serge Stinckwich wrote: >> >> but all the projects are coming from RMOD team, but having all the >> projects proposal coming from the same place might be perceived >> negatively from Google. Can we add

Re: [Pharo-dev] [Pharo-users] Slack, fragmentation and design information

> On 10 Feb 2017, at 11:28, Serge Stinckwich wrote: > > On Fri, Feb 10, 2017 at 10:58 AM, Esteban Lorenzano > wrote: >> Hi Stephan, >> >>> On 10 Feb 2017, at 10:27, Stephan Eggermont wrote: >>> >>> The past year we have

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

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

[Pharo-dev] [pharo-project/pharo-core] 6f7d16: 60385

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

Re: [Pharo-dev] Slack, fragmentation and design information

On Fri, Feb 10, 2017 at 10:58 AM, Esteban Lorenzano wrote: > Hi Stephan, > >> On 10 Feb 2017, at 10:27, Stephan Eggermont wrote: >> >> The past year we have started using Slack to communicate in real-time about >> Pharo. It has nice (mobile) clients and

Re: [Pharo-dev] Slack, fragmentation and design information

Hi Stephan, > On 10 Feb 2017, at 10:27, Stephan Eggermont wrote: > > The past year we have started using Slack to communicate in real-time about > Pharo. It has nice (mobile) clients and makes it easy to share pictures and > snippets. As a result a large part of the

[Pharo-dev] Slack, fragmentation and design information

The past year we have started using Slack to communicate in real-time about Pharo. It has nice (mobile) clients and makes it easy to share pictures and snippets. As a result a large part of the communication about design and how to do things has moved from the mailing lists to Slack. As we're