Re: [SailfishDevel] Sailfish SDK 3.1 has been released to all users

2020-05-07 Thread Caliste Damien 
Hello,

Le jeudi 07 mai 2020, Martin Kampas a écrit :
> Today (May 7th) at 11:00 UTC the Sailfish SDK 3.1 has been released
> to all users. Please, check out the in depth release notes from
> https://together.jolla.com/question/226423/.
I guess Harbour scripts will be upgraded soon. At the moment, when
uploading a newly built package, it complains that no OS matches the
requirements.

Is it an issue with my own package, or the scripts have not been
updated yet ?

Thanks,

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Sailfish SDK 2.2 has been released to all users

2019-11-06 Thread Caliste Damien 
Hello,

Le vendredi 01 novembre 2019, Martin Kampas a écrit :
> Today (Nov 1) at 14:00 UTC we published an update to the Early Access
> Build Targets. These match the Sailfish OS release 3.2.0.12
> (Torronsuo) now.
Does anyone already succeed in upgrading the SDK ? When I run the
maintenance tool and click on update modules, it replies there is no
update available. I've got the -ea repositories entries in the
parameters and only these are checked (the non -ea ones are unchecked).

Have a nice day,

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Secure storage for login data

2019-06-13 Thread Caliste Damien 
Hello,

Chris Adams was quicker than me to provide an example. Thanks Chris for
this comprehensive and commented code.

I may add some more words and comment another example:
https://github.com/sailfishos/sailfish-secrets/plugins/gnupgplugin/pinentry/qassuanserver.cpp

This is the implementation of a pinentry for GnuPG and it can store the
provided passphrase to avoid typing it each time.

To enter Sailfish Secrets, it is important to know that you're relying
on plugins to actually store the data. There is a default encrypted
sqlite storage, see:
 Sailfish::Secrets::SecretManager::DefaultEncryptedStoragePluginName

Everything is asynchronous. To dialog with the daemon, you need to
instanciate a SecretManager and provide requests to it, to store or to
read a secret data.

The secret data will be stored in a collection that is defined by a
name. You need to ensure that the collection exists, see
ensureCacheCollection() in qassuanserver.cpp

You can store a secret with a Sailfish::Secrets::StoreSecretRequest and
read it with a Sailfish::Secrets::StoredSecretRequest, see
requestPassphrase() in qassuanserver.cpp. This routine is asking for a
passphrase, but before doing it it is reading the secret cache to see
if the passphrase has been stored already or not.

Last but not least, compile sailfish secret in SDK, it will generate a
HTML documentation that is quite extensive.

As Chris said, this is open source, and you're encourage to open bugs
in Github or give feedback about API, doc...

Don't hesitate to ask if you need more specific help.

Regards,

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] mapplauncherd/booster and C++ QML plugin

2018-12-12 Thread Caliste Damien 
Hello,

Le mercredi 12 décembre 2018, Matthias Fehring a écrit :
> But what works is when I use "generic" booster type, then the app
> works.
From my understanding, this is expected. The booster will preload a
given set of libraries (qt5 for instance) but if your plugin requires a
library outside this set, the plugin will not be loaded because of
unresolved symbols. I had the issue with GnuPG plugin in Sailfish
Secrets. The daemon was launched with -type qt5, but my plugin was
linking on gpgme.so in addition to all Qt libraries. Switching to
generic solved the issue, as you noticed.

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] SQLite linking

2017-03-04 Thread Caliste Damien 
Hello,

Le samedi 04 mars 2017, rinigus a écrit :
> one month + 10 days later - no response for PR nor SQLite linking from
> Harbour / Jolla devs.
Well, the  topic of adding allowed libraries seems to be a sensitive
one, without easy answering. You may propose this discussion for a
coming community IRC meeting. Next one is next Monday, you may add a
topic, or prefer to wait for the next one, announcing your topic early
so Jaymz may arrange to get answers (at least a negative one).

You may try to ask on IRC directly who you may ping to get a review or
a discussion of your PR, sometimes they don't see them.

Good luck,

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] CalDAV/CardDAV Contributor Meeting

2017-02-08 Thread Caliste Damien 
Hello,

Le lundi 06 février 2017, Chris Adams a écrit :
> Thanks for bringing this to my attention!  Shall we say March 13th at
> 0900 UTC?
It's fine with me with this new date (except if there's a meeting at
work that may come later).

Regards,

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] CalDAV/CardDAV Contributor Meeting

2017-02-03 Thread Caliste Damien 
Hello everyone,

Le mardi 31 janvier 2017, Chris Adams a écrit :
> Just a quick reminder that the next CalDAV/CardDAV contributor
> meeting will be held this coming Monday the 6th of February at 0900
> UTC in #mer-meeting on irc.freenode.org.
I'm sorry, I can't attend because I have a full day meeting at work
that particular day. Chris, if you want, we can discuss on IRC another
day just both of us, tell me which moment you prefer, or by message in
Gitlab. I think, I had answered your remarks about the various pending
MR, but don't hesitate to ask if anything is not clear or still  badly
written.

Have a nice week-end,

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] string to double in QML?

2016-05-21 Thread Caliste Damien 
Hello,

Le samedi 21 mai 2016, mariusz sapinski a écrit :
>I'm trying to convert text from a text field:
> to double (property double ekpu)
You may want to use parseFloat().

http://www.w3schools.com/jsref/jsref_parseFloat.asp

Damien.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Howto ship QML plugins for harbour

2014-01-11 Thread Caliste Damien 
Hello,

Le vendredi 10 janvier 2014, Aaron McCarthy a écrit :
 You will have to patch and rebuild the QML plugin. This is because it
 is verifying that the correct import uri is used. You will need to
 patch the source to accept the harbour.appname.QtPositioning uri.
Ok, I see.

 It is also not just a mater of shipping the QML plugin with your
 application, you will need to ship all dependencies not approved by
 Harbour. For Qt Positioning this would also mean the Qt Positioning
 C++ library as well.
For .so libraries, it's fine, I've already shipped them with the
application, using an rpath variable.

 The plugins.qmltypes file is not important at run-time. It is used by
 Qt Creator for syntax highlighting and code completion.
Ok, good to know. I'm not using QtCreator, just emacs.

 QQmlEngine::addImportPath() or set QML2_IMPORT_PATH
Ok, thanks that was the missing information I need.

Thanks for the quick reply.

Damien.
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Howto ship QML plugins for harbour

2014-01-11 Thread Caliste Damien 
Hello,

Le vendredi 10 janvier 2014, Reto Zingg a écrit :
 lets take an other example ;-)
 
 https://github.com/nemomobile/nemo-qml-plugin-dbus
 
 which is not allowed as such in Harbour, so I had to add it:
 https://github.com/d0b3rm4n/harbour-simpletorch/tree/master/src/dbus
 
 I had to make changes in plugin.cpp and qmldir and install it 
 accordingly (see dbus.pro, qmldir installs to 
 /usr/share/$NAME/lib/harbour/simpletorch/dbus, and lib to 
 /usr/share/$NAME/lib/).
 
 In 
 https://github.com/d0b3rm4n/harbour-simpletorch/blob/master/src/harbour-simpletorch.cpp
  
 I had to set the addImportPath to /usr/share/$NAME/lib/ and then I
 can import is in .qml files as:
 
 import harbour.simpletorch.dbus 1.0
That's absolutely great. Thanks a lot for this, I should be able to sort
it out myself for my requirements now.

Thanks a lot and have a nice day,

Damien.
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] How to activate GPS on device

2014-01-01 Thread Caliste Damien 
Hello,

Le mercredi 01 janvier 2014, Bob Jelica a écrit :
 In QML you should use PositionSource element. Check it’s ”start()”
 and ”stop()” methods.
I feel a bit stupid, I tried my app first without anything, and I got
no GPS. Then I run the map app, accept the licence and then run my app,
which got GPS then.

I didn't realize that I had to accept the licence to use the GPS. Now,
it's working fine, when I start my app, GPS is also started and I got
GPS fix as expected.

So no issue, sorry for the noise.

Damien.
___
SailfishOS.org Devel mailing list

[SailfishDevel] How to activate GPS on device

2013-12-31 Thread Caliste Damien 
Hello,

   Now that I received my device, I can test Mæp for real. That's great.

   It's an app that uses the GPS. If Jolla's map app is running the
GPS is activated and my application can use it also (I use
QtPositioning in C++, the QGeoPositioningInfoSource class), it works
well. But if the map app is not runing, my app is not seeing any GPS
capability.

   So my question, what is the way on the device to activate the GPS
