Smalltalk › Squeak › Squeak - Dev

preference to add Monticello merges to recent changes?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

10 messages Options

Eliot Miranda-2

preference to add Monticello merges to recent changes?

Hi All,

I often times find myself wanting to see the most recently loaded changes after a package update. How about a preference that would cause Monticello to add changes to recent changes if loading a new version of a package (but not if loading a package for the first time)?

_,,,^..^,,,_

best, Eliot

cbc

Re: preference to add Monticello merges to recent changes?

On Wed, Mar 23, 2016 at 11:54 AM, Eliot Miranda <[hidden email]> wrote:

Hi All,

I often times find myself wanting to see the most recently loaded changes after a package update. How about a preference that would cause Monticello to add changes to recent changes if loading a new version of a package (but not if loading a package for the first time)?

Currently, Monticello logs all changes to recent changes, correct?

That always struck me as weird - when replaying them, should I load the package, or replay the changes, or both? Usually, of course, i had also made a few changes intermixed, which made the decision harder.

If there was a way to select recent changes by Monticello package load, would that work for your use case? No idea what kind of work that would involve, though.

-cbc

_,,,^..^,,,_
best, Eliot

Bert Freudenberg

Re: preference to add Monticello merges to recent changes?

On 23.03.2016, at 21:45, Chris Cunningham <[hidden email]> wrote:

On Wed, Mar 23, 2016 at 11:54 AM, Eliot Miranda <[hidden email]> wrote:
Hi All,

I often times find myself wanting to see the most recently loaded changes after a package update. How about a preference that would cause Monticello to add changes to recent changes if loading a new version of a package (but not if loading a package for the first time)?
Currently, Monticello logs all changes to recent changes, correct?

That always struck me as weird - when replaying them, should I load the package, or replay the changes, or both? Usually, of course, i had also made a few changes intermixed, which made the decision harder.

If there was a way to select recent changes by Monticello package load, would that work for your use case? No idea what kind of work that would involve, though.

-cbc

I thought currently every MC load or merge created a new change set.

- Bert -

smime.p7s (8K) Download Attachment

Eliot Miranda-2

Re: preference to add Monticello merges to recent changes?

In reply to this post by cbc

Hi Chris.

On Wed, Mar 23, 2016 at 1:45 PM, Chris Cunningham <[hidden email]> wrote:

On Wed, Mar 23, 2016 at 11:54 AM, Eliot Miranda <[hidden email]> wrote:
Hi All,

I often times find myself wanting to see the most recently loaded changes after a package update. How about a preference that would cause Monticello to add changes to recent changes if loading a new version of a package (but not if loading a package for the first time)?

Currently, Monticello logs all changes to recent changes, correct?

Yes. Newly loaded source lives in the changes file. But I'm talking about Utilities browseRecentSubmissions.

That always struck me as weird - when replaying them, should I load the package, or replay the changes, or both? Usually, of course, i had also made a few changes intermixed, which made the decision harder.

If there was a way to select recent changes by Monticello package load, would that work for your use case? No idea what kind of work that would involve, though.

I'm not interested in the recover changes/change list case here. I'm interested in "browse recent changes (R)" (Utilities browseRecentSubmissions) including the most recent modifications obtained by updating an MC package.

HTH

_,,,^..^,,,_

best, Eliot

marcel.taeumel

Re: preference to add Monticello merges to recent changes?

Hi Eliot,

the "Recent Submissions" tool seems broken in my trunk image. The upper list keeps updating and resetting the selection. Thus, I cannot browse. Can you confirm?

Best,
Marcel

Chris Muller-3

Re: preference to add Monticello merges to recent changes?

In reply to this post by Eliot Miranda-2

I specifically do NOT want changes from loading MC packages to go into
Recent Changes (R), because loading a package or updating my image
blows away all the work in that list which *I* am doing.

If you want to see the differences from a package, just click MC's
"Changes" button befor eyou load it, or if you've already loaded it,
just diff it to its ancestor..

On Wed, Mar 23, 2016 at 1:54 PM, Eliot Miranda <[hidden email]> wrote:

> Hi All,
>
> I often times find myself wanting to see the most recently loaded
> changes after a package update. How about a preference that would cause
> Monticello to add changes to recent changes if loading a new version of a
> package (but not if loading a package for the first time)?
> _,,,^..^,,,_
> best, Eliot
>
>
>

