Author Topic: Briefing texts reformatted  (Read 634 times)

0 Members and 1 Guest are viewing this topic.

Offline Black Wolf

  • Twisted Infinities
  • Global Moderator
  • 212
  • Hey! You! Get off-a my cloud!
    • Visit the TI homepage!
Briefing texts reformatted
So the other day I noticed Admiral Ralwood had added the BP briefing texts in what looked like a very unusual and non wiki-ish way. I edited them, and this started a short conversation where it was pointed out that he'd been following an established convention wherein these pages were formatted in a completely different way to the rest of the wiki, apparently as a result of some straight copy-pasting of a pre-wiki document that set an unfortunate formatting convention which had apparently been followed consistently since then.

Rather than stick with an old way of doing things as the result of a legacy document, I figured we could just reformat all the pages into something more conventional and navigable. Here is the example I've done for FS1. I was hoping for some opinions on whether people are happy with it, or any suggestions for improvements before I go through and do the others.

I've already requested changes that will make the table of contents shorter and more manageable (while still retaining the ability to link to a specific briefing stage through headings), and I'm hoping to add thumbnails of the relevant CBAnims for the various stages once we have images uploaded through this process. Any other thoughts?
« Last Edit: January 29, 2014, 12:14:35 am by Black Wolf »
Rarely Updated P3D.
Burn the heretic who killed F2S! Burn him, burn him!!- GalEmp


Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: Briefing texts reformatted
Looks good to me.


Offline niffiwan

  • 211
  • Eluder Class
Re: Briefing texts reformatted
Sounds & looks good.

(and ps. it was Admiral Ralwood who did the BP briefing texts, not Admiral Nelson :))
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
Linux OBS Packages: FSO 3.7.0 | FSO BP Build | wxLauncher (?) | PCS2 (?) | wxVPView (?)
Debian Packages (testing/unstable): Freespace2 | wxLauncher
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...


Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: Briefing texts reformatted
Shame to lose that bit of credit to Eishtmo, as I doubt anyone new will ever learn who he is. But c'est la vie.


Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Briefing texts reformatted
My first instinct was actually to do something more along those lines, but concerns about the TOC getting out of hand were the only reason I didn't. Excellent work on these FS1 pages. If nobody else gets around to it before me, I'll convert the WiH briefing texts to match.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.