Re: [SailfishDevel] How to access the viewfinder of the QCamera?
Hello again, Am 20.03.2014 08:03, schrieb Stefan Brand: Hello, Am 18.02.2014 09:57, schrieb Andrew den Exter: Hi, As the Sailfish.Media 1.0 import is not allowed for applications in harbour, is there any way to write an application using the Camera with a Viewfinder in QML that would pass harbour QA at the moment? Or do we have to wait for the adapted VideoOutput? The adaptation is in the form of a plugin to QtMultimedia and the code is now up on github at https://github.com/nemomobile/nemo-qtmultimedia-plugins. Hopefully that will be of some help to you while we work to get that into an update. it seems this plugin was not part of the last update (10.4.20), at least VideoOutput is still not working with the camera for me. Is there any ETA for this to arrive in an official update, so proper use of the camera inside apps becomes possible? Or is there any way to implement something like this plugin inside an app without breaking harbour rules (as it seems now, the plugin uses libraries that are not allowed in harbour apps either). Are there any news on this issue? ETA for a working QML VideoOutput as Viewfinder (=inclusion of the plugin in Sailfish) or a supported viewfinder element in an allowed import? Regards, Stefan Brand ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to access the viewfinder of the QCamera?
On 07.04.2014 10:25, Andrew den Exter wrote: We're switching over to using the plugin as part of updating to Qt 5.2. That won't be part of the immediately pending update, but probably the one after that. Andrew Thanks for this info. Stefan ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to access the viewfinder of the QCamera?
Hello, Am 18.02.2014 09:57, schrieb Andrew den Exter: Hi, As the Sailfish.Media 1.0 import is not allowed for applications in harbour, is there any way to write an application using the Camera with a Viewfinder in QML that would pass harbour QA at the moment? Or do we have to wait for the adapted VideoOutput? The adaptation is in the form of a plugin to QtMultimedia and the code is now up on github at https://github.com/nemomobile/nemo-qtmultimedia-plugins. Hopefully that will be of some help to you while we work to get that into an update. it seems this plugin was not part of the last update (10.4.20), at least VideoOutput is still not working with the camera for me. Is there any ETA for this to arrive in an official update, so proper use of the camera inside apps becomes possible? Or is there any way to implement something like this plugin inside an app without breaking harbour rules (as it seems now, the plugin uses libraries that are not allowed in harbour apps either). I would really like to have a solution for this, as it prevents me to submit an update with a often requested feature to harbour. Stefan ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QML C++ Integration not working in Sailfish
Hi,
On 25.02.2014 15:06, antonio.cano.go...@ovi.com wrote:
An I try to connect this with my sailfish application with the code:
QGuiApplication *app = SailfishApp::application(argc, argv);
QQuickView *view = SailfishApp::createView();
Bloomfilters * bloomfilters = new Bloomfilters();
view-rootContext()-setContextProperty(Bloomfilters,
bloomfilters);
view-setSource(SailfishApp::pathTo(qml/bloomfilter.qml));
view-showFullScreen();
return app-exec();
But this is not working.
Someone have any idea about what am I doing wrong?
You can use qmlRegisterType to pass the Info of the C++ class to QML
like this in the cpp:
#include bloomfilters.h
int main(int argc, char *argv[])
{
// Get App and QML-View objects
QScopedPointerQGuiApplication app(SailfishApp::application(argc,
argv));
QScopedPointerQQuickView view(SailfishApp::createView());
// Register Bloomfilter Class
qmlRegisterTypeBloomfilter, 1(harbour.myapp.Bloomfilter, 1, 0,
Bloomfilter);
// Prepare the QML
view-setSource(SailfishApp::pathTo(qml/bloomfilter.qml));
view-show();
// Run the app
return app-exec();
}
Afterwards you can create a Bloomfilter-Object in QML:
Bloomfilter {
id: bloom
}
and use the methods with
bloom.insertElement(myelement)
I hope this helps.
Regards
Stefan Brand
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to access the viewfinder of the QCamera?
Hi, On 03.02.2014 09:57, Andrew den Exter wrote: We're working on a solution which will allow QtMultimedia's VideoOutput item to use that node instead of it's own built in nodes, but in the meantime have been accessing it through the GStreamerVideoOutput type which is defined in the 'Sailfish.Media 1.0' import. As the Sailfish.Media 1.0 import is not allowed for applications in harbour, is there any way to write an application using the Camera with a Viewfinder in QML that would pass harbour QA at the moment? Or do we have to wait for the adapted VideoOutput? I have added a simple QR-Reader to my app (SailOTP), but it only works if using the unsuppoerted GStreamerVideoOutput... Regards, Stefan Brand ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to access the viewfinder of the QCamera?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I would also be really interested in how to do this, since I see the
same error. So did anyone succeed in using the camera with a viewfinder
in QML? Or is this just not supported at the moment? Any comments from
Jolla on this?
Regards
Stefan Brand
Am 25.01.2014 21:22, schrieb Marcel:
Hi,
how can I access the viewfinder of the camera in Qt on SailfishOS?
If I try it in QML like this:
Camera {
id: qmlCamera
}
VideoOutput {
source: camera
focus: visible
}
Or if I use C++ implementing an own QAbstractVideoSurface as viewfinder
for a
QCamera object (which would be my prefered way as I want to precess the
image
data) I get the following error:
[W] CameraBinSession::processBusMessage:912 - CameraBin error: No
common
caps
After some digging in the gstreamer debug log it seems that the camera
source
is just supporting the data format video/x-android-buffer and there is
no
equivalent QVideoFrame::PixelFormat for this. Is there really no
possibility
to access the viewfinder in Qt? Then how is the camera app doing that?
Greets,
Marcel
___
SailfishOS.org Devel mailing list
-BEGIN PGP SIGNATURE-
Version: OpenPGP.js v.1.20131017
Comment: http://openpgpjs.org
wkYEAREIABAFAlLuptUJEEaIfXQX7obRAABSPwCggiulaqRQ3pUIWb1KNGGZ
DZ/xbBUAn143muIsrc0lYCFsoGRgvoQX/3so
=IV7g
-END PGP SIGNATURE-
___
SailfishOS.org Devel mailing list
[SailfishDevel] Update 1.0.3.8 changes LocalStorage location?
Hi there, I just installed the latest update 1.0.3.8 to my Jolla. Afterwards I opened SailOTP (the app I wrote) and was greeted with an empty screen. All off my OTP-Tokens where gone. A little investigation shows that the LocalStorage DB was moved somehow. Before the update it was in /home/nemo/.local/share/harbour-sailotp/QML/... After the update a new DB was created in /home/nemo/.local/share/harbour-sailotp/harbour-sailotp/QML/... Copying the old QML-folder into the second harbour-sailotp folder brought back my tokens. I didn't do any updates to my app, so this can only be caused by the system update. So did anyone else see this behavior with other apps? I think this might be a bug, so any thought on this? Thanks in advance. Regards Stefan Brand ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Update 1.0.3.8 changes LocalStorage location?
Well, I just used the default sailfish app template from the SDK...
In an IRC-Log I saw thp mention that setting organizationName and
organizationDomain to will revert back to the old path. So i changed
my main() in the cpp to this:
int main(int argc, char *argv[])
{
QCoreApplication::setApplicationVersion(APP_VERSION);
// Fix move of LocalStorage in libsailfishapp
QCoreApplication::setOrganizationDomain();
QCoreApplication::setOrganizationName();
return SailfishApp::main(argc, argv);
}
Unfortunately this doesn't seem to work. The first line setting the
application version is working fine, but it still uses the new storage
path. What am I doing wrong here?
Am 31.01.2014 20:24, schrieb Andrey Kozhevnikov:
yes, default path was changed. you might need to set your own
applicationName, organizationName. good written apps wasnt affected by
update ;)
https://github.com/sailfish-sdk/libsailfishapp/commit/3febb7a2204cf13f01ab9e9ff86a84afc9b137d7
On 01.02.2014 00:31, Stefan Brand wrote:
Hi there,
I just installed the latest update 1.0.3.8 to my Jolla. Afterwards I
opened SailOTP (the app I wrote) and was greeted with an empty screen.
All off my OTP-Tokens where gone.
A little investigation shows that the LocalStorage DB was moved
somehow.
Before the update it was in
/home/nemo/.local/share/harbour-sailotp/QML/...
After the update a new DB was created in
/home/nemo/.local/share/harbour-sailotp/harbour-sailotp/QML/...
Copying the old QML-folder into the second harbour-sailotp folder
brought back my tokens.
I didn't do any updates to my app, so this can only be caused by the
system update. So did anyone else see this behavior with other apps? I
think this might be a bug, so any thought on this?
Thanks in advance.
Regards
Stefan Brand
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
