eriks
|
Re:first time impressions/questions - 2006/08/22 14:09
drowley wrote:
Hi guys. Wasn't sure which forum this belonged in, but none seem to have so much traffic that it'll get lost, so I'll just put it here. Coming primarily from a windows/TortoiseSVN usage background I've gotta say I was shocked at the sad state of svn support on the mac. I was very happy to see ZigVersion and like what I see so far, but a few things confuse me - perhaps they're just 1.0-isms. I'll preface by saying that I really like what I see so far, so please take these comments purely as a constructive wishlist. 
Thanks! We always appreciate more feedback
1) I always configure svn not to cache my credentials. zigversion seems to have done so without my asking because it's stopped asking for my login info- I would prefer it didn't remember, or at least let me control how it remembered (e.g. just one session, not at all, whatever).
This is something I never got around to because I'm lazy  We'll try to get it in for 1.1.
2) My svn server is remote and I have to connect through a VPN to get to it, so I am disconnected 98% of the time. Regular polling is bad for me - I used the defaults trick I saw on another forum to set it to 30 days for now.
We're planning on adding in a preference pane in 1.1, we'll having "disable polling" as one of those preferences.
3) I would like to be able to jump back and forth between using the svn commandline and zigversion on the same working copy. Will this be a problem? I'm willing to remember to hit a refresh button or something when I come back into zig, if necessary.
This is fine as long as you aren't using 'svn switch' to muck with the url the working copy points to. If your working copy is small enough (you didn't get the "your working copy is too large..." warning), then you won't have to hit refresh either.
4) I am CONSTANTLY diffing my wc against base, so exposing this functionality on a per-file basis without having to go through the checkin motions would be great. In fact, since I haven't committed anything yet, I didn't even know there WAS a diff until I saw it here. The first thing I looked for in the context menu was "diff" and was surprised not to see it there.
5) Same as #4, but diffing against a specific rev. I often have to track user issues back to a specific rev. I envision just being able to open the log/history for a file, right click on a specific rev, and choose "diff".
These are more well requested feature that we're working on getting into 1.1.
6) I have to agree with the camp that says "please use standard svn terminology" - I want to be sure I know what's happening, and I already know how svn works - I just don't want to muck with the commandline.
Opinion noted We probably won't be changing this.
7) It would be nice to have icons or a slightly more visual way of calling out the modified files.
We've been looking at adding highlighting to designated working copy/repository status, and probably also modified, etc status. This will probably be in 1.1.
8) I'm not sure I understand the over-arching usage model. I tend to think in terms of working copies. I may have several - one on a branch, one on the trunk, and maybe one of a snapshot in time. The repository info is all available in the svn info, so I'm not sure how I should be associating these with a repository in zigversion, or why. I'd like to just be able to point zigversion at an existing wc, and it should just be able to know from what repository it came. As a side note, I never ever ever have a working copy at root - it's always at least at trunk. I never point my working copies at the root of the repository.
The idea was to have you connect to a top level of the repository to start with, and then check out each working copy you would need; you would then connect to the repository whenever you want to do work and you could easily go between different working copies. It doesn't seem to be working out well for some people (especially if you end up using the "import working copy" button), but I think some of the changes we're talking about putting into 1.1 will help this out.
9) love the easy repository browser. Great when I'm hunting for a tag or something.
Thanks!
10) It would be great if I could see a list of which files changed in a particular rev when looking at the history for a directory. Sometimes this tells me as much as my own checkin comment.
This one is a maybe for 1.1. Might get slipped to 1.2.
Again, love what I see so far. Thanks!
Hooray! Looks like pretty much everything you want is already slated for 1.1. Good choices! hehehehe. We're trying for early october on 1.1; features and timeline may change, of course
|
