Multiple instance of cog

[GobGeeklord]

Hi there,

I'm not sure if this question is duplicated with multiple-views, but what i want to know is possible to run multiple cog instances with completely separated apps?
The purpose is not to block app2 (render?) when app1 is blocked executing calls

Example:

Is this scenario even possible?

[ventosus]

I have a similar question. I have weston configured in kiosk mode for two monitors and would like to run two instances of cog. Whenever I start the second cog instance, the first is blacked out (but still seems to run). I Have the feeling, there may be a name clash with dbus, but I am not sure.

I use the gapplication ids and the seem to work, e.g. the browser start up on the correct display, but the first disappears when the second one starts up, but reappears, when the second is stopped.

weston.ini

[core]
shell=kiosk-shell.so

[output]
name=DP-1
mode=28.10  1280 1283 1288 1292  720 721 723 725 +hsync +vsync
app-ids=com.example.Left

[output]
name=eDP-1
mode=28.10  1280 1283 1288 1292  720 721 723 725 +hsync +vsync
app-ids=com.example.Right

cog left

cog --gapplication-app-id=com.example.Left http://left.com

cog right

cog --gapplication-app-id=com.example.Right http://right.com

[GobGeeklord]

Hi @ventosus ,
This is exactly what i was looking for! But the question is, the cog "spawn" seems to be very random (window position), is there any way to control this from a weston perspective? (window size, position, etc?)

[ventosus]

I wouldn't know, I use the kiosk shell exclusively, it's always fullscreen

[ventosus]

When run in weston's desktop-shell.so, both cog browsers are visible, but the desktop shell is really inconvenient for a kiosk system.

[ventosus]

This was apparently a weston bug and got fixed in weston 10.0.1.

[commodo]

This was apparently a weston bug and got fixed in weston 10.0.1.

thanks for that hint; it helped me (at least) :)

[aperezdc]

Using different application identifiers, as suggested by @ventosus, is expected to work from Cog's point of view. This uses two different cog processes.

Note that you can also use cogctl --appid= to indicate which instance's remote control interface to use.

The support for multiple views (see #77) will allow using more than one web view per cog process.