Talk:Super Robot Wars/Z/Secrets

I think this article should be divided into seperate articles covering units, characters, and items and attacks. Kouban 08:59, 8 November 2008 (PST)

As Netmonmatt put it while we're discussing it, "there's nothing worse than having to refer to multiple places for the same information". I'm not against maybe putting the actual textual information into seperate pages, but I think the chart at very least needs to remain as a singular resource. Magenta Galaxy 15:34, 8 November 2008 (PST)

Rubys -- Daichi 20:55, 8 November 2008 (PST)

Yeah, this page is kinda big. Rubies are cool and all, but the Firefox extension is very slow compared to IE's native Ruby viewing. Firefox really lags while trying to render Ruby tags with all the tables. Maybe we could cut back on what really needs them, (like the scenario numbers,) I dunno. Also, note the new threaded discussion extension I just added.

Re: Rubys -- Magenta Galaxy 21:04, 8 November 2008 (PST)

That can definitely be done, no worries. A lot of this was a copy-paste job for speed of completion, which means a lot of Ruby tags that needed to be in for the chart (due to the gaps between steps) can probably be cut from the actual written requirements. If we move the chart itself off onto a seperate page, that could also help - there's no links TO the chart, only FROM it, so moving the chart away from the page (onto /Z/Secrets_Chart perhaps?) would require absolutely no recoding. We could then trim some unnecessary Ruby from the chart - via scenario numbers - and from the written text - via repetitive Ruby - and make it all a lot quicker.

Should also note that I have a topic up on GameFAQs for the page, if you guys wanna consolidate discussion into one place.

Fixups -- Magenta Galaxy 04:34, 10 November 2008 (PST)

Thanks to everyone for all the fixes and corrections you've been making. <3 Lots of sloppiness on my part both in terms of poor editing and just poor writing and <3 you all for fixing it up.

More importantly, state of the page. My apologies for kinda imposing the new layout on you all, but the old page really did need an overhaul even if only in terms of completeness. So here's what I'm proposing we do:

1) As a stopgap measure, it's possibly worth replacing the Ruby tags with Caption tags. That should reduce browser rendering load whilst preserving all the information. Might actually solve a lot of the problem just by itself. I've got the current state of the page saved to file in both Ruby and Caption formats (with a quick Find+Replace) so I can roll that out with a click of the fingers if you guys think it's a good idea. Thoughts?

2) It's probably worth splitting off the table from the rest of the page. It's probably easiest to leave any major overhaul (he says, with a hint of irony) until we have the information from the Perfect Guide that means we won't really NEED to make any more major changes, but that can be done without too much fuss. The main problem if we do it before that point is keeping both pages synched, but that can be worked on - I can keep both pages in my watchlist and watch for any changes and apply them to both sides.

3) I don't know what it is, but something about the Ruby and the table format is causing the column widths to seem to want to screw themselves up with immense furiosity. Changes in resolution, text size, etc when loading up the page can cause the table to render the widths in completely different ways - sometimes shrinking a column to only a few words wide and next time making it far bigger than it needs to be. I have no clue what the HELL is wrong with it, and whilst it's possible to manipulate it slightly with width tags, there's no real consistency. Can someone who knows what they're doing with the Wiki coding take a look at fixing it? I appear to be utterly useless in all my attempts. ;.; Might be worth trying it on the main flowchart first, as that's a simpler setup than this chart.

Your thoughts and suggestions please, members of the jury?

Re: Fixups -- Daichi 02:48, 14 November 2008 (PST)

1) Some of the rubies should just be removed. like the scenario titles 第１２話(だい１２わ)：ブルースカイ・フィッシュ. I'm not sure about the idea of turning the rest into captions though. Some things like names can just be displayed like Camille(カミーユ) or Camille/カミーユ.

2) Maybe we should just keep in all in one for now. easier to keep things in sync. Maybe we can split it when edits start to slow down and formatting is decided upon.

3) what browser are you using? I love the idea of Ruby characters but I don't think most browsers implement it as well as they could. Which is why I try not to use them in tables anymore.

(btw, for general discussion, we probably should be replying to the top most part of the topic. instead of drilling down and indenting more then we really need.)

Re: Fixups -- Magenta Galaxy 05:21, 14 November 2008 (PST)

1) Definitely in agreement on ditching the ones for scenario numbers. I copy-pasted the table format from the Z Flow Chart (itself copy-pasted from the GC one I was testing) and really don't know why the hell I didn't get rid of them. Yeah, they can definitely go.

2) Sounds good.

3) Firefox 2.0.0.18 with XHTML Ruby Support 2.1.2008040101 addon. I'm not a fan of Firefox 3 and hence haven't updated yet.