User talk:Ssg

current entries are on the bottom of the page

old entries are out-commented

---

I'd call your new template "OBD Table", as suggested earlier.

See the "that's a good idea" answer some lines below.

I also don't like "Translation" and "Meaning" at all, ...

You can change it, if you want. Only one template to alter.

As for the "Bytes", I think I'd replace it with a type when applicable

Well, the type is stored indirectly in the "translation" column. So I'd prefer "bytes".

I think a good compromise would be to split the "OBD File Table" in two

Yes, that's a good idea. I'd suggest to take

{| WIDTH=100% BORDER=1 CELLSPACING=0 CELLPADDING=2 STYLE="border-style:solid; border-width:1px; border-collapse:collapse; empty-cells:show; background:#F9F9F9;"
|- ALIGN=CENTER BGCOLOR="#E9E9E9"

as a basic "prettytable"-like template. Maybe we should call the template "wikitable" or something like that. Choose a good name. (Please don't use words like "fancy". It confuses more than it explains.)

The

! WIDTH=5% | Start || WIDTH=5% | Bytes || WIDTH=10% | Hex || WIDTH=10% | Translation || WIDTH=70% | Meaning

I'd put in a template called f.e. "OBD_Table_Title_Row". (Same here. Choose a good name.)

which is a semantic pleonasm BTW

But if I write "Below follows the second package" (because, f.e. the pic shows the second package), instead of "Below follows the first package", and it is the first package in the table, it woundn't a semantic pleonasm any longer, right? (Unbelievable that you still know so much about that stuff. I remember that I heard something about that at school years ago. But I forgot all.)

And that's exactly my problem : no one will ever want to thumbnail them

I don't follow. What's exactly your problem? If you upload an image with 300x150, Wiki shows it with 300x150. Why do you care about so much, that "no one will ever want to thumbnail them". Sorry, but I don't get it.

The inability to rename the images

You can rename them. (Why the heck do you wan't to rename them?)

lousy short-term flexibility

As I said: Split it and override the existing one. I can't see a problem here.

Make it PNG rather than GIF

Yes, Wiki says: use png instead of gif, because gif supports only 256 colours. But: None of my hex screenshots uses more than 50 different colours. So it would be IMO really pretty stupid to change the file format without any need.

Capitalize the names according to the names of the actual files

Er... why should I do that? Are you trying to use a steamroller to crack a nut?

Whatever your "OBD Image" template is supposed to do, it's probably a bad idea.

Well, this has something to do with style. If f.e. someone changes the wiki background colour, so that it isn't longer white, you wou'll have a centered header, an image with white background but with a max. width of 690px on the left, and a table with a width of 100 percent. That sucks. It doesn't look good. But if you put the white-backgrounded image in a white-backgrounded table with a width of 100 percent, it will look much better. (Try it, if you don't believe me.)

So I'd like to use the image template for the hex images (even if we don't need it now).

---

We should have a zip file with all the current struct defs somewhere.

---

Actually, it may sound crazy, but I feel like taking THIS experiment a bit further.

Well, if you have enough time, you can do that. Have fun. :p

But I'd still appreciate if crucial files like AGQG were kept in sync with Oni Stuff...

I'm not sure, if I understand correctly what you want, but if we agree on the design, I'll adapt the html2wiki translator to that and update all file pages with the new code.

Ssg 12:57, 17 November 2006 (CET)