[jitsi-users] jitsimeet: screen sharing using chrome


#1

hello,

after i suceeded to set ui jitsi meet in a way most of our users are
(nearly) satisfied i want to go further.

enabeling screen sharing for firefox(41) was not hard to do, but i do
not know, how to do this for chrome.

i did:

1. git clone https://github.com/jitsi/jidesha.git

2. using chrome, created jidesha.crx

now i do not know what to do with jidesha.crx:

1. where to upload it so that the chrome users can install it

2. where to reference this file in our config.js

in the example config.js i found the lines:
    // Desktop sharing method. Can be set to 'ext', 'webrtc' or false to
disable.
    desktopSharingChromeMethod: 'ext',
    // The ID of the jidesha extension for Chrome.
    desktopSharingChromeExtId: 'diibjkoicjeejcmhdnailmkgecihlobk',
    // The media sources to use when using screen sharing with the Chrome
    // extension.
    desktopSharingChromeSources: ['screen', 'window'],
    // Required version of Chrome extension
    desktopSharingChromeMinExtVersion: '0.1.3',

how to adjust these lines?

thanks in advance

gustav


#2

_monolog_

chrome:
installed the chrome plugin on my windos installation using
chrome-developer interface, got an id which i entered into the
desktopSharingChromeExtId variable in config.js. deskto sharing worked.

i went to my linux box, installed the same code. it did not work.
noticed a different id was generated. entered this new code into the
desktopSharingChromeExtId variable in config.js. screen sharing from the
linux box worked but ceased to work from the windows machine. ...:frowning: .

firefox-41:
screen screen sharing works fine from both machines, but viedo/audio
tend to freeze (sometimes a browser reload fixes this). firefox is unusable.

jitsi desktop client:
too many glitches.

conclusion: i think the 'jitsi-suite' has great potential but i did not
yet find (wonder, if there is one) a configuration, which i could
recommend to a larger audience.

sad, gustav

···

Am 14.10.2015 um 14:23 schrieb Gustav Spellauge:

hello,

after i suceeded to set ui jitsi meet in a way most of our users are
(nearly) satisfied i want to go further.

enabeling screen sharing for firefox(41) was not hard to do, but i do
not know, how to do this for chrome.

i did:

1. git clone https://github.com/jitsi/jidesha.git

2. using chrome, created jidesha.crx

now i do not know what to do with jidesha.crx:

1. where to upload it so that the chrome users can install it

2. where to reference this file in our config.js

in the example config.js i found the lines:
    // Desktop sharing method. Can be set to 'ext', 'webrtc' or false to
disable.
    desktopSharingChromeMethod: 'ext',
    // The ID of the jidesha extension for Chrome.
    desktopSharingChromeExtId: 'diibjkoicjeejcmhdnailmkgecihlobk',
    // The media sources to use when using screen sharing with the Chrome
    // extension.
    desktopSharingChromeSources: ['screen', 'window'],
    // Required version of Chrome extension
    desktopSharingChromeMinExtVersion: '0.1.3',

how to adjust these lines?

thanks in advance

gustav

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

Hello Gustav,

i went to my linux box, installed the same code. it did not work.
noticed a different id was generated. entered this new code into the
desktopSharingChromeExtId variable in config.js. screen sharing from the
linux box worked but ceased to work from the windows machine. ...:frowning: .

AFAIK use a plugin on a normaly configured Chrome Browser you have to
upload it to the office Chrome Appstore, see
https://developer.chrome.com/webstore/publish. That way you should get a
consistent ID*.

Kind Regards,
Benedikt Wildenhain

*I didn't try it myself, as Chrome-Screensharing-Support wasn't
important enough for me to spend 5$ to Google.

···

On Wed, Oct 14, 2015 at 05:46:48PM +0200, Gustav Spellauge wrote:


#4

I used Jitsimeet with Chrome under Linux and noone forced me to enter
any kind of id for screensharing. It just worked out of the box.

I find it interesting, that your FF 41 worked, as i get a security error
for an yet unkown operation with FF.

Marius

···

Am 14.10.2015 um 17:46 schrieb Gustav Spellauge:

_monolog_

chrome:
installed the chrome plugin on my windos installation using
chrome-developer interface, got an id which i entered into the
desktopSharingChromeExtId variable in config.js. deskto sharing worked.

i went to my linux box, installed the same code. it did not work.
noticed a different id was generated. entered this new code into the
desktopSharingChromeExtId variable in config.js. screen sharing from
the linux box worked but ceased to work from the windows machine.
...:frowning: .


#5

..

I used Jitsimeet with Chrome under Linux and noone forced me to enter
any kind of id for screensharing. It just worked out of the box.

maybe this is because you are using https://meet.jit.si and not your own
server?

I find it interesting, that your FF 41 worked, as i get a security
error for an yet unkown operation with FF.

had no such problems installing the extension from our server -- don't
know why.

gustav

btw: at our site jitsi meet works best with google chrome, 2nd best
with chromium, sometimes and most times not (reason(s) are unknown to
me) with firefox 41

···

Am 14.10.2015 um 22:22 schrieb Marius:


#6

going to try this

···

Am 14.10.2015 um 19:34 schrieb Benedikt Wildenhain:

AFAIK use a plugin on a normaly configured Chrome Browser you have to
upload it to the office Chrome Appstore, see
https://developer.chrome.com/webstore/publish. That way you should get a
consistent ID*.


#7

monolog (continued)

yes, this works fine - single id, autoinstallation, screen sharing

it would be nice, if remote control would also work.

···

Am 15.10.2015 um 10:13 schrieb Gustav Spellauge:

Am 14.10.2015 um 19:34 schrieb Benedikt Wildenhain:

AFAIK use a plugin on a normaly configured Chrome Browser you have to
upload it to the office Chrome Appstore, see
https://developer.chrome.com/webstore/publish. That way you should get a
consistent ID*.

going to try this

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users