MySpace regularly changes the id of the default table, which is why in 1.7.52 I added

document.getElementById('photo_list').getElementsByTagName('table')[0].style.display = 'none';

to make the script independent of that change.

Are you using 1.7.52?

Thanks. MySpace changed a few things around with how the comments work, so right now I can't really do that. It used to be able to show all the pages of comments, with the total as well, but I'm still working on fixing it.

I think it's annoying that I can't see all the comments anyways, so I'll definitely get that working.

haha.

thanks.

:]

thanks, guys.

and i'll try getting the comments to work correctly soon.

I went ahead and got PicLens to make sure its works.

My script and PicLens both work perfectly independent of each other, just the way it should be.
I cannot edit anything on the PicLens interface as a greasemonkey user.
It's just not possible.

I cannot create a button to just launch PicLens on demand. To view the current album in PicLens, simply go back the album selection page, hover over the album cover image, and click the little PicLens logo that comes up. I could, however, create a link on each album page that lead to the same exact page...the one you're currently viewing. That would force PicLens to put there little logo on it, so you could launch PicLens. However, this link would be completely useless to any other viewers. So, what I can do, is make it an option, like blkout! suggested, to put in the useless link.

This will be included in the next update.

ok. I've finished new photos, DTA, and fixed the settings thing, but now comments are broken.

is anyone still getting photo comment to show?

@blkout!

I use PicLens, but with it you can't see comments or anything like that. I would add a button to launch the album in PicLens, but that button would be useless to people not using it.

@InsaneNinja

Thanks for the comment, and sorry it took a while to respond. I'm away from home for a while.

Anyways, here it goes. The new photos thing wouldn't be that hard, just ineffcient because the script reads from an xml file that doesn't include that information. The xml just loads faster than each individual photo page. It wouldn't be horrible to just wait until everything is done, then go back and see if the photo is new.

I haven't used DTA!, but it clearly should be implemented. Do the links have to be located anywhere specific, or is the bottom of the page fine? Also, does each link need to be styled to be hidden, or can i just stick em all in a hidden div element?

The small-medium-larger thing is a brillant idea. I guess its just hard for me to think like a non-geek. lol.

And I'd like to think that a revert button wouldn't be necessary, but there are always those cases.

Thanks for everything, I will definately get these into the next version as soon as I can.

Thanks for the feedback.

For the first issue you mentioned, I think I found an okay compromise: by using the small-sized images instead of the medium ones, the thumbnails can stay in a grid pattern as well as not lose much to cropping. I know that several times the cropping can be awkward.

Here's a preview. Tell me what you think.

as opposed to [current]

As for the second issue, the script might only be able to retrieve "new photo" information from the first page, but it would be handy nonetheless.

Thanks again.

To search through the comments, the script would have to bring up each individual comment page for each photo, which would take quite a while. Unless there's some secret xml database for photo comments the script can access, searching through them is not practical.

Note that the script doesn't look for comments until you select a photo. Otherwise, looking for all the comments would be a bit too request-heavy.

It hasn't been working for tagged photos since 1.6. That particular update sped up finding the pictures, but sacrificed compatibility with tagged photos. I'd right another part for tagged photos, but it doesn't seem too practical because you can't see the people who've been "tagged".