Free mess software for linux

Nimages provides an image gallery script featuring themes and a Web-based installation.
Nimages is a simple image gallery script featuring a Web-based installtion and configuration (no editing of the script is needed).
Other features include MySQL support, automatic creation of thumbnails (if supported), themes, and ease of use and configuration.
Nimages is a complete rewrite of the JCS Image Display script.
Main features:
- A nifty web-based install automagically detects most options.
- An advanced and normal mode. Normal mode is for users who arent comfortable setting up and running scripts, and the advanced mode is for people who want a little more control.
- Only one file to mess with...Copy and Go!
- Complete editing of image information from withing the program.
- A system that lets authorized users log in and edit image info, add comments, and manipulate galleries.
- Uses MySQL if available.
- A comprehensive theme system.

MOS 6502 Simulator is sort of an emulator for a 6502 chip. Theres virtually nothing apart from the CPU (minus BCD operations). It also bears no heed to instruction timings.

Whilst (apart from those two things) it successfully simulates the CPU there were a few design flaws, which led me not to continue with it:

- I wrote it in C++.

As the 6502 had no dedicated IO bus, everything was done via memory. I had the idea of having a pure virtual class which provided a generic interface, then as I wrote devices to sit in the memory space, they could just override portions of it, or trap on writes or something.

Whilst writing this, I kept getting the feeling I should have written it in asm instead Especially for manipulating flags and rotates and stuff. (as I could have just rotated AL, for example, rather than the mess I have in the C++ code.

- Sloppy instruction decoding.

I originally set out to decode the instructions properly, but there were lots of exceptions to the system used (esp. if I intended to support the 65C02 for example). This decended into a massive switch statement. I almost considered splitting it up to smaller files, and just #include them in the middle, just to make it more managable.

Also, as they are not in numerical order (grouped according to type, or addressing mode, cant remember atm) it wouldnt compile to a jump table. Does with optimisation on though.

The main thing that prompted me to write this was I found my BBC-B in the loft, and felt a pang of nostalgia for the hours wasted hunched over it in the lowest resolution text mode (IIRC mode 7 to save ram). I had the idea of writing a NES or BBC emulator, however it didnt get that far.

It has a pretty simple image format. The file must be >= 65536 bytes (64k) and that is simply the memory image for the system (16-bit address bus). There is a strange sort of ASCII text display at 0x200, which is ok enough for spewing a string to. As it was just thrown together in the space of 6 hours or so (took a long time to do the switch statement) its not very thouroughly documented, but hey.

Xmame is the X11/Unix port of MAME. MAME is the Multiple Arcade Machine Emulator, an arcade (coin-op) video game emulator.
The latest stable release is capable of playing over 2000 arcade games.
Enhancements:
- Everything from MAME 0.106 (changes-mame.html) and MESS 0.106 (changes-mess.html).
- Reverted a change that was intended to work around some Metacity focus misbehavior but was causing all window managers to have focus problems in fullscreen mode.
- Fixed a link error for messtest. (Arnaud G. Gibert)
- The clean68k target now removes libcpu.a, which fixes link errors for successive builds made without a full clean. (Arnaud G. Gibert)
- Fixed an alignment bug in the OpenGL driver which caused Defender, and possibly other 16bpp games, to be skewed.
- The mouse is no longer automatically grabbed in fullscreen mode. Bugzilla bug 877.
- Replaced fuzzy game name comparison with the method used by MAME for Windows, which lists approximate matches when an exact match isnt found.
- A BadMatch error should no longer occur for the OpenGL target in some cases, such as when 16bpp mode is used with recent releases of the binary NVIDIA driver.
- Fixed the tiny build target. (Mike Frysinger)
- Added CFLAGS for the Blackfin CPU. (Mike Frysinger)
- BUILD_ZLIB and BUILD_EXPAT can now be disabled without having to edit the makefile. (Mike Frysinger)

Pod::InComments is a Perl extension for extracting POD documentation from comments in config file.

SYNOPSIS

use Pod::InComments;
my $podparser = Pod::InComments->new( comment => ; );
$podparser->ParseFile( $my_config_file );
$podparser->Pod2Hash();

my $helptext = $podparser->Pod4Section( $section , $key );

This module was written to solve the problem of describing numerous parameters in a config file. When you add comments to the config file, it becomes a mess quickly. And no-one will take the time to properly read them. You can not add POD directly. So..... here is Pod::InComments.

It was developed when using Config::IniFiles format, so lets take that as the basis. The Config::IniFiles module lets you use config files in the form of the popular windows ini file. That is, they look like

[section]
param1=some value
param2 = another value
param3=20.00

; this is a comment
[operating system]
preferred=Linux
using=Windows XP Pro

METHODS

new( comment => # )

Constructor of the class. Specify the comment character(s) used in the config file. Defaults to ;. You can use whatever you like here. So #### is valid as well, but requires more typing in the config.

ParseFile( $config_file )

Parses the $config_file and extracts all the comment lines. The comment character(s) are stripped of each line. It returns a string with all the POD.

Pod2Hash()

After parsing a config file, you will need to call this function to convert the POD into a hash. The keys of the hash are the head1 titles. If head2 elements are present, they will be subkeys of the hash.

Pod4Section( $section, $param )

Returns the POD belonging to the $section, or to $param of $section.

E.g., when your config file looks like:

;=head1 cpu
;
;Specifies cpu settings for normal boxes
;note that these will override factory settings!
;
;=head2 maxload
;
;The maxload setting gives an upperbound on how hard
;the CPU can be pushed.

[cpu]
maxload=4.0

then doing:

my $pod = $podparser->Pod4Section( cpu, maxload );

will give you:

The maxload setting gives an upperbound on how hard the CPU can be pushed.

SavePod( $file )

Saves the extracted pod to the $file. If you omit a file name, it will append .pod to the config file you parsed and saves to that file.

GetPod()

Returns the entire POD formatted in text.

DisplayPod()

Prints the entire extracted POD documentation to STDOUT.

Maypole is a Perl framework for MVC-oriented web applications, similar to Jakartas Struts. Maypole is designed to minimize coding requirements for creating simple web interfaces to databases, while remaining flexible enough to support enterprise web applications.
What does that mean?
Many web applications follow the same kind of flow of operation in response to a request from a user, they mess about with a database, and present the results of that messing about back to the user through some templating system.
For instance, searching a companys product catalogue will take a query from the remote web client, search the database for the rows matching that query, and format the rows as a list for display on a page.
This set-up is sometimes called "MVC", after the famous Smalltalk-80 Model-View-Controller paradigm. For our concerns, this means that the interaction with the user, (the controller element) the actions required at the database, (the model element) and the presentation of data (the view elements) are all neatly compartmentalised.
Maypole provides a generic way of handling that compartmentalisation. It provides the top-level code which examines the users request, fires off the relevant method in the model, collates the data, asks the view class to format it up and sends it back to the user. * As well as this, some common Perl modules, such as Apache, Class::DBI and Template, already perform important parts required for model, view or controller operation, so Maypole provides wrapper classes to help them fit into the framework.
Enhancements:
Bug Fixes :
- Fixed some db_colinfo test bugs
- Fixed typo in edit form template
- AsForm fixes to stringification _to_select
- made DFV and FromCGI warn instead of die on unexpected cgi params
- small improvements to some factory templates
- fix to path handling in mod_perl and CGI when location ends in /
- fixed template path ordering so i.e. /tablename/list is used before /list when provided with a tablename
- fixed template path with array refs
- fix to template being reset from path in plain templates (i.e. where no model), may affect those relying on the bug ( bug 23722 )
- fix to display_line macro in factory templates (bug 22920)
- fix to correct problem with LocationMatch and regex based Location directives in apache config.
- fix to redirect_request
- Fixed typo in _do_update_or_create (bug 26495)
API additions and enhancements :
- new Class::DBI::DFV based model
- New config method : additional, for stashing additional info, especially from additional_data method
- new warn method in maypole/request class/object, over-ridden by Apache::MVC, etc or own driver
- new build_form_elements attribute for Maypole request and Maypole::Config, set it to 0 to avoid building cgi form if you dont need it
- added CGI params to TT error template
- improvements to factory templates
- added search_columns method to base cdbi model class, provides display_columns unless over-ridden
- added new hook - preprocess_location
- added new attribute to Maypole::Config - request_options
- improved pager template macro
Internal additions and enhancements :
- Inheritence simpler and nicer and less hacked
- add_model_superclass method moves @ISA munging into the model
- new test to check everything compiles
- Model inheritance re-organised

MiniDV Assembler application is particularly useful for owners of digital MiniDV cameras and others who use the Sony MiniDV format for high quality video production.

MiniDV Assembler allows you to append multiple MiniDV files with nice looking transition effects for both audio and video. Multiple transition effects are supported, like cross-fade, zoom, blur and a flash effect.

I created MiniDV Assembler because there are no easy to use video editing applications for Linux yet. Yes, Kino is promising, but its user interface is still a mess and development is slow.

MiniDV Assembler only touches the head and tail parts of the original video files that are needed to create the transition effects. The rest of the video is left untouched, which means zero quality loss.

MiniDV Assembler can also be used to generate video editing scripts that can be run without KDE and Kommander.

Use this tool after your upgrade in a comfortable KDE gui. The idea for this comes from http://kde-apps.org/content/show.php?content=45401 and we would like to thank the author for this and for the kommander work too.

Use with caution.although this tool is tested, it may mess your system and his use is intended for experienced users.

Use this tool only in a Slackware system!