honestly... I'm thinking that it was not a good idea to backport the spec conf browser to 2.0. looks to me that is not ready for production, and we need time to make it ready (time that we have for 3.0, but not for a bugfix release).
just my opinion Esteban On Jul 17, 2013, at 8:43 PM, Stéphane Ducasse <[email protected]> wrote: > :) > > I have a catalogBuilder that starts to work so we will use configurations for > generating > some nice information. > > Stef > > On Jul 17, 2013, at 2:55 PM, "Torsten Bergmann" <[email protected]> wrote: > >> screen attached >> >> Pharo 2.0: Slice and issue 11179 together with a fix for broken buttons >> Pharo 3.0: Slice and issue 11180 >> >> <configbrowserfilter.png> > >
