If I recall correctly, Emdek said that most of the things that could be taken from e.g. Qupzilla are now already standard Qt 5.2 features. But yeah, it sounds to me like e.g. its speed dial might be worth investigating.
The Solutor, it's not always possible to simply borrow some code (licenses are compatible, so it's not a problem), but for sure it could be source of inspiration how some stuff could be done, kind of reference implementation. ;-)
The biggest difference is that QupZilla is focused on single rendering engine (currently QtWebKit, most probably moving to QtWebEngine in future) while Otter aims to support multiple backends (basic support for Gecko should be fairly easy to do using Qt bindings for mozembed).
Otter has already a subset of the opera features, Qupzilla has ha different subset, Opium has another subset, Firefox (with a ton of extensions) can be somewhat "Operized", but none of them is a real replacement.So my hope is that the focus will not be lost during Otter's development.
The Solutor, in worst case not all features will be available in each backend. ;-)
Page created in 0.050 seconds with 39 queries.