Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi everyone,

Unfortunately my bluetooth dongle didn't materialise, so instead I worked on storage of authenticated servers:

I'm still figuring out how settings storage in LO works -- I spent the large part of the day getting the storage working -- it also took quite some time to realise that the RuntimeException I was getting trying to acces the new Setting I'd created was due to the database not being update (which a make dev-install finally fixed). I can now successfully get an editable object, and am now working on actually reading/writing the data to it.

To store the list I'm using a set of a new type called "AuthorisedRemote" with two fields: name and pin. The Set is returned as an XNameAccess -- i.e. each entry already has a name. Is there a valid way of having a set of strings (using xs:string in the .xcs file fails), or should I just remove the name field from the AuthorisedRemote?

For the moment I'm storing authorised remotes in officecfg::Office::Impress::Misc::AuthorisedRemotes, is this an appropriate place, or should I move it elsewhere?

Cheers,

Andrzej

Ps. I'm away at my grandparents next week, so I won't be able to work on bluetooth on windows as I haven't set up my laptop for building on windows (and hadn't bothered moving windows onto my new ssd) -- however I have plenty of other things to get on with. (Internet can also be sketchy there as I'm on 3G and reception is poor -- if all else fails I'll use an internet cafe to push to git / do emails in the evenings.)



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.