[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Notes from Sprint - Plasma Browser Integration
From:       David Edmundson <david () davidedmundson ! co ! uk>
Date:       2018-04-30 10:37:22
Message-ID: CAGeFrHA462OoP8RqUwp2qpzG8M9kxbt2vcYBQS9yxNxqn0is7g () mail ! gmail ! com
[Download RAW message or body]

Plasma Browser Integration has a host part and a client (chrome/firefox
extension) part. The host must be installed by distros,

The plan of action we've agreed upon is that we (by default) won't install
the client part. We'll encourage distros to install the host part by
default.

The host part will also ship a mechanism that will show a non-invasive
popup when firefox/chrome is launched with a link to the relevant browser
store.

We also have an agreed upon git-tagging mechanism for the relevant store
uploads being out of sync with Plasma releases. See Readme in repo.

The extensions will be marked public just before the Plasma beta.

Another sprint decision was that we have a collective duty to make sure
Falkon is at feature parity in terms of Plasma integration. (probably using
PBI doesn't make sense, it'll be easier to just reimplement any features
natively).

----

In terms of other actions:
 - we now have an official KDE account managing the firefox store ready for
me and Kai to get simultaneously hit by a bus.
 - i18n is *hopefully* fixed with custom scripts to handle json->pot->*kde
magic*->pot->json system.
 - a lot of dead code for future features has been removed
 - both firefox and chrome stores have been updated to the current code

David

[Attachment #3 (text/html)]

<div dir="ltr"><div><div>Plasma Browser Integration has a host part and a client \
(chrome/firefox extension) part. The host must be installed by distros, \
<br></div><div><br></div>The plan of action we&#39;ve agreed upon is that we (by \
default) won&#39;t install the client part. We&#39;ll encourage distros to install \
the host part by default.<br><br></div><div>The host part will also ship a mechanism \
that will show a non-invasive popup when firefox/chrome is launched with a link to \
the relevant browser store.<br><br></div><div>We also have an agreed upon git-tagging \
mechanism for the relevant store uploads being out of sync with Plasma releases. See \
Readme in repo.<br><br></div><div>The extensions will be marked public just before \
the Plasma beta.<br></div><div><br>Another sprint decision was that we have a \
collective duty to make sure Falkon is  at feature parity in terms of Plasma \
integration. (probably using PBI  doesn&#39;t make sense, it&#39;ll be easier to just \
reimplement any features  natively).<br><br>----<br><br></div><div>In terms of other \
actions:<br>  - we now have an official KDE account managing the firefox store ready \
for me and Kai to get simultaneously hit by a bus.<br>  - i18n is *hopefully* fixed \
with custom scripts to handle json-&gt;pot-&gt;*kde magic*-&gt;pot-&gt;json \
system.<br>  - a lot of dead code for future features has been removed<br></div><div> \
- both firefox and chrome stores have been updated to the current \
code<br></div><div><br></div><div>David<br></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]