Free master of puppets software for linux

Solving word problems is an area where elementary students overwhelmingly display difficulties. Master Math Word Problems program can help sharpen skills through practice. Third through fifth graders learn to watch for key words and translate those into mathematical operations.

Students can learn new math skills, practice logic, get extended practice with word problems, but most of all they learn that they must read the problem. With regular practice your students may become master math word problem solvers.

Download and try out Master Math Word Problems.

ISO Master is an open-source, graphical CD image editor that runs on Linux; and bkisofs, the underlying library used for reading, modifying and writing ISO images.
The hard part of this project is the library for working with ISOs (bkisofs). My hope is that people will like this library enough to make their own GUIs using it. So my choice of widget set (GTK, that is) will not necessarily annoy too many people.
Main features:
- Display file/directory contents of the image and and the regular filesystem in two panels and be able to navigate them.
- Display file sizes for files on image/filesystem.
- Sort by name or by size
- Select any number of items in the file browsers.
- Extract selected from image to the filesystem
- Delete selected from image.
- Add selected from filesystem to image.
- Save modified image.
- Create image from scratch.
Enhancements:
- Usability and performance improvements.
- 10 new translations.
- A bug that sometimes caused corrupt ISOs to be written has been fixed.

Hanzi Master project is a visual, interactive Chinese character and word dictionary.
Hanzim ("Hanzi Master") is an interactive visual dictionary for learning and seeing relationships between Chinese radicals, characters, and compounds.
All the characters with a given radical, phonetic component, or pronunciation can be displayed, and all words containing a character, with English meanings.
All data is stored locally. Either simplified or traditional characters can be used.
Main features:
- typing in pinyin gives list of characters and definitions with that pronunciation
- clicking on a radical gives list of characters and definitions with that radical
- clicking on any character in any list displays that character along with the compounds it occurs in as the first or second character.

Puppet lets you centrally manage every important aspect of your system using a cross-platform specification language that manages all the separate elements normally aggregated in different files, like users, cron jobs, and hosts, along with obviously discrete elements like packages, services, and files.

Puppets simple declarative specification language provides powerful classing abilities for drawing out the similarities between hosts while allowing them to be as specific as necessary, and it handles dependency and prerequisite relationships between objects clearly and explicitly.

Puppet is a system configuration tool. Puppet project has a library for managing the system, a language for specifying the configuration you want, and a set of clients and servers for communicating the configuration and other information.

The library is entirely responsible for all action, and the language is entirely responsible for expressing configuration choices.

Everything is developed so that the language operations can take place centrally on a single server (or bank of servers), and all library operations will take place on each individual client. Thus, there is a clear demarcation between language operations and library operations, as this document will mention.

Setup

The vast majority of Puppet architectures will look like a star, with a central server running puppetmasterd, and each client node running puppetd, contacting that central server.

Your central manifest, which contains the configuration for all of your nodes, needs to be on the central server, most likely at /etc/puppet/manifests/site.pp.

Start the puppetmasterd daemon, and then tell your clients to contact that server by specifying -s < servername > as arguments to puppetd, replacing "< servername >" with the name of the server. Alternatively, puppetd defaults to looking for a server named "puppet", so you can just create a CNAME for your server, so that it answers to "puppet".

It is a good idea to run both the server and client in verbose mode, enabled with the -v flag, until you are sure everything is working. As each new client connects, you will need to run puppetca --list to list the certificates waiting to be signed, and then puppetca --sign < name >, replacing "< name >" with the name of the client whose certificate you want to sign. You can turn on autosigning by creating /etc/puppet/autosign.conf and put the hosts, domains, or IP addresses or ranges that you want to sign in there.

