+- Southperry.net (https://www.southperry.net)
+-- Forum: Main (https://www.southperry.net/forumdisplay.php?fid=11)
+--- Forum: Site Announcements (https://www.southperry.net/forumdisplay.php?fid=18)
+--- Thread: Transition Q&A (/showthread.php?tid=27307)
Transition Q&A - Jon - 2010-07-07
TøbiasBlack Wrote:not at all.Text before spoiler.
here, all use this to explain what i mean:
-snip-
what is in bold, and in italics, gets moved.
so say that, within the spoiler, theres text underneath the image. that is affected.
but the text outside of the spoiler, after the image, is also affected. what comes before the image is not.
Spoiler
Text after spoiler.![[Image: sandpapery.png]](http://dl.dropbox.com/u/4686946/sandpapery.png)
Hmmm. Odd. It scrollbar's the whole post. I thought it just scrollbar'd the spoiler. o_o
Transition Q&A - Eos - 2010-07-07
What jon said was correct - Your entire post is considered a single window as it were. If you do anything to expand part of your window beyond the normal limit means that the entirety of the window gets scrollbars.
Same with a quote, if you quote something the quote creates a window in your window, and everything within the sub window is confined to your window, which should not have to scroll itself because it's already got a container in it.
Transition Q&A - Rob - 2010-07-07
I was wondering if instead of scroll bars we could have that feat that expands images when you click on them, and it has like a 800x600 px image size limit.
Transition Q&A - shroum - 2010-07-07
Rob Wrote: I was wondering if instead of scroll bars we could have that feat that expands images when you click on them, and it has like a 800x600 px image size limit.
I second this. Its much easier and better then having to scroll around. Also I've seen on other websites it leads to an album where you can click next and basically see every picture on the thread.
Transition Q&A - Eos - 2010-07-07
Rob Wrote: I was wondering if instead of scroll bars we could have that feat that expands images when you click on them, and it has like a 800x600 px image size limit.
Considered and rejected for now.
Images are inline elements, what you've asked for would require them to always be treated as block elements, and would break the ability to scatter little images through your text, like the emoticons for those who want to use their own emoticons, or show pictures of character avatars, or all of Fiel's extraction images.
Creating an entirely new class of image and making everyone differentiate whether their image was one type or the other and then policing that would be a massive nuisance.
Making the post containers explicitly retain their dimensions is so far the practical option. Gigantic pictures aren't really a common area of focus for the site, the smaller icons and whatnot are far more prevalent.
Transition Q&A - Rob - 2010-07-07
Well, Spaz has this feat in his Super Sword Action forum, and it behaves perfectly with Opera and Firefox 3.6
Transition Q&A - Eos - 2010-07-07
Eosian Wrote:The customizable version of it will show up later.
This is functional now.
Examples:
[header]Default/inherits from style[/header]
[header="bgcolor=silver;color=green;"]personalized[/header]
If you only provide partial info to the personalization the defaults are black background and white text and will overlap the pieces you omit.
[header="color=green;"]personalized[/header]
[header="bgcolor=purple"]personalized[/header]
[header="bgcolor=yellow;color=blue"][SIZE="5"]
Really really customized
[/SIZE][/header]Syntax:
[noparse]
[header]plain[/header]
[header="bgcolor=silver;color=green;"]personalized[/header]
[header="color=green;"]personalized[/header]
[header="bgcolor=purple"]personalized[/header]
[header="bgcolor=yellow;color=blue"][SIZE="5"]
Really really customized
[/SIZE][/header][/noparse]
Transition Q&A - Rob - 2010-07-07
[color="#000080"]
Eosian Wrote:I'll consider it, but it doesn't behave well with all browsers.
Considered and rejected for now.
Images are inline elements, what you've asked for would require them to always be treated as block elements, and would break the ability to scatter little images through your text, like the emoticons for those who want to use their own emoticons, or show pictures of character avatars, or all of Fiel's extraction images.
Creating an entirely new class of image and making everyone differentiate whether their image was one type or the other and then policing that would be a massive nuisance.
Making the post containers explicitly retain their dimensions is so far the practical option. Gigantic pictures aren't really a common area of focus for the site, the smaller icons and whatnot are far more prevalent.
Is this really so? I thought there was an easier way to do this. Oh well. The headers are looking sweet now, grats Eos. [/color]
Transition Q&A - Hazzy - 2010-07-07
imjon Wrote:Text before spoiler.SpoilerText after spoiler.
Hmmm. Odd. It scrollbar's the whole post. I thought it just scrollbar'd the spoiler. o_o
I wanna see what his image does to my post when I quote.
I have to say the scroll bar is more annoying than helpful. If an image is spoilered, there's no need to scrollbar it. :|
Transition Q&A - Eos - 2010-07-07
Rob Wrote: [color="#000080"]
Is this really so? I thought there was an easier way to do this. [/color]
The image resizer code being used on SSA is client side javascript that gets processed after the page has already rendered.
I don't much care for that because it means your perception of the sites rendering speed becomes even more dependent on your browser (and that scripts) behavior than the actual site's performance, and anyone without javascript enabled here wouldn't see any benefit of it.
I'll continue to consider it and possibly put a vote about adding that a secondary option on top of the CSS change I made so that the only time people would see the scroll bars is when they weren't allowing JS or had overriden it's settings.
Hazzy Wrote:I have to say the scroll bar is more annoying than helpful. If an image is spoilered, there's no need to scrollbar it. :|
The container has no way to know the image was spoilered, all it knows is that something is trying to display beyond it's boundaries and that's not allowed to happen, so it makes scroll bars so you can see the whole thing. I could change it to clip instead of scroll, but that's even more annoying. What it really needs is a resize to fit option but that's just not something the current standards support.
Transition Q&A - Rob - 2010-07-07
[color="#000080"]
Eosian Wrote:The image resizer code being used on SSA is client side javascript that gets processed after the page has already rendered.
I don't much care for that because it means your perception of the sites rendering speed becomes even more dependent on your browser (and that scripts) behavior than the actual site's performance, and anyone without javascript enabled here wouldn't see any benefit of it.
I'll continue to consider it and possibly put a vote about adding that a secondary option on top of the CSS change I made so that the only time people would see the scroll bars is when they weren't allowing JS or had overriden it's settings.
That sounds totally way better. [/color]
Transition Q&A - ImagineAll - 2010-07-07
Must say, I'm very impressed with your handling things people are asking for. Weighing all of your options and then coming to a decision. I like it.
Keep up the good work, Eos.
Transition Q&A - Shidoshi - 2010-07-07
Eosian Wrote:The image resizer code being used on SSA is client side javascript that gets processed after the page has already rendered.
I don't much care for that because it means your perception of the sites rendering speed becomes even more dependent on your browser (and that scripts) behavior than the actual site's performance, and anyone without javascript enabled here wouldn't see any benefit of it.
I'll continue to consider it and possibly put a vote about adding that a secondary option on top of the CSS change I made so that the only time people would see the scroll bars is when they weren't allowing JS or had overriden it's settings.
The container has no way to know the image was spoilered, all it knows is that something is trying to display beyond it's boundaries and that's not allowed to happen, so it makes scroll bars so you can see the whole thing. I could change it to clip instead of scroll, but that's even more annoying. What it really needs is a resize to fit option but that's just not something the current standards support.
I think for rare cases where we have high resolution images it's not that much of a hassle to: "right click, copy img url, open new tab, paste url, enter"
Once we get maple on 1024xIDK we'll probably start seeing more images bigger than the screen.
Transition Q&A - Stereo - 2010-07-08
I somehow broke my post editing ability by including two anglebrackets (<<) Not sure what's up with that.
edit: can't figure out what exactly is wrong.
http://www.southperry.net/showthread.php?t=28874&p=483808&viewfull=1#post483808
My post display cuts off at 266, whereas the post goes
266% < crit < 281%
When I hit edit, the div just vanishes.
Transition Q&A - Rob - 2010-07-08
Are we gonna have a frontpage again?
Transition Q&A - holyforest - 2010-07-08
Rob Wrote: Are we gonna have a frontpage again?
Eww I hope not....
Transition Q&A - Eos - 2010-07-08
Rob Wrote: Are we gonna have a frontpage again?
What would you want on it?
Transition Q&A - Rob - 2010-07-08
Like what Paul had in mind, content on the forums, direct links to extractions, guides, another content that could be created. Featured blogs, polls, etc. Something the new user could use as a start to get into the board.
Transition Q&A - Eos - 2010-07-08
How would that differ from the default page of the forum being the "What's new" link more or less?
Transition Q&A - Rob - 2010-07-08
Most searches on google would direct you to the front page, and if you're a guest, it looks nice and dandy if you can see what's interesting on the forum. I dunno I just picture it in my head and I don't know if I'm explaining myself.