ConfigurationBrowser, Pharo 2.0

Ingo Hohmann <[hidden email]> (6 mins. ago) (1_Personal sent)
Subject:
To:
Date: Mon, 08 Apr 2013 17:39:54 +0200

Hi all,

I've played with squeak some time ago, and now I'll start doing the same
with pharo.

There are some personal projects I may or may not use pharo for - we'll
just see.

Some words about ConfigurationBrowser from a new user perspective:

- The ConfigurationBrowser is the first thing that you are guided to
  after opening an image, and there all you see is a list of:words like:
  - Tuio
  - Glorp
  - Foo
  - STON
  ...
  (Finding out which of these can not be found there is left as an
  exercise for the reader ;-)

  It would be great to be presented with some info on what these
  packages actually do. In a 1.4 image I tried to find the
  ConfigurationOf... Classes, to go to the download webpages, but even
  there information was scarce.

- the naming change of the tabs is good, but I propose a third tab:
  'Work needed' for Configurations where it is known that some work is
  needed. This would save new users from loading configurations which
  are known to be broken, and send an even stronger message to the
  maintainers.

Kind regards,

Ingo

>
> Hi all,
>
> I've played with squeak some time ago, and now I'll start doing the same
> with pharo.

Welcome

Yes!
We will improve because I want a description of the configuration to be able to
define better tools and also generate html documentation.

>  It would be great to be presented with some info on what these
>  packages actually do. In a 1.4 image I tried to find the
>  ConfigurationOf... Classes, to go to the download webpages, but even
>  there information was scarce.

Yes people do not like to write documents and after they complain :).

> - the naming change of the tabs is good, but I propose a third tab:
>  'Work needed' for Configurations where it is known that some work is
>  needed. This would save new users from loading configurations which
>  are known to be broken, and send an even stronger message to the
>  maintainers.

Yes now we are working on publishing **automatically** only working configurations.
>
> Kind regards,
>
> Ingo
>