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

InstantUpload Path should include the account #78

Closed
smessmer opened this issue Jan 20, 2013 · 12 comments
Closed

InstantUpload Path should include the account #78

smessmer opened this issue Jan 20, 2013 · 12 comments

Comments

@smessmer
Copy link

I'm using two owncloud servers, one for business and one privately. Both are synced to my mobile phone. I'd like to use instant upload to upload my photos to the private cloud and not to the business cloud.
But if I activate the setting and I was logged in to the business cloud before, they of course are uploaded there.
So I'd like to have a setting "upload to" for instant upload. At least it should select the server, if possible it would also be nice to select the folder to upload to.

@davivel
Copy link
Contributor

davivel commented Jan 21, 2013

This is a great idea.

@tobiasKaminsky tobiasKaminsky changed the title Configure server (and maybe folder) for instant upload of photos InstantUpload Path should include the account Dec 27, 2014
@tobiasKaminsky
Copy link
Contributor

I have updated the description as it is now possible to select the folder, but not on which account this should be.

@davivel
Copy link
Contributor

davivel commented Jan 16, 2015

Mmm, I am not sure that the best option is extending the current path selector to include the account. How would we do the UI? Adding an extra input field in the dialog to select it?

We were thinking in diving the settings view in 'settings per app' and 'settings per account'. Not just for the instant upload, but first for it. That would allow the user even upload the new pictures taken to more than a single account.

@jancborchardt , your opinion here?

@jancborchardt
Copy link
Member

What do you mean by »settings per app«? We only need to divide the settings per account really.

That would allow the user even upload the new pictures taken to more than a single account.

That doesn’t really seem needed. At least it seems an edge case that we shouldn’t build on for now.

@davivel
Copy link
Contributor

davivel commented Jan 16, 2015

Thinking in a general sense, I consider could be features that make no sense per account; for instance, the PIN-code.

@davivel
Copy link
Contributor

davivel commented Jan 16, 2015

And sure that multiple accounts to upload pictures is a corner case, but the option should be available per-account in any case - in terms of what would be the settings layout there is no difference.

A different story would be that we'd rather prevent that more than an account may receive the pictures.

@jancborchardt
Copy link
Member

Ah ok – you mean general settings. I was just confused by the wording. :)

@davivel
Copy link
Contributor

davivel commented Jan 19, 2015

You know, here we use to invent words if needed :D .

Maybe we could deal with this issue after the changes in #757, since layout for settings and accounts is also involved there.

@tobiasKaminsky
Copy link
Contributor

In #757 I am currently only displaying the accounts in the navigation drawer. Of course the account can be changed there. But creating, deleting is not something that should be done there, I guess.
So this will still be in Settings. Therefore, if @jancborchardt agrees, you can discuss it here and now...

@davivel
Copy link
Contributor

davivel commented Jan 21, 2015

Good point, you are right, not all the administration of accounts needs to be in the drawer.

@jancborchardt
Copy link
Member

Yeah, we should move step by step here. Administration of accounts can stay in settings for now.

@davivel
Copy link
Contributor

davivel commented Feb 26, 2016

Duplicated in #827, let's track it there, seems there is some info.

@davivel davivel closed this as completed Feb 26, 2016
davigonz pushed a commit that referenced this issue Feb 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants