[ 
https://issues.apache.org/jira/browse/GUACAMOLE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16907848#comment-16907848
 ] 

Michael Jumper edited comment on GUACAMOLE-630 at 8/15/19 11:48 PM:
--------------------------------------------------------------------

It looks like it's all Pickr, actually. Some sort of lengthy init or animation, 
multiplied by 18 (16 palette colors, plus foreground and background):

!guacamole-630-profile-ctrl-alt-shift.png|width=100%!

We may need to either find another decent color picker, or look into ways to 
have an instance of Pickr be both shared and pre-initialized.


was (Author: mike.jumper):
It looks like it's all Pickr, actually. Some sort of length init or animation, 
multiplied by 18 (16 palette colors, plus foreground and background):

!guacamole-630-profile-ctrl-alt-shift.png|width=100%!

We may need to either find another decent color picker, or look into ways to 
have an instance of Pickr be both shared and pre-initialized.

> Allow terminal color scheme to be changed while connection is running
> ---------------------------------------------------------------------
>
>                 Key: GUACAMOLE-630
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-630
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: SSH, Telnet
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Trivial
>             Fix For: 1.1.0
>
>         Attachments: guacamole-630-profile-ctrl-alt-shift.png
>
>
> As mentioned within GUACAMOLE-629, the Guacamole protocol currently imposes 
> limitations on the parameters which configure a connection. As the color 
> scheme used by the terminal of an SSH/telnet connection is one such 
> parameter, the terminal interface is limited to a pre-configured color scheme 
> which cannot be changed while the connection is active.
> It would be awfully nice if the color scheme of the terminal could be changed 
> by the user without administrative access, and without requiring 
> disconnect/reconnect.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to