Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-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 95FAF105BE for ; Fri, 6 Dec 2013 16:42:13 +0000 (UTC) Received: (qmail 60936 invoked by uid 500); 6 Dec 2013 16:42:12 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 60913 invoked by uid 500); 6 Dec 2013 16:42:09 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 60901 invoked by uid 99); 6 Dec 2013 16:42:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 16:42:08 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 16:42:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=vRsQklXp+hjM6K+lGyOh1IkIeOiNgApmz/40TvZfYzk=; b=Wz9BRSgVNZtRxEPe2QJ9Sr6eZGh0yMVl4sKl90f/HQqx4QNkd9eQPDk05KdcUvpG02JzeaZkn5W0TWNSeokJmAhxqdnBmqHqvP59ignBcvImq3ZhCw7U4gDXKgnVZQXeOCh9lDZB1i0g7y9KswZ9TpESrLLHbl6rqgz6KSr6gbY=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VoyTH-0007cB-LR for allura-dev@incubator.apache.org; Fri, 06 Dec 2013 16:41:43 +0000 Content-Type: multipart/related; boundary="===============8443821817274872710==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "Dave Brondsema" Reply-To: "Ticket 6958" <6958@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6958 Better ordinal options for install tool API Message-ID: <52a1fe440910d415c605b746.tickets@allura.p.sourceforge.net> Date: Fri, 06 Dec 2013 16:41:43 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============8443821817274872710== Content-Type: multipart/alternative; boundary="===============4073691153080018030==" MIME-Version: 1.0 --===============4073691153080018030== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit --- ** [tickets:#6958] Better ordinal options for install tool API** **Status:** open **Labels:** allura-api **Created:** Fri Dec 06, 2013 04:41 PM UTC by Dave Brondsema **Last Updated:** Fri Dec 06, 2013 04:41 PM UTC **Owner:** nobody The install_tool API doesn't have any options for setting the order of a new tool. (And the hard-coded calculation for 'ordinal' uses `len(installable_tools)` which isn't correct so the ordinal ends up kind of random). Options I think we should have: * last: make it last * first: make it first * alpha_tool: sort it alphabetically amidst the tools of that type already installed. I think it's fair to assume the rest of the tools are already sorted, so can just loop through them until you find one where the name comes later, and then insert before that. There are lots of possibilities, but alpha_tool is primary use case at the moment. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============4073691153080018030== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

[tickets:#6958] Better ordinal options for install tool API

Status: open
Labels: allura-api
Created: Fri Dec 06, 2013 04:41 PM UTC by Dave Brondsema
Last Updated: Fri Dec 06, 2013 04:41 PM UTC
Owner: nobody

The install_tool API doesn't have any options for setting the order of a new tool. (And the hard-coded calculation for 'ordinal' uses len(installable_tools) which isn't correct so the ordinal ends up kind of random).

Options I think we should have:

  • last: make it last
  • first: make it first
  • alpha_tool: sort it alphabetically amidst the tools of that type already installed. I think it's fair to assume the rest of the tools are already sorted, so can just loop through them until you find one where the name comes later, and then insert before that.

There are lots of possibilities, but alpha_tool is primary use case at the moment.


Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============4073691153080018030==-- --===============8443821817274872710==--