Re: [SailfishDevel] Cellular network information
Hi, it would be nice to get it to store, but not necessary. I just want to do something useful... Maybe it's better to use QtDbus. Is it so that you just have to poll it every time to update the information or is it possible to get interuption through the D-Bus? Regards, Jukka 2013/12/5 Lorn Potter > Hi, > It depends on if you want your app in the store or not. > You could use QtDbus to query the connman and ofono interfaces, much like > connman-qt and libqofono to get this information. > > If you don't mind not being in the store, QtSystemInfo's QtNetworkInfo is > on the device, or you could use libconnman-qt and libqofono themselves. > > Hope this helps! > > > On 05/12/2013, at 10:40 PM, Jukka Heikkilä wrote: > > > Hi, > > > > I'd like to get some cellular network information to my app. Is there > this kind of class like in Harmattan's QSystemNetworkInformation ( > http://harmattan-dev.nokia.com/docs/library/html/qtmobility/qsystemnetworkinfo.html)? > I'm looking forward to get Cell ID etc. information. > > > > I'm quite new with Qt so I hope some of you could provide my a short > example if there is a solution to get that kind of information. > > > > Regards, > > Jukka > > ___ > > SailfishOS.org Devel mailing list > > Lorn Potter > QtSensors/ Connectivity > llornkcor technologies / Jolla Mobile > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Cellular network information
Sorry to interrupt here, but this kind of thing is what i would like to have secure in the future... for any group of apps to run in a different user and have some kind of deny by default access levels, which can still be overrided by user and/or jolla (or packaging) in order for apps not being able to do that, except if they have permission, perhaps dbus is linked with some kind of policykit which could grant or deny such calls... if possible i would urge even if you do not want it in the store to adhere as much as possible to some kind of conventions (preferably also store conventions) I'm sorry to have interrupted, and i also wish to state that i'm not a sailfish dev, nor do i have a device, but i do am fond of security and would prefer for everyone to keep security in mind a bit. > Hi, > It depends on if you want your app in the store or not. > You could use QtDbus to query the connman and ofono interfaces, much like > connman-qt and libqofono to get this information. > > If you don't mind not being in the store, QtSystemInfo's QtNetworkInfo is > on the device, or you could use libconnman-qt and libqofono themselves. > > Hope this helps! > > > On 05/12/2013, at 10:40 PM, Jukka Heikkilä wrote: > >> Hi, >> >> I'd like to get some cellular network information to my app. Is there >> this kind of class like in Harmattan's QSystemNetworkInformation >> (http://harmattan-dev.nokia.com/docs/library/html/qtmobility/qsystemnetworkinfo.html)? >> I'm looking forward to get Cell ID etc. information. >> >> I'm quite new with Qt so I hope some of you could provide my a short >> example if there is a solution to get that kind of information. >> >> Regards, >> Jukka >> ___ >> SailfishOS.org Devel mailing list > > Lorn Potter > QtSensors/ Connectivity > llornkcor technologies / Jolla Mobile > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Cellular network information
Hi, It depends on if you want your app in the store or not. You could use QtDbus to query the connman and ofono interfaces, much like connman-qt and libqofono to get this information. If you don't mind not being in the store, QtSystemInfo's QtNetworkInfo is on the device, or you could use libconnman-qt and libqofono themselves. Hope this helps! On 05/12/2013, at 10:40 PM, Jukka Heikkilä wrote: > Hi, > > I'd like to get some cellular network information to my app. Is there this > kind of class like in Harmattan's QSystemNetworkInformation > (http://harmattan-dev.nokia.com/docs/library/html/qtmobility/qsystemnetworkinfo.html)? > I'm looking forward to get Cell ID etc. information. > > I'm quite new with Qt so I hope some of you could provide my a short example > if there is a solution to get that kind of information. > > Regards, > Jukka > ___ > SailfishOS.org Devel mailing list Lorn Potter QtSensors/ Connectivity llornkcor technologies / Jolla Mobile ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] GB compile
Simply try to build it and then resolve potential problems :) -- Marcin 2013/12/5 Cleber Rodrigues > Allright! I assumed Harbour rules reflected what the (current or future) > SDK would allow. > > Sorry for generating confusion. > > > 2013/12/5 Jonni Rainisto > >> And who says that they cannot be linked? >> >> Harbour intake rules != what developer can do. If intake rules are bad >> then there most likely will be alternative stores available at some point >> for developer mode. >> >> And we are also trying to relax Harbour intake rules in the future, but >> lets see when or if that happens. >> >> re, Jonni >> >> -- >> *From:* devel-boun...@lists.sailfishos.org [ >> devel-boun...@lists.sailfishos.org] on behalf of Cleber Rodrigues [ >> cleber@gmail.com] >> *Sent:* Thursday, December 05, 2013 11:55 AM >> *To:* Sailfish OS Developers >> *Subject:* Re: [SailfishDevel] GB compile >> >> It may not be that simple. For once, Sailfish apps can not be linked >> to qtwidgets (IIRC), and this is probably what that app uses. >> >> A new interface using QML would probably need to be written. >> >> >> 2013/12/4 Randolph >> >>> Hi, can someone give a hint how to compile this encrypted messenger for >>> Sailfish ? >>> http://goldbug.sf.net >>> Regards Randolph >>> >>> ___ >>> SailfishOS.org Devel mailing list >>> >> >> >> ___ >> SailfishOS.org Devel mailing list >> > > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
A style for plain Qt which would display with the native look & feel (compare the unsupported and buggy meegotouch-qt-style) would be great too! -- Marcin 2013/12/5 Filip Kłębczyk > W dniu 05.12.2013 13:30, Sven Putze pisze: > > Hi, >> >> if such an example exists, I could make templates from them. I am sure >> that the folks at Jolla would integrate them ;-) >> > > That's the community spirit! Thanks Sven! > > > Regards, > Filip > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Connecting Jolla device to SDK
Hello, Currently (SDK tagged as 1310) is not capable of doing device deployment. What we are testing right now is a SDK that allows you to create a valid device in Qt Creator and deploy to that directly from Qt Creator's UI. There are couple little quirks still remaining but we're working on them. Hopefully we can push it out really soon. thanks, Jarko From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Seppo Tiainen [seppo.tiai...@gmail.com] Sent: Thursday, December 05, 2013 3:01 PM To: devel@lists.sailfishos.org Subject: [SailfishDevel] Connecting Jolla device to SDK First, is the current Alpha2 QtCreator/SDK capable of connecting to the new Jolla phone through USB for testing apps under development? If yes, there are many parameters (Device type, Username/Password...) that need to be correctly set. Short instructions would be very welcome. I did not succeed yet. Anybody tried? Seppo ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
W dniu 05.12.2013 13:30, Sven Putze pisze: Hi, if such an example exists, I could make templates from them. I am sure that the folks at Jolla would integrate them ;-) That's the community spirit! Thanks Sven! Regards, Filip ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Connecting Jolla device to SDK
Yes, I have been looking into the issue. Out of the box no, you have to manually handle the connectivity part (upload etc), ie deployment out of the box does not work. I could imagine rsync step from within Qt creator is still possible, but attaching to device + debugging might not be as straightforward. best, tortoisedoc On Thu, Dec 5, 2013 at 3:01 PM, Seppo Tiainen wrote: > First, is the current Alpha2 QtCreator/SDK capable of connecting to the > new Jolla phone through USB for testing apps under development? > > If yes, there are many parameters (Device type, Username/Password...) that > need to be correctly set. Short instructions would be very welcome. > > I did not succeed yet. Anybody tried? > > Seppo > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
[SailfishDevel] Connecting Jolla device to SDK
First, is the current Alpha2 QtCreator/SDK capable of connecting to the new Jolla phone through USB for testing apps under development? If yes, there are many parameters (Device type, Username/Password...) that need to be correctly set. Short instructions would be very welcome. I did not succeed yet. Anybody tried? Seppo ___ SailfishOS.org Devel mailing list
[SailfishDevel] Cellular network information
Hi, I'd like to get some cellular network information to my app. Is there this kind of class like in Harmattan's QSystemNetworkInformation ( http://harmattan-dev.nokia.com/docs/library/html/qtmobility/qsystemnetworkinfo.html)? I'm looking forward to get Cell ID etc. information. I'm quite new with Qt so I hope some of you could provide my a short example if there is a solution to get that kind of information. Regards, Jukka ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
Hi, if such an example exists, I could make templates from them. I am sure that the folks at Jolla would integrate them ;-) BR. Sven On 05.12.2013, at 10:44, Filip Kłębczyk wrote: > W dniu 05.12.2013 09:56, Thomas Perl pisze: >> Are we missing code examples of how to integrate C++-based OpenGL rendering >> like QGLWidget (initializeGL, resizeGL and paintGL) with Sailfish Silica QML >> UIs? Would it help you if such examples were available (a simple hello world >> with Silica buttons and a rectangular area where things are rendered with >> OpenGL)? > > Very good idea, even better if there would be appropriate templates in the > SDK like I've stated in previous mail, so there wouldn't be a problem in > searching for those code examples somewhere on the Internets. > > Regards, > Filip > > ___ > SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
Hi Thomas, Thanks. I'll just boil down to your last important remark On 12/05/2013 09:56 AM, Thomas Perl wrote: Are we missing code examples of how to integrate C++-based OpenGL rendering like QGLWidget (initializeGL, resizeGL and paintGL) with Sailfish Silica QML UIs? Would it help you if such examples were available (a simple hello world with Silica buttons and a rectangular area where things are rendered with OpenGL)? Yes, please! In my case -and also others on the list-: C++ driven/controlled and a combination of an openGL window and and a GUI window in one screen. This combination is sometimes necessary when you want to see the GUI interaction result immediately on the openGL window (e.g. [aircraft navigation] input of longitude/latitude values for way points should be visible on the openGL map directly). I know this is not the Sailfish way, but -by exception- it is necessary. Also: I have been struggling over the C++-QML-Sailfish GUI sometime. But I managed to get an app working. It is an example of a C++ controlled app, using 'standard' QML lists, and a 'main' Sailfish GUI, with quite some C++<>QML communication implemented. This might also be useful as an example. see https://github.com/sailfishapps/checklists regards, wim ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
> Are we missing code examples of how to integrate C++-based OpenGL rendering > like QGLWidget (initializeGL, resizeGL and paintGL) with Sailfish Silica QML > UIs? Would it help you if such examples were available (a simple hello world > with Silica buttons and a rectangular area where things are rendered with > OpenGL)? +1 Please do it !!! This kind of example is what I'm looking for, and it would be a great starting point for people coming from qglwidgets :) Em Quinta-feira, 5 de Dezembro de 2013 9:44, Filip Kłębczyk escreveu: W dniu 05.12.2013 09:56, Thomas Perl pisze: > Are we missing code examples of how to integrate C++-based OpenGL rendering > like QGLWidget (initializeGL, resizeGL and paintGL) with Sailfish Silica QML > UIs? Would it help you if such examples were available (a simple hello world > with Silica buttons and a rectangular area where things are rendered with > OpenGL)? Very good idea, even better if there would be appropriate templates in the SDK like I've stated in previous mail, so there wouldn't be a problem in searching for those code examples somewhere on the Internets. Regards, Filip ___ SailfishOS.org Devel mailing list___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] 1310-Alpha installer issue
Hi, On 12/02/2013 07:53 PM, Gabriel Garcia wrote: > So far, so good, except that for some reason QtCreator can't connect > with the VM's - I'll play a bit more and jump on IRC if I can't get > it to run. Did you succeed to connect? I have also this problem with Gentoo. -- evis ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] GB compile
Allright! I assumed Harbour rules reflected what the (current or future) SDK would allow. Sorry for generating confusion. 2013/12/5 Jonni Rainisto > And who says that they cannot be linked? > > Harbour intake rules != what developer can do. If intake rules are bad > then there most likely will be alternative stores available at some point > for developer mode. > > And we are also trying to relax Harbour intake rules in the future, but > lets see when or if that happens. > > re, Jonni > > -- > *From:* devel-boun...@lists.sailfishos.org [ > devel-boun...@lists.sailfishos.org] on behalf of Cleber Rodrigues [ > cleber@gmail.com] > *Sent:* Thursday, December 05, 2013 11:55 AM > *To:* Sailfish OS Developers > *Subject:* Re: [SailfishDevel] GB compile > > It may not be that simple. For once, Sailfish apps can not be linked to > qtwidgets (IIRC), and this is probably what that app uses. > > A new interface using QML would probably need to be written. > > > 2013/12/4 Randolph > >> Hi, can someone give a hint how to compile this encrypted messenger for >> Sailfish ? >> http://goldbug.sf.net >> Regards Randolph >> >> ___ >> SailfishOS.org Devel mailing list >> > > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] GB compile
And who says that they cannot be linked? Harbour intake rules != what developer can do. If intake rules are bad then there most likely will be alternative stores available at some point for developer mode. And we are also trying to relax Harbour intake rules in the future, but lets see when or if that happens. re, Jonni From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Cleber Rodrigues [cleber@gmail.com] Sent: Thursday, December 05, 2013 11:55 AM To: Sailfish OS Developers Subject: Re: [SailfishDevel] GB compile It may not be that simple. For once, Sailfish apps can not be linked to qtwidgets (IIRC), and this is probably what that app uses. A new interface using QML would probably need to be written. 2013/12/4 Randolph mailto:rdohm...@gmail.com>> Hi, can someone give a hint how to compile this encrypted messenger for Sailfish ? http://goldbug.sf.net Regards Randolph ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] GB compile
It may not be that simple. For once, Sailfish apps can not be linked to qtwidgets (IIRC), and this is probably what that app uses. A new interface using QML would probably need to be written. 2013/12/4 Randolph > Hi, can someone give a hint how to compile this encrypted messenger for > Sailfish ? > http://goldbug.sf.net > Regards Randolph > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
W dniu 05.12.2013 09:56, Thomas Perl pisze: Are we missing code examples of how to integrate C++-based OpenGL rendering like QGLWidget (initializeGL, resizeGL and paintGL) with Sailfish Silica QML UIs? Would it help you if such examples were available (a simple hello world with Silica buttons and a rectangular area where things are rendered with OpenGL)? Very good idea, even better if there would be appropriate templates in the SDK like I've stated in previous mail, so there wouldn't be a problem in searching for those code examples somewhere on the Internets. Regards, Filip ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
W dniu 04.12.2013 23:21, Wim de Vries pisze: Hi all, This basically a very strong request to the Sailfish an Qt people. I mean this in positive sense: please don not enforce QML at the cost of C++ on the developers community. At some point default Sailfish application template got simplified to practically one line: return SailfishApp::main(argc, argv); I'm not at all surprised that some people started to think that only pure QML apps are the ones expected. The good solution to these confusion would be providing in the next version of SDK more than one template. Like templates for: * Pure QML app * Mixed C++/QML app * OpenGL Qt app * SDL app * Sailfish Python app etc. Also I'm wondering when the update with correct icon size will finally appear in the SDK. For now people must do workarounds, throwing sailfishapp from CONFIG and other stuff, to properly prepare RPM for publishing. That may really scare new people away and we for sure don't want that, don't we? Regards, Filip ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] opengl again..
Hi, On 05 Dec 2013, at 09:56, Wim de Vries wrote: >> 1) using QML writing C++ items to integrate into the scene graph (see >> http://qt-project.org/doc/qt-5.0/qtquick/qquickitem.html for the base class) >> - this also means you’ll be able to use Silica in your application >> 2) using C++, instantiating a QWindow, and doing all your rendering by >> yourself (ideally using OpenGL ES) - something like >> http://qt-project.org/doc/qt-5.0/qtgui/openglwindow.html > > Does this example run on Sailfish (it's now all QQuickView as mainwin in SF)? Yes, every application should have (from the point of the compositor) one window, and that basically is one fullscreen QQuickView (or QWindow, as QQuickView is subclassed from QWindow). > Very, very important, how do create a second GUI (QML) Window? In Sailfish Silica, you can have multiple “Page” elements which are basically “windows” inside the main window. That’s the native UI paradigm here, not multiple windows. You can use the page stack to push and pop windows (or pop’ing of windows can also happen by the user swiping back or tapping back): https://sailfishos.org/sailfish-silica/qml-sailfishsilica-pagestack.html HTH :) Thomas ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Serious request: please let us use C++!
Hi, On 04 Dec 2013, at 23:21, Wim de Vries wrote: > I mean this in positive sense: please don not enforce QML at the cost of C++ > on the developers community. > First, C(++) is THE language for openGL. Actually the OpenGL API is specified in C. Of course, as you can call C API functions from C++, you can also write C++ applications using the OpenGL API. I’d argue that “THE” language for OpenGL is GLSL, i.e. the C-lookalike language that you use to write shaders that get compiled by the drivers and uploaded to the GPU to be run there. Of course, you need another language to actually call OpenGL API functions. But C++ is not in any way “more” the language than e.g. Java[1] or JavaScript[2] is. [1] http://developer.android.com/reference/android/opengl/GLES20.html [2] http://www.khronos.org/webgl/ > We want to program shaders and heavy calculations (C++). No problem, you can even write and use shaders directly from QML: http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-shadereffect.html Of course, this is mostly for doing fragment shaders on top of some QML 2D content, but my point is: Shaders have as such nothing to do with C++. > Qt used to be well suited for this, offering a Q(GL)Widget set that enabled a > nice 'stage' for OpenGL and also a nice GUI for the rest of app. A QWindow is basically the same as a QGLWidget without the actual overhead of the QWidgets library. In fact, it even gives you more control of the rendering than the QGLWidget does. Again, here’s the link to an example: http://qt-project.org/doc/qt-5.0/qtgui/openglwindow.html We do even have an example with RPM packaging and everything ready to go: https://github.com/mer-qa/qt5-opengles2-test The only confusing thing might be that you don’t have convenience callbacks like initializeGL(), resizeGL() and paintGL(), however, if you really depend on those, these are quickly and easily to write on top of the QWindow API. > Now we have go through Qpainters, QQuickitems (oh no, that's black listed > also). > Our QWidgets are useless now. The reason for this is that the drawing model used by QWidgets and QPainter come from a time when rendering was done using the CPU, and they are optimized in this way. On mobile devices, both CPU and GPU are limited (compared to Desktop machines), so for rendering, it’s important to use the GPU as much as possible for rendering. Combined with Z-buffering and sorting, this might allow the engine (such as the Qt Scene Graph renderer) to avoid overdraw and cull as much as possible - the most efficient code is everything that you actually don’t run (or something like that..). > We are enforced to do this in declarative QML. Nobody forces you to. You can also do pure OpenGL rendering on a QWindow and skip QML completely. Or combine QML with custom OpenGL rendering. > So, how do I simply calculate 1+1 in QML? It’s JavaScript, so the expression “1+1” (without the quotes) will calculate it in QML. > Large floating point arrays for my vertices? Put them into VBOs on the C++ side. > Malloc for images? Ideally allocate a texture on the GPU and render to it using OpenGL FBOs instead of allocating main memory, rendering in software and then uploading to the GPU (it will end up in GPU memory at some point, anyway, and even if it’s just for final composition in Wayland). > Reading buffers from serial devices? Again, just use normal C/C++ APIs for that and expose it to the QML world (if you need to have that data available) via context properties[1]. [1] http://qt-project.org/doc/qt-5.0/qtqml/qtqml-cppintegration-contextproperties.html > So please, make the Sailfish GUI accessible via C++ (like QWidgets). > As it is now, I myself, will not be able to submit my (open source) aircraft > navigation app for Sailfish. > I am sure that a lot of Meego/maemo/Symbian developers will have the same > problem. > Google has been arrogant with their JAVA enforcement, now they are repairing > it by enabling C++ via the NDK. > Please do not make the same mistake. You are free to use C++-only OpenGL rendering, and it will be fine, you just will not be able to use the Sailfish Silica UI components (for native look’n’feel). You are free to use QML-only UIs and make full use of the Sailfish Silica UI components. You are also free to combine both the QML Sailfish Silica UI components and native OpenGL rendering to do custom drawing. And if you really, really want to, you can render all your stuff with any library you want in software (=on the CPU) to a RGB/RGBA buffer in memory and provide that to QML in the form of an image provider. Don’t expect high frame rates this way, but it /does/ work and provides full access to every pixel that gets drawn with the advantage that you can still use all the goodies of QML (yes, it takes some time to get used to, but once you got it, it’s great). Here’s an example where we render the mandelbrot set (!) on the CPU (!!) in Python (!!!) and
Re: [SailfishDevel] opengl again..
Thanks. 1) using QML writing C++ items to integrate into the scene graph (see http://qt-project.org/doc/qt-5.0/qtquick/qquickitem.html for the base class) - this also means you'll be able to use Silica in your application 2) using C++, instantiating a QWindow, and doing all your rendering by yourself (ideally using OpenGL ES) - something like http://qt-project.org/doc/qt-5.0/qtgui/openglwindow.html Does this example run on Sailfish (it's now all QQuickView as mainwin in SF)? Very, very important, how do create a second GUI (QML) Window? 3) other, as-yet-to-be-finalised routes like doing *everything* yourself, using SDL, etc. So it seems that only QML apps are supported, but I have no clue how to add a QWindow in a QML app. There's an example in QtCreator "Scene Graph - OpenGL under QML" but they use QQuickItem, for OpenGL, so I still don't have a clue how to use OpenGL in a QML app. Your QML application has a C++ entry point (though if you're using something like qmlscene... you'll need to create such an entry point yourself) with your 'main' function. You can create a QWindow in there, and show it. You can hook into QML using Q_INVOKABLE methods to show it based on a clicked action on a Silica button, etc, etc, etc. I'd need more information to be able to really provide useful help here :) Regards João de Deus BR, Robin ___ SailfishOS.org Devel mailing list regards wim ___ SailfishOS.org Devel mailing list
