Free config maker software for linux

Config Maker is a tool to automatically create C++ classes that parse configuration files.

Only a few lines of text that describe the possible entries in the configuration file are needed, and the complete class will be generated ready for use.

Basic usage

The input files for Config Maker have a very simple structure (in ANTLR/grep like notation):

objectname (configentry)+
Each configentry looks like this
type entryname defaultvalue (comment)?

type

Type of the entry, can be int, double, string or bool. If the basic type is followed by any number, the corresponding c++object variable will be of type vector < basic type > The number is the initial number of elements that are allocated for the vector, but the actual configuration file can contain more components. These are added using the push_back method.

If there are less elements specified in the configuration file, the object variable will still contain the number of elements specified here. No warning will be issued.
configentry

Name of the entry and corresponding variable. Has to be at least two characters long and can contain characters and numbers. Case insensitive.

defaultvalue

Default value for the entry. This is optional.

comment

Each comment starts with // and is completely ignored

El Jay Icon Maker is a Firefox extension that allows you to right click on any image and create an icon for use with livejournal.com There are two options to choose from when making an icon "Create Icon Instantly" and "Create Icon With Options".

Selecting either link redirects you to the El Jay icon maker home page where you can rotate, crop, add text and borders to the image. The El Jay icon maker was made for use with llivejournal.com, but can be used on any site that requires an image smaller than 100x100 for an icon.

This is not a support forum, if you have questions or problems please go here: http://www.livejournal.com/users/lechatron/407511.html?mode=reply

Patch Maker helps you manage multiple in-progress source code patches to software. Patch Maker remembers which files are part of which patch, and keeps them disentangled during the development process.
It speeds up common operations and housekeeping tasks, allowing you to focus on writing code. It is a command-line tool written in Perl, and so is usable on (at least) Windows, Linux and Mac OS X.
Enhancements:
- Initial SVN support was added to go with CVS.
- The configuration was moved to the .pmrc file in the home directory.
- Message and error printing were tidied up and standardized.

Config::YUM is a Perl extension for parsing yum.conf.

SYNOPSIS

use Config::YUM;

my $yp = new Config::YUM;
my $yum_conf = $yp->parse();

foreach(keys %{$yum_conf}) {
print "Section: $_ is called " . $yum_conf->{$_}->{name} . "n";
}

$yum_conf will be a a hash, all INI sections are the primary hash keys.
include= will be automatically downloaded merged with the local yum.conf
mirrorlists will also be downloaded and saved as an array in $yum_conf->{somerepo}->{baseurls}
the first url in mirrorlists will be safed as $yum_conf->{somerepo}->{baseurl}.
exclude statements will be splited and safed to $yum_conf->{somerepo}->{exclude_hash}. Note that we
safe a perl regex string as keys here.

To say it with one sentence. Config::YUM automatically parses a yum.conf does the downloading and provides you
with a ready to use perl hash. :-)

You can define a few things @ new:

- use_cache: 0/1 (1 will enable, default: 0; Uses Cache::File)

- yum_conf: path to your yum.conf (default: /etc/yum.conf)

- yum_repos_d: path to your yum.repos.d (default: /etc/yum.repos.d)

- agent: You LWP::UserAgent agent string (default: Config::YUM/$VERSION)

- releasever: Define your RH/FC release version (rpm -qf --queryformat %{VERSION} /etc/redhat-release; Default: automatically queried)

- basearch: Define your basearch (uname -i; Default: automatically discovered)

- download_primary: Define if we should download/parse the primary.xml.gz

These arguments can be specified this way (dont forget the {!)
my $yp = new Config::YUM({
use_cache => 1,
yum_conf => /etc/yum.conf,
yum_repos_d => /etc/yum.repos.d,
agent => MyProgram/$VERSION,
relasever => 4,
basearch => i386,
download_primary => 1
});

This module provides you with a few functions,
parse() will return a hash containing the allready parsed local/remote yum.conf.

yumconf_local() will return a hash containing the allready parsed local yum.conf (Will run parse(), if you didnt yet)
yumconf_remote() will return a hash containing the allready parsed remote yum.conf (Will run parse(), if you didnt yet)

Config::Model provides a framework to help in validating the semantic content of configuration data. The project can also be used to provide a semantic check of options of a complex program like mplayer or transcode.
For most complex software, configuration upgrade is a difficult task for most people. By using Config::Model, a software can provide a smooth upgrade path for their users.
How does this work ?
Using this project, a typical configuration validation tool will be made of 3 parts :
The user interface
The validation engine which is in charge of validating all the configuration information provided by the user.
The storage facility that store the configuration information
Dont we already have some configuration validation tools ?
Youre probably thinking of tools like webmin. Yes, these tools exist and work fine, but they have their set of drawbacks.
Usually, the validation of configuration data is done with a script which performs semantic validation and often ends up being quite complex (e.g. 2500 lines for Debians xserver-xorg.config script which handles xorg.conf file).
In most cases, the configuration model is expressed in instructions (whatever programming language is used) and interspersed with a lot of processing to handle the actual configuration data.
Whats the advantage of this project ?
The Config::Model projects provide a way to get a validation engine where the configuration model is completely separated from the actual processing instruction.
The configuration model is expressed in a declarative form (i.e. a Perl data structure) which is always easier to maintain than a lot of code.
The declaration specifies:
the structure of the configuration data (which can be queried by generic user interfaces)
the properties of each element (boundaries, check, integer or string, enum like type ...)
the default values of parameters (if any)
mandatory parameters
the targeted audience (intermediate, advance, master)
on-line help (for ach parameter or value of parameter)
the level of expertise of each parameter (to hide expert parameters from newbie eyes)
So, in the end:
maintenance and evolution of the configuration content is easier
user will see a *common* interface for *all* programs using this project.
user will not see advanced parameters
upgrade of configuration data is easier and sanity check is performed
audit of configuration is possible to check what was modified by the user compated to default values
What about the user interface ?
Config::Model will also come with a Curses::UI interface that queries the users model and generate the relevant user screens.
What about data storage ?
Since the syntax of configuration files vary wildly form one program to another, most people who want to use this framework will have to provide a dedicated parser/writer.
Nevertheless, this project can also provide a writer/parser for most common format: like ini style file, or provide an interface to the Elektra or debconf projects. This point is open for discussion.
It is entirely possible for a single configuration model to use several parsers and writers so one model will ensure the consistency of several configuration files together.
Enhancements:
- The Xorg model was updated to Config::model version 0.609.
- Some bugs were fixed.

Soundboard Maker is a tool for making and running soundboards.

You can play selected audio, save soundboards, load soundboards, and distribute your soundboards to other users.

The interface is easy to customize.

Config::General is a perl module opens a config file and parses its contents for you.
Config::General library provides variable interpolation, saving of configs (kinda serializer), an OOP-Interface and much more.
The format of config files supported by Config::General is inspired by the well known apache config format, in fact, this module is 100% compatible to apache configs(read-only), but you can also just use simple name/value pairs in your config files.
In addition to the capabilities of an apache config file it supports some enhancements such as here-documents, C-style comments or multiline options.
Installation:
To install, type:
perl Makefile.PL
make
make test
make install
To read the complete documentation, type:
perldoc Config::General
perldoc Config::General::Extended
perldoc Config::General::Interpolated
See some example config files which can be parsed with Config::Genreal in the subdirectory t/cfg.*
Enhancements:
- A number of bugs were fixed and unit tests were improved.

File::Maker is a Perl module that mimics a make by loading a database and calling targets methods.

SYNOPSIS

#####
# Subroutine interface
#
use File::Maker qw(load_db);

%data = load_db($pm);

######
# Object interface
#
require File::Maker;

$maker = $maker->load_db($pm);

$maker->make_targets(%targets, @targets, %options );
$maker->make_targets(%targets, %options );

$maker = new File::Maker(@options);

Generally, if a subroutine will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}. If a subroutine will process an array reference, @options, [@options], that subroutine will also process a hash reference, %options, {@options}. See the description for a subroutine for details and exceptions.

When porting low level C code from one architecture to another, makefiles do provide some level of automation and save some time. However, once Perl or another high-level language is up and running, the high-level language usually allows much more efficient use of programmers time; otherwise, whats point of the high-level language. Thus, makes great economically sense to switch from makefiles to high-level language.

The File::Maker program module provides a "make" style interface as shown in the herein above. The @targets contains a list of targets that mimics the targets of a makefile. The targets are subroutines written in Perl in a separate program module from the File::Maker. The separate target program module inherits the methods in the File::Maker program module as follows:

use File::Maker;
use vars qw( @ISA );
@ISA = qw(File::Maker);

The File::Maker methods will then find the target subroutines in the separate target program module.

The File::Maker provides for the loading of a hash from a program module to provide for the capabilities of defines in a makefile. The option pm = $file> tells File::Maker to load a database from the __DATA__ section of a program module that is in the Tie::Form format. The Tie::Form format is a very flexible lenient format that is about as close to a natural language form and still have the precision of being machine readable.

This provides a more flexible alternative to the defines in a makefile. The define hash is in a separate, very flexible form program module. This arrangement allows one target program module that inherits the File::Maker program module to produce as many different outputs as there are Tie::Form program modules.