Re: Plasma Browser Integration is in kdereview

[Aleix Pol]

On Tue, Jul 11, 2017 at 1:08 AM, David Edmundson
 wrote:
> Do you know if you can me it be a bit more quiet and only output errors on
>>
>> failure?
>
>
> I changed that a few weeks ago, I assume it's fine now?
>
>
> If there are no complaints I'll move this to Plasma.

+1
\o/

Aleix

Re: Plasma Browser Integration is in kdereview

[David Edmundson]

Do you know if you can me it be a bit more quiet and only output errors on

> failure?
>

I changed that a few weeks ago, I assume it's fine now?


If there are no complaints I'll move this to Plasma.

Re: Plasma Browser Integration is in kdereview

[Albert Astals Cid]

El divendres, 9 de juny de 2017, a les 13:59:20 CEST, David Edmundson va 
escriure:
> >StaticMessages.sh
> 
> Didn't know about that, thanks.
> I've implemented it, but can only test so much. Can you send me scripty
> logs if it fails.

Seems to be working-ish?

Do you know if you can me it be a bit more quiet and only output errors on 
failure?

At the moment it says things like

kdereview_plasma-browser-integration /home/scripty/prod/trunk/l10n-kf5/
templates/messages/kdereview
.
start converting
--> reading file from: ./extension/_locales/en/messages.json
<-- writing file to: /home/scripty/prod/git-unstable-kf5/kdereview_plasma-
browser-integration/po/plasma-browser-extension.pot
file written
.
start converting
--> reading file from: /tmp/tmp.Nyi0t2h1Gt/pt.po
<-- writing file to: ./extension/_locales/pt/messages.json
file written
start converting
--> reading file from: /tmp/tmp.Nyi0t2h1Gt/sk.po
<-- writing file to: ./extension/_locales/sk/messages.json
file written


Which is a pain since what we do to detect scripty errors is diff the new run 
with the previous run to see what text changed and this is going to be a huge 
cause of diffs :/

Cheers,
  Albert

> 
> David

Re: Plasma Browser Integration is in kdereview

[David Edmundson]

>StaticMessages.sh

Didn't know about that, thanks.
I've implemented it, but can only test so much. Can you send me scripty
logs if it fails.

David

Re: Plasma Browser Integration is in kdereview

[Albert Astals Cid]

El dilluns, 5 de juny de 2017, a les 15:42:34 CEST, David Edmundson va 
escriure:
> Hey all,
> 
> We'd like to add project plasma-browser-integration into KDE[0].

I'm not happy how the json is filed only on release time, can you not uses the 
StaticMessages.sh approach that kdeconnect-android uses to fill them back on 
scripty-time?

Cheers,
  Albert

> 
> The goal is to make chrome and firefox integrate better into a Plasma
> desktop environment through browser extensions.
> 
> How?:
> Firefox and chrome (and potentially others) allow plugins to talk to a
> native binary host [1]. This binary host is launched by the the browser and
> has a socket to a conventional browser extension. This project consists of
> both parts allowing a chrome extension to make normal DBus calls to
> services just like other apps.
> 
> Integrating what?:
> This gives us the following features:
>  - Finding open tabs via krunner
>  - Download progress in the task bar
>  - Showing now playing information with shortcuts (if the website supports
> it)
>  - "Send to KDE Connect" context menu on links
>  - Loading windows on the correct activity (WIP)
>  - An SNI if incognito windows are open with action to close them.
> 
> And potentially more in the future. There is a config to enable/disable
> parts as appropriate.
> 
> Deployment:
>  This repo consists of two parts. The binary host which should be
> distributed by normal distro means, and the browser extension which is
> going to be different.
> 
> The browser extension can be deployed in one of 3 ways.
>  - manually by the user from the code (useful for devs)
> 
>  - through the webstore [2][3]
>  - chrome also has a feature where we can ship a text file on the distro
> side that will make the browser automatically fetch an extension from their
> store.
> 
> Ideally we want the extension available on the store from an official KDE
> channel.
> 
>  - potentially it could also be done by the distro, but it seems like FF
> might be removing that possibility and the digital signing is an issue.
> 
> [0] https://cgit.kde.org/plasma-browser-integration.git/
> [1] https://developer.chrome.com/extensions/nativeMessaging
> [2]
> https://chrome.google.com/webstore/detail/plasma-integration/cimiefiiaegbelh
> efglklhhakcgmhkai [3]
> https://addons.mozilla.org/en-US/android/addon/plasma-integration/?src=cb-dl
> -updated
> 
> Regards
> 
> David and Kai

