File Repository

[Jupix]

OpenTTD 32bit graphics development file repository

Upload all your 32bit graphics development stuff here, doesn't matter if it's unfinished.

URL: http://jupix.info/openttd/gfxdev-repo

Important information and user manual



About categories

All categories at the repo can be used to put files in, including ones with subcategories. Use common sense in placing files, and if there is a category that isn't currently in the repo but ought to be, please post and I'll add it, it's real easy.

The current tree structure of categories is largely based on Douglas Ollivier's (Alltaken) white paper on a gfxdev file repository.

What the repo is not

Obviously, there is the file hoster's obligatory requirement which is for the files to only be related to the OpenTTD graphics development effort.

Also, there are a couple of minute issues having to do with the technical and political side of the repo:

- It's not fast. By which I mean lightning fast. It's running on my home server, which is (I think) an 800MHz Athlon with a whopping 1 MB in upload bandwidth. But at least it is reliable.
- It's not official. It's not recognized by the developers of OpenTTD. I am not an OpenTTD developer. Hence, issue #1.

But mainly, there is a big point I'd like to make about what the repo is not meant to be - and that is a player resource. See, in the past we have also wanted a central repository for files that we consider finished, or in public testing, and want players to test. A place for content to appear first, and appear so that players can browse, pick what they want and PLAY. The gfxdev file repository is not meant to be that place. This repository is for artists.

Final words

Please use this thread for:

- Discussion on how to use the repo, and how to use it to better the graphics development effort.
- Discussion on bugs in the repo.
- Discussion on features that we need the repo to have.
- Discussion on attributes of files in the repo, but not development discussion.
- Discussion on the contents of this post.
- Thank-yous and good-mans to make me feel good, obviously!

So any problems, questions or comments, post away.

[Moriarty]

Yay. Rather a long post, but it starts with a pretty picture so hopefully it won't put folks off.

I've posted a message on the two relevent threads ijust in case some of the inhabitants don't come up from their blendering and see this.
Thanks Jupix.

[=SLJ=DownEast]

My user account is not longer valid?

EDIT: Ok, figured it out, the DB was flushed...

I like the transfer ownership option...

Suggestions (yeah, more..hehe):
1. Everything is editable except File Type
2. In the Add window, the Title field size could be increased, and the File type could be reduced.

Nice work Jupix

[Jupix]

1. Everything is editable except File Type

I think this will be changed in the future.

2. In the Add window, the Title field size could be increased, and the File type could be reduced.

I may be misunderstanding again, but is this not what you're seeing?

[=SLJ=DownEast]

I may be misunderstanding again, but is this not what you're seeing?

Hmm...might be an IE7 thing, I tried it from work, looks the same...

[Jupix]

I didn't even bother testing in IE7. It's that un-standards compliant... If it's usable, that's good, but I'm not going to stop using CSS for styling if IE doesn't support it.

Rest assured it'll work fine in Firefox, Opera, Chrome and Safari.

[FooBar]

I didn't even bother testing in IE7. It's that un-standards compliant...

You're probably mistaken with IE6. It's not that hard to get a site working on IE7. If you stick to the W3C recommendations, it usually just works...
IE6 on the other hand is just a pain in the youknowwhat

[CommanderZ]

I didn't even bother testing in IE7. It's that un-standards compliant... If it's usable, that's good, but I'm not going to stop using CSS for styling if IE doesn't support it.

Rest assured it'll work fine in Firefox, Opera, Chrome and Safari.

This is not very good approach. Majority is still using IE.

[Jupix]

Majority is still using IE.

Not at the repo...

From what I can recall, with brief testing some time ago, the main problems were IE doesn't support margin: auto; and input { width }. (I think IE7 and IE6 are just as bad in this respect.)

[CommanderZ]

Majority is still using IE.

Not at the repo...

From what I can recall, with brief testing some time ago, the main problems were IE doesn't support margin: auto; and input { width }. (I think IE7 and IE6 are just as bad in this respect.)

IE does not support margin auto, but there is a simple workaround. And input width is supported in IE.

[Jupix]

IE does not support margin auto, but there is a simple workaround.

You mean toying about with text-align: center? I refuse to do that. If there's a more subtle workaround, please tell...

And input width is supported in IE.

Then why is it not working in our case?

[CommanderZ]

You mean toying about with text-align: center?

Why? You just set text-align:center in the outer container and left in the inner.

Then why is it not working in our case?

I don't know, but I used it for websites I made fine. I'm not so sure about SELECT, but IIRC it works too.

[Jupix]

Why? You just set text-align:center in the outer container and left in the inner.

Simply because text-align is for aligning text. If IE wants me to align containers with it, it can go off drawing containers where it wants for all I care.

I don't know, but I used it for websites I made fine. I'm not so sure about SELECT, but IIRC it works too.

I'll have to experiment when I get home and get back to you on this.

[FooBar]

Then why is it not working in our case?

Mainly because IE doesn't support this method: input[type="text"]
Quite frankly, I'm doing css for years now, but never heard of that method. It appears to be correct css though.

I always assign a class to an input control:
<input type="text" class="text" />
And then just use that in my css:
input.text { width: 400px; }

That works in all cases. So it's not that IE doesn't support the width property for input, it just doesn't support the css method you're using.
This javascript library might be interesting, as it fixes most css issues in IE. With that you should be able to keep using input[type="text"].

I had margin:auto working once in IE7, but it refuses in IE6. I'm using this now:

Code: Select all

div.maincontainer {
position: absolute;
left: 50%;
margin-left: -475px;
width: 950px;
}

It might work with percentages as well, but since I never use those, I'm not sure. You could try this one:

Code: Select all

div.maincontainer {
position: absolute;
left: 50%;
margin-left: 5%;
width: 90%;
}

[CommanderZ]

It appears to be correct css though.

It is CSS 2.0.

[Jupix]

I'll switch to one of the older methods of identification for that input in order to accomodate IE.

As for the centering, the current solution is what I will be using. I don't consider IE not centering the layout big enough of an issue to warrant completely rewriting that part of the CSS, or adding IE-specific scripting.

[Timitry]

I wouldn't bother too much about the IE 6 & 7, i guess most if not all the artists and coder are smart enough to use an alternative browser, and if someone really likes IE, version 8 will come out in a few days, and since this one is supposed to stick to the w3c recommendations... So i'd maybe just put a note on the mainpage "Don't use IE older than 8 for this page" and that's it...

Really like your repo, now we just need some more content

[CommanderZ]

Is uploading restricted to authors or can anyone upload anyone's stuff?

[Jupix]

I think it's best if we refrain from making restrictions. If the original author wants to forcibly take over or take down a file, he can file a complaint directly to me and I'll make it happen. If he doesn't, I think it can only be good someone maintains a record of that file's progress.

[rbn2903]

Hello Jupix, could you do me (and a few others) a favour? Could you please change the color of the headings in this thread? Not everybody uses the default-style! Thanks