MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Risc_OS_on_ARM_based_CPUs",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "144": {
                "pageid": 144,
                "ns": 0,
                "title": "ReGIS",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "'''ReGIS''' is a vector graphics markup language made by DEC for it's VT125, VT230, VT240/241 and above terminals. commands can be sent to it by serial or any other text/tty connexion.\n\n== Overview of the features ==\nDepending on terminal resolution and features changes\n* VT125 768\u00d7240 pixels, 2 bitplans\n* VT230 800\u00d7480 pixels, 2 bitplans\n* VT240/VT241 768\u00d7480 pixels, 4 bitplans\n\nThere is \"shading\" management allowing to mix simple patterns for fill or border, \n\nIt supports curves with polynomial interpolation, by default with only one point + a value, it builds a circle.\n\n\n== Use it on Linux distros ==\nXterm supports it. Arch Linux and derivative support it from scratch. It must be recompiled on Debian and derivatives, with the --enable-regis-graphics option. Display will change depending on used VT emulation.\n\nLaunch xterm like this to have more capabilities:\n xterm +u8 -geometry 132x50 -ti vt340 -tn vt340 /bin/bash\n\nthen launch the script or connect by one of the available serial tools (screen, minicom, etc...) to the hw producing the markup.\n\nThe markup is send to terminal prefixed, after the documentation by 0x1b 0x50 0x32 x70 (ESC + 'P2p', but on xterm implementation at least, any single digit decimal number instead of 2 works). It is also suffixed by 0x1b 0x5c (ESC + '\\', standard VT endline sequence).\n\nImplementation in Bash:\n echo -e \"\\x1bP2p${command}\\x1b\\\\\"\n\nin Lua:\n io.stream(string.char(0x1b)..\"P2p\"..command..string.char(0x1b,0x5c))\n\n'''Don't forget to flush the stream in tests with system based languages, to avoid a buffer filling few seconds wait''' :)."
                    }
                ]
            },
            "10": {
                "pageid": 10,
                "ns": 0,
                "title": "Resources",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "== Discussions ==\n\nPouet's [http://www.pouet.net/topic.php?which=8791&page=1 Tiny Intro Toolbox Thread] was one of sizecoding.org's main inspirations.\n\nWe also have an active discord server dedicated to sizecoding at: https://discord.gg/pZE5rAQrHx\n\n== Seminars ==\n\nSeminars on various sizecoding topics have been presented at the Lovebyte demoparty, and can be watched here: [https://www.youtube.com/playlist?list=PLr4JCYhdWe8mq3aDvAtL0ooO7hAC9gU2s Lovebyte seminars on YouTube]\n\nIn recent years 256b intro coding has been covered in presentation sessions at other demo parties. The recordings are available on YouTube. There are \n[https://www.youtube.com/watch?v=WbWYBE9vjdk part 1] and [https://www.youtube.com/watch?v=51BOp5Pi4mU part 2] of \u0158r\u0159ola's talk \"Magic of 256-byte x86 intros\" held at Demobit 2017 and 2018 respectively. A similar talk [https://www.youtube.com/watch?v=V_ntnQKemWA \"256 byte intros on modern PCs\"] was held by TomCat/Abaddon at the Function 2017 party. Supplemental files can be downloaded from [http://www.pouet.net/prod.php?which=72454 Pouet.net]. The presentations cover everything from setting up the coding environment to all kinds of code optimization, constant reuse, flag tricks, palette generation, and how to get from an idea to the final intro. TomCat also provides a [https://www.abaddon.hu/usbdos/ dev tools page] and his [https://www.abaddon.hu/256b/ SizeCoding Blog] with lots of optimization ideas.\n\n== References ==\n\nThe Hugi demoscene diskmag has been kind to the sizecoding movement.  They included [http://www.hugi.scene.org/online/coding/hugi%20se%204%20-%20index%20sorted%20by%20topic.htm many programming articles] since it started in 1996.  Additionally, the [http://www.hugi.scene.org/compo/compoold.htm Hugi Size Coding Competition Series] is the gold standard for learning how to sizecode:  Each competition was given a specific task, then participants submitted their results.  ([http://retrolandia.net/hugi/showthread.php?tid=7&pid=13#pid13 All of the entries with their source code] are available, as are [http://retrolandia.net/hugi/showthread.php?tid=7&pid=396#pid396 the rules for each challenge].)  Hugi #35 also provided a [http://hugi.scene.org/online/hugi35/hugi%2035%20-%20demoscene%20forum%20adok%20256b%20intros%20round-table.htm 256b intros round-table] between Baze, Digimind, &#344;r&#345;ola, Pirx, Optimus, and Seven.\n\nfysnet.net has an extensive [http://www.fysnet.net/yourhelp.htm list of DOS .COM register starting values].  If your environment isn't listed, [http://www.fysnet.net/yourhelp.com a program] is also available that can print out all of the register starting values.  See also [https://web.archive.org/web/20170418182707/http://pferrie.host22.com/misc/lowlevel12.htm DOS Register Starting Values] to understand why the register starting values for .COM files are set the way that they are.\n\nThe [http://sparksandflames.com/files/x86InstructionChart.html Sparks And Flames x86 Instruction Chart] is awesome, once you can \"read\" it. Find out what the bright green (1-byte) commands do, and use them. For the extreme sizecoding (<=32 bytes) it's also very useful to have the HEX value in sight.\n\nThe [http://ref.x86asm.net/geek.html Geek Edition x86asm-ref] is comprehensive and dense.  It might be the only reference you'll need.  The [http://ref.x86asm.net/geek.html#modrm_byte_16 last part] covers modr/m bytes, which is useful.\n\n[https://www.felixcloutier.com/x86/ Yet another reference] by F\u00e9lix Cloutier.\n\n[http://www.techhelpmanual.com/2-main_menu.html Tech Help Manual] includes a dense reference of DOS interrupts and x86 instructions.\n\n[http://c9x.me/x86/ c9x.me]: A x86 instruction reference\n\n[https://kernfunny.org/x86/ Rene Jeschke's preservation of siyobik.com's x86 Documentation] is one of the most compact and understandable references to the x86 instruction set you'll ever see.\n\nIntel IA-32 Software Developer's Manual Instruction Set Reference [http://www.jaist.ac.jp/iscenter-new/mpc/altix/altixdata/opt/intel/vtune/doc/users_guide/mergedProjects/analyzer_ec/mergedProjects/reference_olh/mergedProjects/instructions/whgdata/whlstt2.htm hypertext version].\n\n[http://www.rcollins.org/secrets/OpCodes.html Robert Collins' Undocumented Opcodes] page has some gems you can exploit depending on your target environment.\n\n[http://wiki.osdev.org/PC_Speaker PC Speaker Basics] For everything from simple bleeps to sophisticated synthesizers.\n\n[https://en.wikipedia.org/wiki/Program_Segment_Prefix Program Segment Prefix] : what's in front of our .COM code, and why.\n\nNever underestimate [http://www.hugi.scene.org/online/coding/hugi%2017%20-%20coaax.htm The Hidden Power of BCD Instructions].\n\n[http://www.agner.org/optimize/optimizing_assembly.pdf An optimization guide for x86 platforms By Agner Fog] Chapter 10: Optimizing for size.\n\n[http://home.sch.bme.hu/~ervin/codegems.html Code Gems by Ervin/AbaddoN] Nice collection based on the Imphobia diskmagazine article.\n\n[http://wiki.osdev.org/Programmable_Interval_Timer Programmable Interval Timer]: Timing is everything, if you're targeting a slow system. Very old but good text [http://www.phatcode.net/res/246/files/pctim003.txt PCTIM003.TXT]\n\n[http://stanislavs.org/helppc/bios_data_area.html BIOS data area]: Direct system communication overview.  There are environment values here you may be able to utilize.\n\n[https://www.midi.org/specifications/item/table-1-summary-of-midi-message Summary of MIDI messages] : Summary of all basic MIDI messages.\n\n[http://www.voidaudio.net/percussion.html Roland GS/GM2 Drum Set List and Note Map] : Detailed Description of all MIDI drumkits.\n\n[http://www.h-schmidt.net/FloatConverter/IEEE754.html Online IEEE 754 Converter] : Excellent tool for optimizing/reusing FPU constants\n\n[https://baseconvert.com/ieee-754-floating-point Base Convert IEEE 754] : Alternative tool for optimizing/reusing FPU constants with live update\n\n[https://www.reddit.com/r/tinycode Tinycode on Reddit]: Collection of many different size coding productions incl. x86 based ones with discussion (mostly provided by [https://www.reddit.com/user/Hell__Mood/ HellMood] himself)\n\n[https://marquee.revival-studios.com/blog Superogue's sizecoding microblog]: Collection of demoscene and sizecoding related articles and development writeups up [https://www.pouet.net/groups.php?which=14389 various Marquee Design tiny intros]\n\n[https://www.xtof.info/Timing-on-PC-familly-under-DOS.html Timing-on-PC-familly-under-DOS] A complete and very detailed guide about timing, timers, callbacks, interrupts in conjunction with MSDOS\n\n== Repositories ==\n\nTinyprogs are so small that you sometimes don't need the source code to understand them:  Just pop them into a disassembler (like IDA) or a debugger and look at them.  If you want to grab specimens for study, here are some places to start.\n\nPouet can be searched for the latest tinyprogs:  [http://www.pouet.net/prodlist.php?type%5B%5D=256b&platform%5B%5D=MS-Dos&page=1 256b], [http://www.pouet.net/prodlist.php?type%5B%5D=128b&platform%5B%5D=MS-Dos&page=1 128b], [http://www.pouet.net/prodlist.php?type%5B%5D=64b&platform%5B%5D=MS-Dos&page=1 64b], and even [http://www.pouet.net/prodlist.php?type%5B%5D=32b&platform%5B%5D=MS-Dos&page=1 32b and smaller].\n\n[http://hardcode.untergrund.net/ HardCode] is a repository of 7800 64KB and smaller intros.\n\n* [https://files.scene.org/get/demos/compilations/hardcode/hardcode.zip Scene.org link] to this archive\n\n* [https://files.scene.org/get/demos/compilations/hardcode/hc_update.zip Scene.org link] to an archive update from 2017 to 2022\n\n[http://256bytes.untergrund.net 256b.com] is a website dedicated primarily to 256b and smaller releases."
                    }
                ]
            }
        }
    }
}