User talk:Iceheart
From modwiki
About the summary - I know. I wasn't updating summaries because I was actually starting the new pages. The few editions I made to existing pages had a summary. Also, I noticed you edited one of the other pages while I was editing it, I think it's what started up the confusion? Zeh
Contents |
Heh, funny
In your last update to edit guidelines you wrote:
"Linking unlinked linkworthy text is not minor."
Ouch. ;)
no no
heh, I wasn't clear. I meant the aliteration is funny: "linking unlinked linkworthy..." I mean, it's a mouthful. ;)
Nested Categories
How do you enable those neat
Categories: Main Category -> Sub Category -> Sub-Sub Category
displays? I've installed 1.5 on my own site but I haven't figured that out yet. I also blatantly stole some help texts (mainly the editing guide, hope that's okay)
- Democritus 20:24, 3 November 2005 (W. Europe Standard Time)
shakesGen
the in the notes section because that's how you make it re-make all the shakeData. Just letting you know hwy I changed it.
-thf
Navigation
Note: The whole thing is hard for me to explain because a) it's not yet a stable idea in my mind and b) I'm no native english speaker, so please bear with me :)
I've been thinkin about navigation of this wiki lately. Imho it could be improved. Seeing as how editing Doom3 and Quake4 is very similar, I don't think it's a very good idea to seperate the two so harsh.
I think the navigation should be task based (what does the user want to do) and on the lowest level game specific. Take the console commands for example. I know you somehow don't like one page for the two games, because you think it hinders overview and having even 4 of them is easy to maintain, but I still disagree. The way I'm organising the page it's getting harder and harder to not oversee stuff. It's hard to check if there are missing commands or duplicates because it's not a listing of categorized objects in the system but rather just a plain list of the commands. Thinking about having to do that for all 4 games in the future makes me somewhat afraid O_o! Imho all commands should be on one list, not because someone is interessted in the differences between the two games but just because it's easier as a whole. Say you come to a page of a command from some article and you want to see the list as a whole. To which list do you link back? To all 4? What if I just want to see for which game a command is? You'd have to use the page search and this makes it more complex to use. It's also redundant information which is just horrible to manage.
The whole wiki seems a little unorganized to me. It's hard to find existing pages. When I was editing the command list, I wanted to add links to some commands and I had to find out which pages exist and if I found more pages on one topic, I had to find out which is the main one. There should be more structure to it. I wanted to link to a file format from the command list page. I couldn't find it because 3 letter search is disabled. Another example: I wanted to link to the Articulated Figure Editor (sp?) from the editor page and I didn't find one about it at first. I then found a page called "AF editor". Imho there should be a simple description page to a term, which has the full name and always the same format. This format could be 1) short description and 2) link to articles about the term or similar.
Also the different sections should have a basic layout shared. I think the whole layout should be somewhat streemlined. I don't think I know enough about all there is to editing yet, to handle that task alone but maybe we could discuss that somewhere all together, come up with a good layout and apply it to the page.
Another exmaple: The mapping section. It's somewhat confusing. First you have a page about mapping which explains some basic term, and the tools. On the editor page you have some more information but no links to further reading. No info or links to tutorials about creating rooms, no information about simple editing. It's rather confusing.
The menu on the left isn't useful at all. There are only links to the games and from there you're depended on the page to page navigation which is imho very ineffective. There's also no breadcrumb navigation which shows where you are and where you came from like: main -> editing -> mapping -> a basic room (for example).
The wiki itself is rather confusing, as all the features of it are somewhat hidden under "special pages". Maybe some of these pages could be in the main menu? It was a little confusing to get used to this wiki from the start (it's not that hard but it could be improved imho).
Imho the whole separation of the two games from the beginning is useless as they even now share many pages. Some are shared, some are different and the ones different often have the same info on it.
Q: Does anyone know if it's possible to apply templates to pages in certain categories?
I hope it's somewhat clear where I'm going at, but as I'm still confused with the wiki it's hard to explain it better. Maybe it's all nonsense anyway, but I try to somewhat organize the mapping section (of site) when I come home and post a proposal here.
--Legshot 15:46, 20 December 2005 (W. Europe Standard Time)
Okay
First off: You have bread crumbs navigation for categories (only way to do it in mediawiki) on the bottom of each page.
Second: I know that many things between D3 and Q4 are identical, BUT that doesn't mean that that will also be the case for ETQW, Prey, the next wolfenstein game, and god knows what else after that, all of which are pretty much guaranteed to be heavily engine modded. THAT is the reason for the separate lists, even though it might seem pointless now. On the other hand, a master index of CVars and commands would be a nice page to have. Information redundancy is GOOD, information redundancy is only bad if different articles disagree with each other!
Suggestions for organization of the front pages is welcome, but there's no guarantee that it will actually happen.
Re: Mapping page, tutorial links, etc: Well, this is a wiki, which means anyone is free to add things they feel are missing, that's one of the biggest points with it.
The functionality under "special pages" are things regular users shouldn't have to use, if any of them are actually useful there should be a proper wiki page with that info instead, like instead of "all categories", you would go to modwiki:Categories or Category:Modwiki (for following down the hierarchy AND seeing all the articles).
I hope I answered all of it, but feel free to ask or suggest more. --iceheart 23:24, 20 December 2005 (W. Europe Standard Time)
BTW
For more real-time communication you could check into our IRC channel, #modwiki @ irc.gamesurge.net (I'm pretty much always there, even though it has been strangely empty recently). --iceheart 23:26, 20 December 2005 (W. Europe Standard Time)
Spammers
I noticed that you too have had to rollback and block some users. I've done a bit of reading and I would hazard a guess that it's bots at work.
Perhaps we should make use of the $wgSpamRegex variable to block edits that contain matching keywords?
It's explained on this page... http://meta.wikimedia.org/wiki/Anti-spam_Features
I can't see a reason why anyone would ever need to hide anything on a page so if we block the CSS properties that they use to hide their links it should fix the problem. I've got a little experience with regular expressions so for what we've encountered up to this point, this should work...
$wgSpamRegex=/overflow\s*:\s*auto|display\s*:\s*none/i
Let me know what you think.
--Rich 09:33, 29 March 2006 (W. Europe Daylight Time)
Ok rich
I implemented your solution (big blacklist filter didn't cooperate) and it seems to work fine for now but on meta they say this:
Unfortunately there are many workarounds this spammer can use, but for the time being this will get them off your back.
about blocking css attributes, but it's still a help. --iceheart 12:16, 4 April 2006 (W. Europe Daylight Time)
Spam RegEx
I'm sure there are workarounds as their are probably dozens of ways to hide things on webpages.
In the meantime, they can't post spam.
And should they find a way around it, I'll just rework the RegEx. It's like ping pong. Back and forth.
--Rich 07:55, 5 April 2006 (W. Europe Daylight Time)
Shout when those CSS rules are fixed
I wanted to fix the CVar template, but doing that without those CSS rules wouldn't improve it. So let me know then when you get those rules in so that table can be dealt with. --Kamikazee 21:06, 15 June 2006 (W. Europe Daylight Time)
Back from vacation!
In case noone noticed, I've been on vacation for the past two weeks. This means I've forgotten everything I was supposed to do here, so if some helpful soul will clue me in, I will be grateful! --iceheart 00:22, 1 July 2006 (W. Europe Daylight Time)
Special Delivery
I needed to clean up my discussion page, as do you. Here's the CSS relevant discussion from my page as you are the only one who can implement it...
Tables are botched
http://www.modwiki.net/wiki/Commands_%28Doom_3%29
--Rich 05:50, 29 August 2006 (CEST)
Tables were fixed
Some time ago, that table showed all the </li> tags. Since the wiki renderer couldn't live with them, I removed all those tags. Now it seems that they are needed again.
However, I would strongly advise to import the CSS style rules I proposed in the page's Discussion. That way, the page can be cleaned once and for all but still give the same layout. Once those rules are in place, the conversion should be nearly painless by using a simple editor to remove all those redundant <li> tags. -Kamikazee 23:55, 29 August 2006 (CEST)
Downgrade.
Unfortunately, the recent server move required that I downgrade mediawiki to an older version, so that's why they might be needed again.
Which CSS rule was it that I was to insert?. --iceheart 02:15, 30 August 2006 (CEST)
CSS rules to add
Here they are:
- CSS rules for unordered-list-style tables
- CSS rules for better markup of tables (Eg. the CVar template or the table in the Blend (material statement) )
-Kamikazee 13:38, 31 August 2006 (CEST)
Where to add
I guess the CSS rules need to be added to MediaWiki:Common.css so they apply to all skins. -Kamikazee 13:49, 4 September 2006 (CEST)
--Rich 07:55, 2 April 2007 (CEST)
Kamikazee - Elevated Rights
I'd like to give Kamikazee elevated privileges here on the wiki. He's one of our most active members and I think he has a sound head on his shoulders.
Your call.
--Rich 05:44, 23 May 2007 (CEST)
Rights
Thanks. I just wanted to run the idea by you.
--Rich 12:30, 23 May 2007 (CEST)
