You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "SebastianWagner (JIRA)" <ji...@apache.org> on 2012/06/10 16:42:42 UTC
[jira] [Created] (OPENMEETINGS-320) Exception cause log not
configured and layout for screensharing/recording client
SebastianWagner created OPENMEETINGS-320:
--------------------------------------------
Summary: Exception cause log not configured and layout for screensharing/recording client
Key: OPENMEETINGS-320
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
Project: Openmeetings
Issue Type: Bug
Affects Versions: 2.0 Apache Incubator Release
Reporter: SebastianWagner
Assignee: Maxim Solodovnik
Fix For: 2.0 Apache Incubator Release
Attachments: screensharing.png
In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at at java.io.FileOutputStream.open(Native Method)
at at java.io.FileOutputStream.<init>(Unknown Source)
at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at at java.lang.reflect.Method.invoke(Unknown Source)
at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at at com.sun.javaws.Launcher.run(Unknown Source)
at at java.lang.Thread.run(Unknown Source)
=> The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
Further I thought we should find a compromise on the general layout:
- The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
- If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner updated OPENMEETINGS-320:
-----------------------------------------
Fix Version/s: (was: 2.0 Apache Incubator Release)
2.1 Apache Incubator Release
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.1 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons and labels. We have now stop recording and pause sharing with different icons. Either we label it both pause or both stop and with same icons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293806#comment-13293806 ]
SebastianWagner commented on OPENMEETINGS-320:
----------------------------------------------
I think the Exception is gone.
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons and labels. We have now stop recording and pause sharing with different icons. Either we label it both pause or both stop and with same icons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner updated OPENMEETINGS-320:
-----------------------------------------
Summary: Exception and layout for screensharing/recording client (was: Exception cause log not configured and layout for screensharing/recording client)
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner updated OPENMEETINGS-320:
-----------------------------------------
Description:
In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at at java.io.FileOutputStream.open(Native Method)
at at java.io.FileOutputStream.<init>(Unknown Source)
at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at at java.lang.reflect.Method.invoke(Unknown Source)
at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at at com.sun.javaws.Launcher.run(Unknown Source)
at at java.lang.Thread.run(Unknown Source)
=> The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
Further I thought we should find a compromise on the general layout:
- The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
- If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons. We have not stop recording and pause sharing. Either we label it both pause or both stop.
was:
In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at at java.io.FileOutputStream.open(Native Method)
at at java.io.FileOutputStream.<init>(Unknown Source)
at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at at java.lang.reflect.Method.invoke(Unknown Source)
at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at at com.sun.javaws.Launcher.run(Unknown Source)
at at java.lang.Thread.run(Unknown Source)
=> The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
Further I thought we should find a compromise on the general layout:
- The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
- If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons. We have not stop recording and pause sharing. Either we label it both pause or both stop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik resolved OPENMEETINGS-320.
-------------------------------------------
Resolution: Fixed
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.1 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons and labels. We have now stop recording and pause sharing with different icons. Either we label it both pause or both stop and with same icons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner updated OPENMEETINGS-320:
-----------------------------------------
Attachment: screensharing.png
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik closed OPENMEETINGS-320.
-----------------------------------------
Closing all old 'Resolved' issues
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.1 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons and labels. We have now stop recording and pause sharing with different icons. Either we label it both pause or both stop and with same icons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner updated OPENMEETINGS-320:
-----------------------------------------
Description:
In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at at java.io.FileOutputStream.open(Native Method)
at at java.io.FileOutputStream.<init>(Unknown Source)
at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at at java.lang.reflect.Method.invoke(Unknown Source)
at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at at com.sun.javaws.Launcher.run(Unknown Source)
at at java.lang.Thread.run(Unknown Source)
=> The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
Further I thought we should find a compromise on the general layout:
- The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
- If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons and labels. We have now stop recording and pause sharing with different icons. Either we label it both pause or both stop and with same icons.
was:
In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
at at java.io.FileOutputStream.open(Native Method)
at at java.io.FileOutputStream.<init>(Unknown Source)
at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at at java.lang.reflect.Method.invoke(Unknown Source)
at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at at com.sun.javaws.Launcher.run(Unknown Source)
at at java.lang.Thread.run(Unknown Source)
=> The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
Further I thought we should find a compromise on the general layout:
- The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
- If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons. We have not stop recording and pause sharing. Either we label it both pause or both stop.
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons and labels. We have now stop recording and pause sharing with different icons. Either we label it both pause or both stop and with same icons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENMEETINGS-320) Exception and layout for
screensharing/recording client
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295541#comment-13295541 ]
Maxim Solodovnik commented on OPENMEETINGS-320:
-----------------------------------------------
I never saw this exception (both Ubuntu and Windows)
according UI:
I do agree we need to unify it BUT
0) In english "Bildschirm teilen stoppen" has label "Close" and different icon
1) I saw no dialogs with close button on the bottom right. All dialogs I saw on Mac, Windows and Ubuntu has close button on the very top (top-right in Windows and Ubuntu, configurable on Mac). Maybe it make sense to leave close on standard close button?
2) I agree to make both buttons the same. I'll make necessary changes
> Exception and layout for screensharing/recording client
> -------------------------------------------------------
>
> Key: OPENMEETINGS-320
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-320
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.1 Apache Incubator Release
>
> Attachments: screensharing.png
>
>
> In Windows if you open the console while starting the screensharing WebStart application you can see this exception:
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - This appender no longer admits a layout as a sub-component, set an encoder instead.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
> 16:35:41,762 |-WARN in ch.qos.logback.core.FileAppender[FLOG2] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
> 16:35:41,762 |-INFO in ch.qos.logback.core.FileAppender[FLOG2] - File property is set to [log/current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,764 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - Failed to create parent directories for [C:\Program Files\Mozilla Firefox\log\current_openmeetings_context_name_IS_UNDEFINED.log]
> 16:35:41,765 |-ERROR in ch.qos.logback.core.FileAppender[FLOG2] - openFile(log/current_openmeetings_context_name_IS_UNDEFINED.log,false) call failed. java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at java.io.FileNotFoundException: log\current_openmeetings_context_name_IS_UNDEFINED.log (Das System kann den angegebenen Pfad nicht finden)
> at at java.io.FileOutputStream.open(Native Method)
> at at java.io.FileOutputStream.<init>(Unknown Source)
> at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:30)
> at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
> at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
> at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
> at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
> at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
> at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
> at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
> at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
> at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
> at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
> at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
> at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
> at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
> at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
> at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
> at at org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
> at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at at java.lang.reflect.Method.invoke(Unknown Source)
> at at com.sun.javaws.Launcher.executeApplication(Unknown Source)
> at at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> at at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> at at com.sun.javaws.Launcher.run(Unknown Source)
> at at java.lang.Thread.run(Unknown Source)
> => The consequence is that 1000 of log events are written to the Console. I think this somehow does even slow down the application.
> Also if you have a look at the attached screenshot, that is taken from a OSx Client, you can see that the layout is not optimal. The buttons on the bottom have a strange bar as the they need more width.
> Further I thought we should find a compromise on the general layout:
> - The button to close the dialog should be on the bottom-right of the dialog, same as in every window that we are doing
> - If we make a toggle button (start sharing and pause sharing is a "toggle button") the button to record should be the same. Either we do make both buttons a "toggle button" or non. I think we should better change both buttons to behave the same to have a common UI. Same for the icons and labels. We have now stop recording and pause sharing with different icons. Either we label it both pause or both stop and with same icons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira