I personally leave the G environment only when I have
to edit code or run tests.
We have put quite some effort on hapao, who test coverage tool. We will soon
announce it. It is already integrated in the G environment.
Alexandre
Le 14-09-2014 à 14:53, Tudor Girba <tudor(a)tudorgirba.com
<mailto:tudor@tudorgirba.com>> a écrit :
Hi Phil,
Thanks for the kind words. I am really happy this experience makes it to the
core of Pharo.
Indeed, the goal is to offer a comprehensive set of arguments to get people to
not leave the environment. I myself, do my best to not leave it. As soon as I
notice that I have to leave the environment, I try to build the tools to help
me not do it. For example, this is how the database, file and Pillar support
were born.
It would be cool to know the reasons why people have to use other tools.
Perhaps we can do something about it.
Cheers,
Doru
On Fri, Sep 12, 2014 at 6:14 PM, phil(a)highoctane.be
<mailto:phil@highoctane.be> <phil(a)highoctane.be
<mailto:phil@highoctane.be>>
wrote:
I've been working in a data acquisition scenario today and GToolkit proved
to be of immense help.
Working in the live application, looking around for data (including file
contents), and inspecting it all + live debugging is really a sweet
experience.
With CommandShell I may not have to leave the environment...
Phil
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch