From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: Amit Kumar Chaudhary <amit@floatingpondtech.com>,
"Damian, Alexandru" <alexandru.damian@intel.com>
Cc: "Wymore, Farrell W \(Wind River\)" <farrell.wymore@windriver.com>,
"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: toaster: review request for build dash board page
Date: Wed, 12 Mar 2014 18:20:22 +0000 [thread overview]
Message-ID: <CF465504.3F4FC%belen.barros.pena@intel.com> (raw)
In-Reply-To: <etPan.5320a3d6.6b8b4567.f6@Amits-MacBook-Pro.local>
On 12/03/2014 18:13, "Amit Kumar Chaudhary" <amit@floatingpondtech.com>
wrote:
>
>Hi Alex, Belen,
>
>
>Thanks, that¹s where I have added it, pushed the branch to
>achaudhary/errors_warnings_ondashboard_v6.
Hi Amit,
This is looking good, although you don't need lines 95 and 113, since
there is already a $(document).ready(function(){}); block in the script.
You just need to paste the additional lines inside it.
Cheers
Belén
>
>
>
>
>--
>Amit Kumar Chaudhary
>
>
>
>On 12 March 2014 at 11:33:50 pm, Damian, Alexandru
>(alexandru.damian@intel.com) wrote:
>
>this is also a good solution :)
>
>Alex
>
>
>
>
>On Wed, Mar 12, 2014 at 4:03 PM, Barros Pena, Belen
><belen.barros.pena@intel.com> wrote:
>
>On 12/03/2014 15:10, "Amit Kumar Chaudhary" <amit@floatingpondtech.com>
>wrote:
>>
>>If not, the javascript code should be in the same file as the elements it
>>changes.
>
>
>FWIW, I have been putting all javascript code in static/js/main.js
>
>Cheers,
>
>Belén
>
>
>
>
>
>
>
>--
>Alex Damian
>Yocto Project
>
>SSG / OTC
>
>
>
>
>
>
next prev parent reply other threads:[~2014-03-12 18:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AK+VCmoAAG8gUxi9AQYk62sJbK4>
2014-03-07 12:26 ` toaster: review request for build dash board page Amit Kumar Chaudhary
2014-03-07 13:35 ` Reyna, David
[not found] ` <AKyVCmoAAJsFUxnLKgZOH0WH3co>
2014-03-10 13:31 ` Amit Kumar Chaudhary
2014-03-12 14:55 ` Damian, Alexandru
[not found] ` <ALCVCmoAAVwIUyB1bwf8Cgtv27s>
2014-03-12 15:10 ` Amit Kumar Chaudhary
2014-03-12 15:35 ` Damian, Alexandru
2014-03-12 16:03 ` Barros Pena, Belen
2014-03-12 18:03 ` Damian, Alexandru
[not found] ` <AK+VCmoAAGZtUyChnw2g9Wc6N64>
2014-03-12 18:13 ` Amit Kumar Chaudhary
2014-03-12 18:20 ` Barros Pena, Belen [this message]
2014-03-12 18:25 ` Damian, Alexandru
[not found] ` <AK+VCmoAAKpzUyCmtQTGVB7YOjI>
2014-03-13 14:13 ` Amit Kumar Chaudhary
2014-03-15 22:13 ` Reyna, David
[not found] ` <ALCVCmoAAGNbUyTQkw2GsRVYn2E>
2014-03-17 13:29 ` Amit Kumar Chaudhary
[not found] ` <ALCVCmoAAVslUyClbwlngif8v9g>
2014-03-19 11:43 ` Amit Kumar Chaudhary
[not found] ` <etPan.532982de.643c9869.100@Amits-MacBook-Pro.local>
2014-03-19 11:53 ` [review-request] " Amit Kumar Chaudhary
2014-03-20 12:10 ` Barros Pena, Belen
2014-03-20 15:49 ` Damian, Alexandru
[not found] <AK2VCmoAADpfUxdr5wtA/mUvrCc>
2014-03-06 11:12 ` Amit Kumar Chaudhary
2014-03-06 18:22 ` Reyna, David
2014-03-05 18:24 Wymore, Farrell
2014-03-06 14:40 ` Barros Pena, Belen
2014-03-06 18:36 ` Wymore, Farrell
2014-03-07 10:54 ` Barros Pena, Belen
2014-03-07 13:46 ` Reyna, David
2014-03-07 14:20 ` 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=CF465504.3F4FC%belen.barros.pena@intel.com \
--to=belen.barros.pena@intel.com \
--cc=alexandru.damian@intel.com \
--cc=amit@floatingpondtech.com \
--cc=farrell.wymore@windriver.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.