Free accidental file deletion software for linux

C Comic Collection project is a GTK application for downloading, cataloging, and viewing Web comics. It uses a MySQL database.
To compile this software, just type "make".
It requires development libraries for gtk, gtk_imlib, cURL, mysql and pthreads. If youre on Linux these should come with your distrobution; I dunno for other OS. If you only have the runtimes and are using a 386 derivative (Pentium et al) you can get a binary from http://c-comiccollect.sourceforge.net.
Compilation will produce a binary called "gtk-cc"; copy this to your /usr/bin (youll need root privileges, copy to your ~/bin (you wont) or just run it from where it is (./gtk-cc &).
You can populate the database by running the included "comiccollection.sql" against an empty database. (mysql -u < username > < dbname > < comiccollection.sql). It even includes some comics to get you started!
Enhancements:
- Minor improvements - only really relevant if you view KeenSpace comics.
- Fixed file non-deletion problem
- Fixed KeenSpace file download problem

Postfix SMTP Monitoring Solution is a set of three Perl CGI scripts used to monitor the SMTP queue, allowing the deletion of messages that for one reason or another become "stuck" in the queue.

I needed a web-based solution to monitor my Postfix SMTP relay, which enabled me to remove messages that become "stuck" in the queue. I wrote three simple Perl scripts, and used Sudo to give me the desired functionality.

I am uploading these scripts in case they are useful to others. Assuming you have Apache configured correctly on your Postfix server, it should be as easy as placing the three .cgi files into your webservers cgi-bin directory, and making the appropriate modifications to your /etc/sudoers file (see the README contained in the tarball).

Class::StrongSingleton is a stronger and more secure Singleton base class.

SYNOPSIS

package My::Singleton::Class;

use base qw(Class::StrongSingleton);

sub new {
my ($class, %my_params) = @_;
# create our object instance
my $instance = { %my_params };
bless($instance, $class);
# and initialize it as a singleton
$instance->_init_StrongSingleton();
return $instance;
}

1;

# later in your code ...

# create the first instance of our class
my $instance = My::Singleton::Class->new(param => "value");

# try to create a new one again, and
# you end up with the same instance, not
# a new one
my $instance2 = My::Singleton::Class->new(param => "other value");

# calling instance returns the singleton
# instance expected
my $instance3 = My::Singleton::Class->instance();

# although rarely needed, if you have to
# you can destroy the singleton

# either through the instance
$instance->DESTROY();
# or through the class
My::Singleton::Class->DESTROY();

# of course, this is assuming you
# did not override DESTORY yourself

# Also calling instance before calling new
# will returns a new singleton instance
my $instance = My::Singleton::Class->instance();

This module is an alternative to Class::Singleton and Class::WeakSingleton, and provides a more secure Singleton class in that it takes steps to prevent the possibility of accidental creation of multiple instances and/or the overwriting of existsing Singleton instances. For a detailed comparison please see the "SEE ALSO" section.

Here is a description of how it all works. First, the user creates the first Singleton instance of the class in the normal way.

my $obj = My::Singleton::Class->new("variable", "parameter");

This instance is then stored inside a lexically scoped variable within the Class::StrongSingleton package. This prevents the variable from being accessed by anything but methods from the Class::StrongSingleton package. At this point as well, the new method to the class is overridden so that it will always return the Singleton instance. This prevents any accidental overwriting of the Singleton instance. This means that any of the follow lines of code all produce the same instance:

my $instance = $obj->instance();
my $instance = My::Singleton::Class->instance();
my $instance = $obj->new();
my $instance = My::Singleton::Class->new();

Personally, I see this an an improvement over the usual Gang of Four style Singletons which discourages the use of the new method entirely. Through this method, a user can be able to use the Singleton class in a normal way, not having to know its actually a Singleton. This can be handy if your design changes and you no longer need the class as a Singleton.

File::Repl is a Perl module that provides file replication utilities.

SYNOPSIS

use File::Repl;

%con = {
dira => C:/perl,
dirb => M:/perl,
verbose => 1,
age => 10,
};

$ref=File::Repl->New(%con);
$r1 = $ref->Update(.p(l|m),ab,1);
$r2 = $ref->Update(.t.*,ab,1,.tmp$);

The File:Repl provides simple file replication and management utilities. Its main functions are

File Replication

Allowing two directory structures to be maintained, ensuring files that meet selection logic criteria are mirrored and otherwise synchronized.

Bulk Renaming

Allowing files in a directory structure to be renamed according to the selection logic.

Compressing

Allowing files in a directory structure to be compressed according to a given logic.

Process

Run a common perl process against files in a directory structure according to selection logic.

Deletion

Allowing files in a directory structure to be deleted according to the selection logic.

Major Features:

1. Management of Unix user and group accounts (posixAccount/posixGroup)
2. Management of Samba 2.x/3 user and host accounts (sambaAccount/sambaSamAccount)
3. Mnagement of Kolab 2 accounts (kolabInetorgPerson)
4. Scalix
5. Profiles for account creation
6. Account creation via file upload
7. Automatic creation/deletion of home directories
8. Setting quotas
9. PDF output for all accounts
10. Editor for organizational units (OU)
11. schema browser
12. Tree view
13. Multiple configuration files
14. Multi-language support (Catalan, Chinese (Traditional + Simplified), Czech, Dutch, English, French, German, Hungarian, Italian, Japanese, Polish, Portuguese, Russian and Spanish)
15. Support for LDAP+SSL/TLS

Enhancements:

• Support NIS netgroups
• Support EDU person accounts (RFE 1413731)
• Personal: support departmentNumber attribute
• DHCP: allow file upload
• Added config option to search LAM login users in LDAP (RFE 2494249)
• Help messages are displayed as tooltips

The Introspector enables the programming tools that deal with source code such as the compiler to communicate in a standard and neutral manner reducing the accidental cost of programming.

Like a telephone switchboard connects many parties who might wish to talk to each other, the Introspector allows multiple consumers and producers of data about software to quickly and painlessly transfer information to each other.

This data about software, or meta-data is read and written in and out of existing software tools via a standardized plug-in interface. Each producer has its own flavour of data and format of data that it stores about your software, and the introspector allows for each software to speak its native language.

The Introspector plug ins act analogous to network cards in an ethernet allowing for broadcasting of the meta-data to the network of consumers.

The usage of RDF or Resources Description Format as the underlying representation is of essential importance. RDF is the foundation of the next generation of the internet, the Semantic Web where hypertext links is replaced by meaningful references to resources of type and quality.

The introspector uses the excellent Redland RDF Application Framework for parsing/serializing, storing/retrieving and querying/traversing the RDF data. The Berkley DB storage mechanism provides an efficent indexing system, and the SWIG Simplified Wrapper Interface Generator provides native langauge interfaces for all major programming systems.

The GCC interface uses Redland to create repositories of data that can be processed by any tool needed. Experiments have been made with compiling this graph data into arrays, so called "ICE Cubes" that can be traversed even quicker than the redland database.

This new technology when available will be able to be used from the same introspector API that gives access to Redland.

QDevelop project is a development environment entirely dedicated to Qt4.
QDevelop requires Qt4, gcc under Linux or MinGW under Windows, possibly gdb for programs debugging and ctags for code completion.
QDevelop is available in English, French, German, Dutch, Polish, Spanish, Chinese, Russian and Italian. If you want to translate in your language, please contact me.
QDevelop is not a Kdevelop like or reduced. Its an independent IDE dedicated to Qt and is totally independent of KDevelop. Less complete, but faster, light and especially multi-platforms. QDevelop and KDevelop have different code sources.
Main features:
- Cross Platform: Supports Linux, Windows 2000/XP/Vista, Mac OS X and FreeBSD
- Reading and writing project files (with some small restrictions)
- Add / Delete and edit project files (or external files)
- Management of normal projects and project SUBDIRS.
- Independent build for each projects. I.e. are rebuild only the really modified projects.
- A powerful editor with code completion, syntax highligthing, bookmarks, auto-brackets, auto-indentation, auto-save before build, line numbers and selection margin.
- A class browser who allows the programmer to browse, navigate, or visualize the structure of classes, members and functions of projects.
- In the event of errors or warnings of compilation, double-click on the line opens the corresponding editor.
- Debugging with gdb. Toggle breakpoints by click in the line number on editor or by right click. When the program is stopped on breakpoint, the local variables are automatically showed on output dock.
- In the editor, F1 call Assistant to show help for the word under the cursor.
- Open Source
- Its Free!
Enhancements:
Name:
- QIde becomes QDevelop at October 4, 2006
Corrections:
- A crash if a file is opened without project
- Bug in classes explorer when a sub-project have a name identical of the main project.
- Deletion of Auto-Hide docks, not working with Qt 4.2
- The settings are now written in qdevelop.ini file in the user home directory.
- The database of project is named "qdevelop-settings.db" in project directory.
- New C++ highlighter
Adds:
- The Default projects directory can be set in options dialog.
- Bookmarks. Bookmarks can be toggled on menu bar and by right-click in margin number or editor.
- Add "Next Bookmark" and "Previous Bookmark" to menu Bookmark.
- Add Bookmarks toolbar.
- Save bookmarks and breakpoints in project settings
- Add "console" to CONFIG variable in (.pro) file for new projects to have qDebug() written on debug console under Windows.
- Modification of the class browser to understand functions overloading.
- When a project is closed, the content of class browser is saved in database project.db. With this database, the content is reloaded very quickly during the loading of the project. This feature require to have the SQL driver sqlite enable. On build enter the option -qt-sql-sqlite after the configure command.
- Moving tabs with mouse to switch between us
- Detection when a file was modified by another program and ask for save or reload.
- Two tabs to show debugged variables program. Deletion of line edit "Debug command", obsolete with new tabs.
- Templates to create a project (based on dialog or main window).
- The code completion list contains the name and signature of functions.
- Entries "Close Other Tabs" and "Close All Tabs" in popup menu showed by right-click on editor Tab.
- Add Polish, Spanish, Chinese and Russian translations
- The application can be build using cmake (experimental!)