New weapons help document & HTML template

[Bluecher]

Hi raynor and coldsteel,

this is really good work. And an Index is a good idea.

Very nice ...

[ColdSteel]

raynor, I just sent you some email with the fix to the "Range and Damage" inconsistent cell size problem. Other info and comments in there as well. Let me know if I can do anything else to help.

[Arralen]

Hello ColdSteel !

Just tried out CompHTML and had some minor quibbles about it
- there are some errors and "not-so-nices" in the HMTL code (I promised to look through it and send raynor some "sample pages" this weekend)
- and I would suggest moving all format/layout info into a seperate .css file, so it would be easier (or possible at all) to adjust colours and font size for personal preference.

What do you think about that ?!

Arralen

[ColdSteel]

Hi Arralen,

I too found some errors Last night in the first template and sent the corrections to raynor. My HTML editor error checker now say everything is fine.

I'm not sure how to move the formatting out into another file as you suggest. This is my "learn HTML" project and I've never played with it before so I'll freely admit that I'm a rank beginner when it comes to this stuff.

Here is the latest updated SE4Weapons HTML template that I just sent to raynor. It fixes a problem with cell sizes for the Range and Damage Tables. The latest SE4index HTML template is available in an earlier message under this topic. If you want to play with them and make suggestions or improvements, please feel free to do so. Bear in mind that raynor has to replicate everything in the templates in his code within the program so some reformatting when he does that is probably inevitable.

Thanks for the input.

[Arralen]

Ok, I'll have a look at it tomorrow (at work ), fi I find the time for this.

Doing everything in CascadingStyleSheets in a seperate file will in fact make the programming a lot easier - you needn't care about layout etc., as you can adjust this later when the acutal HTML-pages are already generated ..

I hope I can get some example done soon !!

A.

[Possum]

Guys, if you want to learn more about CSS, which really is very very cool stuff, go to Webmonkey. The CSS tutorial just rocks too hard for words.

A few caveats -

1. Netscape still does not properly implement some features of CSS.

2. Absolute positioning and z-index are massively cool features, but only really display properly when viewed at the same resolution for which they were created

[Will]

If you need any help with all that positioning and stuff, send it along to me (e-mail is cerban_imperium@yahoo.com). I've been doing HTML for a hobby for about... wow... four years (this is where my young age starts to feel, very, very old...). I got into CSS and dHTML Last year, and am fairly good at making them cross-browser/platform compatible (though I can only test on Windows )

For the alignment of the weapons, I haven't taken a look at the HTML code you have, but from looking at the problem the way you set it up, the following should work (the angle brackets will be represented by parenthesis ( & ), since forums seem to mess up HTML most of the time, even when they "shouldn't".):

(table)(tr)(td width="30" align="right")1(/td)(td width="30" align="right")2(/td)(td width="30" align="right")3(/td)(/tr)(/table)

That would give you a table with fixed values for the width, and the values inside the table data (td) tags aligned to the right (I believe that otherwise, they are aligned to the center, but, it's been a while since I've used tables). If you want to use CSS on the individual data stuff, you should switch from (table) to (div), but that's just a pain in the @$$, and more trouble than it's worth for something like this.

Oh, and sorry if the lowercase tags mess up anything that you've learned... it's not necessary to have them capitalized in HTML, and the new XML and XHTML specs call for lowercase only tags... plus lowercase tags have been my style from the beginning, because I found capitalized tags to be very annoying...

Some things on CSS: those two things are only problems if you don't know how to implement a fix to them Give Netscape a break, IE doesn't implement some of CSS's features either, they just have a few more of them. Absolute positioning works fine with a bit of JavaScript to determine the user's screen area (between toolbars, statusbars, scrollbars, etc.), and z-index doesn't have much to do with screen size, but is buggy in all browsers.

You guys should consider helping out with the manual too

And, one final thing: WebMonkey rules.