I have an Perl/Tk client reading all the XML data including a more efficient access method (it gets the update times from the server then compares them to the dates for its displayed data and only gets new data if needed, though this isn't the final solution I have planned).
Yomi, I'm considering making a front-end to the player, market, and run listings. What's a good minimum refresh time for me to code for these (It's likely I'll have reasonable defaults, but I really don't want folks hammering the server with my client)?
I'd like to move over to the newer system soon, and would like some opinions on formatting for the static pages. Eventually we'll get better pages with settable persistant options but it's not looking like that will be in the near term. Send me a PM, X-Fire, in-game message, or reply as to what you think.
Message log - Liking the local time, run highlighting is OK except when people are shouting for uboros and phelg runs, lol.
Player list - Really liking this (uptime & guild listing). Would like local time and second chirikov's suggestion for player class
Market list - Don't use it, but really like the sortable table format
On formatting - if it's a trivial thing, would be nice to see all data in sortable tables. It could even be done much like the market list with a page combining playerlist and message log data (thinking off the top off my head so ignore if this sounds crazy . The page could have 3 headings (like the market list) Server Uptime, Player List & Message Log that expand into their respective tables. The 'Player List' table would then be list of all servers that you could sort by guild, server#, level, etc.
edit: also, liking the market list color scheme over the other two