An important issue was raised; I've been making quite a few changes to the skin, and while you, the community of SEN, have been awesome about reporting bugs when you see them, I haven't been asking you too much about the new features I've been adding. Here's my first attempt at changing that, by seeing which you prefer: the old fullview or the new.

Note that both have an important flaw of their own, so you may want to read this post. And for those who've forgotten (somehow) the differences between the two, I've also described how each fullview work(ed/s).

Old image fullview.
Large images in posts and private messages are shrunk to about 400px, and given a thick grey border. When you click such images, the page is hidden, and the full picture is shown. If it's bigger than your screen, it gets clipped, and you can scroll to view it. You could scroll using the scrollbars on the window or by clicking in your mouse wheel and moving the cursor. When you're done, you would click the image to get back to the page.

This, unfortunately, had a few disadvantages, especially in Turtle. Turtle introduced a bug where a thin strip of space (anchored near the right edge of the window) would act as a small "invisible wall" for the mouse. If it covered up an element and you tried to click on that element, nothing would happen. The bug is still here (though it's about to be fixed, now that the old system isn't in use), and can be extremely annoying when trying to interact with textboxes, links, etc..

New image fullview.
A large image is shrunk and bordered like before. Clicking it opens it in a fancy modal dialog (resembling those that appear when interacting with the buttons on the BBCode Console while posting); this modal stretches to mostly fit your screen. The scrollbars are on the modal, such that its buttons are always visible.

The modal has "Previous", "Close", and "Next" buttons. You can use the "Previous" and "Next" buttons to "travel" between all fullviewable images on the page. The modal can be closed by clicking the image or by clicking "Close". As soon as a certain script update is added to the site, there'll be another button that allows you to make the image shrink to fit the modal (and hence the window). This turns the fullview modal into something like a "middleview": the image is larger than before, but small enough to still fit in the window.

This script has the disadvantage that you cannot scroll by clicking in the mouse wheel and moving the cursor; this scrolls the page behind the modal. You must use the scrollbars.

If a good number of people have voted in favor of the old system, I'll, with Dev's permission, give him the files he needs to revert the site back to that.

Use the new one you made, but don't put a border (Like it used to be.) Make all the buttons appear at the bottom of the page. If possible, do something like Google image where if the picture is too big, it will be resized to fit the screen, if you click on it, it puts the image to it's real size and the other way arround.

I also like the new view. With the new one I can just click the image, then click close when I'm done viewing. It's great

Just. Link. To. The. Image.

All this fancy schmancy JS crap makes it more difficult to navigate IMO. Browsers have built in methods for viewing images. I just remembered that the resizing is client-side so I can right-click and use "view image" to get my desired effect. Anyone else who hates the frames can do the same.


But... the old one did the same thing...

I prefer using the old system, since it was quick and easy; one-click was simple and intuitive. New system is pretty annoying, especially on mobile devices that don't really have the ability to directly view the image.

Maybe you could put more work on your plate and let users decide which method they would prefer to use by default in their UCP. (Though I would definitely be selecting the old method. IMO, new system is wishy-washy.)

"One-click"? It's still one-click -- click the image to fullview, click it again to close. The "Close" button is just for newbies who may be a little slow.

Up to Devourer. If he can script SEN to write settings as classNames to the BODY tag (or something similarly easy for a script to detect), I can edit the JS to detect what's been picked and run the appropriate scripts.

(Actually, it may be cleaner to reserve a single hidden element and write classNames to IT... and keep the BODY tag uncluttered. I can handle that as well. Point is, Dev needs to be able to translate settings to classNames on an HTML element for me to do something like this.)

This.

I don't need a border taking away parts of my screen when I want to enlarge a picture.

Also middle mouse click and then scroll-dragging by moving the mouse is so much more convenient than using scrollbars: You have to look away from the picture to place the mouse over a scroll bar, scroll roughly to where I want to go, then again move my eye away from the picture to find the other axis' scroll bar and again scroll, just to find that I scrolled too far with the first axis, so I have to look away from the pic a 3rd time to finally see the spot of the pic I actually wanted.
Just let me drag it with the mouse. Thanks.

Having a close button is entirely unnecessary when the whole picture is a big back button on the old method.

Those prev/next buttons are neat, but I wouldn't use them nearly often enough to justify all the other disadvantages.

There should be an "I don't like both" option. Heres a quick pic I threw together showing how it SHOULD be. Yes, it may be old school but it works very well.



Edit: Also, if people say that it will be annoying with the thumbnails border above it and a border below it (due to the signature) just remove the border above the thumbnails. It'll still look good.

What you suggest is pretty much the old system, no?
Except that it opens a new window, which you can do with middle mouse click anyway.

Well, it depends on what you call "old" The system we used before this update was not AS bad as the one we have now but it was still ugly.

Also, my middle mouse button does not function anymore when you click it. It scrolls but it's click function doesn't work. I understand this is my problem but still... I should be able to just left click it, view the raw image, close the tab and continue browsing.

You cannot do that, either with the new or old systems. It is JS and not a link so it is ignored.

I'm posting from mobile safari right now and I can confirm that the picture modal is anchored to the top of the screen rather than being displayed over your current screen position.

I can confirm that this is Mobile Safari's fault for not supporting position:fixed. Browsers that support position:fixed mean that the modal scrolls with you, such that it would be on the current screen position.

I could maybe try to code detection for mobile browsers (essentially compensating for any broken position:fixed support), but testing that would be a major bitch, seeing as I don't have one...

I'll say it again.

The old version was better than the new version.

The new version would be better IIF it resized the image.

I coded exactly that feature and sent the JS file to Devourer. No clue why it isn't up yet. D:

You could with the old system. Middle click for new tab or left click for enlarge.
When it was enlarged you could only left click to close or middle mouse drag-scroll.

It was ugly, but efficient.

I could never open new tab with middle click on those.

Hm sure? I can't test it anymore lol

Anyways, then make it so that we can.

Using the middle mouse button with JavaScript is impossible IIRC. JS can only register left clicks, and thus to allow us to open a new tab with middle click, the image must also have a link to it.

But having a link breaks the left-click behavior, because the JS will try opening a modal while the browser, upon registering a click on a hyperlink, will try opening a new page/replacing the current page with the image.

A much better solution: stop framing images to 429 pixels. It doesn't slow down users (you download the full pic anyways), scroll-wheel navigation stops breaking, and it allows people to use banners for their topics without cutting them up to 400-pixel wide chunks. Images that are too large can just be framed OPTIONALLY by the user. Sometimes when we want to post images, we want them INLINE, not forcibly resized with a shitty "nearest neighbor" downsampling algorithm built into browsers.

No, I like the resize. Granted it would be better to just click 1 time to zoom to screen via a preset size limit in your profile settings, then click again to zoom full size, without bringing up anything fancy/hiding any text. fuck, you can make a greasemonkey script to do that with ease.

As for viewing full size in a new link, I know it's not all that nice nude, but you can right click -> middle click on view image.

I still vote for at least having an option to NOT resize any images, or to at least set an upper bound in our profiles above which the image will be resized.

For instance, say I wanted to post these images:





Are they better off resized? No. Anyone claiming otherwise is just arguing for the sake of disagreement.