Misplaced Pages

User talk:Edokter

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

This is an old revision of this page, as edited by Edokter (talk | contribs) at 15:25, 2 January 2015 (→Please do not pre-empt the outcome of an "XfD" discussion: I will roll back). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 15:25, 2 January 2015 by Edokter (talk | contribs) (→Please do not pre-empt the outcome of an "XfD" discussion: I will roll back)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

This is Edokter's talk page, where you can send him messages and comments.
Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10Auto-archiving period: 30 days 

If you leave me a message, I will respond here.

Question at Village Pump

https://en.wikipedia.org/Wikipedia:Village_pump_(technical)#AfC_Invite_Template_Questions

Template:Irrational number

(Revert per BRD; this is an accessability nightmare.)

And you don't regard small symbols clustered together among potentially confusing dots/interpuncts as an accessibility nightmare..?
Sardanaphalus (talk) 01:27, 29 November 2014 (UTC)

Not at all. Dispersing the links over two table rows however, is. -- ] {{talk}} 08:41, 29 November 2014 (UTC)
  • Not at all..? That's... interesting. (Do you have any vision impairment?)
    As regards the "dispersing" of links, the intention was to maintain a distinction between these numbers' particular names and symbols whose reference can change. Perhaps, though, you'd accept links that included the symbols..?
Would you object to the use of e.g. Template:Tnf to give this template's contents some room to be seen more readily?
Sardanaphalus (talk) 20:54, 4 December 2014 (UTC)
It is a list of links, so it should be formatted as such. Any other structure for the sake of presentation is hurting accessability. I see no benefit in using columns either. -- ] {{talk}} 20:58, 4 December 2014 (UTC)
When you refer to accessibility, do you have something like screen-readers in mind..? Sardanaphalus (talk) 22:29, 4 December 2014 (UTC)
Yes. Perhaps WP:ACCESS is a good read. -- ] {{talk}} 23:55, 4 December 2014 (UTC)
It's something to read if you haven't done so. I also wonder if you have accessibility as regards editing in mind. Perhaps, from time to time, too much is relinquished for the sake of making something "accessible" to screen-readers and/or editors over non-editors and/or those without (visual) impairments. (The subtext, in other words: screen-readers etc also need to develop; and isn't, ultimately, the point of an encyclopedia to be presented and consulted more than edited..?) Sardanaphalus (talk) 01:54, 5 December 2014 (UTC)
Accessability is not an aption. It is not something to let go in favor of prettyness. Rest asured that screen readers are constantly being upgraded, just ask User:Graham87, who is using one. (One copy of JAWS cost over $1000!) -- ] {{talk}} 09:20, 5 December 2014 (UTC)
Prettiness..? Please don't confuse prettiness with presentation (more precisely, its Prägnanz). Accessibility of both output and code may be the ideal, but surely not the accessibility of editing code at the expense of the accessibility of its output..? Sardanaphalus (talk) 21:13, 5 December 2014 (UTC)

Media Viewer RfC close

A half-close on just part 2 was previously reverted as improper. Please either do a full close or withdraw your partial close. (Or better yet withdraw the partial close and list yourself as a first name for a panel of 3 to do a full close, as multiple people have said this warrants.)

Note that Part 1 issues an immediate call to implement. A "No consensus" result on part two eliminates the 7 day bar against immediate implementation. As noted in the discussion section, consensus can be reached on part 2 by dropping the final bullet point of part 2. Alsee (talk) 20:17, 5 December 2014 (UTC)

I attempted to discuss this with you in good faith, you have demonstrated bad faith by going actively non-responsive both here and on Administrator's Noticeboard. (I find it painfully notable you are exactly repeating MDann52 actively non-responsive behavior, and that it was a contributing factor in the case against him.) You leave me no choice but to file a formal action on Administrator's Noticeboard. ******** In the middle of writing this I see someone has preformed a close on the RfC just moments ago. Consider this a notice that I have a standing objection to your part2 close and I may still file a close review, but I am am going to examine this new development before filing formal action. Alsee (talk) 17:17, 10 December 2014 (UTC)

How long are you going to badger me over this? I have closed the RfC (or part thereof) and you don't agree with the outcome. What "formal action" would you seek? That someone else reclose it until it agrees with your desired outcome? I don't think that os going to happen. If it was a bad close, another administrator would have taken some action already, but none have. -- ] {{talk}} 18:37, 10 December 2014 (UTC)
I have avoided "badgering" you. However I am required to notify you of WP:Administrators'_noticeboard#Close_Review_Request_after_overturn_and_reclose Alsee (talk) 13:29, 17 December 2014 (UTC)

A barnstar

The da Vinci Barnstar
Great detective work. I didn't even realize the WW2 navbox even had those icons. Oiyarbepsy (talk) 06:41, 12 December 2014 (UTC)

Template:Tag and /doc

(Not an accident; these are superfluous and redundant.)

Like the state= in Navboxes etc..?

Also, why did you remove the correction to the code heading?

(Rv; tables are too wide, even at 1280px wide!)

