Static pages modality until Opera Mini 13
-
hybris2 last edited by
Hi. What is the name of the protocol used by the Opera Mini browser up to version 13 in which the pages are static and do not automatically update in real time? for example, the Facebook home is made up of a series of static pages connected to each other by links to click or any already loaded page must be manually updated in order to be reloaded. In later versions this disappeared.
Thank you! -
tao102 last edited by
Hmm, Opera Mini 13 was quite a long time ago!
I was going to say that around the time of Opera 13, the layout engine shifted from Opera's proprietary "Presto" engine to Google's "Blink" engine. And the layout engine in Mini likely shifted as well.
https://en.wikipedia.org/wiki/History_of_the_Opera_web_browser
A number of years ago I noticed a remarkable difference when changing from Mini on my Symbian phone to Mini on Android. But according to
https://en.wikipedia.org/wiki/Opera_Mini
if it can be believed, Mini has continued on with Presto.
Being unable to go back and look at that Facebook code, I'd guess that whatever issues you were having, I don't think it was anything as blunt as a major missing feature, but something more akin to Mini's poor Javascript support, a server Javascript timeout, etc. that Opera (or Facebook...there is a Mini developer's guide) fixed over time.
-
hybris2 last edited by
Do you think it is possible to still use this engine on another modern browser?
I think it wasn't bad at all, at least for this navigation function on Facebook...@tao102 said in Static pages modality until Opera Mini 13:
Hmm, Opera Mini 13 was quite a long time ago!
I was going to say that around the time of Opera 13, the layout engine shifted from Opera's proprietary "Presto" engine to Google's "Blink" engine. And the layout engine in Mini likely shifted as well.
https://en.wikipedia.org/wiki/History_of_the_Opera_web_browser
A number of years ago I noticed a remarkable difference when changing from Mini on my Symbian phone to Mini on Android. But according to
https://en.wikipedia.org/wiki/Opera_Mini
if it can be believed, Mini has continued on with Presto.
Being unable to go back and look at that Facebook code, I'd guess that whatever issues you were having, I don't think it was anything as blunt as a major missing feature, but something more akin to Mini's poor Javascript support, a server Javascript timeout, etc. that Opera (or Facebook...there is a Mini developer's guide) fixed over time.
-
tao102 last edited by
With Mini, I have my doubts. The functionality is split between the client and server, and so likely won't be easily adapted. It's not like making a new port of WebKit. On the other hand, if you had the Mini client/server source and nothing else, it would be easier than starting from scratch.
But this is all theoretical because the Mini code is proprietary and secret.
Incidentally, I was rather happy when Opera abandoned Presto for desktop. For me, it seemed to crash a lot.
