This wiki is a XML full dump clone of "Heroes Wiki", the main wiki about the Heroes saga that has been shut down permanently since June 1, 2020. The purpose of this wiki is to keep online an exhaustive and accurate database about the franchise.
User talk:Admin: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Hardvice No edit summary |
imported>Hardvice nevermind |
||
| Line 54: | Line 54: | ||
** Haha. Check your talk page, we were thinking the same thing. I'll rename your account now. ([[User:Admin|Admin]] 18:18, 5 October 2007 (EDT)) |
** Haha. Check your talk page, we were thinking the same thing. I'll rename your account now. ([[User:Admin|Admin]] 18:18, 5 October 2007 (EDT)) |
||
*** Thank you! ([[User:NissanVersaDootDoot|NissanVersaDootDoot]] 18:36, 5 October 2007 (EDT)) |
*** Thank you! ([[User:NissanVersaDootDoot|NissanVersaDootDoot]] 18:36, 5 October 2007 (EDT)) |
||
==Greasemonkey== |
|||
* You don't by any chance have any experience writing Greasemonkey scripts, do you?--[[User:Hardvice|Hardvice]] <small>[[User talk:Hardvice|(talk)]]</small> 07:17, 6 October 2007 (EDT) |
|||
Revision as of 11:30, 6 October 2007
Instructions
When posting here, please post at the bottom and use the following example syntax:
==Title of your message== *This is your message to me. (~~~~) **This will be my reply. (~~~~)
this will make it easier for me to keep track of conversations.
If I post or contribute to a conversation on your talk page then there's no need to repost the conversation here on mine. I'll either watch your page or check it frequently myself.
Thanks!
| Archives | Archived Discussions |
|---|---|
| Oct-Nov 2006 | Timezones? • Wikipedia (RE: Genesis) • Categories • GD Library • OMG • A Possible Site Logo • Episode Template • Forgot to ask • Adding my fan site • Adding a german version • Main Page: Podcasts • Portal Pages • XML Files for Upload? • French interlanguage links from German wiki • Renames • Portal Pages & Screen Resolutions • Google Adwords • greetings from wikia • Changing Screen cap to {{image-screenshot}} • Pages for Deletion • Google Translations |
| Dec 2006 | excess redirects • Audio uploads • Redirects • Template:Infobox • Community Building • Contributor Category • Template Form • Hebrew HeroesWiki • Re:Interwiki links • Seven Minutes to Midnight ATOW stuff • Peter's sketch • Hits per Page • 10th Wonder salute! • Re:Vandalism • Admin • blurbs on graphic novels • Merry Christmas! • YouTube Embedding • Spelling |
| Jan-Feb 2007 | Image rendering problem • Meta: StringFunctions • Episodes to Chapters • IMDb Images • Edits not registering on "Recent changes" • Re: Affectations on HRG's Glasses • StringFunctions • Mark as Patrolled • Clach • Removing info • Re: Hebrew site • Authors of Changes and EMail Notifications • AFD • Ad blocking • Spelling Nazi • Hana Gitelman page and notes regarding email/IMs • MediaWiki Without Subdirectory? • Angela Petrelli • Page Restoration • Site Translation • Well I WAS a little harsh... • Section Edit links • Userboxes • The Traffic? • Links • Fan Creations - Incidental Heroes • Heroes Wiki Contributor • Interwiki Links • Sorry to sound pushy... • Airdates • Edit Count • Linderman |
| Mar-Apr 2007 | The activatingevolution.org stuff • Heroeswiki in Portuguese • Suggested mediawiki plug in • An Area for Descriptions & Links to Heroes Fanvids • Two questions? okay • Linkage to Got-Heroes.com • MSN • New Category • Admin • Finding Copy/Pasted Articles • Oh crap • CSS? • Ice Vision • Dates • Interwiki links • Linderman & www.heroesforum.co.uk • Bots attack!! • Slow day? • Belgium • New Namespaces? • Old Linderman Archive picture changed • Thank you! • Seeking your inputs • Request for Spanish Subdomain • Lists • War Buddies User List |
| May-Jun 2007 | Votepetrelli.com Texts • Admin • Hmmm • Persuasion power for Sylar • Redirect • Parody category • Request on Got-Heroes.com again • Hello • Main Page intro • Free wiki hosting with profit sharing • New server • thanks :) • Lag? • A request • Domain • Job Queue • 2 Questions • Strange Behaviour of functions • Site down • GD Library • Working... • Spanish • Chinese • Jason La Padura interview • Site Notice • Joe Kelly • JavaScript |
| Jul-Sep 2007 | Ad-jacking? • Interwiki • Hungarian • Other languages not working • Searching • Happy SysAdmin Day • Spoilers on german Wiki • My friend • French Wiki • PNG • Timeout • Mediawiki plug in suggestion • Bionic Woman wiki • Digging • Ding! • Shirt • Site Crash • Stats update • Hi • Move Timing • French Ad • Seth images • Skins • Patrol shortcut on new pages • Displaying foreign characters • nl.heroeswiki.com • Daniel Linderman • Four Months Later synopsis • Problem with Wiki-Function in german wiki • Prison Break Wiki • "sister wiki" • Rounded Corners |
Rounded Corners implementation
- Where is this Nifty talk page? Now you got me interested in checking it out. PS: Spraying the pan with Pam, even the generic kind, helps too. ;)--MiamiVolts (talk) 22:22, 30 September 2007 (EDT)
- Ok, I found the link in MediaWiki:Common.js and refreshed my memory. I think this was discussed before, but I'm not sure how you are considering to implement it now. We could define a new class for tables and divs that automatically converts the borders to be rounded when specified. And another thing to note is not every box or even every corner needs rounding... the character box is fine as-is, imho.--MiamiVolts (talk) 00:21, 1 October 2007 (EDT)
- Character box is already rounded in browsers which support it. What we're talking about is making the IE version look like the Firefox version. We're not going to pick and choose which ones to make look like they were rendered in a competent browser.--Hardvice (talk) 00:52, 1 October 2007 (EDT)
- I'm at loss, then, as to why you were suggesting needing to change template code to make it work in IE? Couldn't the changes just be done in MediaWiki:Common.js after testing that the browser is IE?--MiamiVolts (talk) 01:24, 1 October 2007 (EDT)
- No. Nifty corners requires a combination of CSS and Javascript. The CSS needs to be in the templates for the script to affect them.--Hardvice (talk) 02:54, 1 October 2007 (EDT)
- Hmm, when I view the source for the main page in IE, I see things like "-moz-border-radius:10px;" as a table attribute. That's what firefox uses to determine that a corner is required and I thought you could just add the extra info IE needs every time such code appears. I'll take a closer look at Nifty tommorrow and try to determine what the CSS is that needs to be added tp the templates (not Common.css). I'm not seeing it right now.--MiamiVolts (talk) 03:36, 1 October 2007 (EDT)
- We're actually already working on this offsite and have a pretty good idea what we're doing. The Nifty script we're using requires that IDs be assigned to the elements to which it will be applied. Those IDs need CSS at both the stylesheet level and the wiki article level, as well as individual function calls in common.js, and a lot of the markup we currently use in our templates is incompatible with the way the script does up the rounded corners. Since the CSS needs to be in the template level anyway, we're looking at possibly replacing, not supplementing, the -moz-borders (the script generally leaves things looking OK if Javascript is turned off, so it's possible to leave the moz code in and make the Javascript agent-specific, but we might have to make incompatible changes to the templates because some of the stuff we do all the time in templates (like image links) breaks the way the script renders either borders or corners.) But yes, to get it to work properly in a wiki, we need three separate things (well, four if you count the actual script): a function call in common.js, a style block in common.css, and at least an ID (and possibly an inline style block, depending on the formatting) in the individual element to which it needs to apply. Since a lot of the actual formatting (colors, borders, and the like) is specified in both common.js and common.css, it's not quite as simple as setting up a class and applying it to all the elements we want affected--and that's setting aside the compatibility issues with the actual existing markup in our templates. We can't simply apply the same class or ID to all corners we want rounded on the whole site because each function call needs to know the inside and outside colors of the corner, the border style, the corner size, and which corners to round, and that changes from template to template. One function won't do it; neither will one class in common.css--and in any case, we're always going to have to go through each and every rounded element to assign an ID so the script will apply to it and make sure the markup doesn't break the corner rendering.--Hardvice (talk) 04:40, 1 October 2007 (EDT)
- You can do multiple functions and class definitions in common.js, and I don't see why you can't grab all of that info. using one or more javascript functions and pass it to another. Thanks, I appreciate the lengthy explanation, but the only thing that made sense to me is about the image links breaking the script. I'll check into it more, I guess, when you finish adding it, since it's being worked on offsite where I can't see.--MiamiVolts (talk) 13:50, 1 October 2007 (EDT)
- We're actually already working on this offsite and have a pretty good idea what we're doing. The Nifty script we're using requires that IDs be assigned to the elements to which it will be applied. Those IDs need CSS at both the stylesheet level and the wiki article level, as well as individual function calls in common.js, and a lot of the markup we currently use in our templates is incompatible with the way the script does up the rounded corners. Since the CSS needs to be in the template level anyway, we're looking at possibly replacing, not supplementing, the -moz-borders (the script generally leaves things looking OK if Javascript is turned off, so it's possible to leave the moz code in and make the Javascript agent-specific, but we might have to make incompatible changes to the templates because some of the stuff we do all the time in templates (like image links) breaks the way the script renders either borders or corners.) But yes, to get it to work properly in a wiki, we need three separate things (well, four if you count the actual script): a function call in common.js, a style block in common.css, and at least an ID (and possibly an inline style block, depending on the formatting) in the individual element to which it needs to apply. Since a lot of the actual formatting (colors, borders, and the like) is specified in both common.js and common.css, it's not quite as simple as setting up a class and applying it to all the elements we want affected--and that's setting aside the compatibility issues with the actual existing markup in our templates. We can't simply apply the same class or ID to all corners we want rounded on the whole site because each function call needs to know the inside and outside colors of the corner, the border style, the corner size, and which corners to round, and that changes from template to template. One function won't do it; neither will one class in common.css--and in any case, we're always going to have to go through each and every rounded element to assign an ID so the script will apply to it and make sure the markup doesn't break the corner rendering.--Hardvice (talk) 04:40, 1 October 2007 (EDT)
- Hmm, when I view the source for the main page in IE, I see things like "-moz-border-radius:10px;" as a table attribute. That's what firefox uses to determine that a corner is required and I thought you could just add the extra info IE needs every time such code appears. I'll take a closer look at Nifty tommorrow and try to determine what the CSS is that needs to be added tp the templates (not Common.css). I'm not seeing it right now.--MiamiVolts (talk) 03:36, 1 October 2007 (EDT)
- No. Nifty corners requires a combination of CSS and Javascript. The CSS needs to be in the templates for the script to affect them.--Hardvice (talk) 02:54, 1 October 2007 (EDT)
- I'm at loss, then, as to why you were suggesting needing to change template code to make it work in IE? Couldn't the changes just be done in MediaWiki:Common.js after testing that the browser is IE?--MiamiVolts (talk) 01:24, 1 October 2007 (EDT)
- Character box is already rounded in browsers which support it. What we're talking about is making the IE version look like the Firefox version. We're not going to pick and choose which ones to make look like they were rendered in a competent browser.--Hardvice (talk) 00:52, 1 October 2007 (EDT)
- Ok, I found the link in MediaWiki:Common.js and refreshed my memory. I think this was discussed before, but I'm not sure how you are considering to implement it now. We could define a new class for tables and divs that automatically converts the borders to be rounded when specified. And another thing to note is not every box or even every corner needs rounding... the character box is fine as-is, imho.--MiamiVolts (talk) 00:21, 1 October 2007 (EDT)
Rounded Corners - involved?
- Is it really that involved, though? There are less than 200 templates, and as far as I can tell, it's mostly a cut and paste job after the script is written. Or am I completely missing something. BTW, the best gravy has chunks. -- RyanGibsonStewart (talk) 22:38, 30 September 2007 (EDT)
- It depends. Most of them will be cut-and-paste. And most of the infoboxes are enough alike that, even if we have to redo them, we can do it once and update twenty or so templates quickly. But some of them are designed in ways that are incompatible with the Nifty scripts, so we might have to recreate them--particularly anything with alternate or variable colors. I messed around with the character box, for example, and it might prove challenging. The nice thing is we can pretty much spend as long as we want getting them working on the other site, and then copy them over here when they're working. Some other snags: it's not going to work very well with pages that have more than one blurb without some redesign work. It's manageable, all in all, but I wanted to make sure we agree it's worthwhile before we start ripping stuff apart.--Hardvice (talk) 23:18, 30 September 2007 (EDT)
- Did things really look that bad using IE7? Or did they just look different? Maybe it's just easier for me to force everyone that comes here to install Firefox. :) I wouldn't do that, but I can wish. (Admin 23:45, 30 September 2007 (EDT))
- It depends. Most of them will be cut-and-paste. And most of the infoboxes are enough alike that, even if we have to redo them, we can do it once and update twenty or so templates quickly. But some of them are designed in ways that are incompatible with the Nifty scripts, so we might have to recreate them--particularly anything with alternate or variable colors. I messed around with the character box, for example, and it might prove challenging. The nice thing is we can pretty much spend as long as we want getting them working on the other site, and then copy them over here when they're working. Some other snags: it's not going to work very well with pages that have more than one blurb without some redesign work. It's manageable, all in all, but I wanted to make sure we agree it's worthwhile before we start ripping stuff apart.--Hardvice (talk) 23:18, 30 September 2007 (EDT)
Please Change my Username
- So I tried to change my username via move. It didn't work. I tried changing my nickname and some redirects. Close, but no cigar. Could you pretty please change my username to Yatta!? If you think it'll confuse people between the User and the article, don't sweat it and I'll just stick with Danielandthelions (NissanVersaDootDoot 18:17, 5 October 2007 (EDT))
- Haha. Check your talk page, we were thinking the same thing. I'll rename your account now. (Admin 18:18, 5 October 2007 (EDT))
- Thank you! (NissanVersaDootDoot 18:36, 5 October 2007 (EDT))
- Haha. Check your talk page, we were thinking the same thing. I'll rename your account now. (Admin 18:18, 5 October 2007 (EDT))