tachzusamm wrote:Looking at the work di gama already did, gives me hope that we will be able to implement the whole thing. Good job, man.
I understand there must be much logic and programming behind, especially for the full functionality. Looking at the currently used output "style", gave me the impression we should split design and programming, so I did some research and think we should use template techniques to accomplish this.
So, I already did some web design to get a nice user frontend, and currently I'm working out a first compilation of such a PHP/design combination, using the smarty engine. I will show some examples of the web design soon (next few hours or days, I hope).

Yeah, in case you haven't noticed, I'm not exactly known for my art skills. I have been giving the functionality higher priority than the beautification of the site. I do take direction well, though--if anyone has any ideas, they can give me the gist and I can make it work.
Also, I'm scrapping the texture categories from CGTextures. I don't think that they fit our purposes well enough, so I think we should start from scratch, adding categories to describe the files as they come in. (On that note, can someone actually
give me a file to work on? It's diffcult to work without a test base--it's like painting with a blindfold on. You can't be sure if it's working unless you take the blindfold off.
tachzusamm wrote:I am not aware about security holes regarding this solution, but I would really prefer to use the TextURU-server use it's own database. I understand that managing user accounts would be a big challenge (although PHP already offers some techniques like the PHPSESSID thingy), but I trust in your "eating php for breakfast" skills here.

If that's the way you think we should go, then I have no problem with it. I don't believe there are any technical hurdles for this alternative; the linked-database idea was just a design concept (which I didn't think was going to happen anyway). I'm sure I can whip something up.

tachzusamm wrote:Most of them (especially just "photographers" without any other intentions regarding age writing) are from Germany, Austria or Switzerland and don't understand english very well so for some it's a bit hard to participate in the whole GoW part here. My first intention was to provide a multi-language interface on the server, in some parts, like user-login and categories naming.
Although I haven't actually done anything toward this end, I have been planning some multi-lingual support for the site, although I have to admit that I have essentially
no knowledge in the other languages into which it may be translated, so I'll need some help from translators over here or over at H'uru.
tachzusamm wrote:Most of the people I know have dynamic IPs, maybe this is different in the USA?
I'm not sure if an approval process is favored or necessary, but I still believe users should have to login before they can do any upload - and besides of that, we do need a mechanism to identify admins. Simply using FTP would work for files, but not for contents in the database; imagine how confusing it would be to *move* misplaced files together with descriptive content if your only interface is phpMyAdmin?
Obviously, the final version of the site would require no direct database access, except in rare cases. There will be PHP forms which should deal with these issues well enough. As for dynamic IP's, yes, they use them here a lot in the States, but from my experience, they only change 2 or 3 times a year (I like to run servers at home and use the IP directly, so it's very obvious when they change). This, I think, should be a ban of sufficient length (I assumed these weren't
permanent bans anyway).
tachzusamm wrote:When the project starts first, I could play the role of an admin, but I would appreciate if other can do this job as well - and maybe we will need moderators.
Again, I assume these positions will be filled once the site is up and running, although I keep getting the feeling that I am making decisions on the part of the GoW without much input from the masses. I hope all this activity is more than just the two of us.
Chacal wrote:Will the system impose limits on the size of textures?
I'm asking this because I have a lot of 3072 x 2304 close-up pictures that could be cut down (as opposed to scaled down) to any number of smaller (such as 512 x 512) textures. But I would like to let people do their own cutting down according to their own needs. So the system would have to accept larger pictures for this to work.
I haven't been planning to impose limits on image dimensions and file size, although I would ask that people keep our 40GB limit in mind. Keep watching the site I posted: There are changes both to the PHP and the SQL coming, and that is the only source which is always up-to-date.