User talk:קיפודנחש

Template parameter
I wanted to say thank you for creating the template parameter gadget. I stumbled across it today, and I can tell it is going to be very useful. Also, I have created a documentation page for the template in your userspace by copying your post from the Village Pump. Thank you! ~Adjwilley (talk) 21:11, 19 November 2012 (UTC)
 * you are welcome (and thanks for salvaging the doc from vpt). unfortunately, i do not know my way around enwiki (politically speaking) to successfully push this to become a sanctioned gadget (as it is on hewiki and arwiki). peace - קיפודנחש (talk) 22:30, 19 November 2012 (UTC)

Signature
Shalom,

I've seen you around the village pump and was just wondering if you'd mind adding a Latin-alphabet component to your signature as a courtesy to those of us who can't read Hebrew? There's a suggestion at WP:SIG.

Best wishes, — Hex    (❝  ?!  ❞)   10:57, 5 December 2012 (UTC).
 * sure, no problem. i usually do not touch my sig in different wikis, and it's the same everywhere (i have > 0 contribution counter in some 17 wikis, though many of them are just for single-digit edits - see Special:CentralAuth/קיפודנחש).
 * peace - קיפודנחש (talk) 14:49, 5 December 2012 (UTC)
 * test -קיפודנחש (aka kipod) (talk) 14:51, 5 December 2012 (UTC)
 * ! — Hex    (❝  ?!  ❞)   15:00, 5 December 2012 (UTC)

I would like to learn the alphabet you use (Hebrew, right?) and was wondering if you had any recommendations for a good site to do that? Thanks Kipod. Technical 13 (talk) 01:07, 16 May 2013 (UTC)
 * Shalom,
 * ahmmm... believe it or not, but when i learned the language there was no internet (literally - it took them quite a few years after this event to even _begin_ developing ARPANET, not to mention the World Wide Web...). you guessed correctly - the language is Hebrew, but i am not familiar with good sites that teach it. i am sure there are such sites, though. if you are serious about it and willing to invest some money, i heard good things about Rosetta Stone (not specifically the Hebrew version - as mentioned, i have no use for it). If all you are interested in is just the alphabet, you should probably start by reading Hebrew alphabet, and continue from there. peace - קיפודנחש (aka kipod) (talk) 15:09, 16 May 2013 (UTC)
 * Thank you! It seems like it shouldn't be too difficult to learn.  In the meantime, I've developed User:Technical_13/Scripts/CommonHebrewUserNames.js so that I can clearly tell your posts apart.  I'd like to develop that script to be able to "translate" if you will any Hebrew name into English/Latin.  Would you be interested in helping with that?  Technical 13 (talk) 14:30, 17 May 2013 (UTC)

Rollback
Following the discussion at WP:VPT I've just given you the rollback permission. I would suggest caution in using it for anything other than testing but you seem trustworthy enough to read the documentation before using it for anything else. If you do not want the permission just let me know and I'll remove it again. Dpmuk (talk) 05:09, 10 December 2012 (UTC)
 * so i created User:קיפודנחש/apiRollback.js.
 * here is how it works: it changes the behavior of the "rollback" link in:
 * recent changes
 * watchlist
 * history view
 * diff view
 * i do not know of any other place where "rollback" links exist, but if there is such a place, we prolly want to add it too.
 * the new behavior is so:
 * when pressing "rollback", instead of being transferred to the diff page once the rollback is successful, you stay on the same page, and a little message appears telling you the rollback was successful, and the "rollback" link itself disappears.
 * if you hold the  key while pressing "rollback", you are prompted to provide a summary. if you press "cancel" or just leave the summary line empty, no rollback will occur. otherwise, the summary you entered will show on the rollback instead of the default one.
 * if you add to Special:Mypage/common.js the following line""rolling back an edit will automatically add the page to your watchlist.
 * let me know what you think.
 * peace - קיפודנחש (aka kipod) (talk) 19:32, 10 December 2012 (UTC)

Consider me appeased!
Success. — Francophonie&#38;Androphilie (Je vous invite à me parler ) 16:43, 11 December 2012 (UTC)

For your work at WP:VPT
Since you already have a da Vinci :

and ribbon.

Thanks!
I've used this to start generating some data on the statistics. =) A belated thank you. Biosthmors (talk) 19:26, 14 January 2013 (UTC)

Lua chess diagrams and graphs
I notice your chess diagram script requires CSS lines. Is this a general problem in Lua we should tell people about? I was fooling around with a "plotter" routine for generally making graphs from numbers at but I was having trouble trying to figure out absolute and relative positioning code that would actually insert a working graph. Is this just me being clueless (very possible) or is that too something that would require common.css to be changed? If so we should point out this general problem. Wnt (talk) 03:03, 21 February 2013 (UTC)
 * i just took the easy rout, i guess. it is possible to inject the "absolute" and "relative" into the styles directly instead of using CSS, so this is not necessarily a limitation of the system. in many cases (like the chess example) 2 simple lines in the CSS can save countless repetitions of  and   statements, but it's not really necessary to use CSS.
 * in any event, it should not be impossible to add a line or two into common.css if it makes life easier for a popular enough template. just look in Mediawiki:common.css - it's full of stuff that's specific to specific templates.
 * peace - קיפודנחש (aka kipod) (talk) 06:43, 21 February 2013 (UTC)
 * Thanks! I RTFMd and started Template:Plotter.  I hope eventually it is something useful, though admittedly there's a way to go... Wnt (talk) 07:57, 22 February 2013 (UTC)

==Re: The user talk on hewiki here== Shalom, I want to thank you anyway because the solution I figured out today, is based on a chess diagram which seems you worked on, too. --DancingPhilosopher my talk 15:06, 22 February 2013 (UTC)

Lua requests
Hi קיפודנחש, I noticed you worked on a Lua script at Module:Chess from fen. I just created a request page for Lua scripts at Lua requests and it'd be great if you could watchlist it to assist anyone who needs help with Lua scripts. Thanks! Dcoetzee 23:30, 23 February 2013 (UTC)
 * sure thing. thanks.
 * if you are active in this area, i think it might be a good idea to create some kind of "Lua workshop" also, where people active in writing lua modules will be able to ask question, share "best practices" knowledge, and maybe even do some shared development (this is possible with Lua, because you can use one module from another module).
 * for instance, i just learned that lua can be snadboxed using the "Template sandbox" infrastructure - i learned it from a comment-in-passing made by User:Anomie in WP:VPT, but it's really not documented anywhere, ttbomk.
 * so if there was this "Lua workshop", this kind of knowledge could be accumulated, and new developers would have some resource to learn and get assistence.
 * if ever such a "Workshop" is established, i would love to be notified, just like you notified me about the requests page.
 * peace - קיפודנחש (aka kipod) (talk) 23:37, 23 February 2013 (UTC)
 * Those are some interesting thoughts. For now some tips are gathered at Lua and Help:Lua debugging, and of course some docs are on the extension's website, but this could definitely use more organisation. Thanks for the suggestions. :-) Dcoetzee 23:47, 23 February 2013 (UTC)

he:שיחת משתמש:קיפודנחש

Totally should have notified you...
Hi Kipod. I found your PGN chess viewer thing from someone else's suggestions and I should have posted on your talk page to let you know that I was reviving it. (WP:Village_pump_%28technical%29)

I'm glad you found out anyway. (I'm pretty new as a Wikipedia editor.)

Chag sameach if you celebrate Passover... Mattj2 (talk) 18:56, 25 March 2013 (UTC)

