From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 77D6AE008DD; Mon, 16 Mar 2015 04:24:15 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.212.180 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id C43A1E00712 for ; Mon, 16 Mar 2015 04:24:13 -0700 (PDT) Received: by wixw10 with SMTP id w10so28353647wix.0 for ; Mon, 16 Mar 2015 04:24:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0j7gzRK8iaMBPUO/z7k9AdCtmbbCejtDTLkg8YTd6aQ=; b=ZqZnFCLKIMCCV9D4VT3L6f3JvOwkHwUSPxxV1IBu2mrpQEWR8Xl6aNyTD5TXu1OvPF Sj09IDzBmMkT0Eg7fR2Rfqargs1pba6cgf7iavspsFoSDi1d1ayzAEUBFuHAT/ZcJkZX fEK85XmxVdrHVB7rKaC9P7NsYZxclv5Y2M95GK1CoCIfk1t2u16vrkFOLE6y1cVH2LwC OIoAQ9mJPGgVMN5QLfcz/yPOBm6/5XiXTSWt6J5C6nSsX89ieiNLPONWVPOFcn/O2DJG 0xxqD2/uzp8+gr9lAVsfSNDT+YdW8zmidruEb2huojalpEZVpmDmPAzcYEGnkG/FyPD1 Q0Ww== X-Gm-Message-State: ALoCoQkc8QebXBFBeHjp1NM9H4VG56kx6IR+kK4atit67hxEcVdhS4X9rBOQgV/sLEbLNr0UpYpz X-Received: by 10.194.76.146 with SMTP id k18mr27078128wjw.115.1426505052146; Mon, 16 Mar 2015 04:24:12 -0700 (PDT) Received: from [192.168.2.82] ([83.217.123.106]) by mx.google.com with ESMTPSA id u18sm14936621wib.1.2015.03.16.04.24.11 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Mar 2015 04:24:11 -0700 (PDT) Message-ID: <5506BD5B.2080904@intel.com> Date: Mon, 16 Mar 2015 11:24:11 +0000 From: Michael Wood User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "Reyna, David" , "BARROS PENA, BELEN" , "DAMIAN, ALEXANDRU" References: <5E53D14CE4667A45B9A06760DE5D13D0778817CB@ALA-MBA.corp.ad.wrs.com> In-Reply-To: <5E53D14CE4667A45B9A06760DE5D13D0778817CB@ALA-MBA.corp.ad.wrs.com> Cc: "toaster@yoctoproject.org" Subject: Re: Questions about date range function X-BeenThere: toaster@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Web based interface for BitBake List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2015 11:24:15 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit What about a bootstrap plugin such as https://github.com/eternicode/bootstrap-datepicker for the date picker? Michael On 16/03/15 06:47, Reyna, David wrote: > Hi Belén, > I have the date range selectors working now for Toaster-1.8, with > just a few remaining requested enhancements in progress. To that end > I had a few questions. > 1) How persistent do you want the date range values? > Do you want them just persistent to the page, in other words revert to > dateMin and dateMax and you leave and return to the page? > Or do you want them persistent to the session, in other words > preserved in the cookie stash? > 2) To get the Datepicker to work I will need to restore > “toastergui/static/js/jquery-ui.js” file. This file was apparently > removed since Toaster-1.6. > I will mention that this file is 436 Kb in size, and will overwhelm > any patch file submission. Should I commit this file in a separate > patch? Or is there another way to get it back into Toaster without the > overhead? > BTW, I do not think that there is an easy way just to push the > Datepicker code from “jquery-ui.js”, without hacking and risk. > 3) For the dateMin and dateMax, it would appear that I need to > instantiate the build table in the view in order to sort it by the > “started” and “completed” fields. > Should I perhaps avoid a second sort for “completed” by using the > minimum “started” date as dateMin and perhaps the maximum “started” > date plus one as dateMax? The build tables are small now, but they > could conceivably be quite large, and these values should nicely > bracket the actual dates. > Thanks, > David > >