Andreas: thank you.

Interesting! The fileIndex part wouldn't have been obvious to me, even though it makes enough sense.

I wonder: am I experiencing a new (ish) problem? 

One of the things that's fascinated me over the past year is that Squeak has really fantastic tools for solo development, which scale up really well to a small team (read: researchers,) but don't seem to be convenient in the context of a larger, distributed group of people working asynchronously on different things.

Have other people also had the "where are my changes/the changes from Trunk scroll forever" problem?

Given, if I'd been checking in with MC, I might not have this issue. But working in multiple images (especially when they differ by major versions) usually means multiple MC repos, so...

I'm going to add a method on SystemNavigation (and stick it in a menu) that does something like what Andreas has suggested to my personal images. "show my changes"

My question is: would this be useful to other people, or would it be another method/menu item that no one else uses? Should I push the change to the inbox?


On Jul 31, 2010, at 2:21 PM, Andreas Raab <andreas.raab at gmx.de> wrote:

> How's this for starters?
> 
> SystemNavigation new browseAllSelect:[:method|
>    method fileIndex > 1 "only look at changes file"
>        and:[method timeStamp beginsWith: 'your-initials-here'].
> ].
> 
> Cheers,
>  - Andreas
> 
> On 7/31/2010 1:30 PM, Casey Ransberger wrote:
>> Hey all,
>> 
>> I have a giant pile of images from the last two years. Many of them have
>> experiments I'd rather not lose, but I tend to meander in a Squeak
>> image, and forget to name the image files well, so I basically have a
>> lot of images that might have interesting changes, and no easy way to
>> figure out which ones I want to keep around, or extract things from.
>> 
>> I've gone through most of them manually. I'd like to be able to search
>> an image for changes that have my initials attached to them, though,
>> because poking around in a change sorter is perilous when there've been
>> changes from the trunk (it's noisy.) I don't know enough about how/where
>> changes are kept in the system to do that though.
>> 
>> Any help would be much appreciated! I'd love it if I could inspect
>> something in particular and find the data structure that my changes live in.
>> 
>> --
>> Casey Ransberger
>> 
>> 
>> 
>> 
> 
>