Re: [Pharo-users] Submitting bug fix or enhancement: still "Pharo50Inbox"?

2017-07-08 Thread Stephane Ducasse
I updated the web site. On Sat, Jul 8, 2017 at 5:50 PM, Pavel Krivanek wrote: > You should use Pharo60Inbox > > -- Pavel > > 2017-07-08 17:45 GMT+02:00 Matteo via Pharo-users > : >> >> >> >> -- Přeposlaná zpráva -- >> From: Matteo >> To: "Pharo is welcome (ML)" >> Cc: >> Bcc: >>

Re: [Pharo-users] 2 questions around gitlab, gitfiletree, BaselineOf

2017-07-08 Thread Pierce Ng
On Fri, Jul 07, 2017 at 06:48:50AM -0700, Sabine Manaa wrote: > 1) For loading my own code, I currently have a bad solution > I would like to load it within my baseline like this below but I dont know > what to write in the fileTreeRepository method... > > baseline: spec >

Re: [Pharo-users] Submitting bug fix or enhancement: still "Pharo50Inbox"?

2017-07-08 Thread Pavel Krivanek
You should use Pharo60Inbox -- Pavel 2017-07-08 17:45 GMT+02:00 Matteo via Pharo-users < pharo-users@lists.pharo.org>: > > > -- Přeposlaná zpráva -- > From: Matteo > To: "Pharo is welcome (ML)" > Cc: > Bcc: > Date: Sat, 8 Jul 2017 17:45:15 +0200 > Subject: Submitting bug fix or

[Pharo-users] Submitting bug fix or enhancement: still "Pharo50Inbox"?

2017-07-08 Thread Matteo via Pharo-users
--- Begin Message --- Dears, I would like to submit some snippet of code, as "enhancement", to the Pharo code. I'm using Pharo 6.0 image, so I thought that I should send my code "Pharo60Inbox", but in http://pharo.org/contribute-propose-fix is stated that should I send my code to t

Re: [Pharo-users] PreDebugWindow: Report to whom?

2017-07-08 Thread Stephane Ducasse
Luke use the force. It is Pharo so the code is there to browse :) On Sat, Jul 8, 2017 at 3:28 PM, Juraj Kubelka wrote: > Hi, > > I understand that it is an obsolete (not maintained) function. The button has > been removed in Pharo 7. > > Juraj > >> El 08-07-2017, a las 10:37, horrido escribió:

Re: [Pharo-users] PreDebugWindow: Report to whom?

2017-07-08 Thread Juraj Kubelka
Hi, I understand that it is an obsolete (not maintained) function. The button has been removed in Pharo 7. Juraj > El 08-07-2017, a las 10:37, horrido escribió: > > In the PreDebugWindow, there is an option to Report an exception. But to whom > does it report? I can't find any documentation

Re: [Pharo-users] Pharo starts completely minimized

2017-07-08 Thread Juraj Kubelka
Might be related to https://pharo.fogbugz.com/f/cases/20094/Headless-mode-breaks-image Juraj > El 08-07-2017, a las 08:26, Stephane Ducasse > escribió: > > pharo-ui is a script. > > On Fri, Jul 7, 2017 at 9:36 PM, Andreas

Re: [Pharo-users] How to view hierarchy of multiple classes in a package?

2017-07-08 Thread Tim Mackinnon
That's awesome and it reminds me that I need to make a baselineof for all my fav tools so that I load them when I grab a new image, as I don't have calypso loaded on my lambda experimental image. Tim Sent from my iPhone Sent from my iPhone > On 7 Jul 2017, at 16:55, Denis Kudriashov wrote

Re: [Pharo-users] Should I be running 32bit or 64bit pharo 6?

2017-07-08 Thread Tim Mackinnon
It would be great if the snap instructions were on the download page as I can never remember them when I point fellow devs to Pharo (who often are using Linux) Tim Sent from my iPhone Sent from my iPhone > On 7 Jul 2017, at 14:49, Alistair Grant wrote: > > If you're on Ubuntu, the snap ins

[Pharo-users] PreDebugWindow: Report to whom?

2017-07-08 Thread horrido
In the PreDebugWindow, there is an option to Report an exception. But to whom does it report? I can't find any documentation for this. I presume most developers would never need to Report anything. -- View this message in context: http://forum.world.st/PreDebugWindow-Report-to-whom-tp4953974.h

Re: [Pharo-users] installing iceberg

2017-07-08 Thread Norbert Hartl
> Am 08.07.2017 um 08:24 schrieb Stephane Ducasse : > > Sergio > > You should pay attention we discovered incompatibilities in the libgit lib. > So we will produce a Pharo 6.0.1. I hope it is 6.1 > > Now did you try the latest VM because it should contain the latest > version of the plugin. >