Recently having upgraded to 3.5, I finally wanted to start playing with DVS. The fileIn and fileOut features seem to work as expected, but the "changes" choice doesn't seem to do anything.
Here's what I do
1. create two images in the same folder, im1 and im2 2. Switch to im1 3. Use the DVS package browser to create a new package - EFoo 4. Add some methods to the package 5. fileOut the package. I notice that all the EFoo-* methods are in the resulting .st file. So far so good. 6. Switch to im2 7. Load the EFoo package into the package browser 8. Great! The classes are now there. 9. Modify the classes, add some methods, change some, ... 10. Go back to the package browser - there is a * next to the package. Good, it has changed. 11. hit the "Changes" button, to compare the current version to the one on disk. IT DOESN'T DO ANYTHING. I get an empty message browser. 12. ok, well file-out the package. Again, that works, and the changed things are in the resulting .st file. 13. switch back to im1 14, now, the version on disk is newer than the stuff in im1 15. I don't get any indication of changes from DVS 16. Again, hitting the "Changes" button doesn't do anything. 17. But, I can fileIn and it does properly add the methods.
The change features (of both CVS and DVS) are really important to me. Otherwise, I'm just going to continue to use change sets since browsing changes is so important.
Did I do something obviously stupid or wrong?
-Eric
On Friday, May 2, 2003, at 08:59 AM, Eric Scharff wrote:
Recently having upgraded to 3.5, I finally wanted to start playing with DVS. The fileIn and fileOut features seem to work as expected, but the "changes" choice doesn't seem to do anything.
[snip]
The change features (of both CVS and DVS) are really important to me. Otherwise, I'm just going to continue to use change sets since browsing changes is so important.
No, Eric, you're not doing anything wrong. I've had the same problem. Here's two things that might help.
First, it might be a good idea to switch to Monticello. Someday, it will be a full-fledged versioning system for Squeak. For now, it's a better DVS.
Second, you can still use change sorters in conjunction with Monticello or DVS, they just don't know anything about packages.
For my own work, I use Monticello for package management, fileIn and fileOut, CVS for versioning and change sorters for reviewing.
Hope this helps.
Colin Putney Whistler.com
Colin Putney wrote:
On Friday, May 2, 2003, at 08:59 AM, Eric Scharff wrote:
Recently having upgraded to 3.5, I finally wanted to start playing with DVS. The fileIn and fileOut features seem to work as expected, but the "changes" choice doesn't seem to do anything.
[snip]
The change features (of both CVS and DVS) are really important to me. Otherwise, I'm just going to continue to use change sets since browsing changes is so important.
No, Eric, you're not doing anything wrong. I've had the same problem. Here's two things that might help.
First, it might be a good idea to switch to Monticello. Someday, it will be a full-fledged versioning system for Squeak. For now, it's a better DVS.
While Monticello should work fine, I want to make sure everyone is aware it's in much earlier development. I just fixed a sorting problem yesterday, and the fileout format will likely continue to change for a while.
When the fileout format changes, you essentially have to re-fileout all your packages again, which makes everyone else who works on them update Monticello, which means they have to re-fileout all the other packages they work on, etc... so I can't guarantee stability at the moment.
Still, if you'd like to use it, it's great to have more people testing it. And the model is pretty darn stable, it's just the fileout format that isn't.
And yes, I too have seen the problem of the Changes button not working but it does sometimes. I haven't ever figured out what conditions determine whether it works or not.
Julian
On Friday, May 2, 2003, at 11:11 AM, Colin Putney wrote:
First, it might be a good idea to switch to Monticello. Someday, it will be a full-fledged versioning system for Squeak. For now, it's a better DVS.
Ah. I was afraid of something labeled "Alpha" with respect to version control.
Second, you can still use change sorters in conjunction with Monticello or DVS, they just don't know anything about packages.
I don't see how. Yes, changes show up in the change sorter, but I don't see how you can easily compare stuff on disk to stuff in the image. All the changes go into the current change set, rather than into a new change set which would make it easier to tell what has changed in what versions.
What I want is really pretty simple. After I do a CVS update and a fileIn, I want to browse the new changes, just the ones since my last update. What is the easiest way to do this?
-Eric
On Friday 02 May 2003 11:03 am, Eric Scharff wrote:
What I want is really pretty simple. After I do a CVS update and a fileIn, I want to browse the new changes, just the ones since my last update. What is the easiest way to do this?
It works for me.
I know this doesn't help, but what I did:
* add a package to the DVS package panel * edit it to point to where the source was * choose "file in"
I believe there's a difference between "file in" and "load".
On Friday, May 2, 2003, at 12:49 PM, Ned Konz wrote:
On Friday 02 May 2003 11:03 am, Eric Scharff wrote:
What I want is really pretty simple. After I do a CVS update and a fileIn, I want to browse the new changes, just the ones since my last update. What is the easiest way to do this?
It works for me.
I know this doesn't help, but what I did:
- add a package to the DVS package panel
- edit it to point to where the source was
- choose "file in"
I believe there's a difference between "file in" and "load".
I can file them in, but the changes button doesn't ever seem to do anything. What I wantis twofold:
1) Before I fileIn, I want to see the changes between the version on disk and my current version. 2) Before I fileOut, I want to see what I've changed in the package since the last time I filedOut. Obviously it knows that *something* has changed because it puts that asterisk in the package browser. It simply refuses to tell me what has changed.
-Eric
On Friday, May 2, 2003, at 11:03 AM, Eric Scharff wrote:
On Friday, May 2, 2003, at 11:11 AM, Colin Putney wrote:
First, it might be a good idea to switch to Monticello. Someday, it will be a full-fledged versioning system for Squeak. For now, it's a better DVS.
Ah. I was afraid of something labeled "Alpha" with respect to version control.
A sensible attitude. And thanks to Julian for pointing out what I should have - it works very well, but it's still under development, so the fileOut format can still change. This is a bit of a hassle when you have concurrent development going on.
Second, you can still use change sorters in conjunction with Monticello or DVS, they just don't know anything about packages.
I don't see how. Yes, changes show up in the change sorter, but I don't see how you can easily compare stuff on disk to stuff in the image. All the changes go into the current change set, rather than into a new change set which would make it easier to tell what has changed in what versions.
What I want is really pretty simple. After I do a CVS update and a fileIn, I want to browse the new changes, just the ones since my last update. What is the easiest way to do this?
Ok, here's the scenario, broken down pedantically.
- "Load" the package using DVS. - start a new change set, called 'working' - make some changes. - "File Out" using DVS. - cvs update - resolve conflicts - start a new change set ('update') - "File In" using DVS - switch to 'working' change set - make some more changes - "File Out" using DVS - cvs update - cvs commit
At this point, you've got two change sets. The one called 'update' is all the changes made by somebody else. The one called 'working' has all the changes you made.
Colin
Colin Putney Whistler.com
squeak-dev@lists.squeakfoundation.org
-
Colin Putney -
Eric Scharff -
Julian Fitzell -
Ned Konz