Is it time to start regression testing yet?

[Jeremy Lavergne]

Most of that functionality can be embedded into javascript, which  
avoids putting all the work on the backend dev (C.Florian).

Additionally, there are plenty of people who know Javascript/jQuery --  
regardless of Ruby or PHP -- and can add it as a patch.

Just a thought.

On Jun 10, 2009, at 4:56 AM, Ian Eiloart wrote:

> Looks great to me. Some feature requests, from an MacPorts user  
> perspective.
>
> When I'm considering using MacPorts to help me out with a build, I  
> need to know whether it's going to succeed. The first thing I want  
> to do is search for a specific port to see whether it will build. So  
> these might be useful:
>
> 1. Sort the list alphabetically.
> 2. Instead of numbering the pages of results, give an alphabetical  
> index.
> 3. Include a search facility - perhaps it could call "port search",  
> so that I don't need to know the exact port name.
> 4. Include a category column, to help me find relevant ports. That  
> might help me to find the port even if I've got the name wrong, or  
> it might help me find an alternative solution.
>
> I guess that any of the above might help developers, too. They're  
> more likely to know the port name that they're looking for, but  
> right now it's hard to find anything :(
>
> Or, perhaps the results could be integrated at <http://www.macports.org/ports.php 
> >. Even if a port description simply had a link to the relevant page  
> on Florian's list. Ideally, behind some build status icon.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2435 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20090610/915973fc/attachment.bin>