Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion Is Redmine a better Trac? What's gone wrong with Trac?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Christopher Lenz  
View profile  
 More options Jul 1 2008, 4:35 pm
From: Christopher Lenz <cml...@gmx.de>
Date: Tue, 1 Jul 2008 22:35:01 +0200
Local: Tues, Jul 1 2008 4:35 pm
Subject: Re: [Trac-dev] Re: Is Redmine a better Trac? What's gone wrong with Trac?
Hey Jeff,

On 01.07.2008, at 22:11, Jeff Hammel wrote:

> Also, if I wasn't verbose enough about it in the first email, I'd  
> love feedback on how to do anything I'm doing here better so that I  
> can write better code in the future.

When asking for patch review on the mailing list, including the patch  
inline would be helpful ;)

On the patch itself:

* What's the use case for configurable default query_args? Couldn't  
the default options for the query module itself be reused instead, if  
possible? Or just some sane default like all open tickets?

* The excluded_fields option refers to fields not included with Trac  
core. This should probably default to an empty list instead, if it is  
even necessary at all (note how I like to avoid adding config  
options :P )

* The option group should probably be just "ticket" instead of  
"autoquery"

* Don't use self.env.href, use req.href.

* The query_link thing is kind of brute force. Would be nicer to just  
use the **kwargs of req.href to construct the URL qith query string  
params. And it probably should be `query_link(owner=ticket.owner)`  
instead of `query_link('owner', ticket.owner)`. It would probably be  
possible to have query_link be just a partial binding of req.href.

* The template has two py:if="" directives that serve as if/else.  
Should be using py:choose instead.

On a related note, I'd prefer if the links in the ticket properties  
box (the yellow box) would be more subtle (I'm assuming they're the  
default red right now), possibly even only really discoverable on  
hover. Many pages in Trac have already gotten way to "linky"; at some  
point you end up with content where every second word is a red link,  
which is ugly and distracting :P

Cheers,
--
Christopher Lenz
   cmlenz at gmx.de
   http://www.cmlenz.net/


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google