Open doc within Collanos, then save as new version

[MattC]

Situation: I open a word doc, then save as a new doc name. Currently it saves to the Collanos Temp directory by default.

Is there any way to
a) save it right back to the workspace directly? Or,
b) safely move it from the temp directory to the workspace?

Thanks!

[Gil Heiman]

If I understand you correctly, you are opening a doc from within Collanos and are renaming it outside of Collanos using 'Save As', correct?
If this is the case, you will need to add the new file manually to the workspace just as you had added the original file.
If you want to rename the file yet keep it in the workspace, select the 'rename' option (right click and select rename in Windows).

[tim.moore]

Hi,

We're looking at this as an alternative to Groove. I have to say we're really impressed so far. The UI and functioanlity is brilliant, except for this aspect.

The ability in Groove files tool to save a file back under a different name is one we really need. They way Groove does it is (forgive me if I'm teaching you to suck eggs here) that where Collanos asks if you want to update the workspace, Groove provides the filename and enables you to change it, effectively saving a new version of the file into the workspace.

This is a really improtant aspect that allows us to retain version control over our files. Are there any plans to introduce this type of feature in the future or any other kind of versioning functionality?  I'm assuming that only deltas are saved back into the tool and distributed as part of a sync....

[Franco Dal Molin]

Hi Tim, thanks for stressing this point one more time. I clearly see your point and need.

I pushed this issue into the scope of the next development sprint, currently under scope planning. I can't promise it will make it into the release, but if we can find a "quick win" solution (vs. very high development efforts) and if there aren't too many other important features lines up, it might well make it into the late summer release. Please understand that we are permanently forced to take trade-off decisions because of limited development resources.

About the deltas... correct, we do calculate the binary delta between the previous version and the new version, and send only this part to the other members. In case of renaming and saving back, we would have to think carefully how to "send" this "new" file across the network.