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

Jason Keltz commented on GUACAMOLE-1080:
----------------------------------------

I had some time to get back to this.  I managed to add a "NOTIFICATIONS" 
section to the Guacamole main page.  Obviously if I placed the messages in the 
"html" file that is bundled with the extension, that wouldn't be very useful.  
I need to read the messages from a file.  I need to do that every time the page 
is loaded so that the messages will be current.  Now, it would be ideal if I 
could insert a PHP call into the HTML fragment that adds the notifications 
section which would read from a file, and add properly formatted notifications. 
 I don't think that's possible? The QuickConnect plugin has buttons, but it 
doesn't generate dynamic output.  Can you please give me an example of what I 
could insert into the plugin which generates dynamic output.  I can then try to 
figure out the rest.

It would be great if the guacamole-ext section of the documentation could 
provide more details and examples.  I'm sure a lot can be done if someone knows 
how.

> allow notifications tab on Guacamole main screen
> ------------------------------------------------
>
>                 Key: GUACAMOLE-1080
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1080
>             Project: Guacamole
>          Issue Type: New Feature
>            Reporter: Jason Keltz
>            Priority: Minor
>
> I would like if Guacamole had an option to enable a "notifications" or 
> "notices" section on the main screen between RECENT CONNECTIONS and ALL 
> CONNECTIONS.  It would be nice if Guacamole could read this information from 
> a configurable file on the system.  Here, I could include messages like:
> "05/24/2000 10:00 AM - Hosts 1-50 are reserved for class X right now - but 
> hosts 51-100 are available."
> "05/24/2000 10:00 AM - Hosts in the Windows group are presently unavailable. 
> We are presently investigating the cause." 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to