Difference between revisions of "User talk:Seb26"
(→Model Viewer: new section) |
|||
Line 111: | Line 111: | ||
Seb, I need to speak with you over steam at some point, when you have time. --[[User:Org|Org]] 08:34, 25 February 2011 (UTC) | Seb, I need to speak with you over steam at some point, when you have time. --[[User:Org|Org]] 08:34, 25 February 2011 (UTC) | ||
+ | |||
+ | == Model Viewer == | ||
+ | |||
+ | Hi, it's possible to do [http://www.andrewhatch.net/2010/11/flash-collada-3d-model-viewer-in-flex.html this] for a fast view of weapons (and with other items)? I think that's it a great idea for the wiki =D [[User:Dio|Dio]] 00:54, 27 February 2011 (UTC) |
Revision as of 00:54, 27 February 2011
- Create a new section
- Archives — 2010: July · August · September · October · November · December
- 2011: January
Contents
Icon items template
I asked about this on the IRC channel, and was told that you were one of the people to ask about this. Could you please edit the Template:Icon item template to include the new Rift items? The Weapons, Community Pyro strategy and Community Scout strategy pages in particular have broken image links that could be fixed. Thanks. --LordKelvin 18:18, 4 February 2011 (UTC)
JS/CSS compression
Ohai, I just moved around the JS and CSS of the site quite a bit.
- Deleted MediaWiki:DynamicBackground.js and MediaWiki:Egg.js and merged them with MediaWiki:Common.js
- 2 HTTP requests sawed off each page load
- Blanked MediaWiki:Valve.js (also merged with MediaWiki:Common.js)
- Makes it easier to manage scripts; both .js files are combined server-side, so it makes little difference to have them in one or the other. Since we only have one skin, it also makes little sense to separate both. Having them all in one file removes the "Now where did I put that code" moment
- Moved all MediaWiki:Common.js code to MediaWiki:Common.js/Code.js
- This page holds the readable version of MediaWiki:Common.js
- Compressed MediaWiki:Common.js using http://jscompress.com/ (Packer Method)
- Much smaller, thus much faster to load
- Blanked MediaWiki:Valve.css (merged with MediaWiki:Common.css)
- Same rationale as Valve.js
- Moved all MediaWiki:Common.css code to MediaWiki:Common.css/Code.css
- Again same rationale as MediaWiki:Common.js
- Compressed MediaWiki:Common.css using http://www.csscompressor.com/ (Highest)
- Again, much smaller, thus much faster to load
Hope that's okay :3 It does mean more steps whenever we need to poosh new JS code, but it means noticeably faster loading times (try it, browse around while your cache still has the old copy, Ctrl+F5, and then keep browsing around) — Wind 20:47, 6 February 2011 (UTC)
Bot Question
I have a long article with mostly links. Unused Content <- this ist it. Wanted to translate it into german. I translated all beta weapons and so i hoped that your bot can use the displaytitle on every german page and makes the english ones german. For example: Overhealer change into Überheiler <- is this possible ? Because there are many links and names to change....this would take a while... NoWhereMan_(DSvY) 19:14, 8 February 2011 (UTC)
- Unfortunately this isn't something the bot is capable of, sorry – seb26 [talk] 06:47, 9 February 2011 (UTC)
- It may sound a bit arrogant but you can't maybe think about a way to implement that? I know about the hats and other items to be in templates used with language switches. Couldn't it be maybe made possible to gather all relevant german wiki articles and save there real names(which are needed), and then used it and replace the german with the english linkin. Just curiously thinking about it. NoWhereMan_(DSvY) 06:53, 9 February 2011 (UTC)
- The thing is that I'm not a programmer and most edits made by the 'bot' are just me using an automated editing program ;) I really wouldn't know where to start to create something to do a task like this. Templates with language switching could be used on the pages but I believe that the item name templates aren't used generally inside articles and instead inside other templates (such as the navigation boxes & blueprint tables, etc). For the unused content page, I suppose there's a lot of pages to look through, but by quickly flicking through open tabs you could probably have it done pretty fast heh. Sorry I couldn't have been of more assistance. seb26 [talk] 07:04, 9 February 2011 (UTC)
- No problem. I'm by myself aren't capable of doing things with bots, i have many ideas but don't know the things behind it. So i will do it the oldschool way like i always do and start editin by hand using my editor(notepad) and startin with replacin after finding one name and will revert it slowly like always. Just thought there is maybe some clever guy who has an idea about my issue, there is always a guy like this...most of the time 3years later rollin his dice, and sayin (later then) how stupid the people were these days and he knew it all day long...Whatever i'm pleased enough with your answer and will do it the old way. NoWhereMan_(DSvY) 07:23, 9 February 2011 (UTC)
Hello, I'm relatively new on this Wiki, so I'm not sure that the following suggestion hasn't already been discussed before.
When you create an article a level under an already existing article, you get a nice navigation bar that can quickly get you back to the root article. The problem is that when the page you're browsing is localized, the links in that navigation bar will bring you on the English version of the wiki... and not on the localized version you were using.
This picture sums it up pretty well : . As you can see, in this example /fr should be appended to the root "WebAPI" link.
I first asked Moussekateer about it and he told me I should drop a line on your talk page, so here I am. Heffebaycay 16:53, 13 February 2011 (UTC)
- I'm not sure of a proper fix to this problem. Some JS code could be written to correct the links but it seems like a hacky solution for something that only occurs on a small section of pages. I'll look into it nevertheless but I suggest maybe creating a navigation bar-type thing for the WebAPI pages? That would probably be the best solution. seb26 [talk] 19:58, 13 February 2011 (UTC)
Text shadowing
Wow, I like it! I even used it in the CSS of my server's MOTD on like, everything (though I did change the color to #13110E, abit darker). But hey, here's an idea: If I think the text shadowing looks good on that quality hex code chart, maybe you should start a new wiki-wide poll/discussion, and see what people think of the text shadowing. If enough people like it, then I say add the text shadowing to the itembox template. What do you think?
By the way, here's what the item quality template would look like if you changed the background behind the text to #24201B, and changed the text-shadow to #13110E. Personally, I think it looks alot better. 404 User Not Found 18:47, 17 February 2011 (UTC)
Color | Quality Name | Example |
---|---|---|
#B2B2B2 | Normal | Scattergun |
#FFD700 | Unique | The Degreaser |
#476291 | Vintage | Vintage Natascha |
#4D7455 | Genuine | Genuine Sun-On-A-Stick |
#8650AC | Unusual | Unusual Napper's Respite |
#70B04A | Community | Community Medi Gun |
Self-made | Self-Made Dalokohs Bar | |
#A50F79 | Developer | Valve Rocket Launcher |
Greetings, Wintergreen suggested that I ask you about the new Navs. I don't think that he/she trusts me though, which may explain why there is a note pinned to my clothing. Let's see, what does it say... Oh yes, I am supposed to ask you about the Template:All_class_nav, and how Wintergreen and I should proceed. Does anything more need to be done? Is any tweaking required? Just let us know if you would be so kind. Esquilax 23:27, 20 February 2011 (UTC)
Need to talk to you
Seb, I need to speak with you over steam at some point, when you have time. --Org 08:34, 25 February 2011 (UTC)
Model Viewer
Hi, it's possible to do this for a fast view of weapons (and with other items)? I think that's it a great idea for the wiki =D Dio 00:54, 27 February 2011 (UTC)