Please design the webpage with the generic font families in mind...
"serif", "sans-serif", "cursive", "fantasy", "monospace"

sans-serif which often will result in Arial or Helvetica is in my eyes the way to go...

Later on when the design is finished I don't mind if more special fonts are used. But that makes only sense when they are available on close to 90% of the systems.
This page might help to find out which will be most commonly available and its generic matches:
Code Style: Font code sampler for CSS font-family properties and Web fonts

Oke let me see : i download the complete source on my pc with svn .

i use ant to build phex , and iam able to start the new version ...........

so for your question , afcourse give me details on what to do and how to do it , and i have the time to create and upload new svn versions to the site or server ............let say once a week .

@king2: That sounds great!

@Gregor: Could you create a short description of the release process?
Is there a way to create special version numbers for weekly builds - i.e. using the date (2007-12-03 - yyyy-mm-dd)?

About the website:
I tested the website with the fonts, and serif seems to look good for me while sans-serif looks a bit too clumsy.

The for family I use is:
font-family: "URW Palladio L", Sylfaen, Verdana, "Lucida Sans", serif

- URW Palladio L 75.15% - comes from GNU/Linux
- Sylfaen 94.08% - Comes from Windows
- Verdana 93.04% - Comes from Apple/MacOS
- Lucida Sans 88.37%
- Lucida Sans Unicode 91.24%
- serif

-> I know that Lucida Sans is a sans-serif font, but it looks and feels right.

URW Palladio L looks best and is avaible on 75% of the systems, the others are good substitutes.

I hope that this improves the fonts quite a bit for all users.

My opinion is you spend way to much time with strange and complex font definitions.
I have really seen many great designed web sites, they are all based on very basic font definitions and I have never seen a single one with such strange font definitions...
But in the end I don't care if the page looks good ;)

There is no way yet to create special version numbers for weekly builds.

@king2: Though we can't do weekly builds at the moment, there's one very important thing you could do for Phex:

Set up a blog and write about the changes.

This is something Phex is seriously lacking: A source of up-to-date information for other people.

For example you could get information about changes from the subversion commit messages.

(links:
- Phex - CIA.vc
- Phex - P2P Gnutella filesharing program - Ohloh )

Also you could write about your experiences with Phex (but be careful not to do any illegal downloads or uploads (and even less write about them)).

What do you think?

Could you give the new design a glance, again?

I redid the transitions in the tab-bar and worked on the texts (i.e.: How to place the links, etc.).

The site isn't an "any user come in" page like LW (I can't beat them in simplicity - their website is great), but a site giving interested users information to get them to stick with Phex, going into a niche, LimeWire doesn't fill: Openness and friendlyness, along with offering people background information on everything stated there.

Phex - take back p2p

What do I still have to change to make it ready for users?