PrestoXen / openopera-issues

Issue tracker for OpenOpera
26 stars 0 forks source link

FEATURE_EMBROWSER #20

Open pabloko opened 4 years ago

pabloko commented 4 years ago

Hello, did somebody tried to add emBrowser feature? id like to integrate opera on my app to test hybrid tv apps on my lab, ive managed to compile opera without FEATURE_EMBROWSER, but it seems some files are missing.

Affecting files are from OUniAnsi (Opera Unicode Ansi conversion layer) can be found on OUniAnsi.dll on internet, and also missing softcore module. emBrowser exposes some methods like WidgetInitLibrary that allow embedding with api.

Zero3K commented 4 years ago

Any news regarding this issue?

pabloko commented 4 years ago

I didnt had much time for this since i had to build a NPAPI component for my tests, but tried to reverse what is missing from binaries obtained from Adobe CS4 (mainly adobe bridge) they come packed with ASpack2.12 and dint had a chance to unpack them and continue working on it. Its still interesting to me since im seeing HUGE usage of presto 8-12 on most cheap TVs still even sold last year (hisense/toshiba/telefunken/tcl... wtf) im doing HbbTV apps, testing on this platform is mandatory for coverage, and embrowser would be nice for embedding it on our test suite

cynthia commented 3 years ago

Barking up the wrong tree - FEATURE_EMBROWSER is not what you think it is.

You won't be able to get the same results as what you see on a TV, as it is built under a different core profile - plus all of the HbbTV stuff is a separate codebase and I'm pretty sure that's missing. (I can't say for sure as I have steered clear from the leak, but I'm pretty sure that what is out there is the desktop code based on what I read from the news articles.)

I have no idea if you can still get a hold of builds with the company now split up (the TV part is now called Vewd) but the closest thing you can get is a special build called "Opera TV Emulator" if you can find it.

pabloko commented 3 years ago

Hi @cynthia, yes, my point on using emBrowser is just the intended usage, embed a view in my own host app, then the HbbTV stuff is handled by an NPP plugin i've wrote covering the 1.1.1 spec that i use in another browsers too. So i know its possible ill have different results, but im fairly near because presto behaves similarly on both codebases.

I could download from archive.org the "Opera TV Emulator" virtual machine and planned to reverse a bit the hbbtv features from there. Also got a "Opera Mobile Emulator" wich found interesting and planned to reverse the emBrowser feature, since the Adobe files seem to have been heavily customised...

Ive spent few time on this but moved on since we just used the npp plugin on the browser itself and i lost the interest for such cosmetic issue, but i wont call it closed as presto could be a formidable GUI compositor even for today's standards.

You guys did an amazing job ;)