1024 pixel wide images

[peterh337]

Now that Photobucket supports and defaults (at last!) to 1024 pixel wide images, it is silly to limit this site to 800 pixels. Nobody is going to deliberately limit their Photobucket library to 800 wide just so they can post pics on Flyer.

[Keef]

They don't have to.

They can link to their 1024-pixel pix. I link to some of mine that are 1600 pixels (and sometimes more) wide. All it takes is use of the rimg (rather than img) function to fit the pix to the forum screen-size. I did post a tutorial on how to do that; maybe it needs to be repeated, or stickied.

Widening the screen limit to 1024 means either smaller text size, or the need to scroll from side to side. Neither is ideal for what is primarily a discussion forum.

[Propwash]

I did post a tutorial on how to do that; maybe it needs to be repeated, or stickied.

That would be handy, Keef, when you have the time. On the odd occasion that I post pics, I re-size a copy in Photobucket just for that purpose. If there is an easier, less time-consuming way to post that would be good.

PW

[Timothy]

What he said.

[Keef]

The Forum software is set up to display in a certain font size (with larger and smaller sizes being available for those who want to shout or whisper). That in turn sets up the appropriate size for pictures. If we were to adjust the maximum picture size to something else, then we'd have to mess around with the font size settings. The net result would be the same image on the screen. Lot of work, net effect minimal. No doubt the change would have other side effects, and someone else would be unhappy. So we leave it as it is, with 800 pixels as the width limit.

Hence if you go over 800 pixels using the "image" command [ img ], the PHP will cut off the rest. To prevent that happening, the forum system tells you when your pic is too large.

To avoid the need for resizing pix from elsewhere, the PHP also includes a "reduce image" function that will resize pictures on the fly. So if your pic is larger than 800 pixels wide, here's the easy way:

[ rimg width=800 ] <picture URL> [ /rimg ] (leaving out the spaces).

And hey presto!

Some of us (ie older forumites) like to sit back from our screens, so we have the display set to magnify. In my case, pix over about 700 pixels wide still scroll off the RHS of the screen, so I prefer using width=600. If there are some good pix that I want to look at, I hold down the Ctrl key and use the scroll wheel on the mouse to resize the whole screen on the fly.

That any help? If so, I'll put something similar in a sticky at the top of the Pix forum.

[Keef]

Here's an example:

A car I fancy looks like this at the maximum width of 800 pixels.
The code is [ rimg width=800 ]http://jillings.org/aviation/ah100six.jpg[ /rimg ]



If I reduce the width command to 600, it looks like this:


You can do the other thing with it, too. Here's a young lady of my youthful acquaintance in [ img ] tags:


and then in rimg at width 600


Any help?

[Propwash]

Any help?

Brilliant, Keef. Thanks.

PW

[Timothy]

That's great, Keef, thank you. Sorry I missed it first time, it would have saved me a lot of work.#

Next request is to include rimg in the editor tool bar, preferably including the width=800.

[Keef]

Thought about that, but decided not to go messing around in the PHP. There's lots to break, and the next software update goofs it all up again.
Simple instructions are easier. Most Forumites seem able to drive them, and the Mods sort out those who get it a bit wrong.

[SteveN]

Here's a young lady of my youthful acquaintance in

Mmmmmmmm! Do tell

[Timothy]

BTW, Keef, are you aware that you don't have to put in spaces if you click the "Disable BBCode" box?

[rimg width=800]<picture URL>[/rimg]

[Keef]

Yes, but I'm lazy.

[Timothy]

hmmm....

Your laziness is misdirected if entering eight spaces is thought to be less effort than clicking one checkbox.

Must work harder at laziness.

[Keef]

Most times I post about rimg (and other) tags, I also include a picture (etc) to show the end-result. Disabling BBCode rather spoils the effect. Anyway, I can type spaces quite quickly whereas finding the mouse and scrolling down takes a conscious effort.

This discussion has now used far more energy than the spaces did, and I'm off down the road for coffee with the local chicken farmer.