Free true love software for linux

True Color Picker is a PHP class that can be used to present a palette to let the user pick colors.

It displays an image with all the tones for the user to pick by clicking in an image point with the desired tone similar to Photoshop.

It uses AJAX to update the picker boxes without reloading the page.

Struct::Compare is a recursive diff for perl structures.

SYNOPSIS

use Struct::Compare;
my $is_different = compare($ref1, $ref2);

Compares two values of any type and structure and returns true if they are the same. It does a deep comparison of the structures, so a hash of a hash of a whatever will be compared correctly.

This is especially useful for writing unit tests for your modules!

PUBLIC FUNCTIONS

$bool = compare($var1, $var2)

Recursively compares $var1 to $var2, returning false if either structure is different than the other at any point. If both are undefined, it returns true as well, because that is considered equal.

Pantry is a command-line nutrient analysis program for Unix-like operating systems. The project is still under development. What needs the most work right now is error checking and documentation. Below is a section from the Pantry user guide that describes Pantry in brief.
In addition to using Pantry from your shell prompt, you also interact with it through XML files. Using XML, you can edit Pantrys configuration file. You can also add nutrient information for custom foods (though Pantry includes nutrient information for over 7,000 foods to get you started) and recipes using XML.
Pantry currently runs only on Unix-like operating systems. Porting Pantry to Windows would be possible, but not trivial.
Pantrys advantages
Pantrys true command-line interface gives it many advantages. Because Pantry works from your shell prompt, you can easily combine it with other text-processing tools. You can also easily write scripts incorporating Pantry, in ways that even I cannot anticipate. This is the strength of the Unix "toolbox" way of using a computer.
In addition, nothing beats the speed of a command-line program for something you use frequently and are familiar with. If you are using a nutrient-analysis program to track your daily food intake, you will appreciate how quickly you can use Pantry for this purpose. Indeed, I developed Pantry due to my frustration with current tools because it was very tedious to use them to quickly tally a days food intake.
Because Pantry runs from a text console, you can easily set it up on one computer that has an SSH server running. You may then access your nutrient data from any computer that has an SSH client.
Pantry disadvantages
The biggest disadvantage of using Pantry is the same as its biggest advantage: its command-line interface. Graphical user interface programs attempt to be self-documenting: just sit down, click on some buttons, and hopefully you can figure things out. With Pantry, on the other hand, you will absolutely have to read this manual to figure out how it works, and you will need some practice before you are comfortable with Pantry. In this way, Pantry resembles other command-line oriented Unix programs. As with other Unix programs, once you learn Pantry, you will love its speed and efficiency--but you will have to spend some time learning.
Similarly, because of its command-line interface, you will find that you are most efficient with Pantry if you know your way around a Unix shell prompt. For example, you will find that you can use Pantry more quickly if you know how to use your shells features to manipulate your command history. Such knowledge is useful for any Unix command-line program, not just Pantry; however, building up this knowledge takes some time.
Pantry has no tools to graphically visualize your food intake. I might eventually add such features using Gnuplot or something similar.
A final disadvantage of using Pantry is that it is still new. I am still tweaking it, making changes, adding features, and improving the documentation. But perhaps this is not such a disadvantage: software that improves is nice. If you have any features that you would like, ask!
Enhancements:
- The --edit option was changed so it works correctly with plain text data files.
- The file format was changed to save disk space and memory; however, this makes Pantry native files that Pantry 19 uses incompatible with earlier versions.
- If users report this as a problem, then the author intends to write a converter.
- This release also includes minor bugfixes and improvements to error messages.

ustr (Micro string library) is a string API for C. A few years ago now I wrote a very extensive String API for C, called Vstr, it was designed to perform extremely well for IO like patterns as that was my planned usage (for instance And-httpd, my Web server). It works very well, for that usage.
Also due to the extensivness of the API I basically used it everywhere, even though there are some things it is somewhat "overkill" for, and I wanted other people to use it so I didnt have to resort to using string.h when creating patches for their code. However more than a few C coders I speak to have one of a few reasons why they dont want to use Vstr. The ustr API should solve all of these problems, and hopefully fill in all the gaps where Vstr is the 500lb hammer.
A Significant example of usage, with comments:
Ustr *s1 = USTR(""); /* == "", always works */
Ustr *s2 = ustr_dup(s1); /* == "", always works */
Ustr *s3 = ustr_dup_cstr(""); /* == "", always works */
ustr_cmp_eq(s1, s2); /* == TRUE */
ustr_cmp_eq(s1, s3); /* == TRUE */
if (ustr_shared(s2)) /* This is TRUE, as a constant/read-only string cannot be freed */
/* whatever */ ;
if (ustr_ro(s2)) /* This is TRUE */
/* whatever */ ;
if (!ustr_add_fmt(&s2, "%s %d %c%d", "x", 4, 0, 8))
/* error */ ;
if (ustr_owner(s1)) /* This will return FALSE, as noone owns the "" read-only string */
/* whatever */ ;
if (ustr_owner(s2)) /* This will return TRUE, as weve now got allocated memory for s2 */
/* whatever */ ;
foo_API(ustr_cstr(s1), ustr_len(s1)); /* == "", 0 */
foo_API(ustr_cstr(s2), ustr_len(s2)); /* == "x 4 008", 6 */
s3 = ustr_dup(s2); /* dont need to free s3 as its empty */
/* dont need to check for errors as s2 == s3 */
if (ustr_owner(s2)) /* This will now return FALSE, weve got two references: s2 and s3 */
/* whatever */ ;
if (ustr_shared(s2)) /* This is FALSE, its a non-shared string referenced by both s2 and s3 */
/* whatever */ ;
ustr_free(s2); /* freed one reference to the data pointed to by both s2 and s3 */
ustr_set_share(s2); /* Make s2/s3 "shared" data,
so it always has infinite references */
if (ustr_shared(s2)) /* This is TRUE */
/* whatever */ ;
if (ustr_ro(s2)) /* This is FALSE */
/* whatever */ ;
s3 = ustr_dup(s2); /* This is the same as s3 = s2; */
ustr_free(s2); /* These do nothing */
ustr_free(s2);
ustr_free(s2);
ustr_free(s2);
if (!ustr_add_cstr(&s3, "abcd"))
/* error */ ;
ustr_add_cstr(&s3, "1234");
ustr_add_cstr(&s3, "xyz");
if (ustr_enomem(s3)) /* check for errors on the last 2 ustr_add_cstr() functions at once
ustr_owner(x) has to be true for this to be reliable,
hence the explicit first check */
/* error */ ;
ustr_set_owner(s2); /* Make s2 be "non-shared" and have a single owner */
ustr_set_owner(s1); /* This fails, as you cant make a read-only string be "non-shared" */
ustr_sc_del(&s2); /* freed s2 and set s2 = USTR("") */
ustr_cmp_eq(s1, s2); /* == TRUE */
s2 = USTR1(x0b, "Hello world"); /* Constant string with data */
if (ustr_shared(s2)) /* This is TRUE */
/* whatever */ ;
if (ustr_ro(s2)) /* This is TRUE */
/* whatever */ ;
/* dont need to "free" anything else */
Enhancements:
- A lot of new functions were added, such as insert, replace, split, substitute, and io_getdelim.
- Documentation improvements were made.
- Build fixes were made for Win32.

Garden is a dependency injection for PHP5.

Inspired by Spring Framework, it uses XML application context with syntax as similar as possible to Spring context definitions.

Kickstarter

Create example.xml file like this (dont forget to put garden-beans.dtd next to it!):

< ?xml version="1.0" encoding="UTF-8"? >
< !DOCTYPE beans PUBLIC "-//GARDEN//DTD BEAN//EN" "garden-beans.dtd" >
< beans default-lazy-init="true" >

< bean id="dog" class="Dog" file="ext/Dog.php" >
< property name="collar" >
< ref local="dogCollar"/ >
< /property >
< /bean >

< bean id="dogCollar" class="Collar" file="ext/Dog/Collar.php" >
< property name="spiked" value="true"/ >
< /bean >

< /beans >

etx/Dog.php contains:
class Dog
{
private $collar;
public function setCollar($collar)
{
$this->collar = $collar;
}
public function getCollar()
{
return $this->collar;
}
}

etx/Dog/Collar.php contains:
class Collar
{
private $spiked;
public function setSpiked($spiked)
{
$this->spiked = $spiked;
}
public function getSpiked()
{
return $this->spiked;
}
}

Autodia::Handler::Torque Perl module contains an AutoDia handler for Torque xml database schema.

This provides Autodia with the ability to read Torque Database Schema files, allowing you to convert them via the Diagram Export methods to images (using GraphViz and VCG) or html/xml using custom templates or to Dia.

SYNOPSIS

use Autodia::Handler::Torque;

my $handler = Autodia::Handler::dia->New(%Config);

$handler->Parse(filename); # where filename includes full or relative path.

Description

The Torque handler will parse the xml file using XML::Simple and populating the diagram object with class, superclass, and relationships representing tables and relationships.

The Torque handler is registered in the Autodia.pm module, which contains a hash of language names and the name of their respective language.

An example Torque database schema is shown here - its actually a rather nice format apart from the Java studlyCaps..

< ?xml version="1.0" encoding="ISO-8859-1" standalone="no" ? >
< !DOCTYPE database SYSTEM "http://db.apache.org/torque/dtd/database_3_0_1.dtd" >
< database name="INTERPLANETARY" >
< table name="CIVILIZATION" >
< column name="CIV_ID" required="true" autoIncrement="true" primaryKey="true" type="INTEGER"/ >
< column name="NAME" required="true" type="LONGVARCHAR"/ >
< /table >

< table name="CIV_PEOPLE" >
< column name="CIV_ID" required="true" primaryKey="true" type="INTEGER"/ >
< column name="PEOPLE_ID" required="true" primaryKey="true" type="INTEGER"/ >

< foreign-key foreignTable="CIVILIZATION" >
< reference local="CIV_ID" foreign="CIV_ID"/ >
< /foreign-key >
< foreign-key foreignTable="PEOPLE" >
< reference local="PEOPLE_ID" foreign="PEOPLE_ID"/ >
< /foreign-key >
< /table >

< table name="PEOPLE" >
< column name="PEOPLE_ID" required="true" autoIncrement="true" primaryKey="true" type="INTEGER"/ >
< column name="NAME" required="true" size="255" type="VARCHAR"/ >
< column name="SPECIES" type="INTEGER" default="-2"/ >
< column name="PLANET" type="INTEGER" default="-1"/ >
< /table >
< /database >

Gtk2::Ex::Dialogs is a Perl module with useful tools for Gnome2/Gtk2 Perl GUI design.

SYNOPSIS

use Gtk2::Ex::Dialogs ( destroy_with_parent => TRUE,
modal => TRUE,
no_separator => FALSE );

# do some stuff like creating your apps main $window then,
# to ensure that all messages use the right parent, set it:
Gtk2::Ex::Dialogs->set_parent_window( $window );

# now popup a new dialog
my $r = ask Gtk2::Ex::Dialogs::Question ( "Is Perl only hackers glue?" );
if ( $r ) {
# end-user thinks so
} else {
# end-user does not think so
}

# now popup a new dialog ( blocking the main loop if there is one )
new_and_run
Gtk2::Ex::Dialogs::Message ( title => "Dialog Title",
text => "This is a simple message" );

# now popup a new dialog ( blocking the main loop if there is one )
new_and_run
Gtk2::Ex::Dialogs::ErrorMsg ( "Simple error message." );

This module provides the Gtk2::Ex::Dialogs::Message, Gtk2::Ex::Dialogs::ErrorMsg and Gtk2::Ex::Dialogs::Question classes to the main application while setting the initial defaults to those specified upon using Gtk2::Ex::Dialogs.

Group Shell is a tool to aggregate several remote shells into one. It is used to launch an interactive remote shell on many machines at once. Group Shell is written in Python and requires Python ≥ 2.4.

There is a control shell accessible with Ctrl-C that is used to list some information about the current remote shells. It also allows common terminal manipulations like sending a Ctrl-C, Ctrl-Z, Ctrl-D …

The prompt shows the number of listening shells and the number of active shell. A shell is said to be listening if its prompt has returned and it is accepting commands, active shells are those whose connection is still alive. Shells can be individually enabled and disabled.

Here is the transcript of a sample session:

[g ~/gsh]$ ./gsh.py machine{0-9}

[10/10]> date

machine4: ven nov 10 23:26:36 CET 2006
machine7: ven nov 10 23:26:36 CET 2006
machine3: ven nov 10 23:26:36 CET 2006
machine5: ven nov 10 23:26:36 CET 2006
machine9: ven nov 10 23:26:36 CET 2006
machine0: ven nov 10 23:26:36 CET 2006
machine2: ven nov 10 23:26:36 CET 2006
machine1: ven nov 10 23:26:37 CET 2006
machine6: ven nov 10 23:26:37 CET 2006
machine8: ven nov 10 23:26:37 CET 2006
[10/10]>
Now, Ctrl-C is pressed, it triggers the control shell.
(Cmd) help

Documented commands (type help < topic >):

EOF enable list send_eof set_print_first
continue get_print_first quit send_sigint unset_print_first
disable help reconnect send_sigtstp

(Cmd) list
machine0 fd:3 r:3 w:0 active:True enabled:True idle
machine1 fd:4 r:3 w:0 active:True enabled:True idle
machine2 fd:5 r:3 w:0 active:True enabled:True idle
machine3 fd:6 r:3 w:0 active:True enabled:True idle
machine4 fd:7 r:3 w:0 active:True enabled:True idle
machine5 fd:8 r:3 w:0 active:True enabled:True idle
machine6 fd:9 r:3 w:0 active:True enabled:True idle
machine7 fd:10 r:3 w:0 active:True enabled:True idle
machine8 fd:11 r:3 w:0 active:True enabled:True idle
machine9 fd:12 r:3 w:0 active:True enabled:True idle

10 active shells, 0 dead shells, total: 10
(Cmd) quit
[g ~/gsh]$