Hey,
On Wed, Mar 06, 2019 at 02:07:31PM -0800, Jay Kamat wrote:
>
> Florian Bruhin writes:
>
> > - Chromium embedded framework (CEF) [1][2] - has Python bindings[3] with
> > Qt integration[4], so the only one which would be reasonably possible
> > to integrate with qutebrowser. However, I do
Florian Bruhin writes:
> - Chromium embedded framework (CEF) [1][2] - has Python bindings[3] with
> Qt integration[4], so the only one which would be reasonably possible
> to integrate with qutebrowser. However, I don't see much benefit over
> QtWebEngine, seeing that both are based on Chr
Hi,
On Wed, Mar 06, 2019 at 01:29:03PM -0300, Javier Ayres wrote:
> I would love to see servo working with qutebrowser (once it is stable,
> which I think is far from) or even gecko
Gecko is pretty much unusable outside of Firefox AFAIK - I'm not aware
of any projects using it as a standalone eng
Thanks for the responses guys. It makes a lot of sense that you don't have
a definitive answer (although your expectations seem to go off in opposite
directions :D) given that this highly depends on the availability of
external projects.
I would love to see servo working with qutebrowser (once it
Hi,
On Tue, Mar 05, 2019 at 10:58:46PM -0300, Javier Ayres wrote:
> With the ongoing work happening as part of the research project and
> the idea of dropping support for QtWebKit, I'm wondering what is the
> plan for the future of qutebrowser regarding the support of multiple
> web engines. Are y
Javier Ayres writes:
> With the ongoing work happening as part of the research project and
> the idea of dropping support for QtWebKit, I'm wondering what is the
> plan for the future of qutebrowser regarding the support of multiple
> web engines.
Most likely, the abstract base classes will con
