[
https://issues.apache.org/jira/browse/GUACAMOLE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17936951#comment-17936951
]
Carl Anderson commented on GUACAMOLE-315:
-----------------------------------------
For my extension, I would like to provide a custom `manifest.json`, which
requires that it be linked in the head. I do see that `1.5.5` includes such a
link, but the path to the manifest is static. Perhaps my change could be
addressed in a different Jira issue.
As an extension developer, I would like to be able to inject a `manifest.json`
and reference it using the resource URL from the main client. For example, if
my extension namespace is `foo`, I would like to configure the manifest link in
the client to be `<link rel="manifest" href="app/ext/foo/manifest.json">`
For this to work, I think `guacamole.properties` would need to support a new
attribute to customize the `manifest_link_href`.
> Allow root level of Guacamole interface to be modified via extensions
> ---------------------------------------------------------------------
>
> Key: GUACAMOLE-315
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-315
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
> Reporter: Mike Jumper
> Priority: Trivial
>
> Though GUACAMOLE-9 added support for modifying/patching HTML structure via
> extensions, that support relies on the templating system used by AngularJS
> for directives, and thus cannot be used for any part of the Guacamole
> interface not implemented using directives. This means that absolutely all
> parts of the Guacamole UI can be modified except the top/root level of the
> interface.
> Lacking this support prevents extensions from adding things like notification
> services which would be best placed at the root level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
