Those MC upgrades which I think you ported over are needed. Using a remote connection is recommended, because a local connection would lock files and wouldn't be able to access multiple images simultaneously.
Can I automatically publish in magma local and squeak source/ss3/...
It is just a MC repository -- it _could_ be used as a back-end for SqueakSource, but I don't believe that has been done. On Thu, May 17, 2012 at 7:27 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Cool I should try. Should I install Magma locally? Can I automatically publish in magma local and squeak source/ss3/...
On May 17, 2012, at 4:59 AM, Chris Muller wrote:
Magma 1.3 runs on Pharo 1.3. Â Did anyone ever get a chance try Magma's new capability in this area?
 http://wiki.squeak.org/squeak/5603
Of course you get all versions, but I myself have been really enjoying "Browse mc origin" which it adds to the method menu -- it opens the standard MCVersionInfo box to see the version notes for when that version of the method was originally created.
On Wed, May 16, 2012 at 1:53 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
yes
Now we would love to have a database storing all the methods based on the ring meta model
Isn't the .changes somehow shrinked before every release? Â That should explain that.
On Wed, May 16, 2012 at 8:16 PM, Sean P. DeNigris <sean@clipperadams.com> wrote: For DateAndTime class>>#readFrom: ...
In Pharo 1.0, only one version: 'PeterHugossonMiller 9/3/2009 01:10' In Pharo 1.2.2, two versions, minus the one from 1.0: "#('SeanDeNigris 8/5/2010 15:51' 'StephaneDucasse 4/24/2010 12:46')" In Pharo 2.0, only the last version from 1.2.2 remains: 'SeanDeNigris 8/5/2010 15:51'
-- View this message in context: http://forum.world.st/Are-we-losing-method-versions-tp4630520.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.