Re: I knew I should not edit using the !@#$%^ tablet...
– PartTimeGnome (talk&#160;&#124; contribs) 22:57, 30 March 2013 (UTC)

Classic skin and CSS
Thank you for your instructions on modifying Vector. I don't use Vector, but apparently I'm going to have to start.

I'll let you know how your instructions work. DS (talk) 23:18, 4 April 2013 (UTC)
 * I recommend you run your experiments and tests before "Classic" is killed, so you'll have a point of reference and something to compare to. after tax day you'll have to work from memory.
 * peace - קיפודנחש (aka kipod) (talk) 00:01, 5 April 2013 (UTC)

what is in the tleft/tright class?
I thought that replacing a class with a style is simple: you just look it up in the CSS sheet and copy the contents. I found that any attempt to put my imagemap in the pie chart wasn't getting it processed, so I started doing this - but replacing class="tleft" with the margin: statement it appears to contain led to a complete change in output where the graph no longer floats. There's a hint in that a comment by these classes says "@noflip", but I don't see how/where that affects it. Can you explain?

Diff. "Thumb" is either "right" or "left". Wnt (talk) 14:41, 6 April 2013 (UTC)


 * hi. i saw some of your experiments and was going to contact you earlier, but other urgent things kept me... what i am writing here is not 100% authoritative, but i *am* 87.37% sure it is true: the way the parser works, tags are processed *before* templates, and hence, before "#invoke:"s also.
 * so if you want to squirt out an imagemap from a module, you have to use the magicword {{#tag:imagemap . let me know if you need more information about how to do so. as to tleft and tright: they are defined in the vector skin (maybe in other skins also) in the main package. it's not very interesting, but i can dig it up if you want. use "debug=true" and search the resources (chrome). peace - קיפודנחש (aka kipod) (talk) 16:30, 6 April 2013 (UTC)
 * Well, the function returns through frame.preprocess, and more to the point -- I get a link (in the wrong place) if I put the imagemap after the last div tag, just not if I put it after the second to last. I also get the link if I change the class="tleft" to a style I think is synonymous, but I also lose the ability of the chart to float.  My first priority here is to understand what miscellaneous magic occurs in that class="tleft" and how to replicate it in a style I've defined from scratch - until then I'm just playing with a black box with no idea what effect anything will have. Wnt (talk) 17:51, 6 April 2013 (UTC)
 * regarding @noflip: the CSS that comes from bits.wimimedia.org is run through preprocessor that changes right to left and vice verse for RTL wikis. @noflip tells the preprocessor to leave this specific CSS alone. i believe yo can find it here: and  (two separate parts of tleft are defined in those two files). i do not know anything about this preprocess thing - you might be 100% correct, but i still think the right way to do it is via #tag:. also, please note that if you use imagemap, i don't think you should include the Circle image directly: do it as the "File" parameter to imagemap. the reason is layering: when something is layered on top of something else, it captures the events (such as mouse events) and does not let it sip down. since the transparent circle image must be on top of the divs (otherwise it does not do its job), the simplest thing is to wrap it with the imagemap tag, instead of using a different image for the imagemap. also please note that the imagepap is "normalized", i.e., the coordinates are calculated based on the original image size, regardless of the magnification/reduction it's actually displayed. i do see that you tried to place the imagemap on top of everything, but i think you used attribute "z-value", which as far as i know is a mistake: the name of this attribute should be "z-index". again, i believe the best thing you can do is place the imagemap around the image of the circle, instead of adding yet-another-transparent-image on top of everything.
 * peace - קיפודנחש (aka kipod) (talk) 19:02, 6 April 2013 (UTC)
 * Eventually I found the thing - there are actually three rel="stylesheet" links in the source, only one of which has a "css" in it. The first one contains a tleft class, and applies styles to it also.  It isn't actually what was at fault though - I was looking in the wrong place because there was a div buried at the very center of "output".  The hack I picked in the end involves doing a find-and-replace to force the image right where I want it at the center of the output, immediately after the circle image.  I could go back and try to fuse with circle, but for now I'm happy it works!  Now, if only I understood where "noresize" class is defined, I'd be satisfied... :) Wnt (talk) 15:46, 8 April 2013 (UTC)


 * very nice, and congrats for cracking it at last!
 * i still think you are doing one thing wrong: creating a raw tag (using "<" and ">") and then forcing parsing of the output by calling frame.preprocess is not the civilized way to do things.
 * IMO, the correct way is to be polite and return a simple string that contains everything you built, and use the #tag: magic word in the output to induce further parsing of tags (it might also be the more efficient way, which would make wikid77 happy, though i don't think speed should be real consideration here).


 * regarding tleft and tright: you want to use chrome, add debug=1 to the address line, and in "developer tools" you want to go to the "resource" tab, and hit {{Keypress|Ctrl|F}}, and type either "tleft", "tright". the "debug=1" tells the server not to squash/minify the JS and CSS sources, and not to consolidate many pages to a single page. it also lets you see the comments and such in those pages - sometimes you can get useful hints why something happens. as to "noresize": normally "noresize" is not a class, but rather a html attribute. specifically, the imagemap extension squirt a div with "noresize" class (you can find it on line 283 of "imageMap_body.php in latest snapshot on mw:Extension:Imagemap), but this class has no css attributes. it may be there so wikis can define css attributes for it, or so JS script will be able to find these divs on the page. it has no effect (you can try it by running in the browser console a single JS line that will remove this class from all elements, e.g. . nothing in the page display will change after running this line.
 * BTW: you are invited to see and comment on how i create the legends in Module:Chart - you might want to adopt this way also, or you may not want to do so. unlike you, i do not create DIVs, but rather a ul element containing li elements. this allows me to use the "column-width" attribute to display the legends in multiple columns. i think it's better. maybe i should create a sample with large number of legends in the doc page to see how it works.
 * peace - קיפודנחש (aka kipod) (talk) 16:30, 8 April 2013 (UTC)
 * Well, to be honest, I never really understood the #tag magic word - I remember seeing it come out a year or two ago but with no examples of when you'd use it. I could be wrong, but I think that when I didn't frame.preprocess the templates in the output never got expanded?  I don't know where to find a manual on this stuff and everything is just based on whatever I saw/whatever worked last time.  I meant to rewrite the part with the legend templates at some point, but haven't gotten around to it.  (They depend on something with "safesubst", which I don't understand what the point of that is either).  Your idea with ul's and li's may indeed be good - I'll have to look it over carefully.  The divs I used in this function were copied directly from the original template.
 * Thanks for the suggestion about Google Chrome ... the problem is, last time I had Google software (Google Earth) on the computer, it was creating slowdowns and annoyances with its mandatory hourly updater, and it didn't uninstall properly, won't reinstall without an error either, and it took all kinds of deleting and disabling to get it to quit throwing hourly error messages. I am very reluctant to let that plague back on my system. Wnt (talk) 20:44, 8 April 2013 (UTC)
 * regarding #tag: it's explained, e.g., here: mw:Help:Magic words. it's by no means a new thing - defintely way before 1.15. this is what you're supposed to use when you want to generate an extension tag inside a template. i believe "module" here should be considered to be "same as template" for this.
 * regarding chrome: the important part is not necessarily chrome itself, but rather the "debug=1" on the address line (you can just as well use "debug=true"). if you use FF with firebug extension, you can get it at the "CSS" tab on firebug (F12). if you use FF with "Web developer" extension, you can get it through the "View CSS" menu item of web developer. if you use vanilla FF or if you use IE, then i do not know how to find stuff in the CSS, but it's probably also doable the reason i said "chrome" is because a) i'm used to it, and many web developers use it because of the fantastic JS debugger, and b) because it does not require any extension for web development - it's all inbuilt. peace - קיפודנחש (aka kipod) (talk) 21:27, 8 April 2013 (UTC)

Geonotice
Thanks for spotting that - I've no idea how the space crept in. Andrew Gray (talk) 19:24, 16 May 2013 (UTC)
 * space is still there - is it intentional? peace - קיפודנחש (aka kipod) (talk) 21:30, 16 May 2013 (UTC)
 * Sorry, I misread your message and thought you were saying you'd fixed it! I've corrected it now. Andrew Gray (talk) 11:08, 17 May 2013 (UTC)
 * well, i couldn't have possibly modified it - i do not have permissions to modify pages in mediawiki namespace... peace - קיפודנחש (aka kipod) (talk) 15:06, 17 May 2013 (UTC)

chess diagram performance testing
see here. thank you. Frietjes (talk) 00:00, 21 May 2013 (UTC)

Proposal: mark default gadget as "default"
At WP:VPT, you mentioned that the method we use at Commons is rather optimal. While I agree that it isn't good practice to maintain the state at 2 locations, how could we improve this? Wouldn't this require a MediaWiki bug request and a change in the MediaWiki software which usually takes ages? It is already an improvement not having to update each translation if the state changes. But if you could show a way (perhaps a LUA module parsing MediaWiki:Gadgets-definition), this would be great. -- Rillke (talk) 15:42, 12 June 2013 (UTC)
 * I've found that MediaWiki bug requests and change to the MediaWiki software don't really take that long if there is consensus for the change on wiki. I would be happy to submit the request and get that ball rolling. Technical 13 (talk) 16:21, 12 June 2013 (UTC)
 * (working from leaky memory here - don't have time to dig ATM): iirc, what i meant is exactly that: i can't think of a way to improve the way it's done on commons (we do something similar in hewiki). i think improvement to mediawiki software (more precisely, to mw:Extension:Gadgets) is exactly what i meant. i think i even considered opening a new bugzilla ticket, and found one already in existence. again - i believe this is so, but can't be 100% sure the above report is not just some dream i had... peace - קיפודנחש (aka kipod) (talk) 18:41, 12 June 2013 (UTC)
 * I don't see a ticket yet based on my search. Technical 13 (talk) 19:19, 12 June 2013 (UTC)
 * Thanks for reporting this to bugzilla:49501. -- Rillke (talk) 22:07, 12 June 2013 (UTC)
 * i thought i saw one, but now i can't find it. opened a new one: 49501. if it's a dupe, i hope it will be marked as such. if you can find the appropriate wp:vpt discussion in one of the archives, you are more than welcome to add a link (again, i do not have time to do so right now). peace - קיפודנחש (aka kipod) (talk) 22:10, 12 June 2013 (UTC)

Explaining
I patrolled your page. I went through the enormously-backlogged list of newly-created pages and confirmed that your page was okay: not spam, not an attack page, not a copyright violation, not any of the other reasons for which I would delete someone's page without asking. Then I clicked "patrolled" to remove it from the list of "pages that have not yet been patrolled", and moved on to the next entry. That's all. DS (talk) 16:56, 5 August 2013 (UTC)
 * thanks. i forgot that patrolling is active on enwiki (for new pages only). because it's a piece of code, i took the word "review" as in "code review", which was, of course, a silly mistake. thanks.
 * peace - קיפודנחש (aka kipod) (talk) 16:59, 5 August 2013 (UTC)

pgn template
Hi, I am impressed with pgn template at the Hebrew wikipedia, which I saw used in the World Championship 2013 article. Could this gadget be adapted for use in the English wikipedia? MaxBrowne (talk) 00:50, 2 December 2013 (UTC)
 * ok I found the subproject page, village pump discussion, demo page at the Hebrew wikipedia etc. Sorry I haven't kept up with developments. MaxBrowne (talk) 02:12, 2 December 2013 (UTC)
 * the "project page" linked above is not very serious, i think - it was an attempt by a clueless editor to push something forward, despite the fact that this editor does not know (almost) anything about chess, nor about javascript. this "project page" only real value is the links to past discussions.
 * (strike that - i was confused with a different attempt made by a different user. this "project page" is just fine).


 * as to the pgn script and template: the template is a very simple and straightforward package that allows the script to work by wrapping the pgn with some DIVs with specific calsses, so the script knows which pieces of text should be analyzed as pgn. it support some features ot demonstrated anywhere on hewiki (specifically, it supports the FEN= attribute, which allows displaying games from the middle (not very interesting), but also allows displaying games in chess960 (hope i got the name right). i think the script itself is language-independent - the only little perversion is some "easter egg" that cause it, if the user running it has some special line in her common.js, to add two new buttons. pressing these button cause the script to squirt out a Chess diagram template specific to hewiki (on of the buttons cause it to do so for the current state of the game, and the other will generate one template for each of the plys (i think that what you call a "half move", i.e., a single player move). let me know if you need something else. i will be very happy to see this script being used on enwiki, but i do not think it makes sense as a gadget, or user script - it only makes sense, IMO, if it's added globally. it's very easy to add it in a way that will only load the script on pages which contains the template, though, admittedly, we did not bother in hewiki and just added it unconditionally. peace - קיפודנחש (aka kipod) (talk) 21:41, 2 December 2013 (UTC)

Possible css help?
Hey קיפודנחש. Given how facile you appear with css coding from that recent discussion at VPT, I was wondering if you might know a fix for something. Quite a while back they moved the insert symbols field/dialogue above the save page/preview/show changes buttons. It used to be below it (like this). Is there a hack to move it back below the buttons? Also, is there a way to hide the text "By clicking the "Save page" button, you agree to the Terms of Use, and you irrevocably..." Basically, I am trying to make it so that when I open the edit screen on my browser, I can edit and see the save page button in one view, without ever having to scroll down all the time to get to the save page button, which is extra work. Thanks much in advance. Please feel free to tell me it's too much work to find/figure out a hack, even if you could.--Fuhghettaboutit (talk) 23:30, 26 December 2013 (UTC)
 * you can do something, but it's not css - it's js, so it goes in your Special:MyPage/common.js (and not in the css): try it. HTH - קיפודנחש (aka kipod) (talk) 05:10, 27 December 2013 (UTC)
 * Thanks much! I was playing around with it and changing .editButtons to .editOptions makes it perfect, so the symbols are completely below both the edit summary and save page buttons (I know just enough to inspect elements and see what labels you used, though I could never put it together myself). Thanks again--Fuhghettaboutit (talk) 11:20, 27 December 2013 (UTC)
 * of course - this was just dumb of me. i didn't even look at the summary... (in my defense i can say that many editors do not bother to write summaries for their edits, but this is just a bad habit...). if you want to get fancy, you could do:

which puts the most useful stuff immediately under the textarea, and leaves everything else below (now i think it's useful enough that i'll use it myself - thanks for the idea). peace - קיפודנחש (aka kipod) (talk) 16:41, 27 December 2013 (UTC)
 * Aha! that allowed me take it one step further. For me this is the absolute ideal (it gives access to the minor edit button):

I can't even imagine anyone preferring the current setup over it. Much obliged for the help.--Fuhghettaboutit (talk) 00:22, 28 December 2013 (UTC)

Interactive Chessboard
Please see The DJ's comment on the script, as it very well surmises one of the key points that I wanted from the script.

Will this be possible?

TheOriginalSoni (talk) 10:33, 3 January 2014 (UTC)

A comment for you
See. --Piotr Konieczny aka Prokonsul Piotrus&#124; reply here 15:17, 4 January 2014 (UTC)
 * you are too late, my friend: see ... peace - קיפודנחש (aka kipod) (talk) 15:35, 4 January 2014 (UTC)

F8
Sorry, busy with other articles (as you saw). As to the F8 and Noyce, this book from MIT seems pretty direct. However, they may have copied it from the Wiki, but I'm not sure how to figure that. Maury Markowitz (talk) 15:13, 6 January 2014 (UTC)

p.s. Next time perhaps mark it up and take it to the talk page? Not everyone has time to jump to every requested edit in under 24 hours! Maury Markowitz (talk) 15:14, 6 January 2014 (UTC)
 * Maury Markowitz: thanks for the reply, and thanks for pointing to the source.
 * regarding my order-of-actions: in principle you are correct, but in particular, the claim seems so improbable as to be "patently false": noyce left fairchild in 1968, at which time the technology only allowed order-of-magnitude less transistors-per-chip than even the 4004 requires (f8 has roughly double that - around 4000). moreover, the F8 was produced using a technology (namely, NMOS), which first appeared (in labs and on papers, not in products) in 1969, and first became available in products in 1970, so the claim that he started developing this chip while at fairchild just does not make sense.
 * regarding the quoted source: it is clearly a gross anachronism: it says "a specialty processor created by future intel founder noyce". the F8 was announced in 74 and became available in 75, while noyce left fairchild and founded intel in 68, so a source that talks about "future intel founder" clearly does not know what he is talking about.
 * peace - קיפודנחש (aka kipod) (talk) 17:47, 6 January 2014 (UTC)
 * Good points, all. Maury Markowitz (talk) 18:04, 6 January 2014 (UTC)

Chessboard templates and |reverse=true|
I did test myself with all of the documented chess templates before changing the documentation to say |reverse=true| works with odd-sized (but not alice &c) boards. Please see my sandbox for a whole bunch of test boards. If it really doesn't work for you could you show how you tested, please? Zack (talk) 01:03, 11 February 2014 (UTC)
 * kind of funny, really, since it was i who introduced the "reverse" parameter in the first place...
 * i did it for the 8x8 configuration only. the module (Module:Chessboard, which implements the template now) was changed significantly by other people since the last time i touched it, and when i saw your edit to the documentation, i was excited about it, and immediately tested it to see how it looks with boards other than 8x8.
 * i do not know what happened - possibly i misspelled the parameter or something, because it did not work for me. i guess i should have tested more thoroughly, instead of rushing to reverse your edit. sorry about it. peace - קיפודנחש (aka kipod) (talk) 01:51, 11 February 2014 (UTC)

Talkback
Fai zan  16:10, 19 February 2014 (UTC)

Wikipedia:Village pump (technical)/Archive 124#Difference between revisions pages comment truncation
I replied to your question at Village pump (technical)/Archive 124. —Anomalocaris (talk) 11:03, 26 February 2014 (UTC)
 * answered there. peace - קיפודנחש (aka kipod) (talk) 16:31, 26 February 2014 (UTC)

Template editor right
Hi Kipod. :) I saw your comment on WP:VPT about templates being editable by mere mortals. Actually, I think you probably fulfil all of the criteria to get the template editor user right, which would let you edit most templates on enwp. Your template and module edits here and on hewp are more than enough to show you have the technical knowhow for the right. The only thing that is kind of vague at the moment is that due to your low number of edit requests on enwp (I couldn't find any), it is hard to find evidence that you would know when to seek consensus for potentially controversial template changes. I would be prepared to overlook this if you can confirm to me that you have read TPE and that you'll be careful when updating high-risk templates on enwp. There are certainly a lot of template fixes that need to be done on enwp, so if you can be careful to seek consensus when necessary, it would be great to have your help. Best — Mr. Stradivarius  ♪ talk ♪ 11:35, 23 March 2014 (UTC)
 * thanks. i decided to take your advice and request template editor rights. peace. קיפודנחש (aka kipod) (talk) 17:48, 23 March 2014 (UTC)
 * I've answered the request there and given you the standard template editor message below. Thanks for your response at the request page. — Mr. Stradivarius  ♪ talk ♪ 00:50, 24 March 2014 (UTC)

You are now a template editor
Your account has been granted the  user right, allowing you to edit templates and modules that have been protected with template protection. It also allows you to bypass the title blacklist, giving you the ability to create and edit edit notices.

You can use this user right to perform maintenance, answer edit requests, and make any other simple and generally uncontroversial edits to templates, modules, and edit notices. You can also use it to enact more complex or controversial edits, after those edits are first made to a test sandbox, and their technical reliability as well as their consensus among other informed editors has been established.

Before you use this user right, please read Template editor and make sure you understand its contents. In particular, you should read the section on wise template editing and the criteria for revocation. This user right gives you access to some of Wikipedia's most important templates and modules; it is critical that you edit them wisely and that you only make edits that are backed up by consensus. It is also very important that no one else be allowed to access your account, so you should consider taking a few moments to secure your password.

If you do not want this user right, you may ask any administrator to remove it for you at any time.

Useful links:
 * All template-protected pages
 * Request fully-protected templates or modules be downgraded to template protection

Happy template editing! — Mr. Stradivarius  ♪ talk ♪ 00:49, 24 March 2014 (UTC)

Module:Chart
Hi קיפודנחש, great module. I want including calls function barChart from my module, but an error occurs call with nil value. Could you explain how to call barChart from another module? With thanks Игорь Темиров (talk) 20:59, 27 September 2014 (UTC)
 * Thank you again for your module. See template population from ruwiki. Игорь Темиров (talk) 14:49, 29 September 2014 (UTC)
 * sorry for the late reply - i'm on vacation, with very limited internet access. i'm not sure what is the problem calling the module from another one, but it's true that it is not necessarily designed to be called by another lua module, but rather directly from a page or a template. in general, lua errors a "clickable", and when you click on the error message you get a little more information, including the call stack. you may try this - this way you'll at least know which line in the code makde the fuss. peace - קיפודנחש (aka kipod) (talk) 17:56, 5 October 2014 (UTC)

Your graph expertise
The recent nice graphs by EngineeringGuy on the page for Wikipedia look like they could be improved with your expertise. Could you look at this diff. The fix might be simple to save on the graphic visual space on the Wikipedia page, though I don't know how to do it. Maybe you'll have a good idea. Cheers. FelixRosch (talk) 20:19, 9 October 2014 (UTC)
 * Your recent comment on that Talk page was both practical and useful. If the change could be made to tip the vertical-oriented graphs into 'horizontal' mode on the Wikipedia page, then the saving in visual graphic space would be over 50% of the space on the screen being used. This would be a significant advantage across many other Wikipedia pages which could re-use such a new graph module as well. If I can support further on updating the graphs for the Wikipedia page then let me know. Cheers. FelixRosch (talk) 18:55, 14 October 2014 (UTC)
 * i agree that being able to generate horizontal bar-chart will be useful, but specifically for Wikipedia, i think using more modest height and width will be a good idea, especially width.


 * also, for this specific dataset, i am not sure bar-chart is very useful: some of the numbers, and specifically the "fa" and "ga" numbers are so small relative to the other numbers (mere hundreds or thousands relative to millions), that they are practically invisible on the chart. peace - קיפודנחש (aka kipod) (talk) 20:56, 14 October 2014 (UTC)
 * Yes, that is a good point, and I noticed that the language version was using log-scale to smooth out the "practically invisible" issue. The language graph looks pretty good in using the log scale. I agree that the smooth out factor is important to make the graphs be more visually friendly. Cheers. FelixRosch (talk) 18:02, 15 October 2014 (UTC)
 * currently, Module:Chart does not support log scale. also, this particular graph is a stacked graph, and i am not familiar with any form of stacked graph using logarithmic scale, and i can't imagine one that will be useful. peace - קיפודנחש (aka kipod) (talk) 18:21, 15 October 2014 (UTC)
 * It was just a thought. I have noticed that the very top of the graph over 250K is not used at all and perhaps could be deleted if easy to do. You seem to be the graph module expert and thanks for your answers. shalom - FelixRosch (talk) 19:10, 15 October 2014 (UTC)
 * yes, there's some convoluted logic for rounding-up the top of the graph. "round" numbers are considered to be 10, 15, 20, 30, 40 etc. i prolly could handle it better - unfortunately, not anytime soon. peace - קיפודנחש (aka kipod) (talk) 20:43, 15 October 2014 (UTC)

Template:Infobox college coach
any particular reason for duplicating the templatedata in the doc? Frietjes (talk) 16:59, 25 November 2014 (UTC)
 * i did not notice the templatedata in the doc. when using VE, it told me there is no tempatedata for this template... i might have misunderstood this message, but this is what i think it meant. i will report this as an issue to the VE team, instead. peace - קיפודנחש (aka kipod) (talk) 17:30, 25 November 2014 (UTC)

. — Preceding unsigned comment added by קיפודנחש בע"מ (talk • contribs) 00:23, 3 December 2014 (UTC)

Report an error
Hi! It looks like we (Latvian Wikipedia) are gonna use the Report an error form. So I wanted to ask you, what do we need to do? Request it at Phabricator? If yes, maybe you can give a link with Hebrew Wikipedia's request. -- Edgars2007  (talk/contribs) 18:09, 19 February 2015 (UTC)
 * phabricator is not the right place. this is not core functionality - this is a gadget developed in Polish wikipedia and adopted by a dozen or so other wikis. we, at hewiki, modified the way the tool works: the original tool dumped the whole report (and all of them), in a single designated page. we wanted the single designated page, but we wanted the body of the report to persist in the talk page of the article in question, so what we did was to utilize the relatively new "segment transclusion" feature (so the central page transcludes reports from the articles' talk pages). if you wish, you can do one better, b/c the mechanism was recently enhanced to support "section transclusion".
 * so, as i see it, you have 3 options: adopt the Polish gadget (you should probably consult with the people maintaining it on plwiki), adopt the modified gadget from hewiki, or take the one from hewiki and tweak it to use the newer section transclusion. you would probably do best to choose the 1st option, and see if it works for you. the tweaks in hewiki came from specific requirement of the community, and you may not have similar concerns in the Latvian community. if you find that you want it to work like in hewiki (i.e., the report itself persist in the article's talk page), you can always add the hewiki tweaks later. i'd take a bet, based on geography, and guess that you'll find it easier to discuss it with the people in plwiki... the only person i know who is active both here and there, and knows something about this tool, is User:Matma Rex. peace - קיפודנחש (aka kipod) (talk) 23:09, 19 February 2015 (UTC)
 * Thanks! -- Edgars2007  (talk/contribs) 07:14, 20 February 2015 (UTC)

Request with graph
Hi. Please see here. Gun Powder Ma (talk) 15:46, 25 October 2015 (UTC)


 * Ok, understood. Perhaps a different kind of graph could do the trick? Gun Powder Ma (talk) 09:55, 26 October 2015 (UTC)

Module:Chart
I like charts, mostly pie but also bar, where I really like shades of grey - for normal purposes physically printing is just blackandwhite (and shades of grey). However, I see that these days CSS backgroundimage can be specified. These are lots of different things can be made, but for use here I would just what two textures, and just left top to right bottom or the other way, and narrow chevron or wider.. It be easiest to make one colour by using two pairs the same. – Unbuttered parsnip  (talk) mytime= Thu 02:21, wikitime=  18:21, 18 November 2015 (UTC)

Cat-a-lot Script
Hi, I was recommended to use your cat-a-lot script from User:Ser Amantio di Nicolao but you say that the script is only 3 lines and then there are 5 lines. Have you changed the script since you wrote that?

Also, you say that you are providing a 1 line script which links to another page with the 3 lines of script but it actually links to a page with far more than 3 lines of script. Could you please explain this to someone who is new the world of using scripts of user pages? Thank youMonopoly31121993 (talk) 10:33, 13 December 2015 (UTC)
 * the "3 lines" are not the script itself - they load the real script from commons. the reason why 3 lines are required are that we need to load the JS script, and the CSS, and we need to define one windows (aka "global") JS variable. it really was 3 lines for a long time, but at some point i had to add a couple of lines to load a new dependency that the script in common acquired. as to the "1 line" - not sure. which page does it load? HTH - קיפודנחש (aka kipod) (talk) 01:58, 14 December 2015 (UTC)

Phone preview
Hi Kipod, please see Village pump (idea lab)/Archive 20, I'm wondering if something like that (not just the button but previewing each edit in mobile view) is easier to implement based on User:קיפודנחש/mobile-sidebarcopy.js. Thanks! - NQ (talk)  14:28, 20 June 2016 (UTC)

Hello.
I'm afraid there is a bug in User:קיפודנחש/watchlistScout.js. When I clicked "Mark All pages as visited", the orange banner came up linking every page I watched as unreviewed. Is there a way to fix this? Thanks. 1989 (talk) 05:40, 16 December 2016 (UTC)
 * thank you so much for the report.
 * i did not notice it myself, as i'm using a newer version of the "scout". the one i use, adds a 3rd "notification" start icon at the top, next to the bell and the tram front, to the left of the "Talk" link, containing the # of unread item on your watchlist. if you want to switch to it, add the following line to your common.js:
 * you might consider adding it to your global script page, which makes sense if you are active in more than one project.
 * apparently, mw software changed its behavior for the values returned by the api call to get the watchlist. i modified the script, and it should be fine now (shift-refresh if the bad behavior is still there). peace - קיפודנחש (aka kipod) (talk) 14:50, 16 December 2016 (UTC)
 * Thank you for fixing it. On your new version of "scout", are you aware that if you click on the star, the "notices" window pops up? 1989 (talk) 18:48, 16 December 2016 (UTC)
 * the window that pops up is basically your watchlist, but without any bells and whistles (i.e., none of the scripts and gadgets you use to prettify your watchlist takes effect). there's an ancient "todo" item to modernize the window that pops up, ideally showing only the unread items, but i haven't gotten to it, and maybe never will... peace - קיפודנחש (aka kipod) (talk) 20:06, 16 December 2016 (UTC)


 * I have certain edits hidden on my watchlist to not notify me of an edit by certain users (e.g. bots, own edits). Is there a way the original script can act the same way? 1989 (talk) 13:58, 23 December 2016 (UTC)

I am not sure, but it may be possible. I believe it's possible to read user preferences and find your watchlist preferences, and it may also be possible to get the list filtered. I guess i'll have to look at it. Peace - קיפודנחש (aka kipod) (talk) 21:39, 23 December 2016 (UTC)
 * - current version of script does take your preferences into account. please test and verify. thanks again for the feedback, and thanks in advance for testing. unfortunately, i am still stuck with the task of making the popup (displayed when clicking the star) sane.... peace - קיפודנחש (aka kipod) (talk) 21:28, 30 December 2016 (UTC)
 * Is there a way that you can make this work for your old script as well? I'm currently using that one. -- 1989 (talk) 10:13, 1 January 2017 (UTC)
 * ok, i did. unfortunately, i don't have anything in my wl, so i can't really test it... let me know how it works for you. peace - קיפודנחש (aka kipod) (talk) 17:40, 1 January 2017 (UTC)
 * finally i understood your comment ("are you aware that if you click on the star, the "notices" window pops up").
 * apparently something was changed with recent mediawiki version that affected the event-bubbling chain.
 * i think i fixed the problem. thanks again for the reports! - peace - קיפודנחש (aka kipod) (talk) 21:34, 2 January 2017 (UTC)


 * When I click on the notices icon (the bin image), the star changes to the notices icon, and when clicked on, the watchlist box doesn't show up except for the notices box. MCMLXXXIX  19:40, 13 February 2017 (UTC)
 * - i received quite a lot of feedback recently (on hewiki), and made several changes to the script (including one today...). it's possible that some intermediate versions wend wrong (of course, it is also possible that the current version is buggy....). please refresh ("full refresh" for most browsers this can be realized by clicking the refresh icon when Shift is pressed ), and see if the problems persist. if they do, i will appreciate another notification. thanks a lot for trying and testing my script - your feedback is appreciated. peace - קיפודנחש (aka kipod) (talk) 19:59, 13 February 2017 (UTC)
 * The problem is still there. MCMLXXXIX  20:03, 13 February 2017 (UTC)
 * just came here to report: sorry, i misread your previous notice. now i read it more carefully, and finally understood it, i was able to reproduce. will try to fix. peace - קיפודנחש (aka kipod) (talk) 20:27, 13 February 2017 (UTC)
 * i think it's fixed now. please retest. thanks again for the feedback and the testing... peace - קיפודנחש (aka kipod) (talk) 23:49, 13 February 2017 (UTC)


 * When I click on the star, it won't open at all. MCMLXXXIX  16:24, 14 February 2017 (UTC)
 * thanks. i guess is should not edit after certain hour... working now. (how i hate this ui stuff... the worst part is, it is so brittle, that the next time mediawiki will change the way these things look or behave, my junk is likely to break also). peace - קיפודנחש (aka kipod) (talk) 16:56, 14 February 2017 (UTC)
 * my previous fix broke the script for firefox (i had to resort to a "dirty trick", and later found out that FF does not allow it). i changed it now. the plus side is that i do not use any dirty tricks now, and, also produce valid HTML (i knowingly produced invalid html for a while, as a substitute for the "dirty trick", and the problem you found was the result...). the downside of the way it's done now, is the fact that i basically had to duplicate quite a lot of CSS used by the notification system (see T158345), which means that the next time the developers will make changes to the appearance of the notification badges, the "wathclist" badge will lag behind, until i realize it and update my replica. anywhoo, for now, as far as i know, it works with all browsers with no known bugs. peace - קיפודנחש (aka kipod) (talk) 20:38, 16 February 2017 (UTC)


 * Is there a way to disable or limit (confirm window) the rollback button on your newer watchlist script? -- 1989 16:17, 10 April 2017 (UTC)
 * i think it's doable. can you please elaborate (if and) why do you think this will be a good thing to do? peace - קיפודנחש (aka kipod) (talk) 17:57, 10 April 2017 (UTC)
 * It can be difficult sometimes to operate from a mobile device. 1989 17:59, 10 April 2017 (UTC)
 * i assume you mean "mobile device in desktop mode for users with rollbacker permission". i consider this setup aberrant, and i'm not sure if it's good idea to modify the whole gadget to accommodate this edge-case.
 * however, i believe you can get this behavior for yourself, by adding to your personal CSS file the following line:
 * peace - קיפודנחש (aka kipod) (talk) 18:16, 10 April 2017 (UTC)

Hi there. The update you performed for the watchlist badge, I cannot understand the language. Would there be a way to fix it? 1989 (talk) 21:45, 19 February 2021 (UTC)
 * my bad. forgot this was used outside of hewiki... i will add i18n support soon, and will make sure at least english is supported (and will add other languages if/when ppl will submit such). sorry about it. i hope you'll enjoy the new functinolity - IMO it's superior to the old one. peace - קיפודנחש (aka kipod) (talk) 21:53, 19 February 2021 (UTC)
 * ok, i18n done. please lemme know if you find any issues - functionality, grammar, spelling, leftover hebrew string, whatever. peace - קיפודנחש (aka kipod) (talk) 23:02, 19 February 2021 (UTC)

Please create documentation pages for your scripts
Hello, could you please create documentation pages for your scripts? That would be really helpful. They don't have to be long - they just need to state what the script is doing (it doesn't matter if that's already in a comment in the script or not or if you already described them on your userpage).

--Fixuture (talk) 19:11, 14 January 2017 (UTC)
 * I will try, but can't commit. These scripts were typically written and are maintained on hewiki, where most are also documented. I made some of them availabe here, where i thought users of enwiki might find a specific  one useful. Anyone who uses one of them and volunteers to document it, is welcome, and I'll try to find time to add some documentation myself. Peace. קיפודנחש (aka kipod) (talk) 22:19, 14 January 2017 (UTC)

CSS issues with chess diagrams
Hello. I noticed from old discussions that you may have some idea what's going on with the problem I asked about here (and received no answer in a month). Let me know if you have any suggestions for me -- I would love to see chess diagrams properly. Wareh (talk) 00:28, 19 March 2017 (UTC)
 * Many thanks for showing me how to fix my problem!! Wareh (talk) 12:52, 6 May 2017 (UTC)

MfD nomination of Module:Duration
Module:Duration, a page which you created or substantially contributed to (or which is in your userspace), has been nominated for deletion. Your opinions on the matter are welcome; you may participate in the discussion by adding your comments at Wikipedia:Miscellany for deletion/Module:Duration and please be sure to sign your comments with four tildes ( ~ ). You are free to edit the content of Module:Duration during the discussion but should not remove the miscellany for deletion template from the top of the page; such a removal will not end the deletion discussion. Thank you. Jc86035 (talk) Use &#123;&#123;re&#124;Jc86035&#125;&#125; to reply to me 11:45, 22 May 2017 (UTC)

User:קיפודנחש/apiRollback.js
Hi, the script User:קיפודנחש/apiRollback.js is not declaring it's dependency on the resource loader module mediawiki.util. This potentially creates incidental breakages of Javascript functionality of the users of this scripts. Can you please fix it ? —Th e DJ (talk • contribs) 09:24, 31 July 2017 (UTC)


 * Thanks, User:TheDJ. It's easy enough to do, but i wonder, is it even worth it? I don't use this thing, and the only reason to fix it will be, if someone else does. You think anyone uses it? I might just as well delete it, or put it into a comment for posterity or something. Again, this is easy enough - we all did this for many scripts recently, i just wonder if it makes sense to keep maintaining something which i doubt anyone uses. I guess i should try to figure it out... peace. קיפודנחש (aka kipod) (talk) 12:33, 31 July 2017 (UTC)
 * Well at least one person is including it: User:Winged_Blades_of_Godric/common.js (not sure about actual usage). If you don't want to maintain, or if you know a better alternative, I currently advice doing something like this or this. It's better than keeping old, possibly broken code around that is potentially included into the page loads of people who you don't even know are using the script. —Th e DJ (talk • contribs) 13:22, 31 July 2017 (UTC)
 * thanks. it may be useful, so for now i patched it. thank you so much for doing these maintenance tasks. peace - קיפודנחש (aka kipod) (talk) 19:26, 31 July 2017 (UTC)

Nomination for deletion of Template:Param wizard demo
Template:Param wizard demo has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Frietjes (talk) 14:09, 3 September 2017 (UTC)

I now maintain Module:Chart
Thanks for writing such an awesome module! I am now the maintainer of Module:Chart. Luis150902 ( talk  &#124;  contribs ) 12:11, 29 March 2018 (UTC)

Upcoming changes to wikitext parsing
Hello,

There will be some changes to the way wikitext is parsed during the next few weeks. It will affect all namespaces. You can see a list of pages that may display incorrectly at Special:LintErrors. Since most of the easy problems have already been solved at the English Wikipedia, I am specifically contacting tech-savvy editors such as yourself with this one-time message, in the hope that you will be able to investigate the remaining high-priority pages during the next month.

There are approximately 10,000 articles (and many more non-article pages) with high-priority errors. The most important ones are the articles with misnested tags and table problems. Some of these involve templates, such as infoboxes, or the way the template is used in the article. In some cases, the "error" is a minor, unimportant difference in the visual appearance. In other cases, the results are undesirable. You can see a before-and-after comparison of any article by adding ?action=parsermigration-edit to the end of a link, like this: https://en.wikipedia.org/wiki/Arthur_Foss?action=parsermigration-edit (which shows a difference in how infobox ship is parsed).

If you are interested in helping with this project, please see Linter. There are also some basic instructions (and links to even more information) at https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-April/001836.html You can also leave a note at WT:Linter if you have questions.

Thank you for all the good things you do for the English Wikipedia. Whatamidoing (WMF) (talk) 21:18, 19 April 2018 (UTC)

Nomination for merging of Module:IPAddress
Module:IPAddress has been nominated for merging with Module:IP. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 20:49, 19 June 2018 (UTC)

Modify template
Hello קיפודנחש,

Would you please modify Template:Infobox event to be able to contain the information from the official police report from the Shooting of McGlockton? We have waited 13 days from my discussion on the talk page. The time is now to modify the template.

Thank you, --Wyn.junior (talk) 20:35, 31 August 2018 (UTC)
 * sorry, i am not familiar with the template, its purpose, and its usage. i do not understand what are you asking exactly, and, unfortunately, i do not have the time right now to educate myself. קיפודנחש (aka kipod) (talk) 21:16, 31 August 2018 (UTC)


 * You are listed as one of the Template editors on Special:UserList page. This is one of the most common templates on Wikipedia. I am asking you to modify this template so the template is conducive with police reports. I have waited over two weeks and no one has objected to these changes. Please modify the template to say: Please modify the template to contain these --Wyn.junior (talk) 19:19, 1 September 2018 (UTC)


 * Law enforcement agency
 * Report number
 * Report Date:
 * Primary Information
 * Occurrence From:
 * Occurrence To:
 * Source Of Call:
 * Business Area Name:
 * Reporting LEO:
 * Response Information
 * Modus Operandi
 * Description
 * Weaponry
 * Weapon Type
 * Caliber
 * Addresses
 * Offenses
 * Offense Type
 * Offense
 * UCR Class
 * Subjects
 * Relationship
 * Name
 * Subjects - Continued
 * Relationship
 * Name
 * Redaction Date:
 * Total Number of Redactions:
 * i don't think i'll do that. קיפודנחש (aka kipod) (talk) 19:25, 1 September 2018 (UTC)
 * You are a template editor. I do not have privilegs to do so. Please modify the template.--Wyn.junior (talk) 19:51, 1 September 2018 (UTC)
 * sorry to be blunt, but it seems you do not understand how wikipedia works. i do not work for you, and you can't make demands that i do something i have no interest in, because someone, at some point, granted me some permissions. please stop. קיפודנחש (aka kipod) (talk) 19:58, 1 September 2018 (UTC)

Module:Chart
Hi, I used your code for this module on the Macedonian Wikipedia in this article Near-Earth object, and it seems that it doesn't split in the proper coloring on the pie chart for the percentage given. Some of the colors are missing! Can you please see if this is a issue with incompatibility, or we miss on our Wikipedia some other module or template. Thank you!

Инокентиј (talk) 09:01, 13 September 2018 (UTC)
 * i assume you are talking about this chart:

i do not see anything wrong there. of course, the black sliver (Atiras/Apohele) practically disappear, but you should expect that: 1t's 18 out of 18532, i.e., less than 1/1000, so if the circumference is less than 1000 pixels, the black slice would be less than 1 pixels, i.e., not really visible. can you please elaborate - what do you expect to see vs. what do you actually see? peace - קיפודנחש (aka kipod) (talk) 15:55, 13 September 2018 (UTC) Yes that's the one but on the Macedonian it is different I will post the link to the article: mk:Близуземски астероиди As you will see it shows different pie chart with the same data and only 3 colors

Инокентиј (talk) 19:09, 13 September 2018 (UTC)
 * sorry, it's been a while (maybe 5 years?) and i forgot: you need to add to mk:Mediawiki:Common.css the "transborder" definition:  you can actually test it: use browser console (F12 on most windows browsers), and type   - this should show the right chart. if this works, go on and add this to the common.css (or ask some sysop to do that). i'll see if i can add it to the module documentation. peace - קיפודנחש (aka kipod) (talk) 19:56, 13 September 2018 (UTC)

Thank you for the help, cheers !

Инокентиј (talk) 01:04, 14 September 2018 (UTC)

September 2018
Your recent editing history shows that you are currently engaged in an edit war. To resolve the content dispute, please do not revert or change the edits of others when you are reverted. Instead of reverting, please use the talk page to work toward making a version that represents consensus among editors. The best practice at this stage is to discuss, not edit-war. See BRD for how this is done. If discussions reach an impasse, you can then post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection.

Being involved in an edit war can result in your being blocked from editing&mdash;especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring&mdash;even if you don't violate the three-revert rule&mdash;should your behavior indicate that you intend to continue reverting repeatedly. DocFergus (talk) 16:58, 24 September 2018 (UTC)
 * this is not how i see it. i added a date to Kansas City standard. my edit contained a typo. this was rolled back by User:Wtshymanski with summary "excess detail and sp error anyway". i fixed the typo, and explained in the summary why this is _not_ "excess detail". my edit was rolled back by you, with the summary "Unsourced. And date in incorrect format." the first claim is pure BS. as i explained in the summary, the list of participants is "unsourced" just the same: both pieces of information appear in reference #4, which is linked between the two. the "incorrect format." claim is also pure BS: see Manual_of_Style/Dates_and_numbers (quote):


 * day–day: 5–7 January 1979; January 5–7, 1979;  elections were held March 5–8


 * the reason i added this in the first place was, i read the article (i have some interest in the subject), and was trying to figure out _when_ this "Kansas City symposium" actually happened, and there was no clue there. i went to the source, cited in the article, found the date, and as a courtesy to the next reader who might wonder "when", added it to the article. i do not know what tickled you, but your rollback was complete BS, and i'd appreciate it if you put the date (or rather dates) back in the article, in any form you find pleasing. peace - קיפודנחש (aka kipod) (talk) 17:31, 24 September 2018 (UTC)


 * Well, I found a reference quite easily and added the correct dates back (you had got them wrong - that's why references are important) supported by that cite.


 * You are not entitled to put any unsourced material anywhere in Wikipedia no matter how correct you believe it to be without a supporting reference. Please review WP:V and WP:RS. And per WP:BRD, you are certainly not permitted to simply revert your edit once it has been challenged without obtaining a consensus first (unlikely to be obtained without a reference). DocFergus (talk) 17:36, 24 September 2018 (UTC)
 * you were correct about me making an error citing the dates (7-8 rather than 8-9). however, this is _not_ unsourced: the source is referenced not 3 lines from my edit (the BYTE's report about the symposium, which also contains the list of participants) this is why i insist this is not "unsourced". when there are several claims in the same 10-lines section, all sourced from the same source, we do not usually put [1] [1] [1] [1] next to each claim - it helps nobody, and just looks silly. as to "repeating" - since each of the rollbacks summary contained additional reason (typo/date format), and since each time i fixed the issue when reinstating, i think it's not "edit war". again, thanks for catching my off-by-one error (BTW: i would probably have made the same error even if i did re-refered the referenced in the next sentence). peace - קיפודנחש (aka kipod) (talk) 17:58, 24 September 2018 (UTC)
 * Unfortunately, each claim requires a supporting reference for verifiability. If a reference is not specifically added for a claim as you did not do, you cannot expect everyone else to check out every other reference in the article on the off chance it is covered there. The ability to add a name to a reference and repeat it, as you did for the Byte magazine, is the mechanism where a single source can be used to support multiple claims.


 * I happen to know that there are a (very) few others who agree with you over the degree of in-line referencing, but ultimately, every claim must be verifiable and that can only be achieved by following it with a supporting in-line reference. One of the requirements for an article to achieve 'good article' status is that every claim is thoroughly referenced.


 * By the way: good work on sourcing the list of attendees. DocFergus (talk) 11:45, 25 September 2018 (UTC)

editToken
Hello קיפודנחש,

Your script User:קיפודנחש/pageCollector.js is no longer functional because it attempts to get an  from. The script should instead get a. s were removed from  on October 3, 2019 at Phabricator during this edit as they were redundant to  s. –  Brandon XLF  (talk) 00:06, 25 November 2019 (UTC)

Thx. fixed it. Peace - קיפודנחש (aka kipod) (talk) 00:25, 25 November 2019 (UTC)

interested in monotype casters and casting character ?
I had a message of you some time ago about Monotype... What is your interest in this subject? How can I help you?

greetings J.T.W.A.Cornelisse (talk) 11:30, 26 November 2019 (UTC)

Pgn viewer extension
Hi kipod, hope you've been well. I haven't stopped thinking about getting a pgn viewer up and running on the wiki, and given the pushback I've been working on converting your javascript code into a mediawiki extension. I've started an info page at mw:Extension:ChessBrowser and you can see the code at the github repo though I've requested a Gerrit project. Essentially it does what the templates at heWiki do: if an editor adds the  tag it places the PGN source inside and it loads your javascript only if the page needs it. This is all done server side, so it relieves the concern about running unnecessary javascript on every page load.But besides the good news on getting the extension running, I was hoping we could discuss how to move some of the features of the javascript into the PHP. Reading through the code, there seem to be some places that would probably perform better if they were done server rather than client side, especially board building, PGN processing, and internationalization. The JS would need to be modified to use the board in the HTML output, and the extension can pass data and config variables to the javascript after the PHP does the hard work. Essentially, the javascript could focus on the UI and moving the pieces. What are your thoughts and would you be willing to help with the javascript changes? Wug·a·po·des​ 02:29, 27 November 2019 (UTC)
 * Also, I noticed that the javascript uses jquery.ui, and it's been deprecated in favor of OOUI. I got errors on my test wiki while trying to run it because of that, so I needed to change mw.loader.using('jquery.ui').done(doIt); to mw.loader.using('jquery.ui.tabs').done(doIt); which still works at the moment. Wug·a·po·des​ 02:37, 27 November 2019 (UTC)


 * super. i'm really excited about this becoming more widely available, thanks to your "what makes sense" attitude. thank you so much for that!
 * one small suggestion: add a single data attribute, named "config", i think i can dig some "documentation" of sorts to the config data structure, if you are interested. once you move more and more functionality to the php side, you can still use the same "config" variable to pass parameters to the php code.
 * as to rewriting it along the lines you describe: very sensible.
 * so first thing, i think you want to try and connect with User:Fred Gandt, who built a script exactly along the lines of your design, several years ago. we did not agree on the correct approach, but as far as i remember, his thinking was very close or identical to what you describe. for lack of backend support, his script never matured. i actually learned from how to use css for drawing and animation - in my original version, it was all done by calling jquery "animate" or ".css". so my script is better now, and also closer, i think, to his.
 * so you are more than welcome to scavenge from my script anything that makes sense. my first rough thoughts are something along the lines:
 * find a sensible representation to the data that "analyzepgn" generates, or use it as is
 * the script gets several things, like "board" array, representing the specific states, like "board after move 29". the "board" itself is super-simple - just a sparse array, where the index represents a square, and it contents, if there is one, is one of the "pieces". basically sane data structure, that will enable one simple function to move the pieces (css animated) to any given position. piece of cake. at the heart of it is something like so:


 * for sure i botched the syntax, it's just illustration of how minimal is the code. no matter where you are and no matter where you go, it works. so not much from my script. you design the ui using modern


 * then you want to build, or rebuild, the interface, but in a modern way, so i do not have much to contribute
 * i think you want to look at the "config" parameter that evolved. it's a single json string passed to the script, which reads it, and if it's legal, uses its value as "parameters" to the script. i think it's a good way to allow flexibility and adding new features without actually touching "the api".
 * for now, though, it's sweet that you wrapped the existing script by an extension. i have no idea what is the "approval" process. FWIW, this feature is available now, using the "gadget" way, on hewiki, ruwiki, ukwiki (available, but used on single article), and just installed on Basque (eu) wikipedia.
 * looking forward to see what you do. going now to read the sources you linked to...
 * peace - קיפודנחש (aka kipod) (talk) 07:20, 27 November 2019 (UTC)
 * User:Wugapodes: so i did invest significant chunk of time in creating the "chessbrowser prototype" on . this was done basically as a response to your prod here. the prototype basically uses lua to do what the php code is supposed to do, or some estimation of it.
 * it still misses stuff: e.g., no handling of comments, and no multiple games in one browser. i also strolled around the open source well, and it seems it should not be hard to find a ready-made php pgn parser, e.g..
 * the javascript thingy is pretty much done . it weighs about 200 lines. the css is also ready . basically, a variation over the stand-alone css.
 * i hate to sound whiny, but i am: you asked me for help, i did significantly more than i initially intended to do (not your fault), but i _do_ expect some feedback - after all, you did request this. i will really appreciate some clarity WRT your intentions for this project: are you going to take it forward? pass it to someone else who will? leave it as is?
 * peace - קיפודנחש (aka kipod) (talk) 20:44, 1 January 2020 (UTC)
 * Hi kipod, sorry for not communicating better. I had read your previous post and have been working on the PHP so that it can give the javascript the data it needs. I hadn't actually seen the parser you linked to, but going through the code it looks like it will make my job a lot easier. I am definitely going to continue with it because I firmly believe this is something all Wikipedias can benefit from. For what it's worth, a lot of the work and discussion has been occuring on the phabricator project and gerrit repository rather than wikipedia or mediawiki, so it's easier to stay in the loop if you check in on those pages every so often. — Wug·a·po·des​ 22:30, 1 January 2020 (UTC)
 * thank you so much for all the work you guys are doing, and for the update.
 * i roamed around the sources, and it seems the "minimalistic" extension, based on the modified (or "linted"?) current js viewer, is practically ready for the next stage (alfa? beta? security audit?). this is great.
 * as to "real deal", based on your idea listed above, i think i can see what you are doing, and as far as i understand, it will be based on some existing "3rd party" open-source pgn parser. this 3rd party parser is not (or not yet) committed to the repo, which makes sense (i am not familiar with mw standard for "vendoring"), but assuming you already zeroed in on a specific library, can you please specify which, and link to it, e.g., the readme? there is a commit message mention of "DHTMLchess", but it's a bit hidden in the history, and not really clear which project it is. again, thank you so much for the effort.
 * PS: i looked at the data passed by current code, and i am not sure it does en-passant, promotion and castling the same way my lua prototype does, and the current front-end script expect. if you think a different contract should be used, it can help if you document it, so i can modify the lua and JS to adhere to this contract. if you like the current contract, please let me know. peace - קיפודנחש (aka kipod) (talk) 20:42, 5 January 2020 (UTC)
 * The extension is a minimal working example (MWE), yes, but there's still a lot of work that's needed. The next step would be a security review, but right now isn't a great time. Our main security vulnerability is between the PHP and javascript (WP:BEANS) which we're still working on and the code is not stable. Reviewing the MWE isn't a great use of time since both the PHP and javascript are going to change radically in the next few weeks. Once we've resolved T239438, things should stabilize and it would be a good idea to ask for security review. After that we still have a lot to do before submitting to the deployment review queue—documentation, localization, logging, automated testing, etc. We've made a lot of progress and I'm excited, but there's still a good amount of work to do.
 * The external library is the one you linked to, but modified and hosted on my github; I'm not sure the best way to handle dependencies like this either, but I doubt any changes would be too hard if needed.
 * The contract is the same. The DHTML chessParser doesn't output the exact JSON structure our JS wants, but the extension PHP manipulates the standard chessParser output so that the javascript gets passed the input it expects. The current contract should work fine as it is. — Wug·a·po·des​ 01:37, 6 January 2020 (UTC)
 * thank you so much, both for your work on this extension, and for the update(s). as to the contract: just wanted to mention that we might want to extens it in the future, for either one or both of the following: (1) show multiple games in one browser, and (2) to support game variations in comments.
 * (there's no need to do anything for comments themselves - the front-end does not populate the "notations"). variations seems like low-hanging fruit, since the parser already supports them (it supports multiple games too, but this is somewhat less "low hanging" - supporting this will require much more thought, and a little more code).


 * while we are at it: once you have your tag/extension up and running, there is another way to derive some wiki-value out of it, unrelated to the "browser", and requires no JS: some time ago, after i queried the chess-person on hewiki, and after i was told it's actually a good idea, i created a lua module that accepts pgn, and squirts out Chess diagrams. basically, the syntax is approximately like so:




 * IOW, the extension can be taught, relatively easily, to produce either the "browser", a series of diagrams, or both. see demo page at he:User:קיפודנחש/ארגח 3, which uses this module to show in details one of Judit Polgár games (as a side: this module was the basis for my "prototype" on mw).
 * not for immediate action, just food for thought for extra value your extension can provide cheaply - by the time it's done, it will have all the moving parts. peace - קיפודנחש (aka kipod) (talk) 23:29, 6 January 2020 (UTC)
 * Those would all be wonderful improvements. I've tried to write the PHP in a way that it can be extended by keeping the game parsing and wiki output relatively separate so that someone someday could add shogi or go capability. Your lua code for making a chess diagram is great. I could see it as a way of addressing T239446 or as its own hook, like . — Wug·a·po·des​ 23:57, 6 January 2020 (UTC)
 * hmmm.... regarding "no JS" and "mobile" (this is the essence of the phab story, no?), i think my prototype pretty much address both: if you disable JS, the board is still displayed, either at the end position or whatever the "display=" parameter specifies, and the correct notation is marked (one thing it does not do is scroll the correct notation into view - not sure if it's even possible w/o JS, and if it is, i don't know how). the buttons disappear, and the reader sees an ugly red message advising her to enable JS if she wants to see it interactively.
 * as to mobile - everything still works, no? admittedly, on my phone, mw:User:קיפודנחש/huge test is very jumpy, but it's a ridiculous page, showing some 170 games. mw:User:קיפודנחש/mote test (fingercheck - i meant to write "more"...) seems to be working flawlessly. what am i missing?
 * BTW: i practically forgot, but my lua code and template exists on enwiki too. i offered it to the chess community, but i didn't see many takers... see Template:Chess from pgn. i sent you to hewiki b/c there, it's actually used: i copied the demo page from the Judit Polgar article on hewiki. TBH, i practically forgot i even copied it here... peace - קיפודנחש (aka kipod) (talk) 00:34, 7 January 2020 (UTC)

It's not that these aren't addressed, but being more deliberate in how. I'm not an expert in mobile interfaces or accessibility (or any of this really) so the phabricator task is mostly to consider what the best ways to address these use cases may be. Mobile phones have data restrictions and smaller interfaces which provide design challenges; users without javascript may actually be using screen readers so how the content will be presented out loud needs to be considered. These may be simple fixes, but it's useful to think about. — Wug·a·po·des​ 01:08, 7 January 2020 (UTC)
 * - i looked at the linter croaks and tried to understand and address them. one of them seems to me just incorrect ("'advance' was used before it was defined"), some were really good catches (like using global selectors - i just forgot to pass "div" to the $(selector) call), and some i think are silly and petty (like, asserting vars must be at top of function scope, or not allowing ~, which is perfect JS operator "bitwise not" - ), but if linter wants to be an a-hole about it, i can accommodate it - at least in this case (i wouldn't like it if JS was really castrated by total bitwise-sectomy, however, in this case the use of   can be considered "too cute", so i can live without it). cursory test shows that after my changes animation still works. give it a peek, and see if it helps to appease the capricious eslint. peace - קיפודנחש (aka kipod) (talk) 06:16, 12 January 2020 (UTC)
 * Thanks for working on that! and I have managed to work out most of the remaining lint errors at 563326. I realized that I actually did slightly change the output contract, hopefully in a way that makes things easier to handle. An example of the output json can be seen (for now, I messed up some naming stuff) at mw:User:Wugapodes/Test.json. You'll notice that the 'ply' array is uniformly 3 items; I've tried to standardize it so that it follows the scheme [ "source", "destination", ["action type", "action"]]. So for a typical move, it's the source and destination, "action type" says it's a move and there's a null action. For castling, the action type is "castle" and the action is an array of the rook source and destination (in that order).  The specifics can be seen in the checkSpecialMove function of ChessParser.php, though I will be documenting this all soon. There's also a strange problem of almost all the pieces being drawn in the upper left square...I'm trying to track down why that is. — Wug·a·po·des​ 03:02, 14 January 2020 (UTC)
 * Are you okay with me fixing the lint errors for you? I probably should have asked first... DannyS712 (talk) 03:51, 14 January 2020 (UTC)
 * I always appreciate help! — Wug·a·po·des​ 04:53, 14 January 2020 (UTC)
 * (User:DannyS712: FYI. my interaction was mainly with Wug, so i'm addressing this to them). hi. not sure where we stand. if your new responsibility as admin takes all your wiki-time, and the extension is put on the ice, i'd appreciate if you let me know, and maybe also alert me when it's taken off the ice. otherwise, please read the remainder of this message.
 * i'm listing here the status as i understand it, mainly WRT the stuff i did:
 * i created a scribuntu prototype - this is meant to be a "throwaway" piece, for 2 purposes: show the way for the "real" back-end, and facilitate testing and verification for the "front-end"
 * i created a "front-end". this is not a throwaway: IMO, the only thing the front end is missing, is handling variations (not essential - the JS-only viewer, installed on ~4 wikis and actively used by at least 2 of them does not handle them either, and i never heard a request to add this functionality). it's not hard to add, and it will not be an ugly hump on top of beautiful code - it will be completely seamlessly integrated (i can outline what/how, but i don't think it's necessary).
 * doing these 2 pieces, included defining the "contract" (again, supporting variation will require expanding the contract a bit)
 * you suggested a more elaborated contract between the back-end and front-end. i think the structure you defined passes some redundant and unnecessary stuff, which is not useful for the front-end, but is not necessarily harmful. it _will_ have some adverse effect on the size of the attribute, hence the size of the page, but i don't think it's a big deal.
 * that said, i don't want to implement the required changes to adjust to the proposed structure in the front-end myself. i understand you are pretty handy with JS, and it makes more sense for you to work both ends of the new "contract" (i'm also taking an open-ended wiki-vacation, not sure until when - this ping is mainly meant to avoid the sense of "a ball in the air" when i'm off the sauce).
 * bottom line: i will create a talkpage for the front-end code on mediawiki (as one of the last things i do b4 getting off the sauce compltetely), outlining the its basic design. you can then take it, and do anything you want with it. i will try to document specifically the code that parse the "contract", or, more precisely, the data structures this code generates. you can then write similar code to parse the contract as you like it to be - as long as the generated data structures are built correctly, the front-end will work - it does not retain any memory of the "contract" once those structures are constructed.
 * peace - קיפודנחש (aka kipod) (talk) 00:40, 31 January 2020 (UTC)
 * Thanks for the ping! The echo extension seems to have been acting up lately (I only just got a ping about an RfD after it had closed, and there have been problems at WP:DYK recently too). It may be that the mention was on a different line than the signature, but it seemed to work before so I'm not sure that's the answer. Anyway, I'm here now! Thanks for letting me know about all of this and hope your Wikibreak goes (went?) well. I'm not as handy with JavaScript as you, of course, but I'm close to finishing the integration of the front and back end. In the process, I've realized that some of what has been passed is redundant, but we can trim the code later once everything is working. I plan to upload my changes later this evening, and they'll be at 567699 which for now just has the code I copied from MediaWiki. One very helpful thing before you take your wikibreak: if you're open to it, having your javascript licensed under the GNU GPL version 3 would simplify some of the licensing. Because MediaWiki is licensed under creative commons, the license compatibility is fragile. If you could add a comment to the code licensing it under the GPL we could bypass some weird legal hurdles. But I think the extension is close to a testing phase! — Wug·a·po·des​ 00:56, 31 January 2020 (UTC)
 * (hope the ping works...) thanks. no need for either cc-by-sa or gpl(1|2|3|4). i placed it strictly in the public domain - can't imagine this will have any adverse effect on the licensing of the rest. i'm in the middle of "documenting" the front end, and then, presumably, i'm off to a sunnier beaches. peace - קיפודנחש (aka kipod) (talk) 01:17, 31 January 2020 (UTC)
 * finished writing the "documentation" it's more a conceptual description of the code, but since the whole thing is only slightly above 200 lines, and the variable and functions are reasonably named, i think this should suffice. unfortunately, this seems to be using the "flow" thingy, which may not be so great for documentation (maybe it's my punishment for appropriating the talk page this way, but i find it convenient to have these two conjugated). peace - קיפודנחש (aka kipod) (talk) 02:04, 31 January 2020 (UTC)
 * - had another thought, regarding how your extension should treat comments: how about doing it outside of the "game display front end"? one way i thought of goes something like so: each "real" annotation which is followed by a comment, is "marked" as such using classes and attributes, and you use an OOUI component/widget, to show the comment as a popup. this can be done almost entirely outside the animation piece (can share .js file, but the actual code is independent of the "game play" logic). you can even call it from the "attachTemplate" function with sets all the event handlers to the various controls. i think this is a good solution. if you'll want later to make annotations inside comments (aka "variations") playable, i think it can be achieved w/o too much pain. as to the required changes to adjust to a different contract: i'm sure you figured it out already, but i'll say it anyway: when writing the small "documentation", i took a refresher on the front end, and i thing the only function you have to touch is "precossPly". just figure out what it does exactly. pretty simple, really: it does not touch in any way its "input" board, and returns a freshly minted output "board" object (an array, really), representing the new state after the ply). it can have one side-effect - for promotion, it calls the pieces constructor, which is normally called by the initial "processFen". so once you create your own "precossPly", i think the front-end should work with any contract you choose, with no other changes.
 * so build the HTML any way you choose - for the lua model, i "cheated" and basically hard-coded a template, filling in the game-specific details in code - including the "pieces" of the initial board. build the annotations with the appropriate attributes so they can be attached to the correct ply, and for the OOUI display of comments, (maybe use OOUI for the "metadata" too) and you'll have an awesome extension.
 * one possible enhancement to the front-end would be arrows. i saw in on some chess sites, e.g. here. basically, an arrow from "source" to "destination" of the ply resulting in this board. this can be relatively easily done with canvas. i do not know if this is really something you want, but apart from "variations" which i mentioned too many times already, and are easy to add seamlessly, "arrows" are the only enhancement i could think of. if, at any time, you'd like to do it, let me know. should not be that hard. otherwise, i think my part is done. peace - קיפודנחש (aka kipod) (talk) 19:14, 1 February 2020 (UTC)

I was thinking, rather than a pop-up, have it included inline with the rest of the notations. Similar to how Lichess handles comments and variations (example). I think popups would clash with a lot of the existing mediawiki ui for readers, and the comment could be seen in context of the moves around it; plus it would make handling recursive comments and variations somewhat easier to handle. I've mostly managed to get the front end-working; just a few bugs left to work out. As for arrows, I think that's a great idea! It would require some planning, but I've found arrows useful in game analyses before and I think it would be a good feature for an encyclopedia to have. — Wug·a·po·des​ 22:58, 1 February 2020 (UTC)
 * regarding comments: this is entirely in the back-end realm. fwiw, the JS-only pgn viewer does exactly that (embed comments in notations) - you can see in some of the demo pages on hewiki for the viewer. like everything else, the appearance is controlled by CSS. the front-end has one more button - hide/show comments, which basically adds to the top container a class that tells the comments to hide.


 * as to arrows: actually, i don't think arrows will require as much planning as you imply - see the outline below.
 * however, after you pointed me to "Lichess" site, i learned a simpler way to indicate "source" and "destination" - basically, mark the empty "source" square, and the most-recently-moved piece. so i implemented this on the mediawiki prototype. please try it out. the only change for the back-end is the addition of "source" empty chess piece - basically a div appended to the "board image" div. i am sure this can be visually improved by playing with the actual attributes of the source and dest classes.


 * i can outline drawing the arrow: basically, you keep one hard-coded "path" which is the arrow (, horizontal, with its tip at the origin. changing exactly 2 coordinates will make it any length (basically, the 2 X coordinates of the 2 corners of the "tail" of the arrow).

so, given "source" and "dest", you calculate the length of the arrow, and extend it to the correct length. you calculate the angle of the arrow, and rotate (tip still at origin). now translate such that the tip is at destination, and if you do all the calculations correctly, the tail will be automagically at the source.
 * so basically one coords manipulation to stretch the arrow, 3 or 4 canvas commands to draw it (begin/end path, fill, stroke), and 2 canvas commands to place it correctly. easy peasy.
 * so the front end will eventually try to do both - if it finds a canvas it will draw the arrow, if a "source" square exists, it will move it around according to the ply, and will always set the class "pgn-ply-destination" to the last moving piece. peace - קיפודנחש (aka kipod) (talk) 10:53, 2 February 2020 (UTC)
 * so i had a little deficiency, where i forgot to take the "flip" state into account when drawing the arrow, but it's all better now, and arrows show correctly both straight and flipped.
 * again, the demo shows both "source/dest marking" _and_ an arrow - this is done to demonstrate both. in "real life" you'll prolly want just one of the two, or none - i'm not sure both together make sense.
 * i also tweaked the appearance a bit to show the board itself a tad larger. so i think i did there anything i can think of (again, modulo comments/variations: there's very little for front end to do for pure comments - at most one button to show/hide them. variations may by fun to add, but the contract and the annotations mapping to var#/ply# pair needs to be defined first). note that the current logic for "arrow" and source/dest marking, is exploiting the  "input" array. if you change the contract, you might need to to modify the way to "source" and "dest" are determined for each ply. this happens in one place - , which became one more place that need to be changed if you change the "contract". if the contract is a bit complex to extract source/dest easily, just build a list of "source/dest" pairs as by-product of   (which you have to modify anyway), and use this list for showPly, instead of sucking it directly from the input. peace - קיפודנחש (aka kipod) (talk) 17:47, 3 February 2020 (UTC)
 * - i think i forgot to "publish" one or two previous posts (where i pinged you). apologies if this ping is spammy. reading my talkpage i can't find what i thought i published earlier, so a repeat in a nutshell.
 * bottom line: both "arrow" and "source/dest marking" work now. some more details above. one thing i intended can't be done: i thought the back-end can create a "canvas" element as an indication to the front-end that it should dran arrows. unfortunately, it seems that "canvas" is one of those verboten tags which mw parser does not allow (creating from back-end cause the to go through "html-ism", replacing the brackets with &lt/&gt pairs. this limitation is for templates/modules - i suspect an extension _can_ create a "canvas" element, so we may eventually revert to my original idea), so the front-end needs to create the canvas. this probably means that we (finally) really need the "config" structure we begun discussing long ago, so the back-end can tell the front-end whether or not to draw the arrow (again, if an extension is capable of creating "canvas" element, this may not be needed). in current code front-end draws the arrows unconditionally. i don't know about canvas-less browsers - i don't think any of the "supported" browsers falls in that camp, maybe we should be a bit more careful when calling . peace - קיפודנחש (aka kipod) (talk) 18:08, 3 February 2020 (UTC)
 * That solution looks like it will work. I'm planning to hold of on implementing arrows and comments for a bit though. I think it's important to get a 1.0 release of a minimal viable product so that the core PGN parsing and board interface work well, and then start adding "quality of life" improvements like comments, variations, and arrows. It's important that we have working examples and ideas of how to implement them already though!
 * As an update, you maybe saw the phab task I added you on. The Community tech team has agreed to sponsor this as a "10% project" and will be helping to get it through the security and quality reviews required by the WMF for deployment on Wikipedia. It's not on the top of anyone's priority list, so the process will probably be a slow one, but it's a great development and makes it very likely this will be deployed on Wikipedia eventually! Thanks for all your help so far, and I'm looking forward to seeing this through to completion! — Wug·a·po·des​ 01:09, 8 February 2020 (UTC)
 * Thank you so much for the update. From your response it seems like you haven't looked at the demo page recently. It now sports both arrows and source/dest square marking (actual "mark" is css class). The arrow is not configurable ATM, but it will be trivial task to make it so, including an "off" switch.
 * So, i guess that from now on, i will try to assist if asked, but probably not much otherwise.
 * The 2 things i think worth adding to the front-end are, First some configurability . Second thing is supporting variations in comments. Comments are "supported" already: since the back-end does the rendering, it can put them anywhere and style them anyway it wants. Variations are a tiny bit more tricky, but not by much: small change to the contract, small change to front-end, and i'm pretty sure small change to back-end.
 * However, as you say, right now the Minimum viable product is the goal. i went on and on about the other stuff, because it's the only things i could think of for the front-end which are not done yet, and once a new contract is agreed, front-end change should be trivial - I don't have to make it myself, but I'll be happy to, whenever.
 * I really appreciate your updates here. TBH, I do not follow the development: I'm probably "watching" several dozen phabricator stories, and i'm pretty much ignoring those updates almost entirely. So keep me posted, and don't hesitate to ask if you think of something I can help with.
 * Peace - קיפודנחש (aka kipod) (talk) 06:51, 8 February 2020 (UTC)

)
 * i peeked at your personal script page, and it seems you load many scripts. possibly there is some collision.
 * peace. קיפודנחש (aka kipod) (talk) 19:10, 21 August 2022 (UTC)
 * It Seems that the script does work, but my left navbar appears above the main page (due to open screen width). This seems to cause the watchlist popup to float down to the main page, put of sight. (The OOUI popup also behaves strangely flickering etc.) —  Qwerfjkl talk  20:40, 21 August 2022 (UTC)
 * yes. showing it inside "content" is a compromise which allows it to appear on some special pages and such, and has the side benefit of enabling "page preview" from the form (unfortunately, not navpop).
 * it allows you jump straight to history and diff, mark as "viewed", and remove from watchlist. it also supports different filtering (show/hide bots and such). i think it's greatly superior to the old "scout".
 * peace. קיפודנחש (aka kipod) (talk) 21:39, 21 August 2022 (UTC)
 * however, after your Q i revisited, and now it opens under the marker.
 * peace. קיפודנחש (aka kipod) (talk) 21:54, 21 August 2022 (UTC)

קיפודנחש זה לא נכון
אני לא טרול. ביקשתי שיראו את הפרטים לצוות אחר שיבדוק ולא הסכימו. זה לא הוגן שאין מערכת. IIml (talk) 11:28, 12 July 2023 (UTC)

Help on Module:Chart, text being chopped off
Something somewhere on wikipedia has changed and now charts are displaying incorrectly. As you can even see on the help page for the charts at Module:Chart, the top label of the chart has half the text chopped in half. I can't track down why this would have happened. Do you know where this could come from? It didn't use to do this and nothing has changed on the page itself so it must be inherited from elsewhere on wikipedia. Ergzay (talk) 06:31, 3 June 2024 (UTC)


 * Apologies for the late reply.
 * Will try to look at it when I'll get to a desktop, hopefully sometime next week.
 * Peace קיפודנחש (aka kipod) (talk) 13:12, 9 June 2024 (UTC)