From: "Derick Montague" <Derick.Montague@ibm.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: aladyshev22@gmail.com
Subject: Re: Dynamic layout for the Serial-Over-Lan window in phosphor-webui
Date: Thu, 5 Nov 2020 17:15:01 +0000 [thread overview]
Message-ID: <OFD37A2AD5.BA39933E-ON00258617.005D770D-00258617.005EC23F@notes.na.collabserv.com> (raw)
In-Reply-To: <CACSj6VUNsH5c=de2xmNq-KhP9q76xV_BPw8o1JZ72DaKjOi2ww@mail.gmail.com>
> I was working on a Serial-Over-Lan layout in a phosphor-webui. For me
> it seems horribly broken
> I came up with a solution where a terminal window resizes according to
> the window changes.
I agree that the SOL layout in the phosphor-webui GUI does not provide a
good experience. It was also noted by Patrick Williams that the font stack
being used also did not provide a good experience. To that extent, IBM and
Intel, working with other community members that regularly attend the OpenBMC
GUI Design Work Group, collaborated to improve the SOL and KVM over IP
experiences in the webui-vue GUI (www.github.com/openbmc/webui-vue). The
experience of the web based terminals are consistent and significantly
improved.
SOL: https://github.com/openbmc/webui-vue/issues/25
KVM: https://github.com/openbmc/webui-vue/issues/24
We have provide details on the reason for creating the webui-vue GUI
in the repo's README: https://github.com/openbmc/webui-vue#webui-vue
Thank you!
Derick Montague
IBM Cognitive Systems User Experience
next prev parent reply other threads:[~2020-11-05 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 14:54 Dynamic layout for the Serial-Over-Lan window in phosphor-webui Konstantin Aladyshev
2020-11-05 17:15 ` Derick Montague [this message]
2020-11-05 20:42 ` Konstantin Aladyshev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OFD37A2AD5.BA39933E-ON00258617.005D770D-00258617.005EC23F@notes.na.collabserv.com \
--to=derick.montague@ibm.com \
--cc=aladyshev22@gmail.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).