MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Real_World_Mozilla_Adding_Chrome_to_FirstXpcom_Lab",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "1865": {
                "pageid": 1865,
                "ns": 0,
                "title": "Readme.txt",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "<pre>\nPREREQUISITES:\nYou'll need to download some software onto your Windows machine before running\nthese performance tests:\n  * Python 2.4\n    The scripts all run from Python 2.4.  You will need the windows version\n    (not the cygwin version).  You can download it here:\n    http://www.python.org/ftp/python/2.4/python-2.4.msi\n    Make sure to correctly set the path to python in the paths.py file.\n    After you download and install Python 2.4, you'll need to install\n    some extensions:\n      * Python Win32 Extensions\n        These extensions provide some support for process management and\n        performance monitoring.\n        http://prdownloads.sourceforge.net/pywin32/pywin32-208.win32-py2.4.exe?download\n      * Numerical Python:\n        This is required by Matplotlib.\n        http://prdownloads.sourceforge.net/numpy/Numeric-24.2.win32-py2.4.exe?download\n      * Matplotlib\n        This library is used to plot the graphs of performance characteristics\n        of Firefox during the page load test.\n        http://prdownloads.sourceforge.net/matplotlib/matplotlib-0.87.3.win32-py2.4.exe?download\n\n      * PySyc\n        This is used for reading/writing config files in YAML.\n        http://pyyaml.org/download/pysyck/PySyck-0.61.2.win32-py2.4.exe\n\n  * Cygwin\n    For some reason, we can't get output from Firefox unless it's wrapped in a\n    Cygwin sh shell.  So we use cygwin for that, and to sync between Firefox\n    runs.  Download it here:\n    http://www.cygwin.com/setup.exe\n\n    Make sure to correctly set the path to Cygwin in the paths.py file.\n\n  * msvcp71.dll\n    You need a copy of this file to run Python with all the libraries.  If you have\n    Visual Studio 2003 installed, you've already got it.\n\nSETUP:\n  1. Make sure the prerequisites, above, are installed.\n  2. Copy this entire directory and all subdirectories onto your local disk\n  3. Edit the paths.py file to set the paths to Cygwin, Firefox, etc. on your \n     machine.\n  4. Create a YAML config file with info about the profiles you want to test.\n     It should look something like this:\n\n     # Filename will be appended to the timestamp in the report filename.\n     # Use letters and underscores only\n     filename: slowmachine\n     # The title of the report\n     title: 1 GHz Celeron\n\n     # Name of profile to test\n     Test profile 1:\n       # Path to Firefox to test\n       firefox: C:\\Program Files\\Mozilla Firefox 2 Beta 1\\firefox.exe\n\n       # Preferences to set in the test (use \"preferences : {}\" for no prefs)\n       preferences:\n         javascript.options.showInConsole : true\n         xpinstall.enabled : true\n\n       # Extensions to install in test (use \"extensions: {}\" for none)\n       extensions:\n         # Need quotes around guid because of curly braces\n         \"{12345678-1234-1234-1234-abcd12345678}\" : c:\\path\\to\\unzipped\\xpi\n         foo@sample.com : c:\\path\\to\\other\\unzipped\\xpi\n\n  5. Run run_tests.py with the name of your config file as an argument. You can use\n     a space-separated list of config files, to generate a report of startup and page load times. The\n     report will be placed in the REPORTS_DIR directory you specified in\n     paths.py.\n\nDIRECTORY STRUCTURE:\n   page_load_test/\n     This directory contains the JavaScript files and html data files for the\n     page load test. The page load test opens a new window and cycles through\n     loading each html file, timing each load.\n   startup_test/\n     This directory contains the JavaScript to run the startup test.  It\n     measures how long it takes Firefox to start up.\n   base_profile/\n     This directory contains the base profile used for testing.  A copy of\n     this profile is made for each testing profile, and extensions or prefs\n     are added according to the test_configs array in run_tests.py.  For the\n     page load test to run correctly, the hostperm.1 file must be set to allow\n     scheme:file uris to open in new windows, and the pref to force a window\n     to open in a tab must not be set.  The dom.allow_scripts_to_close_windows\n     pref should also be set to true.  The browser.shell.checkDefaultBrowser\n     pref should be set to false.\n   run_tests.py, paths.py\n     These files should be configured to run the test on different machines,\n     with different extensions or preferences.  See setup above.\n</pre>"
                    }
                ]
            },
            "2230": {
                "pageid": 2230,
                "ns": 0,
                "title": "Real World Mozilla",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "=Real World Mozilla Development: a one week crash course=\n\n==Overview==\n\nMozilla, creator of the popular Firefox web browser, is one of the largest collaborative open source projects in the world. Working on Mozilla is challenging, fun, and one of the best ways to gain real-world development experience. Getting involved with Mozilla means learning new skills, meeting new people, and having the opportunity to work on global software products with tens of millions of users. However, as exciting as it is, getting started can be intimidating and overwhelming\u2014Mozilla has millions of lines of source code. This course will give you the knowledge you need to start building Firefox extensions by introducing you to the following topics (NOTE: a [[Topics in Mozilla Development|complete topic list]] is also available):\n\n==Topic List by Day==\n\n'''Monday''' - [[Dive into Mozilla Day 1|Introduction to Open Source and Mozilla]]\n* What is Open Source?\n* What is the Mozilla Project?\n* The Mozilla developer community and its practices\n* Mozilla Platform and Technology overview\n* Using IRC to communicate with other Mozilla developers around the world\n* Using Mozilla\u2019s collaborative documentation tools (wikis, wiki markup)\n\n'''Tuesday''' - [[Dive into Mozilla Day 2|Building Mozilla from Source]]\n* More IRC\n* The Mozilla Build Process and Build System\n* Using Revision Control Systems (CVS and SVN)\n* Introduction to make and writing Makefiles\n* Building Mozilla from source code\n\n'''Wednesday''' - [[Dive into Mozilla Day 3|Developing Mozilla]]\n* Using developer tools (e.g., diff, patch, etc.)\n* Using Mozilla webtools (LXR, Bonsai, Bugzilla, Pastebin)\n* Finding your way around in the Mozilla source tree\n* Introduction to XPCOM Components\n* Writing your first XPCOM Component in C++\n\n'''Thursday''' - [[Dive into Mozilla Day 4|Debugging and Testing]]\n* Finishing your first XPCOM Component\n* Learning how to debug Mozilla (C/C++ and JavaScript)\n* Strategies for Testing XPCOM Components (e.g., xpcshell unit tests)\n* Bugs, Bugzilla, Testing, and QA\n* Bug Triage, methods of manual testing\n\n'''Friday''' - [[Dive into Mozilla Day 5|Firefox and Extensions]]\n* Modifying Firefox\n* XUL and Javascript Firefox Extensions\n* Writing your first XUL/JS Extension\n* Combining your XPCOM and XUL Extension\n* XULRunner and application deployment\n\n<!-- Commented out instance-specific information to make more generic.\n==Cost==\n\nFree for School of Computer Studies students and Seneca faculty/staff\n\n==Prerequisites==\n\nIt is assumed that those taking the course already have some knowledge of programming (e.g., C/C++, JavaScript), but enthusiasm is more important than experience. There will be no tests and no exam, only hands-on opportunities to learn. Upon completion of the course you will have an excellent sense of the Mozilla project and its community, practices, tools, and opportunities.\n\n==When==\n\nClasses will run from '''Monday February 26''' to '''Friday March 2, 2007''', '''10:00 am \u2013 4:00 pm''' (one hour break for lunch).\n\n==Location==\n\nSeneca@York campus rooms '''S1206''' (Monday only), and '''T4046''' (rest of the week).\n\n==Registration==\n\n'''Registration is now closed!'''\n\nComputer Studies students please register by sending an email from your learn account to Daman Panesar. Please include your student number.  Faculty and staff please email David Humphrey\n-->\n \n[[Category:M@S]]"
                    }
                ]
            }
        }
    }
}