MediaWiki 1.22 Math Extension - mediawiki

I am facing a problem to download and configure the MediaWiki's Math extension.
The problem is that the version i am using is the MediaWiki 1.22.6 and the extension's versions avaliable to download here starts at 1.23. Nevertheless, i discovered that the Math extension can be installed since the MW 1.19 but i cannot find this version.
However, the only thing i found was the MathJax that seems to be able to run under the MW 1.22, but i am not sure if the MathJax depends on the Math extension to run.
So my question is, how can add formulas in the MW 1.22? Is it through Math extension or i can use only the MathJax? If the Math extension is necessary, where can i find a version capable of run in the MW 1.22?
Thank you all for the help.

For formulas in MediaWiki don't use the Math extension or MathJax, instead use Extension:SimpleMathJax.

Related

Math extension installation for Mediawiki

I am trying to enable my Mediawiki 1.28 to handle math equations. I followed the instructions given here, here and here.
However, when I write the following in a page on my Mediawiki, it does not get rendered:
<math>x=\frac{-b+\sqrt{d}}{2*a}</math>
My PHP version is 7.0.14. I do not know if I am doing anything wrong. Any help will be appreciated.

How to convert many HTML files to MediaWiki Pages on Windows?

I'm on Windows and I have an index.html in a folder and a huge set of html pages in subfolders.
How can I convert these html files to MediaWiki pages?
Check the Converting content from HTML text file section from the manual at mediawiki.org. Personally I would start with these two, and if that doesn't work I'd build something based on pywikibot. Any of these solutions can be made to work on Windows, though it is advisable to try it on Linux or OS X first, and if not install Cygwin.
You're unlikely to find any kind of streamlined GUI tool for such a specialized action. If you need more help with using the code available there you should hire a programmer or learn how to do it yourself.

objective j loads slowly in browsew

I am iOS developer. I know just a couple of languages and I hate html because of the lack of possibilities there.. I've just red about objective-j. When I try to open any code in web browser (last versions of Safari, Google Chrome) it loads increadibly slow..
Is it normal?
How to make it work fast?
Are there any other languages similar to c, objective-c that I can use for creating a web-site?
And another queastion coming with: How can I make Xcode work with objective-j? I use coda 2.0 at the moment.
Make sure you run jake deploy to create the stripped and precompiled version of the app you're testing. Most sample code out there will be run in uncompiled "debug" mode which is great when you're developing but in actual deployment you'll want the precompiled version of your app.
Also, the current development version of Cappuccino and Objective-J is much faster than the last release 0.9.6, thanks to a new, better compiler. Keep an eye out for a future Cappuccino 0.9.7 release.
I think if you write a significant app in Cappuccino you'll find the load time to be absolutely comparable with other large web apps such as Gmail.
Currently you can only use Xcode to edit the user interface of a Cappuccino app. It does not work well to edit Cappuccino code itself since the latest versions of Xcode don't include the necessary plugin framework. You can learn more about good editor options in the development environment tutorial.
I am not familiar with other languages similar to Objective-C for the web, but Intel has an Objective-C to JavaScript compiler here.

How to set up Dave Raggett's HTML Tidy on Windows?

I'm having a hard time looking for an easy to understand instruction to download, set up and use this HTML Tidy by Dave Raggett.
Please help, I need this kind of tool that can almost perfectly scan html errors.
If there is a GUI version for the latest one, please share the link.
Click the link to the downloads
Pick binary executables
select a version suitable for your edition of Windows
A precompiled Windows binary for the experimental HTML5-fork can be found at http://tidybatchfiles.info/.

Defining a runtime environment

I need to define a runtime environment for my development. The first idea is of course not to reinvent the wheel. I downloaded macports, used easy_install, tried fink. I always had problems. Right now, for example, I am not able to compile scipy because the MacPorts installer wants to download and install gcc43, but this does not compile on Snow Leopard. A bug is open for this issue, but I am basically tied to them for my runtime to be usable.
A technique I learned some time ago, was to write a makefile to download and build the runtime/libs with clearly specified versions of libraries and utilities. This predates the MacPorts/fink/apt approach, but you have much more control on it, although you have to do everything by hand. Of course, this can become a nightmare on its own if the runtime grows, but if you find a problem, you can use patch and fix the issue on the downloaded package, then build it.
I have multiple questions:
What is your technique to prepare a well-defined runtime/library collection for your development?
Does MacPorts/fink/whatever allows me the same flexibility of rehacking if something goes wrong ?
Considering my makefile solution, when my software is finally out for download, what are your suggestions about solving the potential troubles between my development environment and the actual platform on my user's machines ?
Edit: What I don't understand in particular is that other projects don't give me hints. For example, I just downloaded scipy, a complex library with lots of dependencies. Developers must have all the deps setup before working on it. Despite this, there's nothing in the svn that creates this environment.
Edit: Added a bounty to the question. I think this is an important issue and it deserves to get more answers. I will consider best those answers with real world examples with particular attention towards any arisen issues and their solution.
Additional questions to inspire for the Bounty:
Do you perform testing on your environment (to check proper installation, e.g. on an integration machine) ?
How do you include your environment at shipping time ? If it's C, do you statically link it, or ship the dynamic library, tinkering the LD_LIBRARY_PATH before running the executable? What about the same issue for python, perl, and other ?
Do you stick to the runtime, or update it as time passes? Do you download "trunk" packages of your dependency libraries or a fixed version?
How do you deal with situations like: library foo needs python 2.5, but you need to develop in python 2.4 because library bar does not work with python 2.5 ?
We use a CMake script that generates Makefiles that download (mainly through SVN)/configure/build all our dependencies. Why CMake? Multiplatform. This works quite well, and we support invocation of scons/autopain/cmake. As we build on several platforms (Windows, MacOSX, a bunch of Linux variants) we also support different compile flags etc based on the operating system. Typically a library has a default configuration, and if we encounter a system that needs special configuration the configuration is replaced with a specialized configuration. This works quite well. We did not really find any ready solution that would fit our purpose.
That being said, it is a PITA to get it up and running - there's a lot of knobs to turn when you need to support several operating systems. I don't think it will become a maintainance-nightmare as the dependencies are quite fixed (libraries are upgraded regularly, but we rarely introduce new one).
virtualenv is good, but it can't do magic - e.g. if you want use a library that just MUST have Python 2.4 and another one that absolutely NEEDS 2.5 instead, you're out of luck. Nor can virtualenv (or any other tool) help when there's a brand new release of an OS and half the tools &c just don't support it yet, as you mentioned for Snow Leopard: some problems are just impossible to solve (two libraries with absolutely conflicting needs within the same build), others just require patience (until all tools you need are ported to the new OS's release, you just need to stick with the previous OS release).