I completely agree, I am all for minimal image and then the user should be able to install anything he/she wants through Catalog Browser, I think we need to make sure that the welcome text clearly illustrate this and that the new user is not confused.�� But that means that you the people who create project that are not in the main distribution make sure your project is on Catalog Browser and that there is a clear description of what it does.

Pharo already an excellent mechanism for installing packages. Just today I tried to install OSC library in Pharo 5 though monticello and configuration and I failed, then I tried the Catalog Browser and worked like a charm.

Big thanks to Esteban for this amazing tool is by far my favorite, second being GTSpotter of course ;)

On Mon, Oct 31, 2016 at 5:50 PM Sean P. DeNigris <sean@clipperadams.com> wrote:

Denis Kudriashov wrote
> You can look at features here:
> http://dionisiydk.blogspot.fr/2016/04/new-version-of-mocketry-30.html.

Ah, yes. I seem to recall one major hurdle for me was that each test needed
everything wrapped in a block. Is that still the case? Could this be hidden
somewhere in the mechanism? I also wonder whether Mocketry could be easily
integrated with Phexample, as I really love the stacked test concept...

Denis Kudriashov wrote
> BabyMock could not be treated as modern mock library just because it uses
> symbols instead of normal message sends. Even C# and Java mocks are based
> on normal messages.

In practice, I don't see why this makes such a big difference. What am I
missing?

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Mocks-are-missing-in-Pharo-from-thread-OSProcess-is-missing-tp4920574p4920911.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.