Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84100D214 for ; Wed, 19 Sep 2012 18:38:41 +0000 (UTC) Received: (qmail 81760 invoked by uid 500); 19 Sep 2012 18:38:41 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 81735 invoked by uid 500); 19 Sep 2012 18:38:41 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 81726 invoked by uid 99); 19 Sep 2012 18:38:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2012 18:38:41 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates 209.85.220.175 as permitted sender) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2012 18:38:36 +0000 Received: by vcqp1 with SMTP id p1so1558281vcq.6 for ; Wed, 19 Sep 2012 11:38:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/Z7BOdfPZ79EbDG7QSmHyVNXw9S7ZhBBFTOWv0v7mZk=; b=IA07CWpyeP4XNaldXQjpqbmRYbo+VwiPl9MFE55V+2OyNxUbhXOGkQBQsTpF7Qw5/X TYf9SbcRGRDecDj7zNu8e9+Leu+BRaWpjIfWcyRsvo2qxbyeMwzzJp86sX4vFtkrGI6q Wtf9gngUoGU2legucL2Hofy+iuoRuow0F/3t123WpInNV8WR53bq9VztGl71djjJGVI0 rw8x5SK6ngL/jgE+BTjLxjncRmVmWM9Wk8Aq1xqGG74dFgqmryGxKQSZ8hsdjONK0hc4 v4r5Zu5Vr5bhHuBplPGR//vilesgMz22mvSdfgyAEAAiXVMFWUE3STuRn2YTYZZXzvPE N9Rg== MIME-Version: 1.0 Received: by 10.52.37.100 with SMTP id x4mr1958564vdj.56.1348079895897; Wed, 19 Sep 2012 11:38:15 -0700 (PDT) Received: by 10.58.79.177 with HTTP; Wed, 19 Sep 2012 11:38:15 -0700 (PDT) In-Reply-To: <5059FD38.3020105@wandisco.com> References: <058.556d561ac8118c74aff2b0380f421667@incubator.apache.org> <073.4e66acd1d3eab58cf63112d9a398a95c@incubator.apache.org> <50599857.30602@wandisco.com> <5059AB01.60704@wandisco.com> <5423CED3-7E10-48CB-B445-937F444457D4@wandisco.com> <5059FD38.3020105@wandisco.com> Date: Wed, 19 Sep 2012 13:38:15 -0500 Message-ID: Subject: Re: [Apache Bloodhound] #187: Remove row count and results pagination from Dashboard From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 9/19/12, Gary Martin wrote: > Interesting. In that case, I will suggest that we always attach patches > to tickets and refer to them as you have done here. For the smallest of > patches, you can also choose to paste the text directly into an email - > or indeed into a ticket comment as I did recently for #204. I will put > this into a wiki page shortly. > > As for the patch, it looks like good work to me. Unless anyone else > notices any problems I expect to commit it a bit later tonight. > hmmm ... I'm hoping any of my previous comments be considered . IMO we shall not remove pagination . AFAICR there's an option for that ... AFAICR in #80 I submitted a patch (... pending or already committed I don't recall now ...) adding options to render Bootstrap pagination in reports web page and built-in smaller pagination in widgets (considering Joachim's suggestion ;) . Maybe we can follow a bit further and parameterize page index visibility in query and report widgets on top of the work made in there ... About patches . I have the habit of including them in one of two forms 1. {{{ #!diff }}} 2. Attachment having a name of the form t_r_.diff both ticket number and changeset ID are useful to know whether the patch needs to be updated before applying it , and also to tag the exact version modifications were tested against . This is a practice inherited from Trac-dev itself so we might just include a link to their patch submission guidelines wiki page or start from there and customize it for our own usage . -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: