2014-11-05 13:05 GMT+01:00 Torsten Bergmann <astares@gmx.de>:
Hi,

when I initially created the config browser my idead was that (especially for newbees) the packages/frameworks/projects
are easy to load. Key to success is easy access to things.

One should not have to know or fight with Metacello, Gofer, ... in the first place.
Things should just work ("click, load and run"). Advances users know about the script way of loading things or
build configs with dependencies on their own.

So in the beginning there was only ONE repo in the Config browser that should include the configs
that are known to run in a specific Pharo version (therefore MetaRepoForPharo20, MetaRepoForPharo30,
MetaRepoForPharo40, ...

After that we found out it will be usefull to load also from older repos (like loading from
MetaRepoForPharo30 when in Pharo 4) or also allow custom repos.
Thats why I fixed it after the request from Sean: https://pharo.fogbugz.com/default.asp?13941

Now people seem to use this as well and would like to make the different repos more transparent.
No problem with the additional pane.

@Luc: I like your extension as with the config browser now people can see the other
�� �� �� repos, load from them when in newer Pharo versions or use custom ones.

�� �� �� But a newbee might easily be confused which repo to use and may end up in
�� �� �� non-working loading. This is the opposite to what was the original intention of the tool.

I agree with you and Stephan there. It must be simple for newcomers.
That is why I added the Settings and perhaps the default should be to hide the repositories list hence it keeps the actual Configuration Browser.

I just did this extension yesterday evenning because I discovered the "hidden" feature of multiple repositories by inadvertence ;-) ��
��



So we need to support both cases, but IMHO should keep things initially simple (according to the original idea).
So I would like to see:

��- add a toggle to the menu ("Show repositories") to switch the preference also in config browser
��- hide the pane by default��

This way a newbee can just load without getting into (for him complicated) questions
like "from what repo", "why is it not working" (when loading from the wrong), ...
and an advanced user can set the preference according to his need as he might have checked
the menus or preferences.

+1

Luc
��

Bye
T.