Free pain demolition software for linux

Religion is a Perl module that can generate tracebacks and create and install die() and warn() handlers.

This is a second go at a module to simplify installing die() and warn() handlers, and to make such handlers easier to write and control.

For most people, this just means that if use use Religion; then youll get noticably better error reporting from warn() and die(). This is especially useful if you are using eval().

Religion provides four classes, WarnHandler, DieHandler, WarnPreHandler, and DiePreHandler, that when you construct them return closures that can be stored in variables that in turn get invoked by $SIG{__DIE__} and $SIG{__WARN__}. Note that if Religion is in use, you should not modify $SIG{__DIE__} or $SIG{__WARN__}, unless you are careful about invoking chaining to the old handler.

Religion also provides a TraceBack function, which is used by a DieHandler after you die() to give a better handle on the current scope of your situation, and provide information about where you were, which might influence where you want to go next, either returning back to where you were, or going on to the very last. [Sorry - Ed.]

See below for usage and examples.

USAGE

DieHandler SUB

Invoke like this:

$Die::Handler = new DieHandler sub {
#...
};

where #... contains your handler code. Your handler will receive the following arguments:

$message, $full_message, $level, $eval,
$iline, $ifile, $oline, $ofile, $oscope

$message is the message provided to die(). Note that the default addition of " at FILE line LINE.n" will have been stripped off if it was present. If you want to add such a message back on, feel free to do so with $iline and $ifile.

$full_message) is the message with a scope message added on if there was no newline at the end of $message. Currently, this is not the original message that die() tacked on, but something along the lines of " at line 3 of the eval at line 4 of Foo.pln".

$eval is non-zero if the die() was invoked inside an eval.

The rest of the arguments are explained in the source for Religion::TraceBack. Yes, I need to document these, but not just now, for they are a pain to explain.
Whenever you install a DieHandler, it will automatically store the current value of $Die::Handler so it can chain to it. If you want to install a handler only temporarily, use local().

If your handler returns data using return or by falling off the end, then the items returns will be used to fill back in the argument list, and the next handler in the chain, if any, will be invoked. Dont fall off the end if you dont want to change the error message.

If your handler exits using last, then no further handlers will be invoked, and the program will die immediatly.

If your handler exits using next, then the next handler in the chain will be invoked directly, without giving you a chance to change its arguments as you could if you used return.

If your handler invokes die(), then die() will proceed as if no handlers were installed. If you are inside an eval, then it will exit to the scope enclosing the eval, otherwise it will exit the program.

WarnHandler SUB

Invoke like this:

$Warn::Handler = new WarnHandler sub {
#...
};

For the rest of its explanation, see DieHandler, and subsitute warn() for die(). Note that once the last DieHandler completes (or last is invoked) then execution will return to the code that invoked warn().

DiePreHandler SUB

Invoke like this:

$Die::PreHandler = new DiePreHandler sub {
#...
};

This works identically to $Die::Handler, except that it forms a separate chain that is invoked before the DieHandler chain. Since you can use last to abort all the handlers and die immediately, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages from further handling.

This is even more useful in $Warn::PreHandler, since you can just throw away warnings that you know arent needed.

WarnPreHandler SUB

Invoke like this:

$Warn::PreHandler = new WarnPreHandler sub {
#...
};

This works identically to $Warn::Handler, except that it forms a separate chain that is invoked before the WarnHandler chain. Since you can use last to abort all the handlers and return to the program, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages.

This is very useful, since you can just throw away warnings that you know arent needed.

Domino Blast project is a physics-based driving/demolition game with a childrens toys theme.

Domino Blast is a hybrid driving and destruction game with a childrens toys theme. Its environments consist of buildings constructed from domino tiles and a player-controllable toy car. The objective of the game is to wreak as much havoc as possible, within a time limit.

Its game-play is simplistic yet satisfying; similar to the satisfaction gained from watching a tumbling Jenga tower, except the objective is to tumble the tower, rather than slowly deconstruct it. As the game progresses, levels become more dense and the buildings that inhabit them become larger and more complex.

gladder is an extension that eases the pain of Internet censorship in mainland China.
Get over Great Firewall with Great Ladder!
This extension eases the pain of Internet censorship in mainland China.
Main features:
- Automatically try to open a banned page with a online proxy after you entered the address
- Only auto-redirects pages when you are not using a proxy
- Automatically redirects banned links to visitable URLs in ThunderBird
- If you failed to open a page, click the button on the status bar, it will use a default online proxy to open the page
- List of banned pages is being updated from the Internet every hour

