Mac, and Opera 6 C? Does that make sense?
This is what the version infor says:
Version information
Version
6.0
Build
1003
Platform
MacOS X
System
10.2.3
Partner
Java
Java 1.3.1 Plug-in
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Mac, and Opera 6 C? Does that make sense?
This is what the version infor says:
Version information
Version
6.0
Build
1003
Platform
MacOS X
System
10.2.3
Partner
Java
Java 1.3.1 Plug-in
Gentle suggestion: move "About this site" above "FAQ" on the home page. It gives a nice introduction and defines some of the acronyms that the FAQ launches into but doesn't define until later.
Good call, Java.
In fact, more to the point, if we replaced "Read the FAQ, then join in" on the front page with "Read About This Site, then join in", that would resolve all my issues with the fact that the FAQ is long and obscure.
Or perhaps just make that sentence less of an imperative? A person I wanted to introduce here was a bit frightened off by the FAQ, and was only reading it because it unequivocally instructs newbies to read it first before you join in.
I hope she didn't come by during the Tourette'sSyndrome!Rio period...
I was looking at the "About this site" page, and I noticed that the credits include Michele T's, Tom W's, and Jesse's last names, which none of them use over here. Are you guys (Michele, Tom, and Jesse) comfortable with that?
Also, my name shouldn't have a space in it.
Good point, DX. I'm assuming they're not and I fixed it.
You da man!
I've been thinking about the requests/complaints about the posting font. I'm pretty sure I could write code that would allow a user to override that font with his/her own choice of face and size. I'd put two selection boxes in the Set Profile page (one for font face, the other for size). If they're filled in, There would be an extra couple lines of code at the top of every page that would redefine the default style. I should probably do the same for the fixed-width font style so that they stay consistant.
This would require adding a text field to the user class. Let's call it "css" or "custom_css". Length 255 would be sufficient.
ita - Is this a project I should take on? If so, can you add that field to the user array?
Before we start on anything, we should get a list of all outstanding requests, and stuff that's been partially implemented. I can say up front that I'm absolutely terrible at that sort of listkeeping. But right now we have competing code trees, and I'm way out of touch on what's considered priority.
Then we can get back into mods. And hopefully in a less ad hoc way, with actual releases or somesuch.
Sounds good. The only things I've got outstanding are the threadsuck utility and the list-userids-and-emails thingie. Are there others?
I think the ability to view 10000 posts at a time covers threadsucking, though I haven't tried it.