Does anyone have any tips for loading Maui [in, say, a 3.9 based image]? I get all kinds of Magma-looking dependencies when I try to load it... Do I need Magma loaded? Anything else?
Thanks,
Rob
How do I get a change lost from all change sets back into a valid change set? I made a change in a method in an existing system class, but the change was done in a project and so showed up initially in the project's change set and somehow in messing around relearning how to use the change set sorter and the versions browser I managed to remove the change from the project change set and now it doesn't appear in any change set. The versions button when viewing the method still shows the changes though.
Also, how would I view a diff in "reverse" -- or in other words how might I show the diff between the current and original? The versions browser seems to show things backwards to what I would consider to be intuitive. (oh, and the "compare to version..." menu gives me a debug box)
Also how do I _really_ remove intermediate changes from the versions of a method? I don't want all my intermediate changes to be kept any more -- just the original and my final version. The "remove from changes" menu doesn't do what I thought it would (which is probably how I made the whole set of versions for the method disappear entirely from the one and only change set it appeared in)
On Wed, Nov 19, 2008 at 05:15:00PM -0500, Greg A. Woods; Planix, Inc. wrote:
How do I get a change lost from all change sets back into a valid change set? I made a change in a method in an existing system class, but the change was done in a project and so showed up initially in the project's change set and somehow in messing around relearning how to use the change set sorter and the versions browser I managed to remove the change from the project change set and now it doesn't appear in any change set. The versions button when viewing the method still shows the changes though.
One simple way to do this is to look at the versions of your method (versions button on a browser), then revert to an earlier version and revert back. The method and its change history should now be in your current change set. Use a dual change sorter to move it or copy it between projects.
Also, how would I view a diff in "reverse" -- or in other words how might I show the diff between the current and original? The versions browser seems to show things backwards to what I would consider to be intuitive. (oh, and the "compare to version..." menu gives me a debug box)
I don't know where "compare to version..." if coming from (I'm looking at an earlier version of Squeak as I write), but this sounds like a bug. I use a "compare to current" button on a versions browser to look at the difference between an older version and the current version, or when using Monticello, this feature is available in lots of places.
Also how do I _really_ remove intermediate changes from the versions of a method? I don't want all my intermediate changes to be kept any more -- just the original and my final version. The "remove from changes" menu doesn't do what I thought it would (which is probably how I made the whole set of versions for the method disappear entirely from the one and only change set it appeared in)
You will probably find that Monticello does change management in a way that is closer to your expectations (open a Monticello browser from the world menu). That said, here is one possible answer to your question:
Make a change set with with the classes and methods that you are interested in. Add a preamble to document it. Save the change set (file out), then file it in to a clean image. The intermediate changes will be gone in the new image. This may seem awkward, bot note that for any non-trivial changes that you intend to distribute to someone else, you will want to test your changes in a clean image to verify that it is complete and problem free.
Dave
On Wed, Nov 19, 2008 at 05:15:00PM -0500, Greg A. Woods; Planix, Inc. wrote:
How do I get a change lost from all change sets back into a valid change set? I made a change in a method in an existing system class, but the change was done in a project and so showed up initially in the project's change set and somehow in messing around relearning how to use the change set sorter and the versions browser I managed to remove the change from the project change set and now it doesn't appear in any change set. The versions button when viewing the method still shows the changes though.
right-click on the method in the browser (or a category or a class). Somewhere in the menu is "add to current change set"
Also how do I _really_ remove intermediate changes from the versions of a method? I don't want all my intermediate changes to be kept any more -- just the original and my final version. The "remove from changes" menu doesn't do what I thought it would (which is probably how I made the whole set of versions for the method disappear entirely from the one and only change set it appeared in)
Smalltalk condenseChanges
On Thu, Nov 20, 2008 at 7:48 AM, Matthew Fulmer tapplek@gmail.com wrote:
Smalltalk condenseChanges
Note that this will get rid of ALL intermediate changes in the system, including the original, including methods that you did not yourself change. You will be left with just the current version of each method in the system.
On the positive side, it will make you .changes file much smaller.
Chris
On 20-Nov-2008, at 10:48 AM, Matthew Fulmer wrote:
On Wed, Nov 19, 2008 at 05:15:00PM -0500, Greg A. Woods; Planix, Inc. wrote:
How do I get a change lost from all change sets back into a valid change set? I made a change in a method in an existing system class, but the change was done in a project and so showed up initially in the project's change set and somehow in messing around relearning how to use the change set sorter and the versions browser I managed to remove the change from the project change set and now it doesn't appear in any change set. The versions button when viewing the method still shows the changes though.
right-click on the method in the browser (or a category or a class). Somewhere in the menu is "add to current change set"
Yes, it's in the cascaded "more..." context menu (middle/yellow button) from the method name in a method pane! Thanks! I knew there had to be a proper way to do this but I somehow missed this menu item in my frantic search for a solution yesterday.
Also how do I _really_ remove intermediate changes from the versions of a method? I don't want all my intermediate changes to be kept any more -- just the original and my final version. The "remove from changes" menu doesn't do what I thought it would (which is probably how I made the whole set of versions for the method disappear entirely from the one and only change set it appeared in)
Smalltalk condenseChanges
Yeah, that's a little too much overkill as Chris else mentioned.
I'm surprised there's still no easier way to collapse some intermediate changes on individual methods (or even whole classes and/ or projects). In the version control / SCM world it seems to me this is a quite common request; though it is one that's not always handled so well by more primitive systems.
Certainly for whole projects the file-out/file-in method Dave describes is probably still the most complete and correct. However for trivial fixes to one or two methods this seems overkill.
On the other hand maybe I just need to adjust my paradigm for versioning many things a bit more to be in line with the current state of the art in Squeak.
How do folks propose small changes or fixes for Smalltalk these days? I'm still very much entrenched in the diff/patch world of CVS and similar systems. I'm used to looking at diffs to understand changes, and I like to read them directly in e-mail, not have to dive into the programming environment / IDE / emacs or whatever and then perform multiple operations just to then view the change inside the the IDE, no matter how much more powerful the IDE presentation of the change might be.
I am looking forward to learning to use Monticello to see if it really does do the kinds of things I think it should do for full SCM within Squeak.
I think most everyone is just using Monticello (or Monticello 2).
On Thu, Nov 20, 2008 at 1:26 PM, Greg A. Woods; Planix, Inc. woods@planix.ca wrote:
On 20-Nov-2008, at 10:48 AM, Matthew Fulmer wrote:
On Wed, Nov 19, 2008 at 05:15:00PM -0500, Greg A. Woods; Planix, Inc. wrote:
How do I get a change lost from all change sets back into a valid change set? I made a change in a method in an existing system class, but the change was done in a project and so showed up initially in the project's change set and somehow in messing around relearning how to use the change set sorter and the versions browser I managed to remove the change from the project change set and now it doesn't appear in any change set. The versions button when viewing the method still shows the changes though.
right-click on the method in the browser (or a category or a class). Somewhere in the menu is "add to current change set"
Yes, it's in the cascaded "more..." context menu (middle/yellow button) from the method name in a method pane! Thanks! I knew there had to be a proper way to do this but I somehow missed this menu item in my frantic search for a solution yesterday.
Also how do I _really_ remove intermediate changes from the versions of a method? I don't want all my intermediate changes to be kept any more -- just the original and my final version. The "remove from changes" menu doesn't do what I thought it would (which is probably how I made the whole set of versions for the method disappear entirely from the one and only change set it appeared in)
Smalltalk condenseChanges
Yeah, that's a little too much overkill as Chris else mentioned.
I'm surprised there's still no easier way to collapse some intermediate changes on individual methods (or even whole classes and/or projects). In the version control / SCM world it seems to me this is a quite common request; though it is one that's not always handled so well by more primitive systems.
Certainly for whole projects the file-out/file-in method Dave describes is probably still the most complete and correct. However for trivial fixes to one or two methods this seems overkill.
On the other hand maybe I just need to adjust my paradigm for versioning many things a bit more to be in line with the current state of the art in Squeak.
How do folks propose small changes or fixes for Smalltalk these days? I'm still very much entrenched in the diff/patch world of CVS and similar systems. I'm used to looking at diffs to understand changes, and I like to read them directly in e-mail, not have to dive into the programming environment / IDE / emacs or whatever and then perform multiple operations just to then view the change inside the the IDE, no matter how much more powerful the IDE presentation of the change might be.
I am looking forward to learning to use Monticello to see if it really does do the kinds of things I think it should do for full SCM within Squeak.
-- Greg A. Woods; Planix, Inc. woods@planix.ca
Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners
On Thu, Nov 20, 2008 at 02:26:09PM -0500, Greg A. Woods; Planix, Inc. wrote:
How do folks propose small changes or fixes for Smalltalk these days? I'm still very much entrenched in the diff/patch world of CVS and similar systems. I'm used to looking at diffs to understand changes, and I like to read them directly in e-mail, not have to dive into the programming environment / IDE / emacs or whatever and then perform multiple operations just to then view the change inside the the IDE, no matter how much more powerful the IDE presentation of the change might be.
One of two ways usually. The first, and somewhat prefered way, is to use the mantis bug tracker, and upload .cs files as patches.
The second way, preferered by a few less well managed projects (like everything I do), is to just fix a patch in squeak and commit it straight to the monticello repo.
Everything that the 3.11 team is doing (ie, me and keith hodges) works the second way. We make all the repositories globally writable, and let anybody commit, and mark which version is stable in the load script. We also use a somewhat new feature of SqueakSource to review all Monticello commits via email:
http://lists.squeakfoundation.org/mailman/listinfo/packages
I am looking forward to learning to use Monticello to see if it really does do the kinds of things I think it should do for full SCM within Squeak.
If you find it does not, tell me, and I'll fix it. I'm the main Monticello developer. Use mantis, or email the release list or the packages list. I'm planning to service all outstanding bug reports before the next release, Monticello 1.6, which is nearly ready.
beginners@lists.squeakfoundation.org
-
Chris Cunningham -
David Mitchell -
David T. Lewis -
Greg A. Woods; Planix, Inc. -
Matthew Fulmer -
Rob Rothwell