From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: Ravi Chintakunta <ravi.chintakunta@timesys.com>,
"Reyna, David L (Wind River)" <david.reyna@windriver.com>,
"Damian, Alexandru" <alexandru.damian@intel.com>
Cc: "'toaster@yoctoproject.org'" <toaster@yoctoproject.org>
Subject: Re: DRY RUN [Review Request] 4299 "recipes: View detailed information about a recipe"
Date: Wed, 15 Jan 2014 18:01:05 +0000 [thread overview]
Message-ID: <CEFC7BA3.3ADCE%belen.barros.pena@intel.com> (raw)
In-Reply-To: <CFEB29247FA6A94796A15592E348E7B901E836D227FD@exchange07.timesys.com>
On 15/01/2014 17:21, "Ravi Chintakunta" <ravi.chintakunta@timesys.com>
wrote:
>Hi David,
>
>> > return 'style=color:red' else: return 'style=color:black'
>>
>> By the way, Belen had defined these class colors in her CSS style
>> sheet...
>>
>> 'class=error'
>> 'class=muted'
>>
>> ... where no color specified defaults to "color:black".
I am not sure this is important, but just in case. The default colour for
anchor tags inside tables is #333333. The hover effect is set to black
(#000000). Those styles are defined in lines 110 and 111 of default.css
Cheers
Belén
>>
>> We may want to use her CSS values in case Belen changes her mind on
>> the colors :-)
>>
>
>Yes, I agree.
>
>I have pushed my commit
>
>http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=ravi/all-
>tasks-feature&id=2423a9336b66d8c83a139ad50890ffbb88ecd181
>
>to remove the hard coded colors and use the css.
>
>Thanks,
>Ravi
>_______________________________________________
>toaster mailing list
>toaster@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/toaster
next prev parent reply other threads:[~2014-01-15 18:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 6:35 DRY RUN [Review Request] 4299 "recipes: View detailed information about a recipe" Reyna, David
2014-01-12 17:55 ` Lerner, Dave
2014-01-12 18:49 ` Reyna, David
2014-01-13 12:42 ` Damian, Alexandru
2014-01-13 13:42 ` Damian, Alexandru
2014-01-13 14:33 ` Reyna, David
2014-01-13 14:40 ` Damian, Alexandru
2014-01-13 14:46 ` Damian, Alexandru
2014-01-13 14:53 ` Barros Pena, Belen
2014-01-13 14:57 ` Reyna, David
2014-01-13 15:04 ` Damian, Alexandru
2014-01-13 15:07 ` Reyna, David
2014-01-15 6:34 ` Reyna, David
2014-01-15 12:09 ` Ravi Chintakunta
2014-01-15 15:19 ` Reyna, David
2014-01-15 17:21 ` Paul Eggleton
2014-01-15 17:21 ` Ravi Chintakunta
2014-01-15 18:01 ` Barros Pena, Belen [this message]
[not found] ` <5E53D14CE4667A45B9A06760DE5D13D055D7A5A8@ALA-MBB.corp.ad.wrs.com>
[not found] ` <CAJ2CSBvYkLMde7hu0Zhxk7qwBoNdTCTECQv6SxpBXQ1BVx9m1Q@mail.gmail.com>
[not found] ` <5E53D14CE4667A45B9A06760DE5D13D055D7B5BE@ALA-MBB.corp.ad.wrs.com>
2014-01-15 15:36 ` FW: " Reyna, David
2014-01-13 15:01 ` Lerner, Dave
2014-01-13 15:10 ` Damian, Alexandru
2014-01-13 15:23 ` Barros Pena, Belen
2014-01-13 15:44 ` Lerner, Dave
2014-01-13 16:36 ` Barros Pena, Belen
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=CEFC7BA3.3ADCE%belen.barros.pena@intel.com \
--to=belen.barros.pena@intel.com \
--cc=alexandru.damian@intel.com \
--cc=david.reyna@windriver.com \
--cc=ravi.chintakunta@timesys.com \
--cc=toaster@yoctoproject.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.