A few suggestions on version control of SlickEdit

[eruisi]

1. SlickEdit should be able to store password so that users doesn't need to login before performing version operations (commit, check out, etc). When these operations are slow, SlickEdit doesn't respond user inputs, looks like hanging.

2. Display version number right after the file name in the Project View to make the current status clear to users.

3. Add version cotrolling protocols over ssh. They are more secure.

A lot of nice features of version control could be found in eclipse, may be helpful to improve it on SlickEdit.

Best Regards!

[Dan]

1. SlickEdit should be able to store password so that users doesn't need to login before performing version operations (commit, check out, etc). When these operations are slow, SlickEdit doesn't respond user inputs, looks like hanging.

We have avoided storing passwords because they would need to be encrypted somehow.  As for the lack of feedback on these operations, we are looking at reworking some of these features in the future.  Are you using it remotely?

2. Display version number right after the file name in the Project View to make the current status clear to users.

This is an interesting idea, but frankly I'm not that in touch with version numbers.  I wouldn't know if that meant a version was up-to-date or out-of-date.  There is an option in the CVS Options dialog to show you the file's status in the project toolbar.  It is off by default because it has problems sometimes, and it is nearly impossible to debug by email.

3. Add version cotrolling protocols over ssh. They are more secure.

Yes, this fits into the "things we want to rework" above.

[eruisi]

1. Yes, I synchronized my files with a remote CVS server. When I tried to diff files  with CVS server (pserver protocol), SlickEdit hangs.
2. In stead of version number, it might be better to make out-of-date files red in the project view.