< Back to OSY 1.0 thread list

OSY 1.0 Thread Viewer

Thread #: 1700

New features and bugfixes for OSY

Jeremy Reimer

Sat Apr 20 22:32:44 2002

Hi folks!

Today I've been busy hacking away at the board.  It's actually been fun, oddly enough, but I did make a full backup of pegasus3d.com just to be on the safe side.

Well, here are the changes:

1.  Member list added!  From the main banner or the forums list page, you can click on "Memberlist" to get to a page that will show Top 10 posters by postcount (default), full member list by postcount, full list sorted alphabetically, by registration date, status (rank) or by last post date, list of active users, list of banned users, and a full list sorted into the letters of the first name.  This seems to work really well!

2. Link button added to posts:  Every post has a "Link" button that will open that post (basically the thread but with the browser page focussed on that particular post) in a new window.  You can use this as a cut and paste URL to link to a specific post, not just a thread, from any other part of the Web.

3.  New post redirects you to the end of the thread!  This is something I really wanted.  When you finish a reply, there are four choices now: Back to your post, back to the thread, back to the forum, and back to the forum index.  The first choice will be selected automatically if you wait a couple of seconds.  This returns you to the exact point of your post in the thread, even if it is on a different page in that thread!

4.  Text in the code tag now word wraps properly.  Before, as PeterB found to his chagrin, text inside a code tag will not word wrap at all, screwing up the table width for the whole thread and forcing an annoying series of edits.  This no longer happens.

5. New shortcut for the "biggrin" smiley.  On ars and other boards, the standard : D (without the space) is a shortcut to a big grin.  Now it works that way on OSY as well.  You can still use : biggrin : of course, if you really want.  I can add other shortcuts if anyone can think of any good ones. :D

All these improvements... and the cost to you, the loyal OSY member, is exactly $0!  Number of banner ads and popups... well, that's still 0 and will remain so forever.  

Yes, OSY is a small group with an even smaller group of active posters.  Yes, it can get dead from time to time.  But what other forum gives you this kind of feedback from the forum owner?  How often does Caesar give you a custom avatar, or fix a nasty Infopop bug?

Anyway I am about to go out and enjoy the sunshine a bit... have fun!

AllYorBaseRBelong2Us

Sat Apr 20 22:46:20 2002

Thank you :D
Jeremy Reimer

Sat Apr 20 23:06:37 2002

You're welcome!  (I was just about to go out, but Jennifer came home, so we're going to go out together.. anyway.. postcount++ and all that)

Imitation Gruel

Sun Apr 21 01:49:40 2002

The new features are:

[color=blue][size=100]WINTACULAR[/size][/color]

That is all.

DrPizza

Sun Apr 21 13:10:45 2002

4.  Text in the code tag now word wraps properly.  Before, as PeterB found to his chagrin, text inside a code tag will not word wrap at all, screwing up the table width for the whole thread and forcing an annoying series of edits.  This no longer happens.

Um, no.

I wanted a big long line.  That was the point.  But the stupid thing:
(a) put smilies into the code.
(b) ignored whitespace

I clicked edit and unticked the emoticons box to get rid of the smilies, but that seemed to result in the insertion of redundant newlines.

MOST UNSATISFACTORY.

Riso

Sun Apr 21 13:30:41 2002

YOU DA MAN!
Jeremy Reimer

Sun Apr 21 18:51:37 2002


Um, no.

I wanted a big long line.  That was the point.  But the stupid thing:
(a) put smilies into the code.
(b) ignored whitespace

I clicked edit and unticked the emoticons box to get rid of the smilies, but that seemed to result in the insertion of redundant newlines.

MOST UNSATISFACTORY.

Erm, but didn't you want word wrap in code tags?  I thought that's what you asked for.  

The emoticons are done on a per-post global search and replace, so yeah, you have to uncheck emoticons in the post or they get shown everywhere, code tags or no (I could change that, but it seems like a lot of work for a relatively trivial gain)

The redundant newlines weren't inserted by the board, they were inserted by me, manually, to try and fix0r the post so it didn't fux0r the table width.  Now the code just wraps like any other text field.

Magus

Sun Apr 21 22:11:06 2002

This is a useless post. Another thing about me that's utterly pointless.
DrPizza

Sun Apr 21 22:31:26 2002

Erm, but didn't you want word wrap in code tags?  I thought that's what you asked for.  

No, I asked for them to be in pre tags.  So that whitespace would be honoured.

The emoticons are done on a per-post global search and replace, so yeah, you have to uncheck emoticons in the post or they get shown everywhere, code tags or no (I could change that, but it seems like a lot of work for a relatively trivial gain)

The redundant newlines weren't inserted by the board, they were inserted by me, manually, to try and fix0r the post so it didn't fux0r the table width.  Now the code just wraps like any other text field.


