Working with a shared sandbox

Hi,

The reason is that the user is developing at both environments (Linux / win).
He is developing with QT. He performs changes at Windows and then check it also at Linux and would like to be able to perform changes there as well.
Using the other option (different repositories)- he would be needed to deliver - accept each time.

I don't understand why suspending won't satisfy your requirements. Getting out of sync is only an issue if you don't suspend before switching. Even then, you'll only lose changes if they are not checked in to the change set.

Are multiple repositories necessary? You cannot avoid completing a change set if you're moving it between repositories.

Hi,

"you'll only lose changes if they are not checked in": loosing local changes is a big issue for us. I am for sure do not want to be in that situation.
Why can't the user just have a sandbox accesible from both Linux and Windows? Then all he needs to do it change the files at the sandbox using his IDE (which is not Eclipse). At the end go to RTC and chckin-deliver etc.?

Hi,

"you'll only lose changes if they are not checked in": loosing local changes is a big issue for us. I am for sure do not want to be in that situation.
Why can't the user just have a sandbox accesible from both Linux and Windows? Then all he needs to do it change the files at the sandbox using his IDE (which is not Eclipse). At the end go to RTC and chckin-deliver etc.?

Then I would recommend using the command line to do your interactions with SCM. Load your repository workspace to one location that is accessible by both platforms.

Hi yaron,

When I was evaluating the RTC, I tried the following. See if this matches what you want. Let's say I have updated the workspace from sandbox 2. Then when I open sandbox 1 from RTC client:
1. Out-of-sync is detected
2. I disconnect all the projects in sandbox1
3. I share them again ( by dragging from package explorer to the pending changes directly)
4. "out-dated" files in sandbox 1 will be shown as unresolved changes. I can choose to keep the out-dated or "undo" to get to latest.

flowingbear

Hi,

"you'll only lose changes if they are not checked in": loosing local changes is a big issue for us. I am for sure do not want to be in that situation.
Why can't the user just have a sandbox accesible from both Linux and Windows? Then all he needs to do it change the files at the sandbox using his IDE (which is not Eclipse). At the end go to RTC and chckin-deliver etc.?

Then I would recommend using the command line to do your interactions with SCM. Load your repository workspace to one location that is accessible by both platforms.

Hi,

Thanks for the response.
The problem when getting to "out of sync" scenario is that the user will easily loose his local (unresolved) changes.

I could do some command line manipulations, but I prefer to get a "bread and butter" solution for that.

Hi,

Thanks for the response.
The problem when getting to "out of sync" scenario is that the user will easily loose his local (unresolved) changes.

I could do some command line manipulations, but I prefer to get a "bread and butter" solution for that.

The safest method is to check in changes before switching workspaces. If you want to share a sandbox, this is what you'll have to do.