You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I am thinking of is... to identify the thumbnails in bulletin boards that are linked to the full version of the image for imageshack and sites like that.
in gaming-BBs there are often screenshots which I liked to see them in full just hovering over the thumbnail with my mouse.
The text was updated successfully, but these errors were encountered:
Sometimes users embed the full size image, but the bb-software limits the size, as specified by the admin:
(img style="width: 555px; height: 416px;" src="http://img715.imageshack.us/img715/8758/1217232012.jpg" alt="Bild")
There you get the url for the image without any complications.
Using directupload.net the code looks like this:
(img style="width: 160px; height: 132px;" src="http://s5.directupload.net/images/110121/temp/bsv6vsmo.jpg" alt="Bild")
Just strip off the "/temp" from the url and you get the full size image
Sometimes users use the attach file method for images:
(img style="width: 555px; height: 416px;" src="./download/file.php?id=767" alt="1_10_19_42_19.jpg")
Next one is an example where the user had uploaded the image to the gallery board associated with the game:
(img style="width: 555px; height: 419px;" src="http://file.gamescampus.eu/ShotOnline/Gallery/1_25_23_14_53.jpg" alt="Bild")
Same as above, it is only size limited by the bb-software, just get the plain url...
These are the first, but I can look out for more if you like.
Edit: changed <> to (), was wondering the html-code was really interpreted instead of just displayed as text.
What I am thinking of is... to identify the thumbnails in bulletin boards that are linked to the full version of the image for imageshack and sites like that.
in gaming-BBs there are often screenshots which I liked to see them in full just hovering over the thumbnail with my mouse.
The text was updated successfully, but these errors were encountered: