Hi,
what's the status of haptic feedback with QML in SailfishOS now ?
I'm just trying to port an app from Ubuntu Phone, where code looks like :
Haptics.play({duration: 10, attackIntensity: 0.9})
No import or whatever, Haptics is just available as a singleton for
developpers to use...
What's the Sailfish way ? Do I have to import QtFeedback 5.0 ?
and then, is there any example on how to use it ?
thanks in advance,
Franck
Le 30/04/2015 07:57, Reto Zingg a écrit :
On 30.04.2015 01:49, Martin Kolman wrote:
Wed, 29 Apr 2015 12:56:20 +0000 Kimmo Lindholm <kimmo.lindh...@eke.fi>:
Any news about whitelisting QtFeedback?
-kimmo
Also what about QtPositioning ? I know that the pull request for RPM
validator has already been merged a while ago,
but when I recently tried to submit an application using QtPositioning
to Harbour, I got a reply that is actually still not yet allowed...
as always, the new APIs get allowed once the matching SDK is out. As
communicated earlier QtPosition will be allowed with 1.1.4.x, but that
is not even out yet for all (just early access).
So please be patient a little more, thanks.
Regarding QtFeedback, it still needs somebody to step up and take over
maintainership, ideally upstream.
Once it's stabilized then, we can allow it in Harbour.
best regards
Reto
Martin
-----Original Message-----
From: devel-boun...@lists.sailfishos.org [mailto:devel-
boun...@lists.sailfishos.org] On Behalf Of Reto Zingg
Sent: 2. joulukuuta 2014 11:00
To: devel@lists.sailfishos.org
Subject: Re: [SailfishDevel] QtFeedback 5.0 not allowed? Really?
Hi,
On 01.12.2014 23:34, sailfishmail wrote:
Another observation:
You're allowed to require qt5-qtfeedback in your RPM-packaging
according to the faq:
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/all
owed_requires.conf
It's a mistake that qt5-qtfeedback made it into the
allowed_requires.conf file.
It's out for update 10:
https://github.com/sailfish-sdk/sdk-harbour-
rpmvalidator/blob/1.21/allowed_requires.conf
As soon as this libQt0Feedback.so.0 naming mess (note the 0 between
Qt and
Feedback!) is clean up, we will allow QtFeedback in Harbour (will
probably not
make it to the next update, but in a later one).
br
Reto
which installs
/usr/lib/libQt0Feedback.so.0
/usr/lib/libQt0Feedback.so.0.0
/usr/lib/libQt0Feedback.so.0.0.0
/usr/lib/qt5/qml
/usr/lib/qt5/qml/QtFeedback
/usr/lib/qt5/qml/QtFeedback/libdeclarative_feedback.so
/usr/lib/qt5/qml/QtFeedback/plugins.qmltypes
/usr/lib/qt5/qml/QtFeedback/qmldir
However, according to
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/all
owed_libraries.conf
and
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/1.18/all
owed_qmlimports.conf you're not allowed to use what you required
to be
installed.
Maybe some misunderstanding when making the harbour validation
scripts?
-Asser
Mon, 01 Dec 2014 22:08:34 +0100
"Peter Pykäläinen" <peter.pykalai...@gmail.com> kirjoitti:
Thanks Kimmo!
That was new.
And it fails:
Libraries
=========
ERROR [/usr/bin/harbour-sailraid] Cannot link to shared library:
libQt0Feedback.so.0
INFO [/usr/bin/harbour-sailraid] Please see our FAQ here:
https://harbour.jolla.com/faq#Shared_Libraries
FAILED
Requires
========
ERROR [libQt0Feedback.so.0] Cannot require shared library:
'libQt0Feedback.so.0'
INFO [harbour-sailraid] Please see our FAQ here:
https://harbour.jolla.com/faq#2.6.0 how to use
'__provides_exclude_from' and '__requires_exclude' .spec file to
avoid that FAILED
And it fails totally.
Not fun.
So no vibration then, how can this basic stuff not be accepted?
// Peter Pykäläinen
On 1 December 2014 at 22:57, Kimmo Lindholm <kimmo.lindh...@eke.fi>
wrote:
Run the pre-validation tool from SDK, if you get green there,
it’s
much closer to approval…
(I prefer accessing it through browser,
http://127.0.0.1:8080/C/harbour_tools/ )
-kimmo
*From:* devel-boun...@lists.sailfishos.org [mailto:
devel-boun...@lists.sailfishos.org] *On Behalf Of *Peter Pykäläinen
*Sent:* Monday, December 01, 2014 10:34 PM
*To:* Sailfish OS Developers
*Subject:* Re: [SailfishDevel] QtFeedback 5.0 not allowed? Really?
Hi,
yes I did, thank you all for your help.
Especially Andrey, you are the man!
Let's see now if this passes harbour QA or not :)
// Peter Pykäläinen
On 1 December 2014 at 22:30, Gabriel Böhme
<m.gabrielboe...@googlemail.com> wrote:
Have you tried cleaning the project? Helps sometimes.
Am Mon Dec 01 2014 21:18:17 GMT+0100 (CET) schrieb Peter
Pykäläinen:
I give up!
Once I figured out how to add the stupid haptics stuff into the
.pro
file I
then get errors on my main when I try to compile:
error: undefined reference to `SailfishApp::application(int&,
char**)' error: undefined reference to `SailfishApp::createView()'
error: undefined reference to `SailfishApp::pathTo(QString
const&)'
I have used this kind of code succesfully in my other app and no
issue there.
Any help would be much appreciated.
My main looks like this:
#ifdef QT_QML_DEBUG
#include <QtQuick>
#endif
#include <sailfishapp.h>
#include <rumbler.h>
#include <QQuickView>
#include <QQmlContext>
#include <QGuiApplication>
int main(int argc, char *argv[])
{
// SailfishApp::main() will display "qml/template.qml",
if you
need
more
// control over initialization, you can use:
//
// - SailfishApp::application(int, char *[]) to get the
QGuiApplication *
// - SailfishApp::createView() to get a new QQuickView *
instance
// - SailfishApp::pathTo(QString) to get a QUrl to a
resource file
//
// To display the view, call "show()" (will show
fullscreen on
device).
// return SailfishApp::main(argc, argv);
QScopedPointer<QGuiApplication>
app(SailfishApp::application(argc,
argv));
QScopedPointer<QQuickView> view(SailfishApp::createView());
Rumbler rumbler;
view->rootContext()->setContextProperty("Rumbler", &rumbler);
view->setSource(SailfishApp::pathTo("qml/harbour-myapp.qml"));
view->show();
view->showFullScreen();
return app->exec();
}
// Peter Pykäläinen
On 1 December 2014 at 15:08, Andrey Kozhevnikov
<coderusin...@gmail.com> wrote:
I can suggest you to use QtFeedback from Qt side and register
QML
type.
01.12.2014 18:06, Peter Pykäläinen пишет:
Just got my game rejected in Jolla Harbour this morning due
to:
*Import 'QtFeedback 5.0' is not allowed * Is it really so that
vibration is not allowed in Harbour apps?
Is there any alternative?
// Peter Pykäläinen
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
--
Gesendet von meinem Jolla
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
