Hello everybody,
thanks for your feedback.
On 27/10/14 07:01, Marcus Denker wrote:
I was thinking... would it make sense to have this in the image by
default?
On 27/10/14 13:07, stepharo wrote:
It depends:
- is it overriding?
- is it well packaged?
- is it cross cutting a lot?
I have been extremely careful to be as clean as possible. The stack
trace catching is implemented with a PreDebuggingAction without
overriding any of the existing code. It was one of my first design
goals, especially because the purpose of the tool is to be completely
pluggable and unpluggable without influencing the system.
Also, we tested it for three months in daily development activities, so
it is reasonably stable.
We are analyzing the stack traces we collected so far to see if what
useful information a developer can obtain from that. I would love to see
ShoreLine Reporter used to help the development of the Pharo ecosystem
and I would be glad to help if you think that such a tool could be
useful if integrated into Pharo.
Tommaso
On Tue, Oct 7, 2014 at 6:23 PM, Tommaso Dal Sasso
<[email protected] <mailto:[email protected]>> wrote:
Hello everybody,
for those of you who were not at ESUG, I present ShoreLine Reporter.
ShoreLine Reporter is a Pharo plugin to collect stack traces from
exceptions and send them to a central repository.
You can give feedback to the community by breaking things: how
cool is that?
* Why?
We are collecting stack traces for research purposes and to
identify the Pharo components that can be improved or optimized.
We are also working on a web platform where users can access the
submitted data and use them during the debugging process. More on
that soon!
* How?
You can install ShoreLine Reporter by visiting the project page
on SmalltalkHub:
http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/
<http://www.smalltalkhub.com/#%21/%7Edalsat/ShoreLine-Reporter/>
Installing ShoreLine Reporter requires only a couple of seconds,
and you can configure it with the level of feedback that you
prefer. On the SmalltalkHub page you can find a script to
automatically install ShoreLine Reporter with every new Pharo
image. Just drop it in your Pharo preferences directory and
forget about it.
Once ShoreLine Report is installed, you can decide to configure
if you want to be prompted to submit a stack trace, or to
automatically submit each exception without any bother.
* What?
We try to collect as few data as possible: the execution
stacktrace, the name of the author and the Pharo build. We do
*not* any collect personal data, such as passwords or
repositories. The data is currently stored on our server, at the
University of Lugano.
* Compatibility
ShoreLine Reporter is developed for the Pharo debugger. We are
improving ShoreLine Reporter to work with GTInspector, we will
push an update in the following days.
For any problem, contact me!
Thanks, hope to see a lot of your exceptions ;-)
Tommaso Dal Sasso @ REVEAL
--
--
Marcus Denker -- [email protected] <mailto:[email protected]>
http://www.marcusdenker.de
