On 27/10/14 13:05, stepharo wrote:
tommaso
send us a working script
not something that we should browse and understand.
Stef
You are right, the loading script is in the project page, but it is
indeed another step of unneeded indirection.
Thanks,
Tommaso
P.s.: for the sake of completeness, this is the script to load ShoreLine
Reporter and configure it to automatically submit the stack traces
without bothering the user ;-)
StartupLoader default executeAtomicItems: {
StartupAction
name: 'ShoreLine-Reporter Installer'
code: [ [
Gofer it
smalltalkhubUser: 'dalsat' project: 'ShoreLine-Reporter';
configuration;
load.
#ConfigurationOfShoreLineReporter asClass load.
"Setting Reporter configuration"
#SlReporter asClass enabled: true.
#SlReporter asClass autoSubmit: true.
#SlReporter asClass showSummary: false.
#SlReporter asClass showNotification: true.
] asJob run ]
runOnce: true.
}.
On 7/10/14 11:23, Tommaso Dal Sasso 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/
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
