numptyphysics(6) [debian man page]
numptyphysics(6) Numpty Physics numptyphysics(6) NAME
numptyphysics - Crayon-based physics puzzle game SYNOPSIS
numptyphysics DESCRIPTION
Numpty Physics is a Crayon-drawing puzzle game in the spirit of Crayon Physics using the same excellent Box2D engine. It melds cute school- book-style graphics with a kind of realistic physics engine. It includes a built-in editor so that you may build (and submit) your own lev- els. A summary of the keys supported is included below. PLAY KEYS
stylus draw a new stroke space or enter pause/unpause physics esc or backspace undo last stroke q quit r or up reset level to initial state n or right skip to next level p or left go to previous level e or fullscreen edit mode Hints: Each stroke is like a rigid piece of wire with a mass proportional to its length. A closed stroke is just a wire bent into a shape, it has no substance apart from its perimeter. The ends of a strokes can (and will) join onto other strokes when drawn near enough to another stroke. These joints are pivots so you can use this to build levers, pendulums and other mechanical wonders. Jointed strokes don't collide with each other. Join both ends to make a rigid structure Play bugs: goal item does not respawn if lost. EDITOR KEYS
Keys: (as per play mode plus the following) e or fullscreen leave edit mode s or menu save to ~/.numptyphysics/L99_saved.nph zoom-minus + stylus delete stroke at point zoom-plus + stylus drag stroke at point Hints: It's handy to pause the physics when making a new level though this is by no means necessary. Sometimes it is handy to let the physics run for a little bit just to let the items settle down. From the editor palette you can choose the crayon colour and then additional properties such as: * ground (earth arrow) - stroke is fixed in place. * sleeping (Zzz) - stroke is not subject to physics until bumped by something else. * decorator (dashed D) - stroke is not part of the physical world. eg: tutorial text. You should make sure that your level has at least one red item (player token) and at least one yellow item (goal item). Token strokes will only join to other token strokes. Goal strokes will only join to goal strokes. Other strokes will happily join to any non-token non-goal strokes. If this is your first time, you may need to restart the game for your saved L99 to show up. If you wish to be clever, edit the level file directly - it's just a simple text format. Editor bugs: There is not yet any provision to name your level but you can just rename the file to anything. AUTHOR
This manual page was written by Gabriele Giacone <1o5g4r8o@gmail.com> for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 any later version pub- lished by the Free Software Foundation. December 30, 2009 numptyphysics(6)
Check Out this Related Man Page
gschem(1) 1.6.2.20110115 gschem(1) NAME
gschem - gEDA/gaf Schematic Capture SYNOPSIS
gschem [-q] [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o outputfilename] [-p] [-h] [schematic1 ... schematicN] DESCRIPTION
gschem is the schematic capture program which is part gEDA (GPL Electronic Design Automation) toolset. This program is used to draw elec- tronic schematics. Schematics consist of standard symbols (which are either part of a standard library or created by the user) which rep- resent the various gates and components. These components are then interconnected by nets (wires). Schematics may be printed to a Post- Script file for printing or further conversion to other output formats. Output to various image formats is also supported. gschem is also the symbol creation editor. All the standard methods of creating schematics are used in the creation of symbols. There are a few special rules when creating symbols, so please refer to the (non-existant as of now) symbol creation document. Please read the official documentation (very minimal at this point) on how to use gschem, since this man page just describes the command line arguments and a few examples on how to run gschem. OPTIONS
gschem accepts the following options: -q Quiet mode on. This mode turns off all warnings/notes/messages. (optional) -v Verbose mode on. This mode gives as much feedback to the user as possible. (optional) -t Print out more information when using mouse strokes. With this command line flag and the middle button configured for mouse strokes, gschem will output the stroke sequence numbers as the user executes strokes. These numbers can be used to define new strokes in the system-gschemrc file. -r filename Specify a rc filename. Normally gschem searches for the system-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc in the current directory. This options allows the user to specify an additional rc file which is read after all the other rc files are read. (optional) -s filename Specify a guile script to be executed at startup. (optional) -o filename Specify a filename for postscript output. This command line argument is useful when running gschem from a shell script and with a guile script. The filename can be changed through the print dialog box. -p Automatically place the window, especially useful if running gschem from the command line and generating output. -h Print out short command line help. schematic1 [... schematicN] Schematic file to be loaded. Specifying a schematic file is optional. If multiple schematic files are specified they are read in sequentially and put on separate pages. It is important that the schematic(s) follow all the options (ie last). EXAMPLES
These examples assume that you have a schematic called stack_1.sch in the current directory To run gschem and then interact with the program: gschem To run gschem in interactive mode but load a sample schematic: gschem adders_1.sch To run gschem and load up all schematics in the current subdirectory: gschem *.sch ENVIRONMENT
gschem respects the following environment variable: GEDADATA specifies where the various required scheme and rc files are located (the default is ${prefix}/share/gEDA). This environment vari- ables does not need to be set by the end user unless they are moving the executables to a new install ${prefix}. AUTHOR
Ales Hvezda and many others SEE ALSO
gnetlist(1), gsymcheck(1) COPYRIGHT
Copyright (C) 1999-2008 Ales Hvezda This document can be freely redistributed according to the terms of the GNU General Public License version 2.0 Version January 15th, 2011 gschem(1)