Because I do not see why you need to load FileSystem or Moose.
I had forgotten than FileSystem was in 2.0; I don't see Moose anywhere in the groups menu.
But the general question is: when the stable load fails, what is plan-B for the user? I couldn't work this out from the source. I can see that there are various versions defined (eg, '4.0.9') but I'm not clear on where/what class to send the required messages to.
On Tue, 11 Jun 2013 22:44:34 +0100, Sean P. DeNigris <sean@clipperadams.com> wrote:
Thomas Worthington-2 wrote
it would be nice if the "stable version" did not appear as an option on those which do not have one.
I couldn't agree more. The configuration browser seems extremely limited. I guess it will be replaced by Versionner? That having been said, it's better than nothing, and provided to us for free, so if you are really want this fixed, at minimum open an issue, or better yet have a go yourself!
I'm still trying to get to the point where I can produce a working application and be familiar with how things work in a proper, modern OO system. I'm employed during the day as a PHP-programmer and I can feel it rotting my brain.
I agree that the browser is (much) better than nothing, I'm mainly just trying to find out what to do when there isn't a #stable version.
Start using an image that we build on jenkins for example Seaside ((we should have a seaside jenkins job) if not we should do one. Please someone add a bug entry if there is no seaside build.) And load some of the package you need to build your application. - you can read the monticello/metacello chapter on the Pharo by example 2 book. We are working on automatically a process and tool to validate all the packages and dsitribution. This way we will all be sure that configruation are loading. We are also working on a tool to express configuration. So let us know what is missing for you to build your application. Stef