Yes, I was the only user at the moment, and yes, I haven't any credits, only from the old client and the team has been just around and waiting for me to switch over to the new client.

• A user joined your team
  
• He noticed a new button, offering to ask you to let him be a new founder and pressed it
  
• Then he left the team before you were able to take action
  
• You got to the transfer page and noticed that there was nothing to do because of what I posted above.
  
• You got puzzled and reported this, and helping us to improve the system by doing this.
  

So I think it's OK for everyone.

You know what is funny? By the time I got through this thread I had the idea to create a petition to have PrimeGrid release a Linux app. already. ;P

Since it looks like the work is the design property of Effect Web Media any changes should probably be done by them.

Sure I know xhtml is the new standare, but why fix something that isn't broken,m and work well?

which standard is the most appropriate for the BOINC web code

why is that? why use standards?

right, with very few changes, but the fact remains that it doesn't validate without those changes being made, and lets face it, they won't be made (nobody wants to maintain 2 versions of the same document)

and because the XHTML in it's unchanged state can potentially put the browser into quirks mode it's a bad idea to use it

shouldn't use internal style sheets when following best practices

by doing things properly (rather than relying on the browsers interpretation (including when to use which parser) then all these problems are avoided

i really don't see what you propose to do to avoid having to rewrite all your XHTML when you change from serving it as HTML to correctly serving it as XHTML because your scripts and CSS will break

• XHTML 1.0 Strict (which I am proposing) is backwards compatible with HTML 4.01. If the browser can't understand XHTML, it will parse it as if it was plain old HTML. So the point about only 20% browsers being capable to render XHTML is true, but others would fall back and render it anyway.
  
• XHTML is much better for screen readers.
  
• Content and design goes separately using CSS (ok, this is not exactly XHTML feature, but it is enforced by removing tags like <font>).
  
• XHTML makes (ok, it's supposed) pages look the same in all browsers since there is left no place for interpretation of the errors.
  
• I know <p /> is bad for separation. The best solution would be using css margin, but if David can't use anything else, this would at least not throw the browser into quirks mode since the code would be valid.
  
• IE fails miserably at XHTML 1.1 if it server with correct headers (not text/html). This is why I'm proposing XHTML 1.0 Strict.
  
• And the last but not the least - XHTML is current W3C recommendation.
  

You can view changes at PrimeGrid. I have not (yet) made every page compatible. For example, see http://www.primegrid.com/home.php (when you are logged in; if you'd like to validate, use direct input in the validator, because it will not parse the "logged in" page).

[edit] Oh, and I cannot edit the title anymore.
[edit] Changed the title. Thanks, Lee.

Thanks for the diff,
but XHTML conformance is not a goal - I like being able to use <p> as a separator.

@ poorboy (Rytis), ShuR

i'll be more than happy to help you out, especially since you are taking over Pirates vacated "space."

so, do us scuttelbutts from Rusty and th' cap'tn ship get preference tomorrow on account creation day? ;)

good luck with this project!

happy crunching
Micah

That Laptop should be able to handle 50,000 user's easily ... :/