ubuntu-touch-coreapps team mailing list archive

[Thomas Voß <thomas.voss@xxxxxxxxxxxxx>]

On Sun, Jan 5, 2014 at 4:34 AM, Robert Schroll <rschroll@xxxxxxxxx> wrote:
> On Sat, Jan 4, 2014 at 11:45 AM, Nekhelesh Ramananthan
> <krnekhelesh@xxxxxxxxx> wrote:
>>
>> This email is concerning persistent storage options for an Ubuntu Touch
>> application developer. I hope this doesn't turn out to be a big email, but
>> in any case here is a short summary of this email. What is the future of
>> U1dB-Qt? Currently the documentation and tutorials for using U1dB is quite
>> limited and lacking in several area. Would it be possible to engage with the
>> original U1dB-Qt developers to improve this?
>>
>
> [...]
>
>
>> I did find some links to U1dB-Qt resources [1],[2],[3] which help a little
>> but is still missing a big chunk of features.
>>
>
> If it should help, I wrote up a post on using U1DB procedurally back when I
> was trying to learn it:
> http://rschroll.github.io/beru/2013/09/04/using-u1db-procedurally.html.
> Anyone writing up better documentation is welcome to use what I wrote, or
> perhaps just the correct parts thereof.
>
>
> On Sat, Jan 4, 2014 at 3:34 PM, David Marceau <uticdmarceau2007@xxxxxxxx>
> wrote:
>>
>> From the sounds of it you don't want to be limited to using *U1dB *and
>> *Qt LocalStorage*. No problem.
>> *****You can pick your favourite C++ based persistent solution from the
>> standard Ubuntu repositories but targetted for Ubuntu Touch.
>>
> I don't mean to get too distracted on this tangent, but this is a negative,
> not a positive, for the developer trying to learn the Ubuntu SDK.  (See the
> "Paradox of Choice".)  One of the things Ubuntu does very well is make
> opinionated choices on our behalf (even when they're wrong!), and that
> should be the case here as well.

Seconded, the platform should offer a default, well-tested and
well-documented way to solve the task at hand.

> While it's nice that the developer who
> wants to use mongodb can, that doesn't help the developer who just wants
> persistent storage.  For them, there should be one, and only one, obvious
> way to do it.  U1DB seems positioned to be that way, but its documentation
> is wanting.  This is certainly a problem.
>

Agreed, I'm CC'ing Lucio and Christian explicitly. Lucio knows about
U1, and Christian did the QML bindings for U1DB (see
https://launchpad.net/u1db-qt).

@Christian: Could you shed some light on the current status of the QML bindings.

HTH,

  Thomas

> Robert
>
>
>
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp