+1
Am 05.12.2017 um 18:28 schrieb Maxim Solodovnik:
Dear OpenMeetings Community,
I would like to start a vote about releasing Apache OpenMeetings 4.0.1 RC1
Main changes are:
Release 4.0.1, provides following improvements:
* Openlaszlo code is removed
* Login via OAuth is improved
* External
There are 2 options
1) globaly disable remote control: Admin->Config->
screensharing.allow.remote
(http://openmeetings.apache.org/GeneralConfiguration.html)
2) remove "Remote control" right from other users in the room
On Fri, Dec 8, 2017 at 8:04 AM, Chad Palenshus wrote:
> That works. I jus
That works. I just wanted to make sure I wasn’t missing something. I’ll watch
for updates.
Thanks!
> On Dec 7, 2017, at 7:46 PM, David Jentz wrote:
>
> We have a security requirement on this topic to disable screensharing
> control by default and have the sharer manually enable it.
>
> We h
We have a security requirement on this topic to disable screensharing
control by default and have the sharer manually enable it.
We have a small patch to enable this, but it wasn't for 4.0.0 ( Maybe 3.2.1?)
Definitely interested if we could make the upstream version have
screen sharing control of
I appears that when you initiate a screen share, remote control is
permitted by default and you have to uncheck it. Is this a setting
somewhere (that I obviously haven't found yet) or is by design for some
reason?
Thanks!
-Chad
OK, then the easiest solution would be: to zoom document in case it is
smaller than WB
Could you please file JIRA regarding this?
On Thu, Dec 7, 2017 at 8:44 PM, Peter Dähn wrote:
> I believe most of the moderators doesn't care about what kind of width we
> are talking about... ;-)
>
> I think th
I believe most of the moderators doesn't care about what kind of width
we are talking about... ;-)
I think the question is, what will be expected from the majority, if
choosing one of the zoom options. And here I got the feedback, that zoom
on the document (or as you said object dependent) is
I guess this is also some kind of "wording" issue
I read "Page width" as WB width == browser page width
You read it as document page with == browser page width
"document fit" might be the option, but this will add complication to zoom logic
In previous version WB size was sort of fluid, it re-ca
You need to set up Apache to also proxy WebSockets ...
On Thu, Dec 7, 2017 at 8:03 PM, K, Amit (MIND) wrote:
> Dear Maxim,
>
>
>
> I put an Apache server in front of OM server. So I am launching through
> default port which is 80.
>
>
>
> While login it is shown URL "http://IPADDRESS/newgenWB/#us
Dear Maxim,
I put an Apache server in front of OM server. So I am launching through default
port which is 80.
While login it is shown URL "http://IPADDRESS/newgenWB/#user/dashboard";, means
logged in successfully. (Application is hosted on Amazon cloud- Ubuntu 16)
But the problem is dash
I believe this is discussable.
I would say, if I have a presentation/webinar I would have some
documents that I put on the wb and that should take the maximum space
(for me and any of my students). And therefore are full fit and page
width. And afterwards I would start to draw something on my
sure
http://openmeetings.apache.org/WebappNamePath.html#Renaming_openmeetings_context
On Thu, Dec 7, 2017 at 6:40 PM, K, Amit (MIND) wrote:
> Hi Maxim,
>
>
>
> I pull latest code and compiled. Now I just changed “openmeetings” folder
> some other name say “newgenWB”.
>
>
>
> Now if suppose I put
Hi Maxim,
I pull latest code and compiled. Now I just changed "openmeetings" folder some
other name say "newgenWB".
Now if suppose I put "http://myip:5080/newgenWB"; in browser then it is working
fine but in case I put "http://myip:5080/"; except ("newgenWB") then it is
redirecting to "http:
13 matches
Mail list logo
