On 08/12/14 17:32, Sven Van Caekenberghe wrote:
On 08 Dec 2014, at 17:12, Marcus Denker wrote:
We should add this explanation to the tool itself…
Marcus
Yes, and maybe also show the actual stack trace and other info that will be
sent in dialog so that the user can see precisely what
> On 08 Dec 2014, at 17:12, Marcus Denker wrote:
>
>>
>> On 08 Dec 2014, at 16:34, Tommaso Dal Sasso
>> wrote:
>>
>>
>> On 08/12/14 14:47, Sven Van Caekenberghe wrote:
>>> Hi Tommaso,
>>>
>>> I think this is a cool initiative, many environments have something
>>> similar, so this is a wel
> On 08 Dec 2014, at 16:34, Tommaso Dal Sasso
> wrote:
>
>
> On 08/12/14 14:47, Sven Van Caekenberghe wrote:
>> Hi Tommaso,
>>
>> I think this is a cool initiative, many environments have something similar,
>> so this is a welcome addition.
>>
>> However, you must be clearer about the secur
On 08/12/14 14:47, Sven Van Caekenberghe wrote:
Hi Tommaso,
I think this is a cool initiative, many environments have something similar, so
this is a welcome addition.
However, you must be clearer about the security implications (and/or tell us
how these concerns are dealt with in other plac
Hi Tommaso,
> On 08 Dec 2014, at 14:27, Tommaso Dal Sasso
> wrote:
>
> Hello everybody,
>
> I am excited to announce that ShoreLine Reporter is now part of Pharo 4.
> ShoreLine Reporter is a tool to detect and report errors in Pharo: whenever a
> user encounters an exception, she can select t
This is really great news!
Thanks a lot for doing that. I see this as the first step in a completely
new direction for Pharo.
Cheers,
Doru
On Mon, Dec 8, 2014 at 2:27 PM, Tommaso Dal Sasso <
tommaso.dalsa...@gmail.com> wrote:
> Hello everybody,
>
> I am excited to announce that ShoreLine Repo
