Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 2 days, 13 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 4 days, 10 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 5 days, 7 hrs ago - more...
|
2019-11-01
, 09:01
|
|
Posts: 735 |
Thanked: 1,054 times |
Joined on Jun 2010
|
#12
|
Originally Posted by atlochowski
is there any point adopting 5.9 now?
it is posponed to next year
the joy of lts is ongoing support, and at this point even 5.12 lts is getting long in the tooth!
----------------------------------------------
on a separate note i'm glad the browser got some fixes for twitter.
the change is important for apps like quickditt and tweetian are not to be rendered pointless, because the transfer to a browser function leaves the user with a borked experience.
two solutions:
1. fix the damned browser
2. allow user to select the preferred browser to transfer web calls from native apps
right now tweetian and quickditt remain unused - choosing firefox instead - because i'm done with being transferred to the broken native browser. it simply isn't good enough.
but its inadequacy is spoiling the SFOS experience with native apps, which is a real shame.
Last edited by Jedibeeftrix; 2019-11-01 at 09:08.
|
|
2019-11-02
, 12:53
|
|
Posts: 207 |
Thanked: 759 times |
Joined on Dec 2014
@ Poland
|
#13
|
Originally Posted by Jedibeeftrix
Just Jolla had plans to update QT version this year but they posponetd it.
is there any point adopting 5.9 now?
the joy of lts is ongoing support, and at this point even 5.12 lts is getting long in the tooth!
----------------------------------------------
on a separate note i'm glad the browser got some fixes for twitter.
the change is important for apps like quickditt and tweetian are not to be rendered pointless, because the transfer to a browser function leaves the user with a borked experience.
two solutions:
1. fix the damned browser
2. allow user to select the preferred browser to transfer web calls from native apps
right now tweetian and quickditt remain unused - choosing firefox instead - because i'm done with being transferred to the broken native browser. it simply isn't good enough.
but its inadequacy is spoiling the SFOS experience with native apps, which is a real shame.
It's hard to say Jolla fixed browser for twitter. It is more workaround then fix. But for us it's good that we can open twitter in browser.
Last edited by atlochowski; 2019-11-02 at 15:19.
|
|
2019-11-02
, 14:20
|
|
Posts: 281 |
Thanked: 679 times |
Joined on Feb 2010
|
#14
|
Originally Posted by atlochowski
Just to mention: For me the twitter stuff works again for some weeks with 3.1.0.12... This is no 3.2.0.12 thingie.
It's hard to say Jolla fixed browser for twitter. It is more workaround then fix. But for use it's good that we can open twitter in browser.
 |
|
2019-11-03
, 08:53
|
|
Posts: 764 |
Thanked: 2,888 times |
Joined on Jun 2014
|
#16
|
Is it just me or is the TOHKBD no longer working? I haven't used mine for some time so I don't know if this is a new thing or not. The keyboard doesn't get recognised when attached.
 |
|
2019-11-03
, 09:19
|
|
Posts: 1,195 |
Thanked: 2,708 times |
Joined on Jan 2010
@ Hanoi
|
#17
|
Originally Posted by Jedibeeftrix
If I was the head of Jolla I'd say: dump the native browser. As a customer I surely say, start doing/improving what I need and that is not the native browser.
is there any point adopting 5.9 now?
the joy of lts is ongoing support, and at this point even 5.12 lts is getting long in the tooth!
----------------------------------------------
on a separate note i'm glad the browser got some fixes for twitter.
the change is important for apps like quickditt and tweetian are not to be rendered pointless, because the transfer to a browser function leaves the user with a borked experience.
two solutions:
1. fix the damned browser
2. allow user to select the preferred browser to transfer web calls from native apps
right now tweetian and quickditt remain unused - choosing firefox instead - because i'm done with being transferred to the broken native browser. it simply isn't good enough.
but its inadequacy is spoiling the SFOS experience with native apps, which is a real shame.
Fix SIP and other to be integrated primary communication protocols instead , then hunt for partnerships with Mozilla if not other browser developers. Hire a software wizard / geek that can port Fennec to Sailfish OS. I am sure if nicely asked there are people who would do this for free even.
Why do we need a 50 head development team try to compete browser wise with Mozilla?
How long did it take to have Fennec "running" if always out of RAM on N900? A couple of weeks, months? Why this hasn't happened for Sailifsh?
| The Following 8 Users Say Thank You to ste-phan For This Useful Post: | ||
 |