Eliot Miranda-2

Re: preference to add Monticello merges to recent changes?

On Thu, Mar 24, 2016 at 7:50 AM, Chris Muller <[hidden email]> wrote:

I specifically do NOT want changes from loading MC packages to go into
Recent Changes (R), because loading a package or updating my image
blows away all the work in that list which *I* am doing.

That's why it should be a preference. There are circumstances in which the work one /is/ working on is communicated in Monticello packages. So while it may not suit your workflow, there are times when its absence very much does not suit my workflow either. If I'm working on, say, trunk updates, I may very well want to see the dewltas form the previous update in recent changes.

If you want to see the differences from a package, just click MC's
"Changes" button befor eyou load it, or if you've already loaded it,
just diff it to its ancestor..

No. That means I have to go back and interact with Monticello. If I want, it's perfectly reasonable for me to want to see these methods in recent chaznges without having to go and select history and choose a version to diff and diff etc. Way too time consuming.

On Wed, Mar 23, 2016 at 1:54 PM, Eliot Miranda <[hidden email]> wrote:
> Hi All,
>
> I often times find myself wanting to see the most recently loaded
> changes after a package update. How about a preference that would cause
> Monticello to add changes to recent changes if loading a new version of a
> package (but not if loading a package for the first time)?
> _,,,^..^,,,_
> best, Eliot
>
>
>

_,,,^..^,,,_

best, Eliot

Eliot Miranda-2

Re: preference to add Monticello merges to recent changes?

In reply to this post by marcel.taeumel

Hi Marcel,

On Wed, Mar 23, 2016 at 11:36 PM, marcel.taeumel <[hidden email]> wrote:

Hi Eliot,

the "Recent Submissions" tool seems broken in my trunk image. The upper list
keeps updating and resetting the selection. Thus, I cannot browse. Can you
confirm?

In an updated trunk image, derived from the 5.0 release, I can confirm that Browse Recent Changes works. I see the most recent 30 definitions I have changed in a list browser.

Best,
Marcel

_,,,^..^,,,_

best, Eliot

Eliot Miranda-2

Re: preference to add Monticello merges to recent changes?

On Thu, Mar 24, 2016 at 2:59 PM, Eliot Miranda <[hidden email]> wrote:

Hi Marcel,

On Wed, Mar 23, 2016 at 11:36 PM, marcel.taeumel <[hidden email]> wrote:
Hi Eliot,

the "Recent Submissions" tool seems broken in my trunk image. The upper list
keeps updating and resetting the selection. Thus, I cannot browse. Can you
confirm?

In an updated trunk image, derived from the 5.0 release, I can confirm that Browse Recent Changes works. I see the most recent 30 definitions I have changed in a list browser.

found the export... menu a little too late :-(

Best,
Marcel

_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_

best, Eliot

Chris Muller-3

Re: preference to add Monticello merges to recent changes?

In reply to this post by Eliot Miranda-2

>> I specifically do NOT want changes from loading MC packages to go into
>> Recent Changes (R), because loading a package or updating my image
>> blows away all the work in that list which *I* am doing.
>
> That's why it should be a preference. There are circumstances in which the
> work one /is/ working on is communicated in Monticello packages. So while
> it may not suit your workflow, there are times when its absence very much
> does not suit my workflow either. If I'm working on, say, trunk updates, I
> may very well want to see the dewltas form the previous update in recent
> changes.

>> If you want to see the differences from a package, just click MC's
>> "Changes" button befor eyou load it, or if you've already loaded it,
>> just diff it to its ancestor..
>
>
> No. That means I have to go back and interact with Monticello. If I want,
> it's perfectly reasonable for me to want to see these methods in recent
> chaznges without having to go and select history and choose a version to
> diff and diff etc. Way too time consuming.

Recent Changes has a limited size, so you will either face truncation,
or, if you increased it to, say, 1000, you'll not be able to quickly
determine where in the big list the the prior changes ended, and the
new just-loaded stuff begins.

You mentioned you aren't interested in the recover changes/change list
case here. Why? It fits yor purpose in all the ways Recent Messages
doesn't. Would some improvement in that browser allow it to work just
as well?