It’s been just a little over a year since the mystical Blue Systems started sponsoring development of ReKonq. Blue Systems is second only to the KDE e.V. in platform investment, sponsoring not only numerous core applications, but multiple distributions as well. ReKonq has come a long way since 0.9.2 (May 2012) and with the help of Blue Systems developer Adjam, it is taking baby-steps towards Chrome Extension support.
Here is what he has to say about his work so far:
- we can manage chrome extensions (I just copied examples from here): we can recognize unpacked extensions, install, enable/disable. (oops.. uninstall/delete missing. Adding next days..)
- we can interpret (a bit) the version 2 manifest.json inside
- we can manage browse actions
- we can manage page actions
- we can open popups
So, the first easy step is done. Now what to really say we are supporting chrome extensions? Here is my todo list:
- support chrome object and (a subset of) its API (very long task)
- support the callback mechanism (really hard, this is the trick missing to say we’ll reach one day our goal)
- implement a way to retrieve extensions (support chrome extensions site? seems problematic. Add a ghns layer? Should do the trick. Probably…)
- ehm… port/implement extensions
Boon or bust?
It’s unclear to us how many KDE users prefer ReKonq over Firefox or Chrome but I would assume that it’s not an army. That said, ReKonq does have a very compelling ‘web-app’ creation tool that supplements Firefox & Chrome quite nicely! Tools like Google Keep work great in ReKonq as a stand-a-lone web app that iconifies to your taskbar. At the same time, users of tools like Feedly –the ultra-popular Google Reader replacement– can’t take advantage of ReKonq powerful web app wrapper because it requires an extension to be installed in either Firefox or Chrome. Feedly even leaves Internet Explorer users out in the cold with their model!