Re: Sailfish OS 3.2 for early Adaptor
Quote:
|
Re: Sailfish OS 3.2 for early Adaptor
Quote:
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. |
Re: Sailfish OS 3.2 for early Adaptor
Quote:
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. |
Re: Sailfish OS 3.2 for early Adaptor
Quote:
|
Re: Sailfish OS 3.2 for early Adaptor
so dead os:(
|
Re: Sailfish OS 3.2 for early Adaptor
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.
|
Re: Sailfish OS 3.2 for early Adaptor
Quote:
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? |
Re: Sailfish OS 3.2 for early Adaptor
Quote:
Did not take the time to analyse why, though. |
Re: Sailfish OS 3.2 for early Adaptor
Quote:
Also in some cases Android emulation support is simply not available so an Android browser is out of the question:
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. Quote:
So older Firefox core is actually maybe the only thing usable in current circumstances. Quote:
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. |
Re: Sailfish OS 3.2 for early Adaptor
Quote:
|
All times are GMT. The time now is 15:30. |
vBulletin® Version 3.8.8