在Android应用嵌入式铬或Webkit内核 [英] Embedded Chromium or Webkit in Android app

查看:144
本文介绍了在Android应用嵌入式铬或Webkit内核的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有关我们的Andr​​oid应用程序,我们希望我们嵌入自己的浏览器/渲染引擎。对此最有可能的候选人,是的Webkit / 我们正在寻找类似的WebView 的东西,本质上,而是通过一个浏览器的支持(版本),我们控制。

For our Android app, we would like to embed our own browser/rendering engine. The most likely candidate for this, is Webkit/Chromium. We are looking for something similar to WebView, essentially, but backed by a browser (version) that we control.

重要我们的应用程序的部分包括嵌入在视图(由应用程序本身提供)网页片段。我们尝试这样做尽可能透明地(从视觉/用户体验的角度来看)。到目前为止,我们一直使用的WebView 的,这和该工程的大部分。除非它没有。

Significant parts of our app consist of web page fragments embedded in the view (served by the app itself). We try to do this as transparently as possible (from a visual/user experience standpoint). So far, we have been using WebView for this and that works for the most part. Except when it doesn't.

一些手机厂商已经不幸决定在这里和那里调整标准的Andr​​oid浏览器。在某些情况下,这打破我们的应用程序或使我们嵌入一个网页的更为明显的事实。

Some phone vendors have unfortunately decided to tweak the standard Android browser here and there. In some cases, this breaks our app or makes the fact the we embed a web page more noticeable.

我们希望有一个组件类似于的WebView 但如果我们控制的是什么版本的Webkit的/铬(或一些其它渲染引擎)的使用情况。它不一定必须是最新和最伟大的版本。我们可以让我们的应用程序的工作更重要的持续的跨越尽可能多的Andr​​oid设备成为可能。

We'd like to have a component similar to WebView but where we control what version of Webkit/Chromium (or some other rendering engine) is being used. It wouldn't necessarily have to be the latest and greatest version. It is more important that we can get our app to work consistently across as many Android devices as possible.

我们的研究到目前为止还没有止跌回升任何用处。我们已经发现了三具企图港口的Webkit到 NDK (裸露的Webkit为Android端口使用的功能在NDK不可用,因此不应用程序开发者):

Our research so far has not turned up anything useful. We have found three dead attempts to port Webkit to NDK (the bare Webkit for Android port uses functionality not available in the NDK and thus not to app developers):

  • Webkit Android port by Company 100 (no updates for over two years)
  • mogo-browser (their last revision was to delete all source code)
  • NDK Webkit (officially abandoned by its author)

看好计算器,我们也发现了一些类似的问题,其中大部分得到解决所指向的WebView(我们已经做到这一点,它的不够好)

Looking on StackOverflow, we have also found a number of similar questions, most of which being solved by pointing to WebView (we already do that, and it's not good enough)

  • Webkit component for Android
  • Embed basic WebKit + V8 in my app
  • Embedding a newer version of WebKit with Android app

我们目前正在调查铬为Android (或其部分)是否能变成了我们的应用程序可以使用图书馆。有没有其他人这样做呢?

We are currently investigating whether Chromium for Android (or parts of it) can be turned into a library that our app could use. Has anyone else done this?

在看看在GitHub上(接受的答案)的chromeview项目后,我们决定,我们宁愿等待谷歌发布一款Chrome浏览器为基础的WebView未来的Andr​​oid设备。铬渲染引擎结果是相当大的(〜40MB),而不会留下多少空间实际应用:(

After having a look at the chromeview project on GitHub (accepted answer), we decided that we'd rather wait for Google to release a Chrome-based WebView on future Android devices. The Chromium rendering engine turns out to be fairly large (~40MB), which doesn't leave much space for the actual app :(

推荐答案

pwnall / chromeview·GitHub上 https://github.com/pwnall/chromeview

pwnall/chromeview · GitHub https://github.com/pwnall/chromeview

ChormeView就像Android的WebView功能,而是由最新的铬code支持。

ChormeView works like Android's WebView, but is backed by the latest Chromium code.

这篇关于在Android应用嵌入式铬或Webkit内核的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