Re: Plasma Browser Integration is in kdereview

[Aleix Pol]

On Wed, Jun 7, 2017 at 12:23 AM, David Edmundson
 wrote:
> Install the host part with the normal cmake && make.
> The bit that tries to install into /etc/ does need to go into /etc
>
> Easiest thing then is to then install the extension part from one of the
> links in my original email.

Yes, you are right, it's pretty easy.
That said, a wiki or a README.md would be nice too.

I'm having a crash on Chrome [1], on Chromium it's working perfectly
fine though. Impressive!

Aleix

[1] https://bugs.kde.org/show_bug.cgi?id=380186

Re: Plasma Browser Integration is in kdereview

[David Edmundson]

​Install the host part with the normal cmake && make.
The bit that tries to install into /etc/ does need to go into /etc

Easiest thing then is to then install the extension part from one of the
links in my original email.

Re: Distro integration for Plasma Browser Integration (was: Re: Plasma Browser Integration is in kdereview

[Sandro Knauß]

Hey,

> > What options are possible to distribute extensions via distro packaging?

You can package for both browses extensions, that works quite nicely:
Here is one I made for Debian and Firefox:
https://tracker.debian.org/pkg/firefox-kwallet5

For Chrome the debian Wiki tells, that extensions are disabled by default:
https://wiki.debian.org/Chromium#Extensions

Best regards,

sandro


signature.asc
Description: This is a digitally signed message part.

Re: Distro integration for Plasma Browser Integration (was: Re: Plasma Browser Integration is in kdereview

[Neal Gompa]

On Mon, Jun 5, 2017 at 11:22 AM, Martin Steigerwald  wrote:
> Hello David.
>
> Thanks for your effort on plasma browser integration.
>
>
> What options are possible to distribute extensions via distro packaging?
>
> I ask cause I think at least for chrome / chromium you need a Google account
> to use the plugin / extension store. Also it would put the extension outside
> of distro security support. Therefore I mostly use xul-ext packages in Debian
> as extensions for Firefox and also a new uBlock origin extension package for
> chromium.
>
> Eventually this would need to be brought up with browser developers. I am
> willing to help there by creating wishlist item / bug report.
>

In Fedora, we have actually packaged an extension for Chrome[1], so it
is possible to package Chrome extensions and have them work with
Chromium / Chrome.

If they are locally installed, Chrome will activate them, and if they
require special permissions, the user will be prompted to grant them.

[1]: 
https://src.fedoraproject.org/cgit/rpms/fedora-user-agent-chrome.git/tree/fedora-user-agent-chrome.spec


-- 
真実はいつも一つ！/ Always, there's only one truth!

Distro integration for Plasma Browser Integration (was: Re: Plasma Browser Integration is in kdereview

[Martin Steigerwald]

Hello David.

Thanks for your effort on plasma browser integration.

I am unsure whether to keep CC to kde-core-devel and plasma-devel, please drop 
as you deem appropriate. Keeping all text for reference for those that only 
read distributions mailing list.

David Edmundson - 05.06.17, 15:42:
> Hey all,
> 
> We'd like to add project plasma-browser-integration into KDE[0].
> 
> The goal is to make chrome and firefox integrate better into a Plasma
> desktop environment through browser extensions.
> 
> How?:
> Firefox and chrome (and potentially others) allow plugins to talk to a
> native binary host [1]. This binary host is launched by the the browser and
> has a socket to a conventional browser extension. This project consists of
> both parts allowing a chrome extension to make normal DBus calls to
> services just like other apps.
> 
> Integrating what?:
> This gives us the following features:
>  - Finding open tabs via krunner
>  - Download progress in the task bar
>  - Showing now playing information with shortcuts (if the website supports
> it)
>  - "Send to KDE Connect" context menu on links
>  - Loading windows on the correct activity (WIP)
>  - An SNI if incognito windows are open with action to close them.
> 
> And potentially more in the future. There is a config to enable/disable
> parts as appropriate.
> 
> Deployment:
>  This repo consists of two parts. The binary host which should be
> distributed by normal distro means, and the browser extension which is
> going to be different.
> 
> The browser extension can be deployed in one of 3 ways.
>  - manually by the user from the code (useful for devs)
> 
>  - through the webstore [2][3]
>  - chrome also has a feature where we can ship a text file on the distro
> side that will make the browser automatically fetch an extension from their
> store.
>
> Ideally we want the extension available on the store from an official KDE
> channel.
> 
>  - potentially it could also be done by the distro, but it seems like FF
> might be removing that possibility and the digital signing is an issue.

What options are possible to distribute extensions via distro packaging?

I ask cause I think at least for chrome / chromium you need a Google account 
to use the plugin / extension store. Also it would put the extension outside 
of distro security support. Therefore I mostly use xul-ext packages in Debian 
as extensions for Firefox and also a new uBlock origin extension package for 
chromium.

Eventually this would need to be brought up with browser developers. I am 
willing to help there by creating wishlist item / bug report.

> [0] https://cgit.kde.org/plasma-browser-integration.git/
> [1] https://developer.chrome.com/extensions/nativeMessaging
> [2]
> https://chrome.google.com/webstore/detail/plasma-integration/cimiefiiaegbelh
> efglklhhakcgmhkai [3]
> https://addons.mozilla.org/en-US/android/addon/plasma-integration/?src=cb-dl
> -updated
> 
> Regards
> 
> David and Kai

Thanks,
-- 
Martin

Re: Plasma Browser Integration is in kdereview

[Aleix Pol]

On Mon, Jun 5, 2017 at 4:42 PM, David Edmundson
 wrote:
> Hey all,
>
> We'd like to add project plasma-browser-integration into KDE[0].
>
> The goal is to make chrome and firefox integrate better into a Plasma
> desktop environment through browser extensions.
>
> How?:
> Firefox and chrome (and potentially others) allow plugins to talk to a
> native binary host [1]. This binary host is launched by the the browser and
> has a socket to a conventional browser extension. This project consists of
> both parts allowing a chrome extension to make normal DBus calls to services
> just like other apps.
>
> Integrating what?:
> This gives us the following features:
>  - Finding open tabs via krunner
>  - Download progress in the task bar
>  - Showing now playing information with shortcuts (if the website supports
> it)
>  - "Send to KDE Connect" context menu on links
>  - Loading windows on the correct activity (WIP)
>  - An SNI if incognito windows are open with action to close them.
>
> And potentially more in the future. There is a config to enable/disable
> parts as appropriate.
>
> Deployment:
>  This repo consists of two parts. The binary host which should be
> distributed by normal distro means, and the browser extension which is going
> to be different.
>
> The browser extension can be deployed in one of 3 ways.
>  - manually by the user from the code (useful for devs)
>
>  - through the webstore [2][3]
>  - chrome also has a feature where we can ship a text file on the distro
> side that will make the browser automatically fetch an extension from their
> store.
>
> Ideally we want the extension available on the store from an official KDE
> channel.
>
>  - potentially it could also be done by the distro, but it seems like FF
> might be removing that possibility and the digital signing is an issue.
>
> [0] https://cgit.kde.org/plasma-browser-integration.git/
> [1] https://developer.chrome.com/extensions/nativeMessaging
> [2]
> https://chrome.google.com/webstore/detail/plasma-integration/cimiefiiaegbelhefglklhhakcgmhkai
> [3]
> https://addons.mozilla.org/en-US/android/addon/plasma-integration/?src=cb-dl-updated
>
> Regards
>
> David and Kai

General +1 to the features. Really awesome. :)

Do we have any documentation on how to test it?

Aleix

Re: Distro integration for Plasma Browser Integration (was: Re: Plasma Browser Integration is in kdereview

[David Edmundson]

>
> What options are possible to distribute extensions via distro packaging?
>

For chrome see https://developer.chrome.com/extensions/external_extensions.
For firefox I was under the impression you can't, but I haven't extensively
looked.

But the easiest thing to do is see how chrome-gnome-shell is handlded in
your distro, which is a similar tech, but used purely for helping
extensions.gnome.org install extensions.

It's an already addressed issue (or non-issue), so we can basically do the
same.

On Arch and Ubuntu the browser side is fetched from the relevant store by
the user.


> I ask cause I think at least for chrome / chromium you need a Google
> account
> to use the plugin / extension store.


That's not true. Nor for firefox.

David

Re: Plasma Browser Integration is in kdereview

[Luca Beltrame]

In data lunedì 5 giugno 2017 16:42:34 CEST, David Edmundson ha scritto:

>  - chrome also has a feature where we can ship a text file on the distro
> side that will make the browser automatically fetch an extension from their
> store.

You may need to ask distributions if they are OK with it. Also bear in mind 
that, at least for the Chrome ecosystem, Chrome and Chromium (the latter 
actually used by the distributions) handle this mechanism in a slightly 
different way (I had a very high-level discussion with kbroulik on IRC a few 
weeks ago).

-- 
Luca Beltrame - KDE Forums team
KDE Science supporter
GPG key ID: A29D259B

signature.asc
Description: This is a digitally signed message part.