[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Christmas gift



Il giorno Sun, 30 Dec 2007 14:49:45 +0100 (CET)
Andreas Tille <tillea@rki.de> ha scritto:

> On Mon, 24 Dec 2007, David Paleino wrote:
> 
> > Now it's up (follow the "Tasks page" link in the home) :)
> 
> After looking more deeply I have three "bug reports" (one normal
> and two wishlist) :) for this page.

Sure :)

> BTW, is the actual code that produces the pages in SVN?  I found the
> templates, but I did not found the code that does th real work.

Nope.
As for the other scripts in ~/scripts/, I fear some infinite loop when
committing in SVN. You're right though: the loop might happen only for those
scripts called by the post-commit hook. Scripts executed by cron wouldn't loop,
and they are safe to put in SVN. This afternoon I'll commit them :)

>    1) (normal) Not all Dependencies are listed.  For instance I'm
>       missing amide and aeskulap at
>             http://debian-med.alioth.debian.org/tasks/imaging.php

This is strange. amide and aeskulap have correct Depends line in the imaging
task file. This is weird to me: it worked perfectly some days ago :S.
I'll have to check this (probably not today, sorry :()

>    2) (wishlist) I would love to see some ordering principle in
>       the list of packages.  The static web pages are in alphabethical
>       order which might be easy to implement for the moment (even
>       if I'm not fully convinced that alphabethical is the best
>       choice).

Alphabetical is fairly easy; if we want different ordering we should implement
a "Priority:" field into the task files. And, for the moment, this seems
overengineering to me. ;)

We could also use PopCon values, but I don't know if they're easily fetchable
from the Net.

>    3) (wishlist) By using the DDTP translations we could work on
>       (partially) internationalized pages.  All those packages that
>       have translated descriptions could display these translations.

Uhm, this is more difficult.
The Python script generates static pages: they have a .php extension only
because of some include()s (the header and the footer are included). What
you're asking is generating translated pages on-the-fly basing on the browser's
localization: I'm not that good in Python ;) (I've started using / learning it
only here, inside Debian-Med).

One solution could be generating pages like:

imaging.en.php
imaging.it.php
imaging.de.php

and so on. That'd be simpler, far simpler, is it ok for you?

Have a Happy new year,
David

-- 
 . ''`.  Debian maintainer |  http://snipurl.com/qa_page
 : :'  :  Linuxer #334216  |  http://www.hanskalabs.net/
 `. `'`    GPG: 1392B174   | http://www.debianizzati.org/
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

Attachment: signature.asc
Description: PGP signature


Reply to: