Active Topics
-
Maemo repository (4)
to Community by teroyk - 11 hrs, 31 mins ago -
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 1 day, 18 hrs ago -
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 2 days, 2 hrs ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 5 days, 11 hrs ago - more...
 |
nokiabot |
2014-07-29
, 14:21
|
|
Posts: 1,974 |
Thanked: 1,834 times |
Joined on Mar 2013
@ india
|
#161
|
Is this depriciated in favour of qml browser 
|
|
2014-07-30
, 07:01
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#162
|
its on hold.
regardless of if you choose webkit, as in qml-browser, or embedlite as a backend, both are AFAIK no longer supporting qt4. When embedlite dropped qt4, marmistrz and myself looked at alternatives but they all needed gtk3 or qt5 to be actively maintained upstream. embedlite could support gtk2 but it would need effort on our part to bring up to date and maintain the code.
What marxian has done in terms of UI using qt-components-hildon is where the project was planning on going. we were using widgets for the UI but as I'd modified a lot of the existing backend to be more like sailfish-browser the plan is to switch from widgets to qml based UI. obviously, any reference to silica would be replaced.
until there is better support and more uptake for qt5 on maemo, i feel it's not worth pushing forward. as ram is at a premium on device, why load gtk, qt4 and qt5? i'm currently playing with a debian jessie image, so there is the possibility that if i get qt5 with maemo changes installed I might be able to move forward again.
regardless of if you choose webkit, as in qml-browser, or embedlite as a backend, both are AFAIK no longer supporting qt4. When embedlite dropped qt4, marmistrz and myself looked at alternatives but they all needed gtk3 or qt5 to be actively maintained upstream. embedlite could support gtk2 but it would need effort on our part to bring up to date and maintain the code.
What marxian has done in terms of UI using qt-components-hildon is where the project was planning on going. we were using widgets for the UI but as I'd modified a lot of the existing backend to be more like sailfish-browser the plan is to switch from widgets to qml based UI. obviously, any reference to silica would be replaced.
until there is better support and more uptake for qt5 on maemo, i feel it's not worth pushing forward. as ram is at a premium on device, why load gtk, qt4 and qt5? i'm currently playing with a debian jessie image, so there is the possibility that if i get qt5 with maemo changes installed I might be able to move forward again.
| The Following 4 Users Say Thank You to Android_808 For This Useful Post: | ||
|
|
2014-08-02
, 18:36
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#163
|
Yes, it's on hold.
We might simply go for QtQuick Controls and check whether it works approperiately, but it's a big risk. We might do a lot of work and then find out that the performance sucks. We'd better wait until hildonizing QtQuick Controls is better tested. The last time I checked it the examples failed to even work. Besides, I focused on my project or two and some math
The RAM used might be a drawback but it's something we can't avoid. There'll still be some apps using it and it's worth loading it if we can get a browser which handles most mobile pages.
WebKit is simply different. QML Browser might be a great base for future development and a temporary solution for now but as WebKit's no longer developed (even for Qt5) it might be a dead end someday. Even more if we use Qt4 Webkit.
We might simply go for QtQuick Controls and check whether it works approperiately, but it's a big risk. We might do a lot of work and then find out that the performance sucks. We'd better wait until hildonizing QtQuick Controls is better tested. The last time I checked it the examples failed to even work. Besides, I focused on my project or two and some math
The RAM used might be a drawback but it's something we can't avoid. There'll still be some apps using it and it's worth loading it if we can get a browser which handles most mobile pages.
WebKit is simply different. QML Browser might be a great base for future development and a temporary solution for now but as WebKit's no longer developed (even for Qt5) it might be a dead end someday. Even more if we use Qt4 Webkit.
| The Following 3 Users Say Thank You to marmistrz For This Useful Post: | ||
|
|
2014-08-02
, 20:59
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#164
|
When you say webkit, do you just mean webkit1? http://qt-project.org/doc/qt-5/qtwebkit-index.html
| The Following User Says Thank You to Android_808 For This Useful Post: | ||
 |
|
2014-08-02
, 21:24
|
|
Posts: 257 |
Thanked: 2,053 times |
Joined on Sep 2010
@ Warsaw, Poland
|
#165
|
Originally Posted by marmistrz
WebKit is still developed. However, Qt5 starting with 5.3 seems to move towards QWebEngine powered by Blink/Chromium.
WebKit is simply different. QML Browser might be a great base for future development and a temporary solution for now but as WebKit's no longer developed (even for Qt5) it might be a dead end someday. Even more if we use Qt4 Webkit.
http://qt-project.org/wiki/QtWebEngi...ngFromQtWebKit
__________________
Sebastian Krzyszkowiak - https://dosowisko.net/
Long term Openmoko supporter. Owner of two Neo Freerunners, a few N900s and some others too.
Future owner of the Neo900
Sebastian Krzyszkowiak - https://dosowisko.net/
Long term Openmoko supporter. Owner of two Neo Freerunners, a few N900s and some others too.
Future owner of the Neo900
| The Following User Says Thank You to dos1 For This Useful Post: | ||
|
|
2014-08-03
, 18:59
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#166
|
I meant this: https://lists.sailfishos.org/piperma...er/001435.html
Last edited by marmistrz; 2014-08-04 at 17:03.
__________________
If you want to support my work, you can donate by PayPal or Flattr
Projects no longer actively developed: here
If you want to support my work, you can donate by PayPal or Flattr
Projects no longer actively developed: here
Last edited by marmistrz; 2014-08-04 at 17:03.
|
|
2014-08-04
, 16:41
|
|
Posts: 2,292 |
Thanked: 4,135 times |
Joined on Apr 2010
@ UK
|
#167
|
This is worth a read for anyone working on Qt5 and Maemo
https://codereview.qt-project.org/#/c/90909/
Edit:-
Sorry, I think this has already been mentioned in the Qt5 on Maemo Thread...
http://talk.maemo.org/showthread.php?t=84782
Last edited by sixwheeledbeast; 2014-08-04 at 16:48.
https://codereview.qt-project.org/#/c/90909/
Edit:-
Sorry, I think this has already been mentioned in the Qt5 on Maemo Thread...
http://talk.maemo.org/showthread.php?t=84782
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Last edited by sixwheeledbeast; 2014-08-04 at 16:48.
|
|
2014-08-04
, 16:46
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#168
|
Everything apart from src/plugins/platforms/xcb is for sure MeeGo, so it's not Maemo5 related. xcb - I don't know.
|
|
2014-08-04
, 17:01
|
|
Posts: 805 |
Thanked: 1,605 times |
Joined on Feb 2010
@ Gdynia, Poland
|
#169
|
Originally Posted by marmistrz
link gives 404 for me
I meant this: https://lists.sailfishos.org/piperma...ovember/001435
 |
| Tags |
| gecko browser, maemo 5 |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 22:27.