(and deactivate it when not necessary anymore) ? I thought that it was
possible through the GPS entry of the setting app, but it seems not. Is
there a way to do it through C++ like on Maemo 5 ?

Thanks and happy new year !

Damien.
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] Accent with maliit keyboard (QML mockup)

2013-12-03 Thread Caliste Damien 
Hello,

Le lundi 02 décembre 2013, dcali...@free.fr a écrit :
 which would give after pressing it (like the shift key):
 à|w|é
 shift|æ|è|
 Fn|ç|ù
 
 Are my explanations clearer ? What piece of code should I give a look
 at to add a key that acts like the shift key by changing the layout
 of the whole keyboard (once if pressed once or locked if pressed
 twice) ?
Ok, maybe I was not clear so I made a small working QML mockup. Can
anyone would tell me how to implement this in a Maliit plugin so it
would replace the current French layout ?

Press the up button near to capslock button to obtain the alternative
layout.

I didn't implement the triple states (none, once, locked) of capslock
and the new altgr button (only none and once states), but the idea is
here !

Please help !

Damien.

PS : the position of the different letters in the alternative layout is
just an idea.
import QtQuick 2.0
import Sailfish.Silica 1.0

ApplicationWindow {
  initialPage: page

  Page {
id: page
Column {
PageHeader {
  title: Useless keyboard
}

Row {
	BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? fn.highlighted ? À : A : fn.highlighted ? à : a; id: kbd_a }
   onClicked: { test.text += kbd_a.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? Z : z; id: kbd_z }
   onClicked: { test.text += kbd_z.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? fn.highlighted ? É : E : fn.highlighted ? é : e; id: kbd_e }
   onClicked: { test.text += kbd_e.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? fn.highlighted ? È : R : fn.highlighted ? è : r; id: kbd_r }
   onClicked: { test.text += kbd_r.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? fn.highlighted ? Ê : T : fn.highlighted ? ê : t; id: kbd_t }
   onClicked: { test.text += kbd_t.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? Y : y; id: kbd_y }
   onClicked: { test.text += kbd_y.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? fn.highlighted ? Ù : U : fn.highlighted ? ù : u; id: kbd_u }
   onClicked: { test.text += kbd_u.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? fn.highlighted ? Î : I : fn.highlighted ? î : i; id: kbd_i }
   onClicked: { test.text += kbd_i.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? fn.highlighted ? Ô : O : fn.highlighted ? ô : o; id: kbd_o }
   onClicked: { test.text += kbd_o.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? P : p; id: kbd_p }
   onClicked: { test.text += kbd_p.text; caps.highlighted = false; fn.highlighted = false } }
}
Row {
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? Q : q; id: kbd_q }
   onClicked: { test.text += kbd_q.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? S : s; id: kbd_s }
   onClicked: { test.text += kbd_s.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? fn.highlighted ? Ë : D : fn.highlighted ? ë : d; id: kbd_d }
   onClicked: { test.text += kbd_d.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? F : f; id: kbd_f }
   onClicked: { test.text += kbd_f.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? G : g; id: kbd_g }
   onClicked: { test.text += kbd_g.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? H : h; id: kbd_h }
   onClicked: { test.text += kbd_h.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width: page.width / 10.; Label { text: caps.highlighted ? J : j; id: kbd_j }
   onClicked: { test.text += kbd_j.text; caps.highlighted = false; fn.highlighted = false } }
BackgroundItem { width:

Re: [SailfishDevel] How to get GPS Location in QML

2013-10-30 Thread Caliste Damien 
Hello,

Le mardi 29 octobre 2013, tw_bolek a écrit :
 the .pro file does not change anything.There is no trace of
 QtPositioning in sailfishos/mersdk/targets/.../usr/lib/qt5,
 neither for arm nor for x86 (emulator).
I think that Christopher Lamb answered this.

I'm using Qt Positioning in Sailfish from C++ myself and it's working.
Except that there is no GPS in the emulator, so there is no source for
QGeoPositionInfo data. To test, I'm creating data by hand and see if my
application reacts correctly. Is it the right way to do ?

Otherwise, there are nice explanations at :
http://doc-snapshot.qt-project.org/qt5-nosubdir/qtpositioning-index.html

Regards,

Damien.
___
SailfishOS.org Devel mailing list