< Back to OSY 1.0 thread list

OSY 1.0 Thread Viewer

Thread #: 1905

Table fux0ring is in progress

Jeremy Reimer

Mon May 20 18:34:31 2002

So if you see things going way out of alignment, or strange background colors or borders or things appearing as if out of nowhere, don't panic, it's just me fucking around with the tables to try and fix the "big image fux0rs the entire page" problem.

Don't worry, I've backed up the entire website onto ZIP yesterday, so worst comes to worst, we lose like five posts.  

This is all in an effort to constantly improve OSY for you, the loyal OSY members!

One little fix I've already put in: if you click on the "jump to forum" thingy at the bottom, it no longer overwrites the frame at the top.  I know, I know, nobody ever goes to the "Pegasus" or "Jeremy" sections of this website, but one day they will, and we'll be ready.  ;)

Jeremy Reimer

Mon May 20 18:52:36 2002

Okay, I've isolated the tables that encompass an entire thread.  You can see from the thick-ass borders what they are.  Why there are two tables instead of one is beyond me.  I think I can eliminate these uber-table commands and have the thread work with independant tables for each message.  We'll see...
Jeremy Reimer

Mon May 20 19:01:14 2002

Testing noscroll text fux0ring:

[code]
1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
[/code]

(of course, I'll have to put the <pre> tags back into the code before this works....)

Jeremy Reimer

Mon May 20 19:01:57 2002

Er, apparently not...

111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111

Jeremy Reimer

Mon May 20 19:02:25 2002

No, it seems that long text will fuck up regardless.  I'd better put those <pre> tags back in then, to preserve whitespace!  Let's see if this post is okay...
Jeremy Reimer

Mon May 20 19:02:53 2002

It works!  It works!

Now to unfuck the reply buttons...

Jeremy Reimer

Mon May 20 19:06:55 2002

I think I've got it!  Holy HTML, Batman, I think I've got it!
Jeremy Reimer

Mon May 20 19:08:15 2002

WHO'S YOUR DADDY!!!!
HitScan

Mon May 20 19:21:47 2002

Mah Daddy's mah daddy, but you're pretty cool too. :D

I thought they would do something ret4rded like encompass the whole lot in a 1 cell table. That si dum.

Congratufirckinlations! :) (doesn't work on the reply page though. That likely doesn't matter though, as it's all left aligned.)

Magus

Mon May 20 19:35:31 2002

Nice job, JR.
Evil Merlin

Mon May 20 19:42:50 2002

I'm your daddy bitch!
AllYorBaseRBelong2Us

Mon May 20 20:02:54 2002

your all my biatches you fat ugly biatches!
Jeremy Reimer

Mon May 20 20:24:13 2002

Eh, I suppose I could go and try and fix the Reply page, but it looks trickier, as the whole thing has to be in one table anyway to scroll through it... hmm...

I have to go find wherever the fuck it was that the <code> tag is translated and put back the <pre> tag inside, to preserve whitespace, now that line wrapping isn't a big deal.

Still, I did accomplish something!  And it took me about half an hour! Take that, Infopop!

Incidentally, iKonboard is going "professional" with version 2 development scheduled to stop after the release of 2.2.  They will focus on 3.0 and up, with "lite" versions for free and "pro" versions for, well, not free.  I think I will be sticking with 2.x, given what I've seen about how difficult it is to mod and hack 3.0, and the fact that it requires MySQL, which I really don't want to have to fuck with.  Sure, text files might be crap in terms of speed, but if one bit flips, the most you will lose is a thread, whereas with a freeware database and application, if there are bugs.. whoo boy!  

I mean, I can go back and revive threads from last year, and it's no big deal.  Infopop now automatically locks threads that are inactive for more than 30 days, because it was fucking things up so much.  Oh well.

Jeremy Reimer

Mon May 20 20:42:53 2002

Okay, now let's see if the <pre> tags are back:

[code]
Preserving   spacing           is                     cool            isn't                        it?
[/code]

I can't make the words wrap in <pre> tags, though.  I tried this in a blank page in my browser.. the <pre> tag simply turns word wrapping off.  That's part of IE, I can't change that.

HitScan

Mon May 20 20:52:18 2002

I can't make the words wrap in <pre> tags, though.  I tried this in a blank page in my browser.. the <pre> tag simply turns word wrapping off.  That's part of IE, I can't change that.

That's how it works. That's what it does. Such is entirely correct.
<pre> tags tell the browser "No monkey business with this text. You only draw the linebreaks and spaces that are between these tags. Insert nothing, break nothing, reduce nothing." I don't even think HTML between <pre>'s is supposed to render.
DrPizza

Mon May 20 20:57:46 2002

I don't even think HTML between <pre>'s is supposed to render.

Yes, it does, and is.

"pre" says "switch to a monospace font and honour whitespace".  That's all.  So if you have newlines, it inserts them, if you have multiple spaces, it doesn't elide them.  Normal HTML (and XML) will elide any amount of whitespace into a single space.  "pre" says "don't do that".

Jeremy Reimer

Mon May 20 21:33:24 2002

Then why doesn't it word wrap?

EDIT: let's try:

[code]
thisis a woerwoh sfdsdfh jf blah blah blah bl ablbhl bl bl l bl b                 whee                      wheeee                                    eheeeeee     hahahahhahahahahahh  lblah blah blah bl ablh ablh bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
[/code]

HitScan

Mon May 20 22:00:12 2002

Then why doesn't it word wrap?

Because you didn't press enter.
<pre> stands for Pre-formatted. meaning not to wrap if it's too long, and not to put 2 lines together if the window is wide. if you put a newline between <pre>'s, then you get a new line. if you don't though, it's not going to put one in, no matter how long your message is.

[code]
#include <stdio.h>
int main(int argc, char *argv[])
{
    printf("Hoo-rah");

} /* main */
[/code]
See, that's perfect. And if I had a 90 char line of code, it should be 90 chars wide in the browser window, because linebreaks mean something to the compiler in most languages, and you don't want a board to randomly mess with your codie bits. :)

BTW: the board thinks that ") should be a wink. In short, bah.

Jeremy Reimer

Mon May 20 22:27:03 2002

Yeah, C code is too full of smileys.  ;)

I can take out the " ) one though.

AllYorBaseRBelong2Us

Mon May 20 22:57:38 2002

")
Jeremy Reimer

Mon May 20 23:14:03 2002

")

I think the Reply page is fixed too.  It looks a little weird in parts but it does the job.

Jeremy Reimer

Tue May 21 00:41:52 2002

The " ) smiley, I have no idea why it is doing that.  It isn't in the code, only ; ) is in there.  Weird.  Oh well.  I have fixed the tables and that's an honest hour's work, time well spent methinks.

My next adventure... a forum poll hack.  It's big, I need to back up the board again first before attempting it.

DrPizza

Tue May 21 00:47:25 2002

from Jeremy Reimer posted at 10:33 pm on May 20, 2002

Then why doesn't it word wrap?

Because it's honouring whitespace.

That means both keeping the whitespace that's there, and not inserting more whitespace.

You want lines to wrap in code blocks?  You'll have to break 'em yourself.

Jeremy Reimer

Tue May 21 02:15:11 2002

Well, that would seem to indicate that I don't need to fux0r with <pre> tags any more, that they are working properly.  Albeit for smileys, which unfortunately you just have to turn off for any post containing code tags.  :(