← Back to team overview

ubuntu-phone team mailing list archive

Re: ownCloud app.


I disagree about an account setup in the 'Online Accounts' area being harder to use. Actually, that's the first place I'd expect to look for integration with online accounts. Furthermore, this is Owncloud we're talking about - the chances are very high that people using it will be either developers, or have a high degree of technical knowledge - one of the main draws of owncloud being you can install it yourself.

I agree with Daniel - I think the best place to have this is integrated with the other online accounts. How to do that however is a bit harder. In terms of OAuth, while it would be great to utilise it, we can't use something that ain't there - sounds like for the time being, username and password authentication will have to do. What's involved with these details being stored in some kind of secure file - is there any implementation currently for this in Ubuntu Touch? On the 14.04 desktop installs, Ubuntu defaults to ecryptfs for securing the user's home directory. Is there anything similar planned for Touch?

Daniel, I'm happy to post my code to launchpad, but to be honest, I'm not sure there's much point. I literally hacked together a webapp directed to my own server, running Owncloud 7 - nothing special there at all. The main line that does anything was the one to call the webapp - "Exec=webapp-container --store-session-cookies --webappUrlPatterns=https?://apps.curiouslegends.com.au/owncloud/* https://apps.curiouslegends.com.au/owncloud %u"

It's specific to my own install, and won't be much use to anyone else. I like your idea of creating a qml container to wrap around the app, which would ask for your URL, username, and password when you first open it, then plug these into the webapp. This would work fine - providing Owncloud version 7 was being run. Owncloud 6 was a bit of a write off for mobile access. I don't have any experience writing this however - happy to have a go if you want to point me in the right direction.



On 20/08/14 18:06, Matthew Paul Thomas wrote:
Hash: SHA1

Alberto Mardegan wrote on 19/08/14 08:17:
On 08/18/2014 10:36 PM, Rodney Dawes wrote:
We could, but I think we should try to work in the opposite
direction. Moving them into the base system means more strict
requirements on what changes they get and when they get updated,
and requires a system image update to get new ones, unless they
remain in click packages, which still has the same problem of
them being in click packages and click packages not having
dependencies. If they were moved to the .debs instead, we'd also
need new frameworks so that apps depending on the framework
plug-in could declare that; otherwise we can have broken apps.
Good point.
Having account setup in Online Accounts, instead of inside an app,
makes the app harder to use. People have to learn and understand that
there's a separate place on the system listing a separate "online
account" that an app may or may not have permission to access.

So it's worthwhile only if it saves a lot of time -- only if multiple
apps use the same kind of account. As long as there's only one
ownCloud app, having ownCloud accounts in Online Accounts would be

If multiple click packages provide the same account plug-in,
does online-accounts show it multiple times, or does it get
limited to the one account type being shown in the list? Avoiding
duplicates will at least be good in the meantime, while apps do
have to provide their own copies.
When you click on "Add account", you'll see all the available
providers; that is, if two different click packages ship a similar
account plugin, you'll see that twice. I don't think we can merge
them into a single one, and in fact if you create an account using
the plugin provided by the first app, you won't see it in the
second app.

That's an example of why apps shouldn't be able to add account types
to Online Accounts at all.

- -- mpt

Version: GnuPG v1


Follow ups