Re: Issue 3216 in pharo: [enh] Support for Metacello in Monticello

Updates:
        Status: Comment

Comment #4 on issue 3216 by stephane.ducasse: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

I do not understand why this code changes the addSlice implementation?
Why do you do that/
Slices have nothing to do with metacello.
Why dirty packages are removed?

why PseudoClass>>asClassDefinition is removed.....
Sorry but it looks plain bad!!!!

Comment #5 on issue 3216 by stephane.ducasse: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

also the menu are not Uppercased anymore. I suggest that you do a merge in  
the latest unstable to understand what I mean.

Comment #6 on issue 3216 by alexandre.bergel: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

We simply did not work on the latest version. I am updating...

Comment #7 on issue 3216 by alexandre.bergel: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

MonticelloGUI-AlexandreBergel.80 is now in PharoTaskForces.
Sorry for missing up with the version

Comment #8 on issue 3216 by stephane.ducasse: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

Ok I will have a look now

Comment #9 on issue 3216 by [hidden email]: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

Just a note that I expect to update the MonticelloBrowser support for  
Metacello with the introduction of symbolVersions ... I plan to create a  
MetacelloToolKit class (or classes) that will implement support for doing a  
number of operations in Metacello (creating configs, new versions,  
updating, releasing, etc.) with the idea that this code can be shared  
between the MonticelloBrowser commands, the OB-Metacello support and  
hopefully other tools as they become available ...

No problem Dale. We go incrementally.

Cheers,
Alexandre


Le 11/11/2010, "[hidden email]" <[hidden email]> a écrit:

Updates:
        Status: Fixed

Comment #10 on issue 3216 by stephane.ducasse: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

ok

Updates:
        Status: Closed

Comment #11 on issue 3216 by stephane.ducasse: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

  in fact I'm not sure that the metacello creation should be driven by the  
monticello browser
but I will integrate it now and we rethink it later.
in 12235

Comment #12 on issue 3216 by alexandre.bergel: [enh] Support for Metacello  
in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

I agree with you Stef. But I am looking for an easy way to use Metacello

Comment #13 on issue 3216 by [hidden email]: [enh] Support for  
Metacello in Monticello
http://code.google.com/p/pharo/issues/detail?id=3216

I tend to agree, but the MonticelloBrowser is a better place to hang  
Metacello functionality than the code browser (considering that OB isn't  
loaded all of the time).

I use the OB tools all of the time except when I am in a PharoCore and I  
miss the tools there ...

I am building the tool kit so that the functionality can move around or be  
implemented in multiple places while maintaining the same functionality ...