From: James Feist <james.feist@linux.intel.com>
To: "Pine, Kathryn ElaineX" <kathryn.elainex.pine@intel.com>,
Derick Montague <Derick.Montague@ibm.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: GUI Component Library
Date: Wed, 27 Nov 2019 10:24:04 -0800 [thread overview]
Message-ID: <022dfcb8-7401-7ddb-8bba-2a7e0f7c0592@linux.intel.com> (raw)
In-Reply-To: <FD0BD680739BFC41807C96BD23118BB131A1BE@ORSMSX113.amr.corp.intel.com>
On 11/26/19 1:19 PM, Pine, Kathryn ElaineX wrote:
>>> In terms of a design library that matches the style of the web UI we’ve been working on, Bootstrap would be a great choice: https://bootstrap-vue.js.org
>
>> We agree to use Bootstrap-Vue for the Vue framework rewrite. Bootstrap-Vue does not have an icon library and refers to third-party sources. Since we are already using the Carbon Design System icons, can we agree to continue to use
> them?
>
Bootstrap did just release an icon library yesterday fwiw, although it
is only in Alpha https://blog.getbootstrap.com/2019/11/26/bootstrap-icons/
> Yes, I’m ok continuing to use the Carbon Design System icons. I agree,
> also, that if an icon does not exist in the library, we can use the
> library’s icons to make new icons that match that style.
>
next prev parent reply other threads:[~2019-11-27 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 21:47 GUI Component Library Derick Montague
2019-11-20 22:36 ` Jandra A
2019-11-20 22:56 ` Pine, Kathryn ElaineX
2019-11-21 1:45 ` Derick Montague
2019-11-22 15:22 ` Pine, Kathryn ElaineX
2019-11-25 21:03 ` Derick Montague
2019-11-25 21:17 ` Jandra A
2019-11-26 21:19 ` Pine, Kathryn ElaineX
2019-11-27 16:39 ` Derick Montague
2019-12-02 22:08 ` Pine, Kathryn ElaineX
2019-12-03 17:31 ` Jandra A
2019-12-03 21:00 ` Pine, Kathryn ElaineX
2019-12-03 20:34 ` Derick Montague
2019-12-03 21:00 ` Pine, Kathryn ElaineX
2019-11-27 18:24 ` James Feist [this message]
2019-11-27 18:39 ` Derick Montague
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=022dfcb8-7401-7ddb-8bba-2a7e0f7c0592@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=Derick.Montague@ibm.com \
--cc=kathryn.elainex.pine@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.