Dai, the search function is in beta, which is why it isn't on every page yet.
Jon -- strlen($tagline) will count the number of characters in the string.
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Dai, the search function is in beta, which is why it isn't on every page yet.
Jon -- strlen($tagline) will count the number of characters in the string.
it seems like it wouldn't be to difficult to code with PHP, if I knew how to use that function
that would be the strlen() function, and it's just
strlen(whatever)
but the good thing about the JavaScript version is you wouldn't need a hit on the server to get the answer, it would come up instantaneously in a dialog.
After all, you can see if it's over the set length by submitting the form and seeing if some of it disappears.
Anyway, see [link] for the idea in action.
I see. All right then, I'll wait until the kinks have been dekinked. And if I've sounded ungrateful, believe me I'm not.
Jon -- strlen($tagline) will count the number of characters in the string.
Excellent. Let me work on it (unless someone else wants to...?).
Anyway, see [link] for the idea in action.
That's sweet, John. Very elegant. Let's just make sure the anti-javascript contingent doesn't have a problem with it, and I'll add it in.
As long as nothing depends on the JS (ie, the PHP code still counts the length of the tagline and spits back an error message (which still means a hit on the server, but it's an error -- it should be reported)), I have only the most transparent of principle objections.
The problem with JS tends to be that people use it for actual important functionality, and don't provide alternate methods to do the same thing. This is a minor piece of frippery, and not anything anyone needs to use the board, so although I think JS is a mostly-bad idea, I don't see any problem with this except the question of where it should go on the edit profile screen so it'll be clear and not cluttery.
ETA: ita and I have much the same general sentiments about Javascript, just phrased differently.
Let's just make sure the anti-javascript contingent doesn't have a problem with it
The trick is that the button itself is written with JavaScript, so, by definition, anyone who doesn't have JavaScript will never see it.
I haven't tested on Netscape and Mozilla and whatever. What did you look at it with?
Oh, and ita, would anything weird happen on submission of the form, now that it's got a new input? I don't think so, but we could always make it a text/image link, not a button, if that was a factor.
John, as long as none of the original elements are altered, the form should be just fine.
I don't see any problem with this except the question of where it should go on the edit profile screen so it'll be clear and not cluttery.
I like John's placement on his sample page: [link]