What are you trying to view this on? No problems here, at whatever (reasonable) resolution tried. (Usual is 1680 by 1050.)

But if there is a problem, why didn't you try to fix it?

Sardanaphalus (talk) 18:31, 14 December 2014 (UTC)

Where to begin...? I'm viewing this on my 1280x960 screen. 1280 is still the most common screenwidth used. If you think everyone sees the internet as you do on your screen, then you have a problem; Let's forget mobile and tablets! If your layout is breaking outside screens of 1024 wide, it is considered badly broken design.
I also do not have the time to go through all the changes and weed out the mistakes. That usually means a revert of most recent edits. You cannot expect other to clean up the mess. (Though I try to weed them out.)
The parameters again... In templates, there is no need to complement unnamed parameters with named one, and vice versa. If you pay a little attention to where each is used, you will find unnamed parameters are ususally ulilized for required and subsequent optional parameters where no ambiguity can exist. Any more complex parameter structure uses named parameters, or they are added as additional parameters where unnamed parameter already exist. But never should named and unnamed parameter names be combined to accept both. Your approach to provide maximum flexibility (at least, that is what I asume), only runs the risk of creating ambiguity, and locking up the code, blocking any future development (especially in core- and meta template). So I am keeping an eye out on your edits, and will revert (or fix when possible) if they cause any potential problems. -- ] {{talk}} 22:32, 14 December 2014 (UTC)
  • Where to begin...? Indeed. Before posting the above, did you read through it imagining it was directed at you?
"I also do not have the time to go through all the changes and weed out the mistakes. That usually means a revert of most recent edits ... (Though I try to weed them out.)"
You "choose not to spend time going through all the changes to weed out what you've decided are mistakes"; that is what "usually means a revert of most recent edits". Mistakes or not, if you did try to "weed them out", reversion wouldn't be your default response; nor would it be your default response<aside>accompanied by a dismissive and/or patronizing and/or authoritarian comment or commentary (as, for instance, above)</aside> if you did try to work things out with good faith and in collaboration.
You report that tables are "oversized"<aside>as a result, I imagine, of how the page appeared on your screen/screens?</aside> but give no indication or suggestion as to what may be amiss, even after a report that they seem fine at various resolutions (including, incidentally, 1280 by 960). As regards parameters, your attention may've been drawn away from situations that are already potentially ambiguous: Template:Tnf, for example. You are mistaken if you believe I'm aiming to provide maximum flexibility – which, even if that were the case, does not necessarily nor "only" run the risk of creating ambiguity and "locking up the code".
Reversion and keeping an eye on someone's edits... Sounds miserable.
Sardanaphalus (talk) 09:28, 16 December 2014 (UTC)
Deal with it... It may sou harsch, but we are all volunteers, and you cannot demand from someone to fix your mistakes. I give pointers where I can, but if you are reverted, the first place to post comments is the template talk page, not here. You seem to take this too personally; it isn't. However, your editing style resembles a "do first, ask questions later" attitude, and that does not go well with other editors, including me. I watch a lot of templates, and I find edits that adds overcomplicated code/CSS while not providing any net gain, I will revert. So stop coming here, and discuss the issues on the apropriate talk page in the future. Again, this is nothing personal; your code just sucks. -- ] {{talk}} 11:17, 16 December 2014 (UTC)
  1. "...you cannot demand from someone to fix your mistakes." (Note authoritarian tone; not volunteer-like).
    Where is this demand?
  2. "...the first place to post comments is the template talk page, not here."
    Have you considered<aside>with good faith in mind</aside> why I choose to make posts such as the above here rather than elsewhere?
  3. "...You seem to take this too personally"
    Given the manner of your interaction, you don't think that might apply to you?
  4. "a "do first, ask questions later" attitude"
    More accurately, a "do something, see what happens" approach, otherwise too much time disappears. It's preferable to a "revert, reprimand and dismiss under the guise of discussion" approach.
  5. "...while not providing any net gain"
    A net gain – according to whom?
  6. Someone's code might suck, but, sadly, rigidity and the need to be right suck far more fundamentally. It's not a black-or-white world.
Sardanaphalus (talk) 12:30, 16 December 2014 (UTC)
Your opinion of my "choose not to spend time" implies a demand that I do. I fail to see how stating fact is in any way authoritative. If you cannot be bothered to make time to discuss your changes, then don't complain when you are reverted. Being bold never ensures your edits stick. My urging you to take it to the template talk page is nothing more reminding you of WP:BRD. If I do seem dismissive, it is only after having to revert multiple time for the same reason. -- ] {{talk}} 12:44, 16 December 2014 (UTC)

CSS image crop

Edok, you mentioned an editor introduced a bug into Template:CSS image crop. It's probably a good idea to summarize the bug on the talk page to hopefully prevent others from making the same mistake. Oiyarbepsy (talk) 20:22, 15 December 2014 (UTC)

