All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jandra A <jandraara@gmail.com>
To: Derick Montague <Derick.Montague@ibm.com>
Cc: "Pine, Kathryn ElaineX" <kathryn.elainex.pine@intel.com>,
	 OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: GUI Component Library
Date: Mon, 25 Nov 2019 15:17:37 -0600	[thread overview]
Message-ID: <CAMTupoQkeiOYSKwUYV9vCUvsymt2BmNKcBNemCB_GL-a=kJzVQ@mail.gmail.com> (raw)
In-Reply-To: <OFBA22BA42.AE014E7E-ON002584BD.0071CE96-002584BD.0073A72B@notes.na.collabserv.com>

[-- Attachment #1: Type: text/plain, Size: 3177 bytes --]

Updating the OpenBMC Style Guide Prototype link below.


> 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?
>
> > However, I wonder if we could find a happy medium between the two
> styles? I’ve been looking for websites that have elements of both style
> preferences -- that include the more modern look (larger elements, rounded
> corners, light colors), with the more stable look (dark colors, square
> elements) – and found these great examples:
> >
> >- Invision App’s website https://www.invisionapp.com/
> >- Visual Studio Code website https://code.visualstudio.com/
> >- GitHub website https://github.com/
>
> Thank you for sending the site examples. They are great examples of
> well-designed user interfaces. Although the proposed Intel UI updates
> provide some pattern improvements, the overall layout and design changes
> don't feel as polished as the examples you shared. We believe more
> collaboration is needed to improve the design and implementation of the
> proposed changes to meet both Intel's and IBM's needs.
>
> A little over a year ago, we developed an OpenBMC style guide to make it
> easier for designers and developers to contribute to the project. We built
> a living style guide prototype, but Ed's concern about who would develop
> and maintain the guide kept it from moving forward. The inconsistency and
> lack of code reuse throughout the application is the result of not having
> this documentation.
>
> OpenBMC Style Guide:
> https://ibm.invisionapp.com/share/EBNYECMH3Y2#/318986393_Grid
> <https://ibm.invisionapp.com/share/EBNYECMH3Y2#/318986393_Grid>
>
> OpenBMC Style Guide Prototype:
> https://derick-montague.github.io/openbmc-styleguide-proposal/
>
> As we rewrite the application in Vue, we have an opportunity to create
> this documentation and assure that the OpenBMC UI is clean, maintainable,
> and adheres to an agreed-upon set of values. Since joining the project, you
> have been working alone on both design and development. We hope that we can
> work as a team to collaborate and lean on each other's strengths.
>
> I feel the next step is to schedule a meeting to review the existing style
> guide. We can then determine what needs to be updated to meet both Intel's
> and IBM's needs. We can use the updated style guide to create the theme
> changes required for the Bootstrap-Vue out of box experience to adhere to
> the updated style guide.
>
> This effort will require a stronger focus on the framework update and
> style guide development. When we start working on the framework update, the
> only updates to the AngularJS UI will be critical bug fixes. Our goal is to
> have the framework update complete no later than the end of Q2 2020.
>
> What are your thoughts on this plan?
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 6212 bytes --]

  reply	other threads:[~2019-11-25 21:17 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 [this message]
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
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='CAMTupoQkeiOYSKwUYV9vCUvsymt2BmNKcBNemCB_GL-a=kJzVQ@mail.gmail.com' \
    --to=jandraara@gmail.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.