It turns out that what I was looking at whas the source that
Firefox generated to display the page source of the application :(, but
for some reason Firefox will not save the page source if I use the save
function.
On 7/31/23 04:51, Nick Couchman wrote:
On Mon, Jul 31, 2023 at 4:11 AM Robert Dinse
<nan...@eskimo.com.invalid> wrote:
Now that I've looked at the page code, it is ugly, a whole
bunch of <span></span> with NOTHING in between, no class, no id,
no obvious reason to exist other than to obfuscate the code.
Argh! Can't anything be easy? Logical? Well laid out? And it's
ONE LONG LINE, not a single linefeed.
Which page are you looking at, here? Are you talking about the page
source when use the browser tools to inspect it? Or the actual source
code at the URLs the Lorenzo mentioned?
I would agree that looking at the page source can be daunting and not
particularly useful in many cases. This is in large part because the
HTML is dynamically put together by the web application running in
Tomcat (or whatever web application server you're running). It's much
more useful to look at the actual source code.
If there are bits about the branding extension example that Lorenzo
linked to, within the Guacamole Client source, that are confusing or
need further clarification, we'd certainly appreciate feedback on
those. That example branding extension is designed to be something you
can either look at to get a feel for how to write your own, or just
download a copy of it and use it as a starting point and customize it
to fit your needs. It covers things like changing fonts, header text,
logo, etc. - if there are other things that would be useful to add to
it, we can certainly improve upon it.
-Nick
