Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

copy_model is overwriting #82

Open
nconrad opened this issue Aug 18, 2015 · 3 comments
Open

copy_model is overwriting #82

nconrad opened this issue Aug 18, 2015 · 3 comments

Comments

@nconrad
Copy link

nconrad commented Aug 18, 2015

I'm thinking that copy_model should look at existing object names. If the same name already exists, it could create a model with name "my model (1)" or such.

Alternatively, the server could throw an error, and then the user would have to choose to overwrite the existing or name it whatever they want (with the original name already present in the input box).

I like the first option because the interaction is the fastest, but the patric workspace copy command works more like option 2. In any case, the copy_model command currently overwrites, which we probably don't want.

Thoughts?

@chian
Copy link

chian commented Aug 18, 2015

I like the first one. Seems intuitive enough and provides a faster interface.

Sent from my iPhone

On Aug 17, 2015, at 8:01 PM, nconrad [email protected] wrote:

I'm thinking that copy_model should look at existing object names. If the same name already exists, it could create a model with name "my model (1)" or such.

Alternatively, the server could throw an error, and then the user would have to choose to overwrite the existing or name it whatever they want (with the original name already present in the input box).

I like the first option because the interaction is the fastest, but the patric workspace copy command works more like option 2. In any case, the copy_model command currently overwrites, which we probably don't want.

Thoughts?


Reply to this email directly or view it on GitHub.

@cshenry
Copy link
Contributor

cshenry commented Aug 18, 2015

I agree. I like option 1.

Sent from my iPhone

On Aug 18, 2015, at 1:39 AM, chian [email protected] wrote:

I like the first one. Seems intuitive enough and provides a faster interface.

Sent from my iPhone

On Aug 17, 2015, at 8:01 PM, nconrad [email protected] wrote:

I'm thinking that copy_model should look at existing object names. If the same name already exists, it could create a model with name "my model (1)" or such.

Alternatively, the server could throw an error, and then the user would have to choose to overwrite the existing or name it whatever they want (with the original name already present in the input box).

I like the first option because the interaction is the fastest, but the patric workspace copy command works more like option 2. In any case, the copy_model command currently overwrites, which we probably don't want.

Thoughts?


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub.

@nconrad
Copy link
Author

nconrad commented Sep 4, 2015

It would be cool to have a copy option at the workspace level that did this. I'd use it for the edit media workflow, for instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants