Free wants to be software for linux

FALF Player wants to be a smart, compact, light and comfortable mp3 player with tabbed playlists.

Its early pre-release and it does not represent the quality of first stable release so be careful with your notes.

If you want to help, join the project!

ECLI library is an Eiffel wrapper around the X/Open ISO/CLI (Call Level Interface), which defines an API to RDBMS drivers and uses SQL92.
ISO/CLI is also known as ODBC under MS Windows.
ECLI wants to be portable across (1) Platforms, (2) Eiffel Compilers.
(1) Platform portability : ECLI works on any platform that has an ISO/CLI Implementation.
(2) Eiffel Compiler Portability : ECLI uses as "standard" Eiffel as possible. The GOBO Library is used for specific data structures.
Some tricks have been used to be free from the idiosyncrasies of any Eiffel Compiler.
It is a pity that even for basic/kernel classes it seems impossible for compiler vendors/providers to agree on some standard.
Enhancements:
- New features include blob/large data transfer, information on DBMS capabilities, session control and information, different login strategies, and information about installed ODBC drivers.
- The samples, documentation, tests, and class hierarchies were reworked.
- Various bugs were fixed.

Hello! Thank you for donating your knowledge and time to our cause. Pariahware, Inc. is currently working on a Bible trivia game that is a cross between the TV game show "Who Wants to be a Millionaire?" and the electronic game series "You Dont Know Jack!" As one might imagine, this can be a daunting task.
That is why we are asking for your help in coming up with some GREAT Bible questions in order to make this game even more fun than we could do by ourselves! When you are finished submitting all of your questions, please e-mail the "qanda.rsd" file back to submissions@pariahware.com. By submitting the questions that you come up with, you agree to the following:
The Legal:
1. You expect no royalty fees or other payment for Pariahware, Inc. using your questions in the game.
2. Any parts of the questions you submit may be altered at will by the members of Pariahware, Inc.
3. Even though you submit a question for the game, that does not necessarily mean it will appear in the game.
4. If your name is included in your e-mail, Pariahware, Inc. has the right to add it as an acknowledgement, unless otherwise noted. You will not be paid as a result of having your name listed.
The How To:
1. Make sure that the Got Word DB Maker application and the "qanda.rsd" file are in the same folder or the program will not work.
2. Double-click the Got Word DB Maker application icon.
3. Select the radio button in the lower-left-hand corner that says "Add new question".
4. There are five text fields. The large one on the top is for the question. The other four are for potential answers. All of these need to be filled.
5. The correct answer needs to be selected by the "drop down" in the upper-right-hand corner.
6. The book of the Bible, in which the question is referencing, needs to be selected in the upper-left-hand corner.
7. Below the book selection is value (points) for the question. This needs to be selected as well.
8. When all of this has been done, the "Save New Question" button will activate. Click it to save your question.
Word of Caution:
To make changes to question that you have already entered, click the "edit existing questions" radio button.
Enhancements:
- Bug Fixes.

Paldo is a Upkg driven GNU/Linux distribution. Its kind of a mix of a source and a binary distribution. Even though it builds packages like a source distribution it provides binary packages.
Paldo stands for "pure adaptable linux distribution" and we try to accomplish this in every package. paldo comes with very few patches against its packages. We have virtually no local changes, means every patch is one which will go upstream anyway (e.g. compile fixes) or one needed by the LFS build system to enable us to boostrap correctly.
Its very easy to make changes to the distro. You can change every package by providing a local version of the sources and specifications youve changed. You can even configure your system automatically through local differencial repositories (see My paldo). The whole distribution is very flexible because its built on top of Upkg.
Paldo wants to be a distribution according to the "just-works" principle. It tries to configure automatically as much as possible without user intervention. paldo is task-oriented, means, that we wont provide several programs to do one and the same task, we will select the program which we think does this task best, and include it into paldo. paldo aims to support cutting-edge technologies. It is pure NPTL based (no linuxthreads support) and therefore does not work with a Linux kernel older than 2.6.x.
Since paldo is task oriented we also have only one desktop environment, the GNOME desktop environment.
Paldo does not split packages, means, all development files will be installed if you install a library. All files you need around a package will be available as soon as it is installed.
Paldo only supports the x86 architecture at the moment and we do not plan to extend that much (except of the x86_64 platform). It is a _very_ popular arch making us the life very easy.
Main features:
- OpenOffice.org 2.0 Beta
- Support x86_64 systems
- gcc 4.0
- Added Bluefish Web Development Editor
- Many smaller package updates

jSettings package is meant to provide a Java library for dealing with program settings. (I use "settings" as just another synonym for preferences, properties, etc but I chose the word settings because of the already existing Preferences and Properties frameworks in Java). It wants to be a powerful tool for the developers of Java programs that want to manipulate structures of settings.
The code (as well as this page) is at an early development and testing stage. On top of that, I am only doing it as a means to teach myself Java (Im an economist by training and by profession) , so even at later stages you can expect the quality of the code to be quite low.
If you feel like any part of the design, code, Javadoc, examples etc is silly please dont hesitate to let me know about it. Also, I would also be happy to include requested features as long as I can understand the need for them and I also know how to do it. So please write to me if you have anything to say about this project!
Main features:
- Handles INI and FSTAB type of files and settings. There is no XML support yet, but I plan to do it if it seems to be requested.
- INI settings are specified by a setting = value pair.
- FSTAB settings are defined by an array of settings, each in a predefined field. I call them like this because the structure is similar to the fstab file in UNIX environments. Logical structure is quite similar to that of XML files.
- Settings can be logically structured into sections.
- There are two degrees of hierarchy available, called hierarchical and non-hierarchical. For example, in a hierarchical organization, the settings in a file called settings.ini, containing the following lines:
[section1]
setting1=value1
[[section1-2]] //Notice the double brackets
setting1-2=value1-2
would be refered to as
settings:section1:setting1
and
settings:section1:section1-2:setting1-2
In a non-hierarchical structure they would be
settings:section1:setting1
and
settings:section1-2:setting1-2 (section1-2 is not a child of section1 anymore).
- Loads settings from external files, either from individual files in ASCII format or from archives containing several settings files.
- Includes support for default values for settings, both for ini and fstab settings.
- The advantage is that the actual ini and fstab files will only contain the deviations from the defaults.
- Includes support for system-wide and user-specific settings, for multi-user environments.
- A program would first load the defaults, then the system-wide settings and then the user-specific ones. Also when modifying the settings, there is a choice between doing it at user and at system level.
- Support for adding/modifying/deleting settings.
- Default support for validating the settings.
- Each ini-type setting and each fstab-type field have a validation rule in the form of a regular expression. When loading the value for that setting/field, it is being checked against the rule and only accepted if it confirms to the rule. Of course, if the user wants it she can have .* as the rule for each setting.
- Support for flushing the changes made to the settings to the external files.
- Extensive logging/debug messages.

Want is a Perl module created to implement the `want command.

SYNOPSIS

use Want;
sub foo :lvalue {
if (want(qwLVALUE ASSIGN)) {
print "We have been assigned ", want(ASSIGN);
lnoreturn;
}
elsif (want(LIST)) {
rreturn (1, 2, 3);
}
elsif (want(BOOL)) {
rreturn 0;
}
elsif (want(qwSCALAR !REF)) {
rreturn 23;
}
elsif (want(HASH)) {
rreturn { foo => 17, bar => 23 };
}
return
}

This module generalises the mechanism of the wantarray function, allowing a function to determine in some detail how its return value is going to be immediately used.

...

EXAMPLES

use Carp croak;
use Want howmany;
sub numbers {
my $count = howmany();
croak("Cant make an infinite list") if !defined($count);
return (1..$count);
}
my ($one, $two, $three) = numbers();


use Want want;
sub pi () {
if (want(ARRAY)) {
return [3, 1, 4, 1, 5, 9];
}
elsif (want(LIST)) {
return (3, 1, 4, 1, 5, 9);
}
else {
return 3;
}
}
print pi->[2]; # prints 4
print ((pi)[3]); # prints 1


sub backstr :lvalue {
if (want(qwLVALUE ASSIGN)) {
my ($a) = want(ASSIGN);
$_[0] = reverse $a;
return undef;
}
elsif (want(RVALUE)) {
my $t = scalar reverse $_[0];
}
else {
carp("Not in ASSIGN context");
}
return
}

print "foo -> ", backstr("foo"), "n"; # foo -> oof
backstr(my $robin) = "nibor";
print "$robin is now $robinn"; # $robin is now robin

Be::Query is a Perl module to do a query for a given filesystem.

SYNOPSIS

use Be::Query;
@files = Be::Query::Query($filesystem, $query);

do a Query for a given filesystem

USAGE

@files = Be::Query::Query("/boot", "name=lib*.so");

$filesystem is a path anywhere in the target filesystem; $query is a query construction, of the form attribute op value [connector attribute op value]

Such as (name = fido) || (size >= 500)