|
Comments | |
|
|
|
|
|
39
|
 |
|
09-10-2004 02:44 AM ET (US)
|
|
| General comment |
|
Deleted by topic administrator 04-03-2005 07:53 PM
|
| Hi
|
38
|
|
|
09-13-2003 01:46 AM ET (US)
|
|
| Regarding item 2 |
|
Testing
|
| me
|
37
|
|
|
02-19-2003 08:35 AM ET (US)
|
|
| General comment |
|
cool !
|
| J
|
36
|
|
|
12-02-2002 11:18 AM ET (US)
|
|
| Regarding item 1 |
|
Edited by author 12-02-2002 11:20 AM
BATMAN... I say, did you say BATMAN?!
|
| Eve
|
35
|
|
|
04-13-2001 04:45 PM ET (US)
|
|
| General comment |
|
test
|
| iceJim
|
34
|
|
|
04-11-2001 12:36 PM ET (US)
|
|
| General comment |
|
Cool feature
|
| Dan Kalikow
|
33
|
|
|
03-26-2001 12:23 AM ET (US)
|
|
| General comment |
|
Hey! I reversed that, but it isn't a palindrome! I want my money back! :-)
|
| Trish Fish
|
32
|
|
|
03-25-2001 10:48 PM ET (US)
|
|
| General comment |
|
Akin a wiki. A wiki akin? What is a wiki a kin to? A wok, perhaps?
|
| Jeff Belden
|
31
|
|
|
03-24-2001 04:48 PM ET (US)
|
|
| General comment |
|
Brain-dead link.
|
| Steve Yost
|
30
|
|
|
03-23-2001 09:13 AM ET (US)
|
|
| General comment |
|
Actually this one's not a tricky balance of simplicity, etc. I just need to modify the parser to ignore all-whitespace-between-brs, and I haven't gotten to it yet :-)
|
| Dan Kalikow
|
29
|
|
|
03-22-2001 10:11 PM ET (US)
|
|
| General comment |
|
True. I've seen lots of strings-'o'-BRs in HTMLcode... Deprecable, regrettable, but yes, it's common usage. Especially strings-'o'-BRs separated by whitespace chars...
|
| Adam C. Engst
|
28
|
|
|
03-22-2001 08:23 PM ET (US)
|
|
| General comment |
|
I think the trick with <br> tags is that lots of HTML generation tools overuse them in place of proper <p> tags, so supporting them in some way is important.
|
| Dan Kalikow
|
27
|
|
|
03-22-2001 02:09 PM ET (US)
|
|
| General comment |
|
Edited by author 03-22-2001 02:10 PM
I'm one of the folks who's had the privilege of working with Steve Yost, suggesting features, UI twiddles, finding bugs and the like. I've run into this problem too, and have suggested some workarounds. At this writing, QTDR "correctly" handles <br><br> as a poor stab at a para-break. A single <br> is not comment-dotted.
Steve's well aware of this issue and is now generalizing the handling of <br>s. It's a delicate balance between KISS and allowing for flexibility for the more advanced user (or the user who mis-uses <br>s) :-) But I'm confident that the solution he comes up with will be simple yet powerful, hence elegant.
|
| Dan Kalikow
|
26
|
|
|
03-22-2001 02:00 PM ET (US)
|
|
| General comment |
|
Edited by author 03-22-2001 02:02 PM
This is a general comment on the doc as a whole. Same UI as for commenting on any particular Item #, but it (and any other General comments) get put into a different "bin" in the Comment Review... HTH :-)
But WAIT, don't order yet!! There's another DYNAMITE feature you get for FREE!! - The first time anyone enters a General Comment, a cute pair of QTDR sunglasses is put next to the leftmost option on the QTDR page...
|
| Dan Kalikow
|
25
|
|
|
03-22-2001 01:59 PM ET (US)
|
|
| General comment |
|
Not to be totally anal about this <G> but these comments are imho "General" rather than about Item #1 in particular. There's a way to get 'em labeled as such... and I'll do it now...
|
| Dan Kalikow
|
24
|
|
|
03-22-2001 01:56 PM ET (US)
|
|
| General comment |
|
Another of the recent "constant polishings" is the addition of user control over what HTML markup will receive "comment dots." It's a two-stage process: First the user decides whether to award dots to all [TD]s, [H3]s, etc.; then s/he can go thru the actual doc and decide which particular instances of the selected types of of markup will actually get a dot. There's some stuff in most docs that's "cast in stone" in any case -- e.g., a Copyright notice; no need to allow comments on that...
|
