I have been using both Github/FileTree and Monticello for STON this week, and things have definitively progressed. Thank you, Dale & friends. It does seem that I have to save a version to Github/FileTree first and then copy it to Monticello (ss3) and not the other way around - otherwise things seem to get messed up. So Github/FileTree is sticky ;-) Sven PS: in th FileTree code that I am using (from Metacello/Pharo 2.0) there is a small UI problem: SmallInteger>>/ Job>>progress JobChange>>progress SystemProgressMorph class>>updateJob: MessageSend>>value: MessageSend>>cull: MessageSend>>cull:cull: AnnouncementSubscription>>deliver: in Block: [action cull: anAnnouncement cull: announcer] BlockClosure>>on:do: BlockClosure>>on:fork: in Block: [Processor terminateActive] (The stack isn't any longer ;-) On 27 Nov 2012, at 22:05, Sven Van Caekenberghe <sven@stfx.eu> wrote:

Dale, Max,

It might be that I was using an older filetree version, I am just going to overwrite the git files and commit and see from there. It is good to know that it should work.

Thx,

Sven

On 27 Nov 2012, at 21:58, Dale Henrichs <dhenrich@vmware.com> wrote:

...

Sven,

When viewing changes from the Monticello Browser, there are certain circumstances when the Browser doesn't recognize that the package in a FileTree repository is an ancestor (I haven't fully characterized this, but I have seen it happen - I think it usually happens when the package in FileTree is not a direct ancestor of the in-image package) ... This is the type of thing that happens when packages names have been changed in Monticello as well ...

In those cases, you be able to _open_ the repository and do a direct comparison of the in-image package and the package in the repository and get a good comparison ...

Dale

----- Original Message ----- | From: "Sven Van Caekenberghe" <sven@stfx.eu> | To: "Pharo-project@lists.gforge.inria.fr Development" <Pharo-project@lists.gforge.inria.fr> | Sent: Tuesday, November 27, 2012 11:56:18 AM | Subject: [Pharo-project] Combining Regular Monticello with Github/FileTree | | Hi, | | Before I get too frustrated trying, a quick question: is it possible | to combine regular monticello with github/filetree ? | | I have STON both in ss3 as on github, but it seems I cannot compare | my in-image ss3 version with a filetree/github repository on disk: | it reports everything as changed (maybe due to meta data | differences, I don't know). | | How do I know the difference between the ss3 version and the filetree | version ? | I guess I could just save the filetree version and let git decide ? | But maybe, then everything will be different as well ? | | Sven | | -- | Sven Van Caekenberghe | http://stfx.eu | Smalltalk is the Red Pill | | | | |

HI camillo I should release the changes I did: I grouped Job related classes into Kernel-Job and all the progressBar related class into Morphic-Progressbar and this is cool to get them grouped like that. Stef On Nov 30, 2012, at 11:25 PM, Camillo Bruni wrote:

On 2012-11-30, at 19:22, Sven Van Caekenberghe <sven@stfx.eu> wrote:

...

I have been using both Github/FileTree and Monticello for STON this week, and things have definitively progressed. Thank you, Dale & friends.

It does seem that I have to save a version to Github/FileTree first and then copy it to Monticello (ss3) and not the other way around - otherwise things seem to get messed up. So Github/FileTree is sticky ;-)

Sven

PS: in th FileTree code that I am using (from Metacello/Pharo 2.0) there is a small UI problem:

SmallInteger>>/ Job>>progress JobChange>>progress SystemProgressMorph class>>updateJob: MessageSend>>value: MessageSend>>cull: MessageSend>>cull:cull: AnnouncementSubscription>>deliver: in Block: [action cull: anAnnouncement cull: announcer] BlockClosure>>on:do: BlockClosure>>on:fork: in Block: [Processor terminateActive]

my bad, I have to finish my Job/ProgressBar refactoring :P