|
2019-11-03
, 15:02
|
|
Posts: 304 |
Thanked: 1,246 times |
Joined on Aug 2015
|
#18
|
Originally Posted by nthn
The same here: Tried in August with SFOS 2.2.1.
Is it just me or is the TOHKBD no longer working? I haven't used mine for some time so I don't know if this is a new thing or not. The keyboard doesn't get recognised when attached.
Did not take the time to analyse why, though.
| The Following 4 Users Say Thank You to olf For This Useful Post: | ||
|
|
2019-11-03
, 18:33
|
|
Posts: 1,548 |
Thanked: 7,510 times |
Joined on Apr 2010
@ Czech Republic
|
#19
|
Originally Posted by ste-phan
I don't think you can really do that - you simply need a native browser to be always available, even for stuff like captive portals on some WiFi hotspots. The Android emulation layer is (optionally) installed on first start, so you might need a native browser, so you can authenticate with with you hotspot to download Android support & install an Android browser.
If I was the head of Jolla I'd say: dump the native browser.
Also in some cases Android emulation support is simply not available so an Android browser is out of the question:
- community ports
- Russian corporate devices reportedly don't have Android emulation by design
- cases where the user opted to no use the Android emulation layer
Also, even if the Android emulation layer is available, it is quickly approaching obsolescence on all the older devices & Xperia X due to only suportiong Android 4.4.x API level, so it's possible up to date Android browsers will no longer run on it.
Originally Posted by ste-phan
Well, the current default Sailfish Browser already uses the Firefox rendering core (Gecko) and there is actually not many alternatives:
As a customer I surely say, start doing/improving what I need and that is not the native browser.
Fix SIP and other to be integrated primary communication protocols instead , then hunt for partnerships with Mozilla if not other browser developers. Hire a software wizard / geek that can port Fennec to Sailfish OS. I am sure if nicely asked there are people who would do this for free even.
- WebKit is not in much of a good state, QtWebKit as well
- QtWebEngine is hard to build even on Fedora due to horrendous amount of bundling & outdated GCC
- Chromium - again horrendous amount of bundling, outdated GCC & not sure about Wayland support
- Firefox - only recently added support for running natively on Wayland (in Fedora 31 released a couple days ago), might be hard to build due to outdated GCC
So older Firefox core is actually maybe the only thing usable in current circumstances.
Originally Posted by ste-phan
This is not correct - Jolla is not writing their own browser from scratch. The default Sailfish OS browser is just a thin layer that uses the Firefox 45 Gecko rendering core for all the actual website rendering.
Why do we need a 50 head development team try to compete browser wise with Mozilla?
AFAIK, the main issue why the browser if lagging behind is twofold:
1) Gecko does not really have a stable embedding interface, so for each Gecko upgrade, sizeable embedding patches need to be adjusted to all the code changes in the private APIs it has to use in the new Gecko version. This can be a significant endeavor.
I've talked to someone from the Mozilla community and apparently the new Firefox Preview on Android uses some new Gecko embedding API & can be used to provide a generic Gecko based web view to other Android applications. This could be a boon for Sailfish OS as well - if gecko needs to support embedding for Android, it could be possible to use the same API for embedding on Sailfish OS as well.
Also I seem to remember someone from Mozilla attending the Fosdem Sailfish OS meetup & discussing Gecko embedding improvements. So I guess things could improve in this case and hopefully make Gecko upgrades for the native Sailfish OS much less painful.
2) GCC & the overall library stack is currently too outdated to build modern versions of Gecko. IIRC glibc version has been bumped a bit recently, but we will likely be still stuck until GCC is finally upgraded as well.
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
| The Following 16 Users Say Thank You to MartinK For This Useful Post: | ||
Amboss, atlochowski, balta, cy8aer, juiceme, klinglerware, lal, ljo, mosen, P@t, pacman, peterleinchen, pichlo, rcolistete, santeira, wolke | ||
|
|
2019-11-03
, 20:54
|
|
Posts: 764 |
Thanked: 2,888 times |
Joined on Jun 2014
|
#20
|
Originally Posted by olf
Problem solved: for some reason, at some point, the systemd service for the TOHKBD was deleted. Reinstalling the TOHKBD ambience fixed it.
The same here: Tried in August with SFOS 2.2.1.
Did not take the time to analyse why, though.
| The Following 9 Users Say Thank You to nthn For This Useful Post: | ||
Русский военный корабль, иди нахуй!