ResearchMaster project has been designed to make working a little easier. Specifically, the application can be either a storage facility for all of your precious, miscellaneous digital information, or for just some of it. The project began as a way for the author to [1] have a centralized library for all the papers and various snippets he collects, and [2] to have some powerful, built-in support for BibTeX, the LaTeX bibliography system ( The LaTeX bibliography system, as described in the Leslie Lamport book. ISBN 0-201-52983-1).
When the application starts up, it creates a virtual filesystem (vfs) from information contained in records. Each record appends itself under at least one folder in the vfs, and the vfs is represented by a tree-widget system of folders and records. The application is divided into folder controls (left) and record controls (right).
Each record is actually a set of three python dictionaries, stored in a flat ascii text file. The three dictionaries correspond to [1] BibTex information corresponding to the record, [2] Meta information (eg. isbn, call number, url, membership) and [3] an endless notes file. When a record is selected from the tree widget, the corresponding three dictionaries are presented in a three-tabbed notebook widget on the right side of the application.
New records are created via a button on the records toolbar. When you create a new record the application pops a filechooser and you are given the opportunity to import a single file. Perhaps the imported file is a pdf copy of a research paper that you dont want to lose. ResearchMaster is a good place to store it. First, the record and the imported file now have each other. Now you can keep a log of your involvement with the file in the notes portion of the record. The Meta portion of the record contains non-BibTex information, such as which folders the record is a member of. The application accesses the records BibTex information whenever the record has membership within the subtree of a particular folder for which a recursive bibliography is being generated.
Heres a typical example: Say you create a folder for some project. Lets say that after six months your folder now has several subtrees of folders and records, all arranged according to the scheme that happened. Now imagine there are twenty records with BibTex information strewn throughout the projects subtree, side-by-side with other records that dont have BibTex information (notes, whatever). By pushing the Create Bibliography button on the left toolbar the application will produce a perfectly formatted BibTex file with all twenty records.
Each record can be made a member of any folder simply by adding the folders path to the membership list in the Meta portion of the record. The tree widget is dynamically constructed by recursively examining a directory tree (corresponding to the folders of the tree-widget) and the membership list contained in each record. This is done so that we only have one physical copy of each record, despite the fact that the record might show up in fifty different places throughout the tree widget.
The file that gets imported with a record can be any file of any format. You can tell ResearchMaster to launch the file as an argument to any external application, based on the filenames suffix (.gif, .avi, .mpg, .mp3). Then, select the record from the tree, push the launch button (on the records toolbar), and voila! The associated application brings up your file. Thats one feature that makes working a little easier.
Enhancements:
- Small correction was needed on line 1140 of ResearchMaster_wxuser.py, where "researchmaster" needed to be "ReseaerchMaster" for preferences initialization.

Zombie Master project is a multiplayer survival horror FPS/RTS mod for Half-Life 2. A team of FPS-playing humans attempts to complete map-specific objectives while an RTS player controls the zombie horde with only one goal: death to all humans.
He is the Zombie Master.
Enhancements:
- [fix] Weapons were sometimes hard to pick up
- [fix] Fast shooting exploits in shotgun and rifle
- [tweak] Health indication in player identification display
- [tweak] ZM resource limit server setting zm_resource_limit (default 4000)
- [fix] Team changes (including to spectator after death) had erratic results
- [feature] Muting players
- [tweak] Weapon flags failed to reset in some situations after forcehuman/forcemaster team switching
- [fix] ZM preference window came up when the ZM camera toggled
- [fix] Zombie spawns could still be clicked when inactive
- [fix] Voting for roundrestart could be spammed
- [fix] DOTD chalkboard weirded out
- Plus minor fixes to the maps.
As usual, if your game goes horridly wrong after patching, try reinstalling with the 1.1.2 full installer.
UPDATE: If you experience the spectator bug after patching to 1.1.2, it is recommended you do a clean install using the full 1.1.2 installer.

Puppet::Log provides a log facility with an optional Tk display.
This class implements a log facility with an optional Tk display.
I
.e once the class is created, you can log messages in it, but the Tk display does no need to be created at the same time. You may invoke later only when you need it.
When the Tk display is not invoked, the log can be either printed on STDOUT or warned on STDERR (or stay hidden). But in any case, the log message will be stored in the class so that all log messages can be retrieved later by the user or by the Tk display when invoked.
Once the Tk display is invoked, it will be updated by new logs.
Constructor parameters:
- title: Title of the Tk log display (optional)
- name: Name of the log used when printing on STDOUT or STDERR (optional)
- how: Specifies what to do when a log is sent to the object (either print on STDOUT, warn on STDERR). By default the logs will not be printed or warned. (optional)
- help The argument may be a string or a sub reference. When the help menu is invoked, either the help string will be displayed in a Tk::Dialog box or the sub will be run. In this case it is the users responsability to provide a readable help from the sub. (See "help" in Tk::Multi::Manager for further details)
Puppet classes are a set of utility classes which can be used by any object. If you use directly the Puppet::*Body class, you get the plain functionnality. And if you use the Puppet::* class, you can get the same functionnality and a Tk Gui to manage it.
The basic idea is when you construct a Puppet::* object, you have all the functionnality of the object without the GUI. Then, when the need arises, you may (or the class may decide to) open the GUI of the object. On the other hand, if the need does not arise, you may create a lot of objects without cluttering your display.

Puppet::Body provides an utility class to handle has-a relations and logs.
Puppet::Body is a utility class that is used (and not inherited like the deprecated Puppet::Any) to manage dynamic has-a relations between objects.
Main features:
- An event log display so user object may log their activity (with Puppet::LogBody)
- A Debug log display so user object may log their "accidental" activities(with Puppet::LogBody)
- A set of functions to managed "has-a" relationship between Puppet objects.
Puppet framework is made of a set of utility classes. I currently use this framework for a major application Tk application.
If you use directly the Puppet::Body class, you get the plain functionnality. And if you use the Puppet::Show class, you can get the same functionnality and a Tk Gui to manage it.