John, the regex works too well in Homesite. It's also flagging the stuff inside the anchor tags, so there's way too much clutter on a search (even setting the length to 100 gave me 111 hits), and if I let it go ahead and replace, it'll break every link in the file. I had an idea though. I still have the text versions of the threads that I was using when I was compiling the stats the other day, so I can either try the regex on them, or I can dump them back into Excel, and sort on line length, which gives me what I need.

Should be Wednesdays, now.

Fixed.

Kisses and hugs to all the stompies and various people doing work on this. Several posts up there are entirely nonsensical to me, but go y'all!

t edited becuase I decided it was all too much like bureaucracy crap that didnt' so much belong here.

A little detail nit: The text on the bookmarks.php page reads

To delete a bookmark, click on its checkbox and then OK.

But the button says "Delete", not "OK". Also, the code for the button doesn't have an alt attribute.

For the sake of consistency and usability, can we change the text to say "click on its checkbox and then Delete", and add alt="Delete" to that INPUT tag?

Heh. I was trying to clean out my bookmarks today, too.

Some day, far in the future, when there's nothing at all better to do (including lying down in fields of flowers) it would be nice if we could delete the book mark from the page where the post lives. You know, when you click mark and then months later, go to check out your bookmarks and click on the book mark, get to the page, and realize you don't need it bookmarked any more. If we could click on what now reads marked to unmark the post, it would be handy.

Or I could just be more reasonable in my bookmarking in the first place.

If we could click on what now reads marked to unmark the post, it would be handy.

That's a good suggestion Cindy. Similar to how I suggested handling the MARCIE filter.

'Unmark' link on the actual post page, instead of 'Marked'. Now on the requests list, Cindy.

I think I asked my last question too subtly.

Can Jon or ita tell me what a threadsuck form submission would look like, transformed into a clickable URL?

This is so that it can be downloaded directly to disk rather than having to load a megabyte-sized web page into the browser window, then save it. Which sometimes crashes my browser and locks up my computer for a long time.

ita would have to answer that one, John. In my spec, all the parameters were in the URL but she did some PHP magic to hide them. I don't know PHP well enough to know how you'd do what you're asking.

I think that the direct download thing is a good idea, though.

In my spec, all the parameters were in the URL but she did some PHP magic to hide them.

I think what she did was change the form's method from "get" to "post", for the record.

Any form can be reverse-engineered quite easily -- it's how I wrote that autobrowser which we used to stress-test the board -- you just find the name and value pairs in the fields and make them into a query string.

<form action="something.php">
<input type="text" name="firstname">
<input type="text" name="secondname">
</form>

just becomes

something.php?firstname=John&secondname=H

when filled out and submitted. If the method is GET, then you see it. If the method is POST, you don't.

However it may just be that the script will not accept a GET-type request, only a POST.