Free summer software for linux

PHP began as a quick Perl hack written by Rasmus Lerdorf in 1994.
Over the next two to three years, it evolved into what we today know as PHP/FI 2.0. PHP/FI started to get a lot of users, but things didn`t start flying until Zeev Suraski and Andi Gutmans suddenly came along with a new parser in the summer of 1997, leading to PHP 3.0. PHP 3.0 defined the syntax and semantics used in both versions 3 and 4.

fancylogin is one of the most powerful login programs available for Linux. It can do everything your old login program can do, e.g., handling shadowed passwd files, user-time-terminal/network-verification as done with HP-UX login, etc. The project adds a lot of capabilities for logging logins and support for themes to control the logins look.

History:

I first had the idea of creating a better login for linux, when i was working for IBM in the summer. a really big company had lots of 5250 terminals standing around. OS/400 would allow you (just like fancylogin) to insert an ascii-graphic with colors, etc., so all terminals were showing the companys emblem. this really looked great. so why is it, that one of the best server-systems like linux has such a boring login-screen? even Novell Netware has at least bits of color!

The more i studied popular login-programs, such as Julienne Haughs shadow-login, the more i realized that much more capabilities for security and logging are needed, in order to guarantee a secure system. fancylogin shouldnt only be a a fancy login but also a secure and very functional one. And as everybody who wants to do something on a system must be authenticated by a login, a good login-program is one of the most important keys to a secure and reliable system. fancylogin should be the answer.

The first thing i did was write a litte fancy.o with really weird configuration (the signon.*-files). then i had a look at the sources of the shadow-login-program and included a call to my fancy_prompt-routine. that was all. but as i didnt know anything about that code, i decided to take my fancy.o and write my own login-program around it, because i had a lot of improvements in mind. that was in the christmas-holidays of 1999. after those holiday fancylogin 0.99.5 was out, and the first login program that supported techniques from shadow AND from HP-UX-login (usertty). that was when Andreas Krennmair joined the team. soon we released 0.99.6, and for the first time announced it in c.o.l.a. and on freshmeat.net. on the first day of the release we got 5000 hits, and our school-server had three times the workload it usually had. that was when we put the project on sourceforge.

If i had to give a codename to fancylogin 0.99.7 i would call it "0.99.7 - the great odyssee". first we released some minor patches and fixes in 0.99.6b, but we had great plans for 0.99.7. priority number one was an improved way of configuring everything. then Matthew Wormald wrote an email doing suggestions on fancylogin. one of these were to support ANSI-files, which was the solution of our dilemma. then i worked on support for ANSI-files, but just couldnt get an ANSI-interpreted terminal together with ncurses. after a few months we decided to forget about the ANSIs, because it was too difficult to implement. Andreas Krennmair wrote flted, a program to create signon*- configurations. it should never really be released, because he finally managed to do it. in fancylogin-0.99.7-alpha2 everything was finished already, with fancylogin supporting the signon.defs and two ANSI-files. but i wanted to have everything in one file, so themes could be easily installed, and every theme-related information was in one file. so i decided to put everything into a structure, and wrote fltcreate and the neccessary modifications to fancy.o, and fancylogin-0.99.7 was finished. the first fancylogin a normal human could actually configure and write themes for!

CQL::Parser is a Perl module that compiles CQL strings into parse trees of Node subtypes.

SYNOPSIS

use CQL::Parser;
my $parser = CQL::Parser->new();
my $root = $parser->parse( $cql );

CQL::Parser provides a mechanism to parse Common Query Language (CQL) statements. The best description of CQL comes from the CQL homepage at the Library of Congress http://www.loc.gov/z3950/agency/zing/cql/

CQL is a formal language for representing queries to information retrieval systems such as web indexes, bibliographic catalogs and museum collection information. The CQL design objective is that queries be human readable and human writable, and that the language be intuitive while maintaining the expressiveness of more complex languages.

A CQL statement can be as simple as a single keyword, or as complicated as a set of compoenents indicating search indexes, relations, relational modifiers, proximity clauses and boolean logic. CQL::Parser will parse CQL statements and return the root node for a tree of nodes which describes the CQL statement. This data structure can then be used by a client application to analyze the statement, and possibly turn it into a query for a local repository.

Each CQL component in the tree inherits from CQL::Node and can be one of the following: CQL::AndNode, CQL::NotNode, CQL::OrNode, CQL::ProxNode, CQL::TermNode, CQL::PrefixNode. See the documentation for those modules for their respective APIs.

Here are some examples of CQL statements:

george
dc.creator=george
dc.creator="George Clinton"
clinton and funk
clinton and parliament and funk
(clinton or bootsy) and funk
dc.creator="clinton" and dc.date="1976"

SBackup is a simple backup solution intended for desktop use. SBackup can back up any subset of files and directories. Exclusions can be defined by regular expressions. A maximum individual file size limit can be defined. Backups may be saved to any local and remote directories that are supported by gnome-vfs.
This software is written withing Google Summer of Code 2005 for use in Ubuntu GNU/Linux distribution.
To use.
- Install python and python-gnome2 libraries.
- Run make install in the same directory as this README file
- Run simple-backup-config to configure your backup configuration.
Do not forget to save the configuration.
- Run simple-restore-gnome to upgrade existing backups to new format
If you do not run a Debian derrived distribution then you can comment out lines that backup the list of installed packages on a Debian system. An authomatic test will be added soon, but the lack of dpkg command shouldnt raise an exception there.
srestore.py is a command line restore tool and simple-restore-gnome is a Gnome equivalent.
Enhancements:
- This version fixes most of the bugs that have been found in the 0.10 branch without adding extra features unless required by the bugs in question.
- This is suitable for stable production environments.

Inkscape is an open source SVG editor with capabilities similar to Illustrator, CorelDraw, Visio, etc. Supported SVG features include basic shapes, paths, text, alpha blending, transforms, gradients, node editing, svg-to-png export, grouping, and more.
Inkscapes main motivation is to provide the Open Source community with a fully XML, SVG, and CSS2 compliant SVG drawing tool.
Additional planned work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and establishment of a friendly, open, community-oriented development processes.
Enhancements:
- Patch [ 1667939 ]: fix crash when tile-tracing with too small clones
- Patch [ 1666532 ]: Broken link in inkview man page
- Patch [ 1665447 ]: fix for the blur quantization bug 1617082
- Patch [ 1664849 ]: fix for 1662589: increase blur margins
- Patch [ 1664004 ]: embedimage.py with fixed search order
- Patch [ 1662649 ]: markers.svg with reversed order
- Crudely improve check-markup for { markup, fix translations with bugs in that area (dz and zh_TW).
- Patch [ 1659404 ]: Set locale directory from environment variable
- Patch [ 1657072 ]: fix for bug 1654495
- Patch [ 1654636 ]: defocus dropper checkboxes
- Adding japanese.nsh and russian.nsh into files that should go into the release tarball
- Correct russian translation
- Patch [ 1651797 ]: fix for attributes when saving/save-a-copy
- Patch [ 1651752 ]: fix dropper tool
- Pattern along path extension fixed on Windows
- Include libtiff3.dll in the Windows distribution, fixing crash when opening TIFF files
- Patch [ 1673067 ]: fix blur export on flowtext
- Patch [ 1678075 ]: fix FontInstance.cpp compile issue
- Patch [ 1673502 ]: fix broken Envelope (Summers Night) effect
- Patch [ 1680182 ]: fix pattern inversion on bool op (bug 1659445)
- Patch [ 1681754 ]: fix crash when editing text with multiple tspans
- Patch [ 1682425 ]: fix bug 1679477 (crash exporting gradients to ODG)
- Khmer translation now installs correctly
- Updated Slovak translation
- Updated Bulgarian translation
- Updated Catalan translation
- Updated Czech translation
- Security: fixed format string overflows in dialogs (CVE-2007-1463) and whiteboard Jabber protocol (CVE-2007-1464).

rdiff-backup-web is a web front-end to rdiff-backup, a command-line incremental backup application written by Ben Escoto.
The main web interface of rdiff-backup-web is written in php with a mysql backend. The backups are actually run using a command line perl script that can be set up as a cron job. The application was originally written to do a specific task at the company I work for, but it turns out that it might be handy to other people.
This is currently ALPHA quality software.
Enhancements:
- Now you can use SSH connections, if you follow Dean Gaudets instructions for unattended rdiff-backup here.
- Also, an unexpected bonus of adding the SSH backup type (well, unexpected to me, anyway) has been to allow local backups. Just set the "Path to Orig Files" to be /path
- Files and directories are listed using a tree-style view, rather than a big list of files.
- You can deactivate a backup with a single click, but it remains in the system to be reactivated with a similar, singular, click.
- You can now back up to a different location than the default, simply by using a leading / in the backup location field (useful for backing up to a mounted USB drive, etc).
- There is now one required perl module, PHP::Include by Ed Summers, which can be downloaded and installed using CPAN (instructions in the readme).
- Oh, and unlike the previous release, this might actually work

Java::Import::Design is the design of the Java::Import Module.

MOTIVATIONS

The original motivation for writing this module came out of a project I was working on during my previous employment. We had built a system in which a major part was implimented using EJBs on a J2EE server. In addition, we had a large component of the system, that already existed, and was written in Perl. We did not want to scrap our Perl work but it was becoming more tedious to maintain two implimentations as more and more things were being added to the system.

So, we decided that the major pieces of business logic would reside on the J2EE server and the Perl would be modified to make calls to the server. After some time and experimentation we began to realize that the memory footprint as well as the amount of time needed to make calls to the server using existing Perl to Java integration sulutions were just not acceptable. We therefore set out to find some other way. We tried all sorts of things but in the end we couldnt find anything that met our requirements and therefore decided to keep the origional system of doing things.

While at that job we never did find a suitable way to integrate our two systems. However, the problem still haunted me. It wasnt until the end of my career at that company that I saw an announcement for Googles first Summer of Code. It just so happened that as Google was announcing their brand new program that I had begun to play with the GNU GCJ suite of Java tools and came up with the idea of taking advantage of their ability to natively compile Java code for use with Perl. This may not have been a new idea but I couldnt find anything that would help me so I decided to write and submit a proposal to Google. Well, I was accepted and you now have Java::Import.

When I began to work on this project I started by creating my own namespace instead of stepping on the toes of the other existing Java/Perl integration project, Inline::Java. I did this primarily because I wanted a clean slate on which I could fully explore the nuances of GCJ, in particular its CNI interface. As I worked my module started to evolve into its own beast and at that point it seemed locigal to keep my own namespace. It is not my intention to replace Inline::Java and I still think that in te future much of the work I have done can be used by Inline::Java as an option to use GCJ specific functionality.

Template::Tutorial::Datafile is a Perl module for creating Data Output Files Using the Template Toolkit.

This tutorial gives an overview of the Template Toolkit, showing in particular how to use it to read and write data files in various different formats and styles. It was written by Dave Cross and first appeared as a lead article at http://www.perl.com/ earlier in the year (2001).

Introducing the Template Toolkit

There are a number of Perl modules that are universally recognised as The Right Thing To Use for certain tasks. If you accessed a database without using DBI, pulled data from the WWW without using one of the LWP modules or parsed XML without using XML::Parser or one of its subclasses then youd run the risk of being shunned by polite Perl society.

I believe that the year 2000 saw the emergence of another must have Perl module - the Template Toolkit. I dont think Im alone in this belief as the Template Toolkit won the Best New Module award at the Perl Conference last summer. Version 2.0 of the Template Toolkit (known as TT2 to its friends) was recently released to the CPAN.

TT2 was designed and written by Andy Wardley. It was born out of Andys previous templating module, Text::Metatext, in best Fred Brooks plan to throw one away manner; and aims to be the most useful (or, at least, the most used) Perl templating system.

TT2 provides a way to take a file of fixed boilerplate text (the template) and embed variable data within it. One obvious use of this is in the creation of dynamic web pages and this is where a lot of the attention that TT2 has received has been focussed. In this article, I hope to demonstrate that TT2 is just as useful in non-web applications.