[Toaster] Thread: Customizing Bootstrap for new UI Tools

[Levi Da Silveira, Vitor]

Hi!

You're right. This is my main concern about that. What I’m trying to do is working on very top of the core bootstrap but using "LESS" just to override styles. Some times it is not too easy because you want overhauling a button, for examples you need to reset all style basically, even though LESS allows me to create mixins/functions, then I've created one called ".reset-style()” that tries to clean the styles I'm designing for.

I’m avoiding to change or input classes on current HTML. However, when I said perhaps we will have new components or overhauling and it implies to change some class or HTML tags.

Anyway, it is just a study to see how new UI could be applied mainly on prototype and Michael has an wide experience than me and probably he knows the better way to go for it.

Thank you Alex for your considerations.

Cheers,
Levi
:)

From: <Damian>, Alexandru <alexandru.damian at intel.com<mailto:alexandru.damian at intel.com>>
Date: Thursday, 28 May 2015 11:19 am
To: Vitor Levi Da Silveira <vitor.levi.da.silveira at intel.com<mailto:vitor.levi.da.silveira at intel.com>>
Cc: "toaster at yoctoproject.org<mailto:toaster at yoctoproject.org>" <toaster at yoctoproject.org<mailto:toaster at yoctoproject.org>>
Subject: Re: [Toaster] Thread: Customizing Bootstrap for new UI Tools

Hi,

Sorry for the late reply - I would strongly suggest not to fork bootstrap, for both maintenance and legal reasons.

Of course Bootstrap is open source, and we can do whatever we want to it, but if our changes have no chances to be eventually integrated upstream, it will be a nightmare to continue merging our changes when we update Bootstrap, as you say.

Cheers,
Alex

On Wed, May 20, 2015 at 1:59 PM, Levi Da Silveira, Vitor <vitor.levi.da.silveira at intel.com<mailto:vitor.levi.da.silveira at intel.com>> wrote:
Hello all.

I’ve been working on UI and Bootstrap customisation and I am facing questions on which one is the better way. I’m opening this thread to we discuss which way to follow taking in consideration mainly Michel who is working directly on front-end.

We have basically two ways to customise it, Overriding with CSS and Core customisation. I listed below
pros and cons of which one in a way to know your perspective of it and

Overriding with CSS

Pros
- is the most straightforward approach to change basic styles .
- it hardly changes the workflow.
- styles on top of bootstrap.

Cons
- it takes too much effort to overhauling components.
- it is hard to keep style’s consistence for allover the UI.


Core Customisation (Custom Build)

Pros
- flexibility to hard customisation
- access to LESS variables. It means you can set up styles dynamically making styles more consistence.
- access to all componentes separately turning customisation handy and intuitive.

Cons
- set up environment. It means you’ll need to use NodeJS.
- practically you will fork bootstrap and I don’t know what could happen when to upgrade to an other version


I’m still studying these possibilities and trying to join both concepts  in a way to avoid bootstrap's forking.

Cheers,

Levi
:)
--
_______________________________________________
toaster mailing list
toaster at yoctoproject.org<mailto:toaster at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/toaster



--
Alex Damian
Yocto Project
SSG / OTC