math is unparsed but shown as plain wikitext: https://en.wikipedia.org/wiki/User:Raymond/Math
This will require Parsoid to be finished and expose ParserHooks to get alienated, and then a VE node handler to be written. The first bit is relatively easy, but the second is a very significant undertaking, so prioritising as "lowest".
(In reply to comment #1)
This will require Parsoid to be finished and expose ParserHooks to get
alienated, and then a VE node handler to be written. The first bit is
relatively easy, but the second is a very significant undertaking, so
prioritising as "lowest".
Hello James, I have designed and written my proposal for a plugin that will fix this bug. http://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Application
I am not yet familiar with the VE architecture so I need some help understanding it and your comments. Is my design close to what it needed for a "node handler" for the maths elements in a wiki page. Also currently I have two modules named doc reader and doc writer. It would be helpful to know more about how these can interact with the document in visual editor.
The design that I proposed of the User Interface for my plugin be similar to that of google docs. I am wondering if this is closer to what the community wants and needs for VisualEditor. Or if it would be better to stay closer to the existing way special characters are inserted in the traditional wikitext editor.
(In reply to comment #3)
Are there any news on this?
Jiabao was accepted as a GSoC student and will be working on this with us. Updates are going to be added at [[mw:User:Jiabao wu/GSoC 2013 Project Work]].
Wondering how the rendering is going to happen? Is it going to use MathJax which is the only game in town at the moment? The default texvc render won't be up to the job as it need to recreate an image for every keystroke. MathML based renders have basically failed with poor browser support.
If you use MathJax deployment will be a problem unless bug 36496 is fixed.
@Richard this plugin won't be dependent on bug 36496 (MathJax as default). Texvc-compatible syntax remains the internal/wikitext format. MathJax provides a live-preview within VE to enable visual editing. (Of course, a future iteration might use MathJax to save MathML and SVG alongside the TeX.)
@Richard I don't know which VE version is running there. I think I should point out that this is a GSoC project in the middle of development, not anywhere near production ready, frequently breaking etc.
(In reply to comment #7)
@Richard this plugin won't be dependent on bug 36496 (MathJax as default).
Texvc-compatible syntax remains the internal/wikitext format. MathJax
a live-preview within VE to enable visual editing. (Of course, a future
iteration might use MathJax to save MathML and SVG alongside the TeX.)
Have removed the dependency.
(In reply to comment #8)
Is this connect with http://www.mediawiki.org/wiki/VisualEditor:TestMath?
Yes; that's the work being done by Jiabao Wu as part of Google Summer of Code. See https://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Project_Work for updates.
Its important that it will be possible to enter the raw latex and that the text input area is large enough to enter a large formula. Editing the formula for atan2 at https://www.mediawiki.org/wiki/VisualEditor:TestMath now give a multi line box, but its still a bit small and wraps the formula.
It may be an idea to use a different size box for inline formula which tend to be short and display formula which tend to be larger. $ vrs $$ in latex syntax, I don't know how you would distinguish this in VE.
The need for latex input was discussed at https://www.mediawiki.org/wiki/User_talk:Jiabao_wu and came up again at http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&curid=37904286&diff=570517247&oldid=570514963
If you have open tasks or bugs left, one possibility is to list them at https://www.mediawiki.org/wiki/Google_Code-In and volunteer yourself as mentor.
We have heard from Google and free software projects participating in Code-in that students participating in this programs have done a great work finishing and polishing GSoC projects, many times mentores by the former GSoC student. The key is to be able to split the pending work in little tasks.
More information in the wiki page. If you have questions you can ask there or you can contact me directly.
Created attachment 13550
Screenshot of editing a math block
Some small tweaks are needed to the dialog box. Editing the last equation at https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
there are a a few problems
This could be solved the making the dialog, moveable and resizeable.
Also editing the last equation at https://www.mediawiki.org/wiki/VisualEditor:TestMath?veaction=edit
if you actually make a change to the text of the equation the displayed equation becomes very jumbled. Any vertical positioning is lost, and text from different lines are overlaid on top of each other.
This happens with Chrome on a Mac, I can't seem to edit equations at all with firefox or safari.
@Richard/others: Thinking about making the dialog draggable and resizable...
The solution I initially think of is installing jquery.ui and then adding some parameters to OO.ui.Window that allow it to be made resizable and/or draggable. However, if I recall correctly one of the principles of OOJS was to be self-contained... so would this be wrong? Could someone else with a bit more firsthand experience chime in here?
Just a bit of background: Theopolisme is a Google Code-in student working on a task related to #comment 15 that was created by Jiabao:
Jiabao has been silent in the past days. Your help is welcome while she comes back. Thank you!
There are different problems reported here, and we should have separate reports for each. Then we will tie each bug report to a Google Code-in task:
Richard, would you like to create these reports?
I'm going to pull http://www.google-melange.com/gci/task/view/google/gci2013/5861921152565248 in order to create 2 GCI tasks or more. Theopolisme, you can try to work on these issues now, or you can wait until the plan is more defined (and Jiabao is back, or we have found a co-mentor able to help you).
Seems that Jiabao is not currently working on this ticket, hence resetting ASSIGNED status.
It's a bit unclear to me which further steps are required to get this ticket closed (probably creating dependency tickets for the items in comment 19?).
Bug 57437 is to "Allow the VE dialog for math elements to be movable and resizable", which is already a blocker for this ticket. This assigned to a google code-in student, Theopolisme, who I suspect is no longer working on that bug.
I've create bug 61497 to cover up the jumbled up formula in comment 16.
I think Jiabao original plan was to create a GUI I've added a bug for this as bug 61498.
Dialog overlapping the equation might be resolved by bug 57437 or it could possibly resolved by changing the way it is initially displayed.
(In reply to Andre Klapper from comment #21)
It's a bit unclear to me which further steps are required to get this ticket
closed (probably creating dependency tickets for the items in comment 19?).
No, the issues in comment 19 only refer to the short-term LaTeX editor. This bug is asking for a fully-featured visual interactive editor for formulae – will merge bug 61498 back into this.
I hope the LaTeX editor is not going to be short term. This is the preferred input method for the mathematical community. By all means develop a GUI but please make sure you can still use a LaTeX input method.
(In reply to Richard Morris from comment #26)
I hope the LaTeX editor is not going to be short term. This is the preferred
input method for the mathematical community. By all means develop a GUI but
please make sure you can still use a LaTeX input method.
I'm happy to see the interest in the Math extension.
It would be really great to get some code reviews. There are a lot of unmerged improvements that are already implemented that wait for a code review.
The fromula editor for math is one example. The code for Math 2.0 that was finished in beginning of October 2013 is still waiting for review and not moving forward at all. That's really a very sad situation. (Sorry for the spamming)