That won't help. A comment in the template itself may work though. -- ] {{talk}} 20:25, 15 December 2014 (UTC)
I'm sure you've notice the suppress output newlines button by now. You may also find enter "max" in bSize instead of a specific value to be helpful. Also fixed the "XXX>YYY" when scaling down. What do you think of the new buttons? Oh, and by the way, you're welcome to tweak the aesthetics a bit if you'd like since you've got much more skin making experience than I do. Just be careful about moving the crop image preview box because the click to crop lines may not line up properly if you change that. —CodeHydro 21:19, 19 December 2014 (UTC)

Cascading Style Sheets

(Table columns are Bad™)

What, then, produces an output along the lines of the previous version, i.e. with columns whose widths depend on their contents (or perhaps the widest content) rather than e.g. a (potentially very wide) screen width?

(And if table columns are "bad", why are they a standard, a staple?)

Sardanaphalus (talk) 12:23, 17 December 2014 (UTC)

The preferred way is using CSS columns (and {{div col}} is the only generic template using CSS columns). -- ] {{talk}} 16:02, 17 December 2014 (UTC)
  • Perhaps placing Template:Tnf within a width-limiting div will work. I'll experiment.
What problem/s do wiki/HTML table columns create that CSS doesn't..?
Sardanaphalus (talk) 10:49, 20 December 2014 (UTC)

@Sardanaphalus: Table columns are for tables, not for formatting. They’re a standard because tables are a very good way of displaying tabular data. —174.141.182.82 (talk) 06:46, 20 December 2014 (UTC)

<q>...</q> in titles...</q>_in_titles-2014-12-20T06:37:00.000Z">

Since there barely seems to be any interest in the question at WT:AT (which seems the logical place for it), I wanted to ask you if there’s a project page that does have discussion about it. Thanks. —174.141.182.82 (talk) 06:37, 20 December 2014 (UTC)...</q>_in_titles"> ...</q>_in_titles">

Not that I know. So by all means, post your thought there. -- ] {{talk}} 09:37, 20 December 2014 (UTC)

Template:Edit template-protected/editintro

(Undid revision 639370927 by Sardanaphalus (talk) ......

Were all changes I made here improper / unacceptable / not to your taste / etc ..?

Sardanaphalus (talk) 20:19, 23 December 2014 (UTC)

Template:Infobox television-related

Hi. I was wondering if there is a way to have co-producers added to the Template:Infobox-television page since some of the shows and cartoons have co-producers. Or is there another way to list co-producers? I'm just asking. --Rtkat3 (talk) 03:14, 26 December 2014 (UTC)

I think they can be listed under 'Producers', but maybe you should ask on Template talk:Infobox television or Misplaced Pages talk:WikiProject Television. -- ] {{talk}} 09:44, 26 December 2014 (UTC)

Doctor Who episodes

A working version of the use of sublists in List of Doctor Who serials is now viewable in my sandbox. Edits have included conforming table widths, all tables using two decimals for viewership, using one source for all viewership/AI sources instead of a mess of multiple, removing minisodes (these can be added to Other Stories, given that they're not actual episode that contribute to the television series), no double lines after each table, among others (available in the sandbox history). Your thoughts? AlexTheWhovian (talk) 04:41, 27 December 2014 (UTC)

That looks great! But I thought the whole point was to transclude the series tables from their respective pages? Or are you planning to makes these changes there? -- ] {{talk}} 09:17, 27 December 2014 (UTC)
Aye, exactly. The edits I've done to the tables in my sandbox, I'll put these modifications across to the respective series pages (adding the summaries back in), then transclude the series table to the TV series list. So, all good to proceed? AlexTheWhovian (talk) 09:21, 27 December 2014 (UTC)
Go ahead. -- ] {{talk}} 09:23, 27 December 2014 (UTC)

Civil service

(→‎See also: Fix hacky dovs, list layout and bypass redirects)

Thanks for drawing my attention to the nocolbreak class. What makes it less "hacky" than display:inline-block;..? Sardanaphalus (talk) 19:41, 1 January 2015 (UTC)

Inline-block's pupose to to display a block element inline. It only worked because the lists inside it were block element too. -- ] {{talk}} 19:59, 1 January 2015 (UTC)
Okay. I've made a note of nocolbreak. I'm sorry to see that you appear set against the point of "Start/End div col" and I'm wondering what you make of . Sardanaphalus (talk) 23:18, 1 January 2015 (UTC)
I have to echo Redrose64's comments. The use of comment markers should be minimal. Although WediaWiki strips these markers, they are technically not allowed inside HTML tags, but are considered allowable (sparingly) inside parser functions. -- ] {{talk}} 23:27, 1 January 2015 (UTC)

Please do not pre-empt the outcome of an "XfD" discussion

Please do not pre-empt/second-guess/presume the outcome of a " for discussion" discussion by making edits such as these. At least one of them also involved removals that were not addressed in the edit summary. I have requested that Misplaced Pages:Redirects for discussion/Log/2015 January 1#Template:Start div col is closed as subverted and will now restore the pages these edits have affected.

Sardanaphalus (talk) 12:06, 2 January 2015 (UTC)

I am merely preparing for a potential outcome. You reverting everything is quite disruptive, so I will roll back. -- ] {{talk}} 15:25, 2 January 2015 (UTC)