Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of matevzb@gmail.com designates
 74.125.83.47 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: [Apache Bloodhound] #420: Improved styling for `inline code`
From: =?utf-8?Q?Matev=C5=BE_Brada=C4=8D?= <matevzb@gmail.com>
In-Reply-To: 
 <CAGMZAuOsMBAJXR1bsHf6DKvKkLQgNOHJBLLbd0zeqdrc_v_KDg@mail.gmail.com>
Date: Fri, 1 Mar 2013 23:28:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <86301C13-7B05-4199-BDA8-551E6C42B1A4@gmail.com>
References: <056.f54d23e103981cce719026ca72bd4957@incubator.apache.org>
 <071.82fc08d39a98e6494e9791d24aeae9ca@incubator.apache.org>
 <CAGMZAuPEGjh1xenNEgN4JoDgCnCX9R+ZGZdVWozyVVe=py2nSQ@mail.gmail.com>
 <CAPt9QwR9KavdQ9+WxkPXTfBTUpminvnC1pwkOLVSWqLFZK8QXA@mail.gmail.com>
 <CAPt9QwRwyY9crXGoQzj=tO0u8UwG3DHUVBF9=666hbwAjm0oTw@mail.gmail.com>
 <5130DD45.1040506@wandisco.com>
 <CAGMZAuOsMBAJXR1bsHf6DKvKkLQgNOHJBLLbd0zeqdrc_v_KDg@mail.gmail.com>
To: bloodhound-dev@incubator.apache.org


On 1. Mar, 2013, at 21:47, Olemis Lang wrote:

> On 3/1/13, Gary Martin <gary.martin@wandisco.com> wrote:
> [...]
>>=20
>> There are a lot of potential ways of doing this. I am not keen on
>> copying the CSS across if we want to be sticking to whatever =
bootstrap
>> provides. That leaves swapping tags, which itself can probably be =
done
>> in three or more ways, or copying the styles on the client side with =
js.
>>=20
>=20
> I was initially thinking of introducing (overriding) these in
> bloodhound.css rather than modifying bootstrap.css

I think that's what Gary was referring to as well. But overriding things
in bloodhound.css quickly becomes quite cumbersome, as there is no way
to express "inheritance" of one tag's properties from another tag and
then overriding some of them (you have to copy and paste the whole =
style).

However - bootstrap is built with LESS (http://lesscss.org/), which =
extends
the CSS with variables etc. which would allow just that (via mixins).
Maybe we could adopt using LESS for building our custom bootstrap.css in =
the future?

>=20
>> I assume that we are expecting to always show the bootstrap styling =
for
>> all cases as long as the theme is active.
>>=20
>=20
> +1
>=20
> --=20
> Regards,
>=20
> Olemis.