Hi Marcel, Hi All,
minor chaos ensues if one uses the menu update when a commit dialogue for a package covered by the update has been opened but not completed. I guess the update should check for commits in progress and refuse to update until the commit has been closed. The issue is that there is an in-progress versioned working copy that doesn't inherit from the top of the update but from the tip of the imag''s pre-update version. So afterwards one has a damaged history.
When I tripped over this today it didn't upload the broken verison to the repository so all I had to do was quit the image, delete the version in my package cache, repeat the update, and then repeat the commit. But it would have been nicer if the update had refused to go ahead while the uncommitted versioned working copy existed. _,,,^..^,,,_ best, Eliot
Hi Eliot,
minor chaos ensues if one uses the menu update when a commit dialogue
for a package covered by the update has been opened but not completed. I guess the update should check for commits in progress and refuse to update until the commit has been closed. The issue is that there is an in-progress versioned working copy that doesn't inherit from the top of the update but from the tip of the imag''s pre-update version. So afterwards one has a damaged history.
As you know, I've long advocated for the idea that the ancestry is as much a part of MC's model that belongs to the user as the version name and notes. That's why I think the solution should be to expose that part of the domain to the user, and allow them to change it. It could be placed right under the version name, with a button that would activate UIManager's pop up selection list of the ancestors that the user could choose.
That way, if one performed "Update Squeak" with open commit dialogs, upon going back, the new "Change Ancestor" button (or the ancestor name) could be color coded, I suppose, to indicate that the selection is other than the most current. We do something similar in the repository list when a same-named version has a different UUID.
The goal being to open up more access to the MC model, while the software keeps the flow of the user's intentions moving "forward".
Best, Chris
squeak-dev@lists.squeakfoundation.org