Marcus Denker wrote: 
On Oct 13, 2013, at 7:00 PM, kilon <thekilon@yahoo.co.uk> wrote:

  
how you do that ? I try to find in the slice the method I have changed and I
see it has the whole morphic inside it. Very confusing.
Did you use the <Browse> button or <Changes> button.  The <Changes> button compares to the current slice. So if you make the slice in a fresh image (eg #30444), then if you unzip a new #30444 from which you review the slice for <Changes> you should see only your change.  However someone else using another image (eg #30450) that happens to have changes in packages overlapping your slice, the they will see those as changes when reviewing the slice.  It is of course important to see ALL changes a slices is going to make to an image, but as a "change review task" it seems very useful to see "only" the changes from one package version to the next.  As I understand it this is not currently possible - although I'd be very pleased to be correct.

For individual packages the way you compare differences between particular versions is with the <History>.  For Slices this seems useless, since there is no history.  It might be useful for this to be changed to show the history of each dependent package of the Slice?

Alternatively, comparing Versions and Monticello, it seems that:
* Versions defaults to showing the "changes to immediately previous version" plus a <Compare to current> button. 
* Monticello <Changes> button effectively defaults to "compare to current" while "changes to immediately previous" is hard to access.
I wonder if for consistency the existing Monitcello <Changes> button could be changed to <Compare to current> and a new <Changes> button be added that focuses only on the changes made for a slice to revolve a particular Issue.


  

  

Monticello always snapshots the whole package even for a one-character change.
  



As far as my cursor understand of fit goes, it works similar.

-ben


  
	Marcus