Well that's idiotic!

You might as well not have code blocks if you're going to put extra newlines in.

Jeremy Reimer

Sun Apr 21 22:35:34 2002

Well, here's the deal.  It turns out that the code blocks were already being put in <pre> tags.  But the fact that they were in <pre> tags meant that long lines fuxored up the table spacing.  This happens in any web page where you use a <pre> tag, as I found out.

Since there was no way to word wrap within a <pre> tag, I took the tags out and just left the code tags as a simple shift to a fixed-sized font (Courier)

If you want the <pre> tags back in, then you get no word wrap.  If you want word wrap, then you get no <pre> tag.  Unless you can figure out another way of doing this?

HitScan

Mon Apr 22 03:42:10 2002

No word wrap is the preferred way. What would be best is to break out the posts into their own tables, which would mean that any one post could be fooking huge, but not fux0r all the rest. Because code should always honor whitespace and not break other than hard returns :)
DrPizza

Mon Apr 22 14:02:27 2002

from Jeremy Reimer posted at 11:35 pm on April 21, 2002

Well, here's the deal.  It turns out that the code blocks were already being put in <pre> tags.  But the fact that they were in <pre> tags meant that long lines fuxored up the table spacing.  This happens in any web page where you use a <pre> tag, as I found out.

Since there was no way to word wrap within a <pre> tag, I took the tags out and just left the code tags as a simple shift to a fixed-sized font (Courier)

If you want the <pre> tags back in, then you get no word wrap.  If you want word wrap, then you get no <pre> tag.  Unless you can figure out another way of doing this?


Individual tables!

Make it so that each entry gets its own table.  This way, we don't have word-wrap, but one entry being hugely wide doesn't make all the others hugely wide.

But seriously, it *must* use <pre> tags.

Jeremy Reimer

Mon Apr 22 17:09:42 2002

Okay, I'll put the <pre> tags back in, it makes sense to preserve whitespace in code tags.

Making each post in an individual table might be trickier.  I mean, I can add the <TABLE> <TR> </TABLE> tags into the template easily enough, but I don't know how it will screw around with other things, and I'm not sure how to make it so the page will still auto-resize to a browser window for some posts and not others.

However, it might be worth it to figure this out, as it would kill two birds with one stone: large images will no longer screw up threads either.  (I should note that both code tags and large images currently and have always screwed up Infopop, so if I can do this it will be yet another feature win that OSY has and they don't)

I'll look into it.

HitScan

Mon Apr 22 17:34:20 2002

By setting the table widths all to 100% the oversized tables will expand beyond the right edge, but the rest will stay at 100% and be fine. Unless you're putting each posts' table inside a larger table, because then they would all stay the same and it would still screw up. Infopop had done this at one point, but I don't know why they stopped. Odd.
Magus

Tue Apr 23 06:13:44 2002

Because Infopop can't seem to leave good things alone?
DuffMan

Tue Apr 23 09:29:31 2002

I can't afford the 0$ so i guess i cant use the new features.

:(

Imitation Gruel

Tue Apr 23 11:34:22 2002

I can't afford the 0$ so i guess i cant use the new features.

[color=purple][size=200]HA HA!![/size][/color]

:sagrin:

(Edited by Imitation Gruel at 4:35 am on April 23, 2002)

Imitation Gruel

Tue Apr 23 11:36:00 2002

JR, what's the limit on font size and the biggest font so that we can make the text as colossal as possible?
HitScan

Tue Apr 23 13:31:46 2002

IG: the ont size limit is 7, because it uses absolute sizes in the <font> tag, which can only be 1-7.

If he'd turn on HTML we could use CSS and have 200px fonts all over. ;)

Imitation Gruel

Tue Apr 23 13:41:34 2002

the ont size limit is 7

Hmmm....

Edit: Apparently so.

(Edited by Imitation Gruel at 6:42 am on April 23, 2002)

Imitation Gruel

Tue Apr 23 13:42:17 2002

That sucks.
Imitation Gruel

Tue Apr 23 13:42:42 2002

By the way, what's an "ont"?
HitScan

Tue Apr 23 14:30:47 2002

It's like a "f"ont, only smaller. ;)
Harbinger

Tue Apr 23 15:17:00 2002

I thought it was something along the lines of "unt" myself.
Imitation Gruel

Fri Apr 26 10:27:52 2002

JR, would you change the font size please? Like to something at least double digits?
HitScan

Fri Apr 26 14:53:50 2002

IG: It's an HTML standard limit.(they correspond to the CSS named front sizes, xx-small, x-small, small, medium, large, x-large, xx-large) If we want bigger fontage he's got to turn on HTML so we can use CSS goodness. I do not look for this to happen.