some user experience suggests about commit and file brower

1. Sugguest:support delete files in commit's files chosing dialog    Why:sometimes i commit some changes, i may find some files is needless，so i want to delete them. but now i had to manual open the target folders that my places in different path then delete them.    Solution: maybe we could right click the target file and just chose delete file.    2. Sugguest:support "some actions on" files in commit's files chosing dialog    why: reason is similar to suggest 1    actions: add to ignore file/show logs    Solution: right click the target file and then chose some action.    3. Sugguest:support refresh files status in commit's files chosing dialog    why: sometimes i edit a changed file to unchanged status(for example, i find some code changes are useless), then i must close the dialog , right click the project, chose commit. it's boring me.    Solution: auto refresh files status or support manual refresh files status( c-R or F5)    4. Sugguest: view support mode like normal file brower(mac finder)    why: i think we dont need mac finder when we use smartsvn    Solution: view mode like normal file brower, only see files and sub-dicrectories in current dicrectory.      thanks for your good job.

Last updated 8 years ago

Hi there,  I'm happy to pass suggestions on but would rather play devil's advocate in this case just to push back on a couple of suggestions - I'm not saying no, but if you could justify some of your thoughts I'd be grateful.  Steps 1, 2 and 3 are pretty much the same thing - but two points there. The first is, surely its' better practice to make sure everything is ready for commit before opening the dialogue? If that was the case those actions wouldn't be necessary. Also if that much was possible from the commit dialogue it'd make most of the program redundant.  Step 4, why not just work directly in Finder if you want something that looks and works more like it? You could work outside of smartSVN, then once you're close to ready open SmartSVN, refresh the view and make sure you don't have any redundant files etc. That way when you open the commit dialogue there's no need to make any changes from there as well.  As I said, just playing devil's advocate but I'd be grateful if you could put forward a few more arguments in favour of your suggestions - thanks very much.

thanks for your reply.    i understand we could not add too many functionalities to one tool, it make things complicated, but i think the core principle is "simple and practical", not just simple.    the tools are human's extend ability, and this is why we also have gui not just command. Ides has many duplicated functionalities that other softwares already had on account of it's core goal is promoting our productivity as much as possible. we dont need switch our working desktop , we just need do it here.    Basic file manage base on file system and svn is a practical functionality, it can reduce time wasting on switch/target folders and files/duplicated ops.    Programmers need to be perfect but perfect is only belong to god. Some infrastructure can help programmers to be better, no one can realy sure about everything about (s)he want to commit.      

orbrey;169250Hi there,    I'm happy to pass suggestions on but would rather play devil's advocate in this case just to push back on a couple of suggestions - I'm not saying no, but if you could justify some of your thoughts I'd be grateful.    Steps 1, 2 and 3 are pretty much the same thing - but two points there. The first is, surely its' better practice to make sure everything is ready for commit before opening the dialogue? If that was the case those actions wouldn't be necessary. Also if that much was possible from the commit dialogue it'd make most of the program redundant.    Step 4, why not just work directly in Finder if you want something that looks and works more like it? You could work outside of smartSVN, then once you're close to ready open SmartSVN, refresh the view and make sure you don't have any redundant files etc. That way when you open the commit dialogue there's no need to make any changes from there as well.    As I said, just playing devil's advocate but I'd be grateful if you could put forward a few more arguments in favour of your suggestions - thanks very much.

I've raised a feature request to our smartsvn team for you, I'll keep you posted.

thanks very much.

Hi there,  Sorry for the delay in replying. Having discussed this internally, these are the conclusions we've reached:  Being able to delete files from the commit window would be very confusing for new users and could lead to errors (like you say, nobody is perfect). However, being able to revert given files to remove them from the commit would be useful especially if contents could be saved so changes aren't lost. A refresh while in the choosing dialogue would also be useful. I'll raise these internally as separate improvement requests though it may be some time before they're implemented.  The file browser idea however isn't really viable as from our point of view existing functionality is being duplicated there. It's possible that some limited browsing may be useful for externals etc but by the same token this is available through the repository browser.  Having said that, are you evaluating smartsvn as a possible solution for a team or a business here? If so it might well be worth getting in touch with our sales team on the number in the footer to see if something can be worked out.