 | | Re: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) What NNTP server do you use? I was under the impression that it was written in Perl itself. [...] (...) How about a different interpretation - // and ** (and don't forget __ for underlining) might not be interpreted the same as the {} and [] (...) (21 years ago, 2-Jun-03, to lugnet.publish, lugnet.admin.nntp)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) I think that might make more work for the user than is strictly necessary. If the server detects changes automatically (or if JS disabled the "Post" button automatically), then it eliminates a step. --Todd (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) Todd, I was justing post a blog when i thought of something (well, saw how the blog did it) - one the page where you compose the text, it has one button that says "preview". when you hit it, you go to a page with the text, but you are unable (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
Quoting "Brian H. Nielsen" <70401.2635@compuserve.com>: (...) The problem is, that if you have two buttons, one says "Post" and one says "Preview", people would assume they're in the same form. I know I will. You can put multiple forms on the same (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) People already deal with multiple forms on a page and are used to the fact that the button they click is relevant only for the data on that form. The current Message Preview page is layed out in a manner that clearly suggests it is 2 different (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) That part sounds great to me. (...) And this part also sounds great -- except for one thing: What if someone makes edits in the lower form, but then clicks the "Post" button in the top form? --Todd (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) I'll trust you on how other browsers work, you've got to maintain compatability. You can still accomplish forcing a preview before every post by removing the post button from the message edit form, leaving only the preview button. On the (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Do you have Lucida Typewriter? Try setting your fixed-width font to default to that...it's a bit easier on the eyes than Courier. (...) Well, the only consolation I can offer today is a promise that we're making movements towards CSS, which (...) (21 years ago, 2-Jun-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) I guess I don't see the advantage of this part, and I can't stand how when reading via the web it makes the listed posts look one way, and the posts themselves a completely different way. Plus, that fixed-width font is a killer on the eyes. (...) (21 years ago, 2-Jun-03, to lugnet.publish, FTX)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) I like that idea. In fact I could even implement that immediately without any CRC or JS. That's a great idea, Brian, thanks! The top half would have only a "Post" button (and the "E-mail me a copy" checkbox) and the bottom half would have only (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