I suggested a kcontrol option for enabling and disabling ACTIONS for different file types. This way, service menus would be installed and managed easier (if that control center window has that function too,it would be nice) aand maybe you will have the option to choose which actions that KIM (kde image service menu)(for example) is capable of is shown in your right click menu when you choose a jpg file...
Also an option to install the service menu just for the user that opened kcontrol (somewhere in /home/~/.kde/.../konqueror/services...) or for all users [the checkbox],requiring a root password (to copy the needed files in the needed by the service menu directories)...
Also the service menu management control center should have the option to move up and down a service menu in the -right-click-ACTIONS> sub menu.
There should be the option to pick selectably the submenus from the installed service menu and add only the ones you would like to have for the file type(for instance you can add kim-resize picture and under it you can take a submenu from a k3b service menu (add to data disc) and put it right under it for the jpg filetype (see the screenshot).
Some service menus,like kims selected "webexport" should have a > sign at the end of their names,showing that they have an included submenu,that cannot be picked/changes sepparatelly.So if web export is added,you dont have the option to pick which webexport options should be included in the web export submenu (we have to have some borders,right?)..
Another suggestion is that if a service menu is installed for all users (using the root password),it should be marked with red fonts in the service list and if promped for uninstallation,it should ofcourse ask for the root password.
And...since the kde service menus were handled the old fashionate way since this idea popped into my mind (with install.sh scripts that coppied a bunch of files,orr by hand with a READme instruction (which is a pain in the neck really)),service menus should be able to be installed the old fashionate way too,but they should be packed in special kde service menu packages,that are handled by kcontrol.This would greatly improve kdes support for service menus.
This will also resolve the clutterness/bloatness that some service menus tend to create,giving the choice in the hands of the user as to what from the service menu he/she would like to be included in the right-click menu.
Enhancements:
- added a new mockup,which is more simple and intuitive

PHPReports project started when I needed something to create some reports on the browser as replacement of those ones my company used to generate using tools like FoxPro, Visual Basic and all that m$ stuff you dudes know about.
I was starting PHP programming (still am) and was really excited about put all the info we need on the browser, but, no pain no gain, theres that kind of reports that needs to have grouping info, grouping break and all sort of grouping stuff including some operations like sum, max, min, average on group values. And printing !!! Breaking the report into pages to fit on the printer as the regular tools do.
It was perfectly possible using PHP, but a report is different from the other, and the customization of it using pure hand-made-code will take a time that I didnt, dont and wont have. So I decided to make it on a flexible way using XML files to make the report layout, creating PHP code to run it on the browser.
Now its easy to make reports - just define the report layout and put all the functions you want - simple, clean and easy. And the most important! Using this approach you can (I did) show your company that you dont need any other kind of software to make all the stuff you need (by, m$ stuff).
Enhancements:
- Added 3 JavaScript events: ONCLICK, ONMOUSEOVER and ONMOUSEOUT;
- Added the concept of input plugins. The first one convert the SQL query on a way it allows to show crosstab reports.

Universal Module Player or UModPlayer, is a audio module "tool-chain", providing you functions to work with modules like playing, exporting, getting information, and more.
Universal Module Player works in UNIX-like platforms, including Linux, Mac OS X, FreeBSD, Solaris...
It uses the Custom LibModPlug audio library, an improved version of the well-known LibModPlug library, supporting more than 20 formats and giving you high playing quality. It uses LibSDL to handle multiplatform sound support.
Main features:
- You can play the supported formats and seek to any order in the song. You have pause, timer, display, and other standard features.
- You can view the pattern notes while playing.
- You can specify noise reduction, megabass, surround, reverb sound options specifying the grade and the delay of most of the options.
- You can create, save and edit playlists to play a selection of modules.
- You can read and export to a file the song builtin message, the song instrument names and the song sample names.
- Each user of your UNIX box can save all the sound options.
- And much more!
Supported Formats
Supported file formats on both Little Endian (Intel x86, etc.) and Big Endian (PowerPC, SPARC, MIPS, Motorola 68000, etc.) platforms:
Impulse Tracker (IT), Scream Tracker (STM), Scream Tracker 3 (S3M), Extended Modules (XM), Amiga Modules (MOD), OktaMED (MED), Oktalyzer (OKT), Unreal Modules (UMX), Composer 669 (669), DigiBooster Pro Modules (DBM), PolyTracker (PTM), and Farandole (FAR)
Additional file formats supported only on Little Endian platforms (support for Big Endian is on development):
MultiTracker Modules (MTM), AFM, AMS, DMF, DSM, DigiTracker (MDL), MadTracker 2.0 (MT2), PSM, ULT
Exporting Formats
You can export or convert any of the above formats to the following file types:
Impulse Tracker (IT)
WAVE Audio File (WAV)
Audio Interchange File Format (AIFF)
Raw Pulse Code Modulation (PCM)
Enhancements:
- Buffer length fixes.
- Playlist commands were a pain. Now we use the first letter of the command name. Also, pressing ENTER does not quit, the user has to explicitly specify to quit pressing q
- Hopefully fixed AIFF exporting bug.
- New section in the README about LibAo configuration, and some misc. rearrangements.