Oolite Bulletins

JazHaz wrote:

One thing about the Wiki is that the OXP list is a bit unwieldy, to say the least!

Thinking about splitting the large table into several new pages, ie Ship OXPs on one page, equipment on another, etc etc.

What do you think?

There are already some auto-generated lists along those lines. See here.

So personally I'd say no to splitting it up, although I agree it needs a tidy-up and to be made more user-friendly.

Nice idea with the 'NEW' and 'UPDATED' stuff, Jaz. It makes it for new users a lot easier to find the latest stuff. Good idea.

2 minor nitpicks:
- Animated gifs? It always reminds me on 80th webpages with a lot of blinking, peeping things on it. And if it has to be animated why not within the colorrange of that page or using colors that don't 'destroy' the page?
- Would it be possible to set a expiring date, so this doesn't have to be switched off manually?

Svengali wrote:

Nice idea with the 'NEW' and 'UPDATED' stuff, Jaz. It makes it for new users a lot easier to find the latest stuff. Good idea.

2 minor nitpicks:
- Animated gifs?

Yes, I know they are a little annoying. I have had these files for over 10 years, they date from the old school days when websites had lots of animated gifs, soundfiles etc!

Svengali wrote:

- Would it be possible to set a expiring date, so this doesn't have to be switched off manually?

Not sure how to do that, but I may be able to edit the files to stop the animation completely.

JazHaz wrote:

Svengali wrote:

- Would it be possible to set a expiring date, so this doesn't have to be switched off manually?

Not sure how to do that, but I may be able to edit the files to stop the animation completely.

What I meant is - can a marker (UPDATE,NEW) have a duration, e.g. a new oxp could be marked for e.g. a month?

The WIKI knows magic_words like {{CURRENTTIMESTAMP}} and has the ability to compare things {{#ifexpr: 1 > 0 | yes }} if I get this right.
So would it be possible to set a expiring date for a single entry in that OXP-table? Maybe done as template and the expiring date would be passed to that template?

Svengali wrote:

The WIKI knows magic_words like {{CURRENTTIMESTAMP}} and has the ability to compare things {{#ifexpr: 1 > 0 | yes }} if I get this right.

Nope.

Ever noticed how Ahruman's answers just ramble on and on...

All the time.. some people are constantly excessively verbose.. it's like they just can't help themselves..

Y’know, I can go on for two pages to say something someone else will summarize in five words, too.

In any case: those things require the ParserFunctions MediaWiki extension. I’d love to see them on Elite Wiki, but given that it’s busy falling apart at the moment it might not be the best time.

Ahruman wrote:

Svengali wrote:

The WIKI knows magic_words like {{CURRENTTIMESTAMP}} and has the ability to compare things {{#ifexpr: 1 > 0 | yes }} if I get this right.

Nope.

Ah, ok .-)

I have split the OXP table into 2 pages.

The original page now has a table from A to M, and the new page has the table from N to Z.

Before I did this, it was crashing my Firefox browser, because it was too big!

JazHaz wrote:

I have split the OXP table into 2 pages.

The original page now has a table from A to M, and the new page has the table from N to Z.

Before I did this, it was crashing my Firefox browser, because it was too big!

Strange, I use firefox and have never had this happen.

Gimi wrote:

JazHaz wrote:

I have split the OXP table into 2 pages.

The original page now has a table from A to M, and the new page has the table from N to Z.

Before I did this, it was crashing my Firefox browser, because it was too big!

Strange, I use firefox and have never had this happen.

It was crashing Firefox when I opened the table to edit it.

However it may have been just my installation, which hangs ("Not responding") quite often.

JazHaz wrote:

It was crashing Firefox when I opened the table to edit it.

However it may have been just my installation, which hangs ("Not responding") quite often.

That pages puts up a warning when opening. I just opened the new first table for editing (not the whole page) and I still get the warning:

Warning: This page is 36 kilobytes long; some browsers may have problems editing pages approaching or longer than 32kb. Please consider breaking the page into smaller sections.

Safari never had problems with it but such a warning has a reason. And when it is split, maybe it should break in smaller pieces?

And I am not convinced that page 2 should also contain all the other stuff as it forces us to always change both pages when editing one.

Eric Walch wrote:

...am not convinced that page 2 should also contain all the other stuff as it forces up to always change both pages when editing one.

Heh, I had the same idea
And I agree that it's still too cluttered, my PC can handle it, but as has been mentioned, others can not.
Maybe each letter should have its own page. I was thinking that maybe an OXP portal is needed, kinda like a directory for it, something similar too THIS. But with a link for each letter and maybe a seperate page for the categories part.

I would do it myself but I've been bogged down with stuff (working on shadering one of PAGrooves OXP's, and watching the entire season of Stargate Universe which i've been meaning to watch, have just finished watching all 16 episodes after pulling an all-nighter )

We have of course THIS. For comprehensiveness it requires the existence of a seperate Wiki page per OXP, however.

Myself I have watched the 32kb-warning on the OXP-page for quite some time, with an ever growing gap between the actual size and the magical 32kb. My Safari never had a problem with opening and editing it, but I also guess that the warning is there for a reason.

So I think halving the page is probably a step in the right direction. It also makes the background-colour-changing less tedious, especially if you add an OXP that starts with "A".