Esteban wrote:
>But is a superset.
>We do not want to keep two tools with same functionality (we already did this a lot in the past, but we are like alcoholics in recovery now��� :P
Hi Esteban,
you removed the Config Browser in Pharo5.0 Latest update: #50111 much too early.
As I stated in the bug (
https://pharo.fogbugz.com/f/cases/15703)
I would have kept both tools
for a while as the Catalog Browser is not yet a real replacement. Your assumption that it is a
superset is not (yet) right.
We have to check more deeply and give people time for feedback. Did you know for instance that
(after a request in the past) on the mailinglist I added the possibility to ConfigBrowser to allow
for own repositories with own configs. So you can not only use the tool with teh default MetaRepo's
but custom ones as well. As it was requested and delivered I assume people use that and Catalog
Browser offers no alternative for that.
I agree that we should move quickly and reduce amount of code to maintain. But when introducing new tools
replacing old ones we should at least give the opportunity to discuss or wait for feedback if problems
arise from moving over. I do not see any value in having the existing Config Browser removed
so quickly as it can be done at any time and until people are used to the new Catalog Browser - which
was announced just this week waiting for feedback and future improvements (including further feature synchronization).
Thanks
Torsten