Talk:WYSIFTW

Name
Can you tell me what "WYSIFTW" or "WYSIWTF" stands for? Thanks. Kenrick95 14:54, 7 January 2011 (UTC)
 * The original acronym is WYSIWYG - "What You See Is What You Get", meaning the document you edit on screen looks exactly like the result you print or publish. I replaced the last three letters with WTF, to indicate that the page will look more, but not quite like the normal wiki page. It was then suggested to use FTW instead. --Magnus Manske 16:41, 7 January 2011 (UTC)
 * Do you mean WTF = "what the f***" and FTW = "for the win" ? Kenrick95 15:09, 23 January 2011 (UTC)
 * Exactly. --Magnus Manske 13:07, 24 January 2011 (UTC)

Bugs
Unfortunately, couldn't insert any text. I could delete it, and backspace it, but not insert anything. Opera 10.63 under Win7, if it's any help. Can it interefere with other gadgets? Maybe I should switch sth off? It looks too good to give up on it :D It seems also to be rather CPU consuming, am I right? (large page loaded looong)--Felis domestica 21:01, 7 January 2011 (UTC)


 * Yeah, i can confirm. Latest revision in toolserver (link) has some speed issues with Arora (Webkit based browser) but it seemed to work. With Opera 11.00 and Firefox 3.6.13 there is error "elm.children is not function in line 240" of wysiwtf.js. More specific error is in "postProcessBoldItalics : function ( elm )". With Google Chrome editor worked fine. For general usage i think that user experience would work better if templates, refs would expand as whole when one clicks them. Now user needs to click first ref open, then template open... eg.
 * After bug reporting i have to say that your editor is great! Thanks :) --Zache 08:32, 9 January 2011 (UTC)
 * ref suggestion implemented, speed issues are being worked on and should have improved already, FF 3.6.11 works, didn't check Opera. --Magnus Manske 13:09, 24 January 2011 (UTC)

Speed on complicated pages
I just tried editing Anonymous (group). 218 seconds to parse before I could start editing (browser unusable in this time), and too slow to be able to edit effectively. This is on a Dell Mini 9 (1.6GHz Atom, 2GB memory) running Ubuntu 10.10 and editing in Firefox 3.6. How fast is it to open that page for editing for others? (Need numbers before trying to fix :-) ) - David Gerard 14:25, 16 January 2011 (UTC)
 * 10.5 sec on a two-year-old iMac, using Mac OS and Chrome 10.0.634.0. Either is too long for mass usage, but tuning before all functions are working can backfire. Premature optimisation killed the lolcat! --Magnus Manske 22:59, 16 January 2011 (UTC)


 * For what it's worth:
 * {|border=1

!Dell Mini 9, Ubuntu 10.10
 * Anonymous (group)
 * Firefox 3.6.13
 * 218 sec
 * Firefox 4.0b9
 * 71 sec
 * Chromium 8.0.552.224
 * 145 sec
 * Opera 10.62
 * 260 sec
 * } - David Gerard 12:09, 17 January 2011 (UTC)
 * Opera 10.62
 * 260 sec
 * } - David Gerard 12:09, 17 January 2011 (UTC)
 * } - David Gerard 12:09, 17 January 2011 (UTC)

Holy crap! 30 sec in FF 4b9, 17 sec in Chromium 8.0.552.237! - David Gerard 19:06, 19 January 2011 (UTC)


 * Now down to 8.9 sec in FF 4b10. This is approaching usable. Whatever you're doing, keep doing it :-) - David Gerard 22:04, 27 January 2011 (UTC)

Pages with inherent differences
These pages do not survive the parsing/unparsing process unalte red orange, though mostly with only minor changes. Please add them when you find them - they are great "real life" test cases! What about adding a link to "report this page" to pages with "inherent differences" so that users can easily inform which pages contains problematic markup? Helder 01:26, 23 January 2011 (UTC)
 * en:French destroyer Maillé Brézé (1933)

Colors for expanded template with parameters
It would be good if, when we expand a template with multiple parameters, it used different colors to different kind of data. E.g.:

Helder 01:26, 23 January 2011 (UTC)

Templates without parameters
I think the images and  for "show/hide parameters" shouldn't be displayed for templates which doesn't have parameters. Helder 01:29, 23 January 2011 (UTC)
 * What if the user does want to add parameters? --Magnus Manske 13:11, 24 January 2011 (UTC)

Subpages markup
In the current page, the wiki code  generates a link to the page "Talk:WYSIFTW/Subpage" having the text "Subpage" (check: /Subpage/). Nonetheless, the script is currently displaying the text " /Subpage/ ", as if it were the displayed text. The bars shouldn't be displayed. Helder 01:45, 23 January 2011 (UTC)

Math markup
Currently the tooltip displayed when hovering the mouse over a $$ or a $$ tag say it is used for formatting. I think it would be better to say that it is used to insert formulas and other things like that. Besides, it could show a link to meta:Help:Displaying a formula (which has translations in some other languages), using the same style currently used when hovering over links.

Another useful thing would be to have a preview for big formulas, like the following from Heat_equation:
 * $$ u(x,t)=\frac{1}{\sqrt{4\pi kt}} \int_{-\infty}^{\infty} \exp\left(-\frac{(x-y)^2}{4kt}\right)g(y)\,dy $$
 * $$u(x,t)=\frac{1}{\sqrt{4\pi kt}} \int_{-\infty}^{\infty} \exp\left(-\frac{(x-y)^2}{4kt}\right)g(y)\,dy $$

Helder 02:13, 23 January 2011 (UTC)

Positioning of cursor at the end of text
Currently the script doesn't allow us to insert text after the last character. For example, the article Trustmark ends with "US-bank-stub", but we can't put the cursor after the last "b". Helder 13:08, 25 January 2011 (UTC)

Search box
If we click on WYSIFTW and after the script is loaded we click on search box and try to add some text (like "test") it is actually written in the article's beginning. The script should let us do a search (and maybe ask about leaving the page), and this would be another way to cancel the edit mode. Helder 13:08, 25 January 2011 (UTC)


 * Or perhaps searches could open in new windows while you use WYSIFTW? – Minh Nguyễn (talk, contribs) 09:01, 26 January 2011 (UTC)

When to enable/import
I think the script could also be enabled when. Besides, it seems that those " " in the end of script could be moved into, after the following tests: if ( wgAction != 'view' ) return ; // Nevermind... if ( -1 == $.inArray(wgNamespaceNumber,wysiwtf.site.enable_for_namespaces) ) return ; // Nevermind... Helder 17:10, 26 January 2011 (UTC)

Some issues
Ocaasi 03:24, 28 January 2011 (UTC)
 * Awesome tool.
 * I use hide sidebar, a very common .js userscript. WYSIFTW blocks the text and can't be moved.  Maybe an alternate placement at the page bottom, or a floating edit panel would be better.  I realize prototypes can't account for after-market tinkering, but I suspect this could be fairly common for signed in editors.
 * It's having some trouble in lists. Adding items, or playing with spacing between successive bullets *, really anything to introduce a line-break and then try to undo it resulted in sometimes the cursor getting stuck and requiring several deletes to clear.
 * Is there a reason it doesn't work in userspace? It might be helpful for testing to be able to use it there.