Well there were two available starting point, Firefox or Chromium. They
picked Chromium. I am not sure how easy that decision was, but it doesn't
strike me that Firefox/gecko would have been faster to wrap in a QML UI
than Chromium/webkit
On Sunday, April 24, 2016, Krzysztof Tataradziński
wrote:
Bear in mind that Firefox for Android is... already ported for Android.
Native Firefox for Linux would require more power so doing own browser
on chromium was more suitable. (I believe its some kind of based on
Chromium)
Z poważaniem,
Filip Dorosz
W dniu 24.04.2016 o 14:14, Chris Croome pisze
Hi
On Sun 24-Apr-2016 at 01:26:16PM +0200, Filip Dorosz
wrote:
>
> Firefox is quite good example, it is heavy and while
> porting it would be possible I believe it would not
> suite small screen, would drain battery quickly etc.
I have two Nexus 4's, one running Cyanogenmod and one
running Ubunt
Hi.
I believe some apps would be to resource hungry for limited abilities of
mobile world. Firefox is quite good example, it is heavy and while
porting it would be possible I believe it would not suite small screen,
would drain battery quickly etc.
Regards,
Filip Dorosz.
W dniu 24.04.2016 o
Hello,
For some time bothers me one topic. I'm not a programmer, so maybe answer
to my question is obvious. In UT we have browser app created by Canonical
team, yes? It's done almost from scratch and providing basic features. When
UT was starting, why programmers team doesn't decide to, instead of
5 matches
Mail list logo
