cheap airline tickets
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 150
PHP Trouble Ticket 1.4
PHP Trouble Ticket project provides a centralized means of problem reporting and tracking. more>>
PHP Trouble Ticket project provides a centralized means of problem reporting and tracking in multi-user environments (medium to large companies, development groups, etc.).
It helps direct problem reports to the responsible administrator(s), keeps track of the status of a problem being worked on, and offers an up-to-date list of recent changes applied. It aims to be widely configurable, easy-to-use even for those not technically inclined, and multi-language capable.
Main features:
- problem reporting
- submitting update-info
- email-notification of administrators
- email-notification sent to problem reporter after ticket is modified or closed
- watch-function for tickets to be kept up to date on progress of chosen tickets
- file attachments (including on-the-fly virus checking with external virus-scanner)
- powerful list/search function with paged browsing
- tickets can be set into relations/dependencies
- ticket quick-search function directly from the main index
- quickly access all your own tickets from the main index page
- printer-friendly display of lists and ticket details
- css style sheet support for easy customisation
- easy multiple-select/close/delete functions
- username/password protected logins
- varying levels of permissions/access-rights
- the scope of unprivileged users can be limited to their own tickets
- new users can either sign up at the login page or be created by the superuser from the administration page
- detailed userlist available for administrators with info on last login and included search function
- online configuration of all major options
- configuration of the expert/administrator information
- deadlines for trouble tickets
- up to five customizable datafields
- changes and entire tickets can be hidden from unprivileged users by the operators
- "locking" areas against change by other administrators
- national language support (included: english, german. Other language files are made available separately on the download page)
- date/Time format configurable to suit national format
- ability of the program to work with PHPs "safe mode" and "open basedir" security mechanisms
<<lessIt helps direct problem reports to the responsible administrator(s), keeps track of the status of a problem being worked on, and offers an up-to-date list of recent changes applied. It aims to be widely configurable, easy-to-use even for those not technically inclined, and multi-language capable.
Main features:
- problem reporting
- submitting update-info
- email-notification of administrators
- email-notification sent to problem reporter after ticket is modified or closed
- watch-function for tickets to be kept up to date on progress of chosen tickets
- file attachments (including on-the-fly virus checking with external virus-scanner)
- powerful list/search function with paged browsing
- tickets can be set into relations/dependencies
- ticket quick-search function directly from the main index
- quickly access all your own tickets from the main index page
- printer-friendly display of lists and ticket details
- css style sheet support for easy customisation
- easy multiple-select/close/delete functions
- username/password protected logins
- varying levels of permissions/access-rights
- the scope of unprivileged users can be limited to their own tickets
- new users can either sign up at the login page or be created by the superuser from the administration page
- detailed userlist available for administrators with info on last login and included search function
- online configuration of all major options
- configuration of the expert/administrator information
- deadlines for trouble tickets
- up to five customizable datafields
- changes and entire tickets can be hidden from unprivileged users by the operators
- "locking" areas against change by other administrators
- national language support (included: english, german. Other language files are made available separately on the download page)
- date/Time format configurable to suit national format
- ability of the program to work with PHPs "safe mode" and "open basedir" security mechanisms
Download (MB)
Added: 2007-04-26 License: GPL (GNU General Public License) Price:
558 downloads
PHP Ticket 0.71
PHP Ticket is a PHP and MySQL based ticketing system. more>>
phpticket is a ticketing system written in PHP, backed up by a MySQL database. Its purpose is to provide helpdesks/staffs with an easy "to do" application for keeping track of what needs to be done.
The interface is kept fairly simple and easy to use. The code is licensed under GPL.
<<lessThe interface is kept fairly simple and easy to use. The code is licensed under GPL.
Download (0.036MB)
Added: 2005-05-05 License: GPL (GNU General Public License) Price:
1646 downloads
Bluetail Ticket Tracker 4.0.2
Bluetail Ticket Tracker is a workflow management tool. more>>
The Bluetail Ticket Tracker (BTT) is a system for creating, storing and keeping track of tickets. A ticket describes an issue of some sort.
It can, for example, be a Trouble Report or a ToDo note. It is available for use (and distribution) under the GNU Public License.
The users of BTT are divided in four different user categories: Staff, Friend, Customer and Anonymous. The access to the data stored in BTT can be tailored for the Friend, Customer and Anonymous groups, while the Staff group has full access rights. This (hopefully) allows BTT to be used both for Open Source Projects as well as in more commercial settings.
In an Open Source Project:
* one or several people (Staff) hosts a site which runs the Ticket handling for a certain application
* a number of people (Staff + Friends) collaborates in the development which also include Ticket handling
* anyone else interested (Customer or Anonymous) may want to check the status of the Tickets (e.g Trouble Reports)
In a commercial setting:
* a company (Staff) runs the Ticket tracker as an aid in their product development.
* the company may be spread geographically or may have development partners (Friends)
* the customers can report problems and track the progression (Customer)
A ticket consists of a number of fields, e.g denoting a release name, component name, responsible person, staus, priority, etc. The actual field values is defined by the Staff when the Bluetail Ticket Tracker is setup. The daily operation of BTT includes creation, editing, searching and viewing of tickets.
The users can also activate the mail alert function which will send a mail to the user when, for example, a new ticket as been assigned to the user.
BTT can also store information about customers which can be useful in a support desk scenario. This makes it possible to connect a ticket with a particular customer. It is also helpful in a support desk scenario where the support engineer quickly need to find information about a customer.
BTT can also store more general information. This Knowledge Base consists of a mail store and a information store.
The mail store makes it possible to retrieve mails (from a POP3 account) and store it locally in a BTT directory. Stored mails can then be searched, viewed and turned into tickets.
The information store is divided in two parts, one external (for users/customers) and one internal (for staff/friends). The external area can for example be used for creating a FAQ (Frequently Asked Question), a HOWTO area. The internal knowledge base is intended for the Staff and/or Friends, and may for example store information such as address lists, how to fill in the expenses form, or contain description of the work process, etc.
Currently BTT supports English, French, German, Spanish and Galician. Adding new languages is easy, one language definition file has to be created with a translation of all text that can be displayed. (If you do this, make sure to send the new language file to the maintainers so that it can be incorporated into the standard release).
Tickets can also be retrieved and stored via a Unix command line interface.
<<lessIt can, for example, be a Trouble Report or a ToDo note. It is available for use (and distribution) under the GNU Public License.
The users of BTT are divided in four different user categories: Staff, Friend, Customer and Anonymous. The access to the data stored in BTT can be tailored for the Friend, Customer and Anonymous groups, while the Staff group has full access rights. This (hopefully) allows BTT to be used both for Open Source Projects as well as in more commercial settings.
In an Open Source Project:
* one or several people (Staff) hosts a site which runs the Ticket handling for a certain application
* a number of people (Staff + Friends) collaborates in the development which also include Ticket handling
* anyone else interested (Customer or Anonymous) may want to check the status of the Tickets (e.g Trouble Reports)
In a commercial setting:
* a company (Staff) runs the Ticket tracker as an aid in their product development.
* the company may be spread geographically or may have development partners (Friends)
* the customers can report problems and track the progression (Customer)
A ticket consists of a number of fields, e.g denoting a release name, component name, responsible person, staus, priority, etc. The actual field values is defined by the Staff when the Bluetail Ticket Tracker is setup. The daily operation of BTT includes creation, editing, searching and viewing of tickets.
The users can also activate the mail alert function which will send a mail to the user when, for example, a new ticket as been assigned to the user.
BTT can also store information about customers which can be useful in a support desk scenario. This makes it possible to connect a ticket with a particular customer. It is also helpful in a support desk scenario where the support engineer quickly need to find information about a customer.
BTT can also store more general information. This Knowledge Base consists of a mail store and a information store.
The mail store makes it possible to retrieve mails (from a POP3 account) and store it locally in a BTT directory. Stored mails can then be searched, viewed and turned into tickets.
The information store is divided in two parts, one external (for users/customers) and one internal (for staff/friends). The external area can for example be used for creating a FAQ (Frequently Asked Question), a HOWTO area. The internal knowledge base is intended for the Staff and/or Friends, and may for example store information such as address lists, how to fill in the expenses form, or contain description of the work process, etc.
Currently BTT supports English, French, German, Spanish and Galician. Adding new languages is easy, one language definition file has to be created with a translation of all text that can be displayed. (If you do this, make sure to send the new language file to the maintainers so that it can be incorporated into the standard release).
Tickets can also be retrieved and stored via a Unix command line interface.
Download (0.21MB)
Added: 2005-04-22 License: GPL (GNU General Public License) Price:
1645 downloads
EZ-Ticket 0.01
EZ-Ticket provides a multi-user, Web-based ticket/issue tracking system. more>>
EZ-Ticket provides a multi-user, Web-based ticket/issue tracking system.
EZ-Ticket is a Web-based ticket tracking system, built with simplicity in mind. Unlike other ticket systems, this ticket system has the same functionality that other ticket systems have, without all the complexity, making its use efficient and effective.
INSTALL:
-Unpack the tar file in your document root
-Make sure php is enabled
-use a web browser to hit doc root of the ezt-#.#.# dir. This will start the installer
-follow the installer instructions
-remove the install/ directory
Enhancements:
- cleaned up skin includes
- finished installer
- created basic readme
- cut initial release 0.01
- Implimented e-paging system
- got exporing to work (CSV)
- sticky/announce tickets working
- ticket escalations implimented
- Ported to arrays for selection queries, this allows multiple owners, priorities, etc to be selected
- Implimented "next page" links
- MANY other things
- cleaned up profile.php and added hooks for adding users
- added checks so regular users cant reopen tickets (only admins)
- added sticky ticket support (old PTR announce feature, but a little different)
<<lessEZ-Ticket is a Web-based ticket tracking system, built with simplicity in mind. Unlike other ticket systems, this ticket system has the same functionality that other ticket systems have, without all the complexity, making its use efficient and effective.
INSTALL:
-Unpack the tar file in your document root
-Make sure php is enabled
-use a web browser to hit doc root of the ezt-#.#.# dir. This will start the installer
-follow the installer instructions
-remove the install/ directory
Enhancements:
- cleaned up skin includes
- finished installer
- created basic readme
- cut initial release 0.01
- Implimented e-paging system
- got exporing to work (CSV)
- sticky/announce tickets working
- ticket escalations implimented
- Ported to arrays for selection queries, this allows multiple owners, priorities, etc to be selected
- Implimented "next page" links
- MANY other things
- cleaned up profile.php and added hooks for adding users
- added checks so regular users cant reopen tickets (only admins)
- added sticky ticket support (old PTR announce feature, but a little different)
Download (0.54MB)
Added: 2007-02-14 License: GPL (GNU General Public License) Price:
590 downloads
easy TicketManager 0.2.0
easy TicketManager is a system for managing customer requests (trouble tickets or similar) for a group of users. more>>
easy TicketManager project is a system for managing customer requests (trouble tickets or similar) for a group of users.
Each ticket is assigned to a customer and a carer who is responsible for handling this ticket. Tickets can be organized in folders or by categories and can have notes attached to them.
Enhancements:
- You can manage tickets and define a workflow to handle these items.
- The installer has been improved, as well as the plugin concept.
- The following plugins are shipped and installed automatically: notes management, bookmarks management, and the ticket plugin.
<<lessEach ticket is assigned to a customer and a carer who is responsible for handling this ticket. Tickets can be organized in folders or by categories and can have notes attached to them.
Enhancements:
- You can manage tickets and define a workflow to handle these items.
- The installer has been improved, as well as the plugin concept.
- The following plugins are shipped and installed automatically: notes management, bookmarks management, and the ticket plugin.
Download (4.8MB)
Added: 2006-08-15 License: MPL (Mozilla Public License) Price:
1166 downloads
dl Download Ticket Service 0.1
dl Download Ticket Service project is a minimalist and rough download ticket service with automatic expiration, written in PHP. more>>
dl Download Ticket Service project is a minimalist and rough download ticket service with automatic expiration, written in PHP. Ive been using this service as an email-attachment replacement for my company, but there are no plans on extending it. It will remain minimal: no fancy features, just bug fixes.
Installation:
Copy the "htdocs" directory to a directory of choice under your web server. Configure the needed parameters inside "include/config.php" to reflect the external url, main password, etc. The "include" directory must not be accessible: if you use apache, the included .htaccess file should be sufficient; consult your web server documentation otherwise.
A spool directory outside of the web server root must be accessible to the web server process. In the example "include/config.php" this is configured as "/var/spool/dl". If you web server runs as "nobody:nogroup", issue:
mkdir -p -m770 /var/spool/dl
chgrp nogroup /var/spool/dl
to create correctly this directory.
The maximal upload limit is determined by several PHP configuration parameters:
file_uploads: must be "On".
upload_tmp_dir: ensure enough space is available.
upload_max_filesize: change as needed.
post_max_size: must be at least 1M larger than upload_max_filesize.
The upload limit as shown in the submission form is determined automatically from the upload_max_filesize parameter. You can also set these parameters with ini_set() inside "include/config.php" or through apaches directives to localize them to the installation path.
There are several bugs in the dba_open() function in PHP 4.x which cannot be fixed. If you can, upgrade PHP to at least 4.3.5. If you cannot upgrade, you need to configure the "$dbHandler" parameter to something available to your PHP installation (usually db3/db2/dbm) and use the Berkeleys DB "db4_load" utility to create an empty database:
echo | db4_load /var/spool/dl/data.db
echo | db4_load /var/spool/dl/user.db
chmod 770 /var/spool/dl/*.db
chgrp nogroup /var/spool/dl/*.db
Depending on your system, you may have to use "db3_load/db2_load/etc" instead of "db4_load". Sometimes these utilities are part of "db*-util" packages under several linux distributions. If you have PHP 4.3.5 or greater, this is done automatically.
Ticket expiration is performed automatically when any web page is requested. This means that expired downloads will still occupy space on the spool directory until a web page is first serviced. If you need to ensure that the spool is purged regularly (for very low traffic servers), setup a scheduled job that requests the "http://dl.example.com/d/" page. Under UNIX, setup a cron entry like this:
0 0 * * * wget -q -O /dev/null "http://dl.example.com/d/" > /dev/null
Version restrictions:
- Tested with all mayor and minor browsers.
- Tested with PHP 4.2/4.3.
- Byte ranges are currently not supported.
- The submit button is not disabled correctly with Internet Explorer 6 (works on other graphical browsers however).
<<lessInstallation:
Copy the "htdocs" directory to a directory of choice under your web server. Configure the needed parameters inside "include/config.php" to reflect the external url, main password, etc. The "include" directory must not be accessible: if you use apache, the included .htaccess file should be sufficient; consult your web server documentation otherwise.
A spool directory outside of the web server root must be accessible to the web server process. In the example "include/config.php" this is configured as "/var/spool/dl". If you web server runs as "nobody:nogroup", issue:
mkdir -p -m770 /var/spool/dl
chgrp nogroup /var/spool/dl
to create correctly this directory.
The maximal upload limit is determined by several PHP configuration parameters:
file_uploads: must be "On".
upload_tmp_dir: ensure enough space is available.
upload_max_filesize: change as needed.
post_max_size: must be at least 1M larger than upload_max_filesize.
The upload limit as shown in the submission form is determined automatically from the upload_max_filesize parameter. You can also set these parameters with ini_set() inside "include/config.php" or through apaches directives to localize them to the installation path.
There are several bugs in the dba_open() function in PHP 4.x which cannot be fixed. If you can, upgrade PHP to at least 4.3.5. If you cannot upgrade, you need to configure the "$dbHandler" parameter to something available to your PHP installation (usually db3/db2/dbm) and use the Berkeleys DB "db4_load" utility to create an empty database:
echo | db4_load /var/spool/dl/data.db
echo | db4_load /var/spool/dl/user.db
chmod 770 /var/spool/dl/*.db
chgrp nogroup /var/spool/dl/*.db
Depending on your system, you may have to use "db3_load/db2_load/etc" instead of "db4_load". Sometimes these utilities are part of "db*-util" packages under several linux distributions. If you have PHP 4.3.5 or greater, this is done automatically.
Ticket expiration is performed automatically when any web page is requested. This means that expired downloads will still occupy space on the spool directory until a web page is first serviced. If you need to ensure that the spool is purged regularly (for very low traffic servers), setup a scheduled job that requests the "http://dl.example.com/d/" page. Under UNIX, setup a cron entry like this:
0 0 * * * wget -q -O /dev/null "http://dl.example.com/d/" > /dev/null
Version restrictions:
- Tested with all mayor and minor browsers.
- Tested with PHP 4.2/4.3.
- Byte ranges are currently not supported.
- The submit button is not disabled correctly with Internet Explorer 6 (works on other graphical browsers however).
Download (0.010MB)
Added: 2007-06-18 License: BSD License Price:
861 downloads
Rubicon Tracker 2.0.6
Rubicon Tracker is web-based trouble tracking system. more>>
Rubicon Tracker is a Ticket/Issue Tracking System written in C++ using an SQL backend to store and save all ticket information and history.
Tracker is a Web based system. All interaction occurs through a regular Web Browser. Tracker can be used for Bug Tracking, Phone/Help Desk Support, or any other process that requires tracking of items through phases.
Main features:
Issue Tracking from Majentis
- Rubicon Tracker is a Web based system for tracking and managing Defects and Issues in a project or muliple projects. Rubicon Tracker shares information among team members, clients, and management, offering an end-to-end Issue Managment solution.
Web Based
- Rubicon Trackers Web based format allows your team, clients, and management to collaborate from anywhere. Rubicon Tracker requires no Web Server to run, setup, or maintain. Rubicon Tracker is its own Web Server, geared specifically for this application, allowing speedy responses even under heavy loads.
Email Notification
- Keep all team members in the loop using instant notification by email when an issue (we call them tickets) is added or modified in any way. When a ticket is added, email is sent to all Project Managers registered with that project. Once the Project Manager decides who is best suited to work on a ticket, the person assigned is sent an email notifying them that they have a ticket. All modifications to the ticket will will generate email for all persona invlolved.
Move Tickets
- If a ticket is inadvertently added to the wrong project, a Project Manager can move the ticket to any other project the Project Manager has access to.
Online or Self-Hosted
- Majentis offers you two solutions for Issue Tracking. You can install and maintain Rubicon Tracker on your own servers, or you can use our on-line system, outsourcing your Issue Tracking needs.
<<lessTracker is a Web based system. All interaction occurs through a regular Web Browser. Tracker can be used for Bug Tracking, Phone/Help Desk Support, or any other process that requires tracking of items through phases.
Main features:
Issue Tracking from Majentis
- Rubicon Tracker is a Web based system for tracking and managing Defects and Issues in a project or muliple projects. Rubicon Tracker shares information among team members, clients, and management, offering an end-to-end Issue Managment solution.
Web Based
- Rubicon Trackers Web based format allows your team, clients, and management to collaborate from anywhere. Rubicon Tracker requires no Web Server to run, setup, or maintain. Rubicon Tracker is its own Web Server, geared specifically for this application, allowing speedy responses even under heavy loads.
Email Notification
- Keep all team members in the loop using instant notification by email when an issue (we call them tickets) is added or modified in any way. When a ticket is added, email is sent to all Project Managers registered with that project. Once the Project Manager decides who is best suited to work on a ticket, the person assigned is sent an email notifying them that they have a ticket. All modifications to the ticket will will generate email for all persona invlolved.
Move Tickets
- If a ticket is inadvertently added to the wrong project, a Project Manager can move the ticket to any other project the Project Manager has access to.
Online or Self-Hosted
- Majentis offers you two solutions for Issue Tracking. You can install and maintain Rubicon Tracker on your own servers, or you can use our on-line system, outsourcing your Issue Tracking needs.
Download (0.36MB)
Added: 2005-04-22 License: Free for non-commercial use Price: $250
1646 downloads

Skype for Linux SuSE 1.2
Skype Linux SuSE allows you to make calls from your computer. more>> Skype is a little piece of software that allows you to make calls from your computer. Talk for as long as you like without worrying about the cost or the distance.
Free Skype-to-Skype calls
Make video calls
Send cheap text messages
Easy conference calling
Free to download
Skype is a little piece of software that lets you make free calls to anyone else on Skype, anywhere in the world. And even though the calls are free, they are really excellent quality. If you and your friends, family or business contacts are using webcams, you can also make free video calls. You can even call landlines and mobile phones at really cheap per minute rates (and theres no setup or subscription fee).
RPM version
Open console
Log on as superuser ("root")
Find the location where you saved the RPM
Enter the following command: "rpm -U skype-version.rpm", where skype-version.rpm is the name of the file you downloaded, such as skype-0_90_0_1.rpm.<<less
Download (7.39MB)
Added: 2009-04-27 License: Freeware Price: Free
179 downloads
Ticket-IT 3.0
Ticket-IT is a tool for the creation, management, and accompaniment of tickets. more>>
Ticket-IT is a tool for the creation, management, and accompaniment of tickets.
Ticket-IT is a tool directed towards companies that need a better integration and distribution of informantion about service to customers, support, development of products, callcenter, etc, among its several departments.
Ticket-IT has resource of easy utilization, concentration display and distribution of information, making possible its total adaptation to most distintc institutes and applications, being a perfect tool to HelpDesk, CallCenter and online support.
Main features:
Control and management of access
- User registration;
- Group registration;
- Access permission and actions based in group;
- Schedule of events;
- Users profile, top-configured;
Integration among sectors/departments
- Control of context categories, making possible the organization and cataloging of calls (tickets) being made or already made;
- Assign of users group per categories;
- Forwarding ticket to outer users that will be able to display calls and post comments;
- Partial or total ticket forwarding, making possible to manage information and function of the contributors of your company;
Information distribution
- Alerts via e-mail about create, opening, proceeding, close and re-opening or comments of tickets to those involved in categories;
- Main display of personal tickets, or collaborating, getting fast access to tickets, making service easier;
- Exchanging information based in a simple fulfilling of information, which due to Ticket-IT utomation, distribute it to those involved in the process;
- Protocol forwarding to outer agent access (customers, reps, etc) without the necessity of user and password;;
Enhancements:
- This release implements a Web installer and an option for personalization of the feedback message.
- The item "User of Companies" has already been implemented, along with its existing resources.
- A mask was applied (ticket comments and feedback) for guest users, so they will see the groups name instead of the users name in comments.
- Some minor bugs have been fixed.
- The gettext internationalization schema has been finished.
- The English (US) translation is done.
- There are some visual improvements.
<<lessTicket-IT is a tool directed towards companies that need a better integration and distribution of informantion about service to customers, support, development of products, callcenter, etc, among its several departments.
Ticket-IT has resource of easy utilization, concentration display and distribution of information, making possible its total adaptation to most distintc institutes and applications, being a perfect tool to HelpDesk, CallCenter and online support.
Main features:
Control and management of access
- User registration;
- Group registration;
- Access permission and actions based in group;
- Schedule of events;
- Users profile, top-configured;
Integration among sectors/departments
- Control of context categories, making possible the organization and cataloging of calls (tickets) being made or already made;
- Assign of users group per categories;
- Forwarding ticket to outer users that will be able to display calls and post comments;
- Partial or total ticket forwarding, making possible to manage information and function of the contributors of your company;
Information distribution
- Alerts via e-mail about create, opening, proceeding, close and re-opening or comments of tickets to those involved in categories;
- Main display of personal tickets, or collaborating, getting fast access to tickets, making service easier;
- Exchanging information based in a simple fulfilling of information, which due to Ticket-IT utomation, distribute it to those involved in the process;
- Protocol forwarding to outer agent access (customers, reps, etc) without the necessity of user and password;;
Enhancements:
- This release implements a Web installer and an option for personalization of the feedback message.
- The item "User of Companies" has already been implemented, along with its existing resources.
- A mask was applied (ticket comments and feedback) for guest users, so they will see the groups name instead of the users name in comments.
- Some minor bugs have been fixed.
- The gettext internationalization schema has been finished.
- The English (US) translation is done.
- There are some visual improvements.
Download (0.25MB)
Added: 2007-01-29 License: GPL (GNU General Public License) Price:
1008 downloads
Skype for Linux 2.0.0.72
Skype Linux Static binary tar.bz2 with Qt 3.2 compiled in. more>> Skype is a little piece of software that allows you to make calls from your computer. Talk for as long as you like without worrying about the cost or the distance.
Free Skype-to-Skype calls
Make video calls
Send cheap text messages
Easy conference calling
Free to download
Open console
Find the location where you saved the tar.bz2 file
Enter the following command: "tar xjvf skype-version.tar.bz2", where skype-version.tar.bz2 is the name of the file you downloaded, such as skype-0_90_0_1.tar.bz2. Skype is then unpacked to the current directory. Note that this does not require root privileges.<<less
Download (14.7MB)
Added: 2009-04-21 License: Freeware Price: Free
199 downloads
Other version of Skype for Linux
Free Skype-to-Skype calls Make video calls Send cheap text messages Easy conference callingLicense:Freeware
Netpet-CMS 1.8
Netpet-CMS project provides easy-going deployment and administration of Web sites, newsletters, and banners. more>>
Netpet-CMS project provides easy-going deployment and administration of Web sites, newsletters, and banners. After a short introduction, even users with little experience are capable using Netpet-CMS.
Furthermore, you dont need any specially configured server to run Netpet CMS, so you can install Netpet CMS on standard cheap Web hosting accounts.
<<lessFurthermore, you dont need any specially configured server to run Netpet CMS, so you can install Netpet CMS on standard cheap Web hosting accounts.
Download (1.8MB)
Added: 2007-08-09 License: GPL (GNU General Public License) Price:
808 downloads

Skype for Linux Debian 1.2
Skype Linux Debian package allows you to make calls from your computer. more>> Skype is a little piece of software that allows you to make calls from your computer. Talk for as long as you like without worrying about the cost or the distance.
Free Skype-to-Skype calls
Make video calls
Send cheap text messages
Easy conference calling
Free to download<<less
Download (7.54MB)
Added: 2009-04-26 License: Freeware Price: Free
180 downloads
Request Tracker 3.6.1
Request Tracker is a web, command-line, and email-based trouble ticketing and bugtracking package. more>>
Request Tracker (RT) is an enterprise-grade ticketing system which enables a group of people to intelligently and efficiently manage tasks, issues, and requests submitted by a community of users.
The RT platform has been under development since 1996, and is used by systems administrators, customer support staffs, IT managers, developers and marketing departments at thousands of sites around the world.
Written in object-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers.
RT manages key tasks such as the identification, prioritization, assignment, resolution and notification required by enterprise-critical applications including project management, help desk, NOC ticketing, CRM and software development.
RT is used by Fortune 100 companies, government agencies, educational institutions, and development organizations worldwide.
Main features:
- RT is your organizations focal point for tracking tasks, issues, knowledge, and collaboration.
- Its easy to submit, assign, prioritize, search, escalate, and report on issues.
- RT keeps track of each tickets full history and metadata to help your organization better retain knowledge and analyze trends.
- RT can track multiple projects for multiple teams within a single installation.
- RT tracks critical system metadata, including time spent per action, due dates, and estimated time to completion.
- Its easy to record private comments that are not available to end-users.
- RTs web interface comes complete with an intuitive "iterative" search interface that allows end users to construct complex queries by pointing and clicking within their web browsers.
- Users can save and edit queries later, using their browsers "bookmarks" feature.
- Users dont need to do anything special -- they can just send email to RT. RT will take care of thanking them for their message, automatically routing it to the appropriate staff, and making sure all future correspondence gets to the right place.
- RT provides a simple, self-service interface that allows end users to view their own active and resolved tickets online.
- RTs web interface is designed to be easy to use from any browser. Just working in Internet Explorer and Netscape isnt enough. Your staff need to be able to get work done anytime, anywhere.
- Whether you use Windows, MacOS or Unix, your staff already have everything they need to access RT.
- RT works great from a handheld or screen-reader (for the blind.) Best Practical is working with users to ensure that a future release is fully compliant with Section 508 accessibility requirements.
- A powerful new command-line interface that allows power users to quickly and easily work with RT, even if theyre out of the office is currently available for testing by the public.
- Youve got customers around the world. RT lets you interact with them in their own language. Internally, RT converts all data to UnicodeTM, so you can respond to users in their native tongue, but work in yours.
- Youve got staff around the globe. RTs web interface has been fully internationalized. Right now, RT speaks English, German, French, Dutch, Portuguese, Russian, Czech, Japanese, Traditional Chinese, and Simplified Chinese. Adding new languages is a breeze, if you need something RT doesnt support yet. On login, RT automatically detects which language each user prefers, so staff members can collaborate even if they speak different languages.
- Unlike costly proprietary issue tracking systems, an administrator can have a basic RT system up and running in an afternoon.
- RT is built to be useful right out of the box. You dont need expensive consultants
- Theres no client software to manage or keep up to date. Your existing web browser and email clients are all you need.
- RT is written in object-oriented perl. Not only do you get the complete source code to the product with every download, but your staff can begin customizing RT to meet your needs within hours.
- RTs web interface and mail gateway are built on top of the same API we publish for you to write your own tools on top of. The interface is documented and there are numerous third party tools to use as examples and templates.
- Every organization needs to track specialized data. RT lets you define list-based and freeform custom fields to help track your tickets. Once you create custom fields, its easy to search on them, just like RTs predefined fields.
- All of RTs mailing rules are based around a powerful custom business logic system called "Scrips." Scrips make it easy for a local administrator to make RT do ANYTHING whenever a ticket is created or updated, without making it hard to upgrade.
- RTs entire web interface is built on a flexible templating system that lets you build your own web-based tools or alter RTs look and feel to better fit your organization.
- If you dont want to radically change RTs interface, you can add your own components to RTs pages. A web callback system lets you drop miniature templates into RTs web pages.
- If you need even more power, "Code overlays" let you customize RTs internal behaviour without touching RTs core libraries.
Enhancements:
- This release includes numerous small cleanups and improvements.
- It fixes the dreaded "infinite relogin" bug.
<<lessThe RT platform has been under development since 1996, and is used by systems administrators, customer support staffs, IT managers, developers and marketing departments at thousands of sites around the world.
Written in object-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers.
RT manages key tasks such as the identification, prioritization, assignment, resolution and notification required by enterprise-critical applications including project management, help desk, NOC ticketing, CRM and software development.
RT is used by Fortune 100 companies, government agencies, educational institutions, and development organizations worldwide.
Main features:
- RT is your organizations focal point for tracking tasks, issues, knowledge, and collaboration.
- Its easy to submit, assign, prioritize, search, escalate, and report on issues.
- RT keeps track of each tickets full history and metadata to help your organization better retain knowledge and analyze trends.
- RT can track multiple projects for multiple teams within a single installation.
- RT tracks critical system metadata, including time spent per action, due dates, and estimated time to completion.
- Its easy to record private comments that are not available to end-users.
- RTs web interface comes complete with an intuitive "iterative" search interface that allows end users to construct complex queries by pointing and clicking within their web browsers.
- Users can save and edit queries later, using their browsers "bookmarks" feature.
- Users dont need to do anything special -- they can just send email to RT. RT will take care of thanking them for their message, automatically routing it to the appropriate staff, and making sure all future correspondence gets to the right place.
- RT provides a simple, self-service interface that allows end users to view their own active and resolved tickets online.
- RTs web interface is designed to be easy to use from any browser. Just working in Internet Explorer and Netscape isnt enough. Your staff need to be able to get work done anytime, anywhere.
- Whether you use Windows, MacOS or Unix, your staff already have everything they need to access RT.
- RT works great from a handheld or screen-reader (for the blind.) Best Practical is working with users to ensure that a future release is fully compliant with Section 508 accessibility requirements.
- A powerful new command-line interface that allows power users to quickly and easily work with RT, even if theyre out of the office is currently available for testing by the public.
- Youve got customers around the world. RT lets you interact with them in their own language. Internally, RT converts all data to UnicodeTM, so you can respond to users in their native tongue, but work in yours.
- Youve got staff around the globe. RTs web interface has been fully internationalized. Right now, RT speaks English, German, French, Dutch, Portuguese, Russian, Czech, Japanese, Traditional Chinese, and Simplified Chinese. Adding new languages is a breeze, if you need something RT doesnt support yet. On login, RT automatically detects which language each user prefers, so staff members can collaborate even if they speak different languages.
- Unlike costly proprietary issue tracking systems, an administrator can have a basic RT system up and running in an afternoon.
- RT is built to be useful right out of the box. You dont need expensive consultants
- Theres no client software to manage or keep up to date. Your existing web browser and email clients are all you need.
- RT is written in object-oriented perl. Not only do you get the complete source code to the product with every download, but your staff can begin customizing RT to meet your needs within hours.
- RTs web interface and mail gateway are built on top of the same API we publish for you to write your own tools on top of. The interface is documented and there are numerous third party tools to use as examples and templates.
- Every organization needs to track specialized data. RT lets you define list-based and freeform custom fields to help track your tickets. Once you create custom fields, its easy to search on them, just like RTs predefined fields.
- All of RTs mailing rules are based around a powerful custom business logic system called "Scrips." Scrips make it easy for a local administrator to make RT do ANYTHING whenever a ticket is created or updated, without making it hard to upgrade.
- RTs entire web interface is built on a flexible templating system that lets you build your own web-based tools or alter RTs look and feel to better fit your organization.
- If you dont want to radically change RTs interface, you can add your own components to RTs pages. A web callback system lets you drop miniature templates into RTs web pages.
- If you need even more power, "Code overlays" let you customize RTs internal behaviour without touching RTs core libraries.
Enhancements:
- This release includes numerous small cleanups and improvements.
- It fixes the dreaded "infinite relogin" bug.
Download (1.2MB)
Added: 2006-09-11 License: GPL (GNU General Public License) Price:
1364 downloads
Apache2::AuthCookieDBI 2.03
Apache2::AuthCookieDBI is an AuthCookie module backed by a DBI database. more>>
Apache2::AuthCookieDBI is an AuthCookie module backed by a DBI database.
SYNOPSIS
# In httpd.conf or .htaccess
PerlModule Apache2::AuthCookieDBI
PerlSetVar WhatEverPath /
PerlSetVar WhatEverLoginScript /login.pl
# Optional, to share tickets between servers.
PerlSetVar WhatEverDomain .domain.com
# These must be set
PerlSetVar WhatEverDBI_DSN "DBI:mysql:database=test"
PerlSetVar WhatEverDBI_SecretKey "489e5eaad8b3208f9ad8792ef4afca73598ae666b0206a9c92ac877e73ce835c"
# These are optional, the module sets sensible defaults.
PerlSetVar WhatEverDBI_User "nobody"
PerlSetVar WhatEverDBI_Password "password"
PerlSetVar WhatEverDBI_UsersTable "users"
PerlSetVar WhatEverDBI_UserField "user"
PerlSetVar WhatEverDBI_PasswordField "password"
PerlSetVar WhatEverDBI_CryptType "none"
PerlSetVar WhatEverDBI_GroupsTable "groups"
PerlSetVar WhatEverDBI_GroupField "grp"
PerlSetVar WhatEverDBI_GroupUserField "user"
PerlSetVar WhatEverDBI_EncryptionType "none"
PerlSetVar WhatEverDBI_SessionLifetime 00-24-00-00
# Protected by AuthCookieDBI.
< Directory /www/domain.com/authcookiedbi >
AuthType Apache2::AuthCookieDBI
AuthName WhatEver
PerlAuthenHandler Apache2::AuthCookieDBI->authenticate
PerlAuthzHandler Apache2::AuthCookieDBI->authorize
require valid-user
# or you can require users:
require user jacob
# You can optionally require groups.
require group system
< /Directory >
# Login location.
< Files LOGIN >
AuthType Apache2::AuthCookieDBI
AuthName WhatEver
SetHandler perl-script
PerlHandler Apache2::AuthCookieDBI->login
< /Files >
This module is an authentication handler that uses the basic mechanism provided by Apache2::AuthCookie with a DBI database for ticket-based protection. It is based on two tokens being provided, a username and password, which can be any strings (there are no illegal characters for either). The username is used to set the remote user as if Basic Authentication was used.
On an attempt to access a protected location without a valid cookie being provided, the module prints an HTML login form (produced by a CGI or any other handler; this can be a static file if you want to always send people to the same entry page when they log in). This login form has fields for username and password. On submitting it, the username and password are looked up in the DBI database. The supplied password is checked against the password in the database; the password in the database can be plaintext, or a crypt() or md5_hex() checksum of the password. If this succeeds, the user is issued a ticket. This ticket contains the username, an issue time, an expire time, and an MD5 checksum of those and a secret key for the server. It can optionally be encrypted before returning it to the client in the cookie; encryption is only useful for preventing the client from seeing the expire time. If you wish to protect passwords in transport, use an SSL-encrypted connection. The ticket is given in a cookie that the browser stores.
After a login the user is redirected to the location they originally wished to view (or to a fixed page if the login "script" was really a static file).
On this access and any subsequent attempt to access a protected document, the browser returns the ticket to the server. The server unencrypts it if encrypted tickets are enabled, then extracts the username, issue time, expire time and checksum. A new checksum is calculated of the username, issue time, expire time and the secret key again; if it agrees with the checksum that the client supplied, we know that the data has not been tampered with. We next check that the expire time has not passed. If not, the ticket is still good, so we set the username.
Authorization checks then check that any "require valid-user" or "require user jacob" settings are passed. Finally, if a "require group foo" directive was given, the module will look up the username in a groups database and check that the user is a member of one of the groups listed. If all these checks pass, the document requested is displayed.
If a ticket has expired or is otherwise invalid it is cleared in the browser and the login form is shown again.
<<lessSYNOPSIS
# In httpd.conf or .htaccess
PerlModule Apache2::AuthCookieDBI
PerlSetVar WhatEverPath /
PerlSetVar WhatEverLoginScript /login.pl
# Optional, to share tickets between servers.
PerlSetVar WhatEverDomain .domain.com
# These must be set
PerlSetVar WhatEverDBI_DSN "DBI:mysql:database=test"
PerlSetVar WhatEverDBI_SecretKey "489e5eaad8b3208f9ad8792ef4afca73598ae666b0206a9c92ac877e73ce835c"
# These are optional, the module sets sensible defaults.
PerlSetVar WhatEverDBI_User "nobody"
PerlSetVar WhatEverDBI_Password "password"
PerlSetVar WhatEverDBI_UsersTable "users"
PerlSetVar WhatEverDBI_UserField "user"
PerlSetVar WhatEverDBI_PasswordField "password"
PerlSetVar WhatEverDBI_CryptType "none"
PerlSetVar WhatEverDBI_GroupsTable "groups"
PerlSetVar WhatEverDBI_GroupField "grp"
PerlSetVar WhatEverDBI_GroupUserField "user"
PerlSetVar WhatEverDBI_EncryptionType "none"
PerlSetVar WhatEverDBI_SessionLifetime 00-24-00-00
# Protected by AuthCookieDBI.
< Directory /www/domain.com/authcookiedbi >
AuthType Apache2::AuthCookieDBI
AuthName WhatEver
PerlAuthenHandler Apache2::AuthCookieDBI->authenticate
PerlAuthzHandler Apache2::AuthCookieDBI->authorize
require valid-user
# or you can require users:
require user jacob
# You can optionally require groups.
require group system
< /Directory >
# Login location.
< Files LOGIN >
AuthType Apache2::AuthCookieDBI
AuthName WhatEver
SetHandler perl-script
PerlHandler Apache2::AuthCookieDBI->login
< /Files >
This module is an authentication handler that uses the basic mechanism provided by Apache2::AuthCookie with a DBI database for ticket-based protection. It is based on two tokens being provided, a username and password, which can be any strings (there are no illegal characters for either). The username is used to set the remote user as if Basic Authentication was used.
On an attempt to access a protected location without a valid cookie being provided, the module prints an HTML login form (produced by a CGI or any other handler; this can be a static file if you want to always send people to the same entry page when they log in). This login form has fields for username and password. On submitting it, the username and password are looked up in the DBI database. The supplied password is checked against the password in the database; the password in the database can be plaintext, or a crypt() or md5_hex() checksum of the password. If this succeeds, the user is issued a ticket. This ticket contains the username, an issue time, an expire time, and an MD5 checksum of those and a secret key for the server. It can optionally be encrypted before returning it to the client in the cookie; encryption is only useful for preventing the client from seeing the expire time. If you wish to protect passwords in transport, use an SSL-encrypted connection. The ticket is given in a cookie that the browser stores.
After a login the user is redirected to the location they originally wished to view (or to a fixed page if the login "script" was really a static file).
On this access and any subsequent attempt to access a protected document, the browser returns the ticket to the server. The server unencrypts it if encrypted tickets are enabled, then extracts the username, issue time, expire time and checksum. A new checksum is calculated of the username, issue time, expire time and the secret key again; if it agrees with the checksum that the client supplied, we know that the data has not been tampered with. We next check that the expire time has not passed. If not, the ticket is still good, so we set the username.
Authorization checks then check that any "require valid-user" or "require user jacob" settings are passed. Finally, if a "require group foo" directive was given, the module will look up the username in a groups database and check that the user is a member of one of the groups listed. If all these checks pass, the document requested is displayed.
If a ticket has expired or is otherwise invalid it is cleared in the browser and the login form is shown again.
Download (0.022MB)
Added: 2007-03-19 License: Perl Artistic License Price:
949 downloads
MapGeneration Project 0.3.0
MapGeneration Project is a project featuring a server and helper programs to collect GPS information. more>>
MapGeneration Project is a project featuring a server and helper programs to collect GPS information from various sources and to then automatically generate a continuously improved, time annotated road map.
Nowadays gps-receivers are quite cheap and many people use them for route planning in their cars. On the other hand updated maps for the route planing systems are relativly expansive, if available at all.
The idea is to collect the data that people have recorded with their gps-receivers and combine it into one freely available road map. Besides being cheap and always current this map would also contain actual driving time information: Route planning on such a map would not have to use road type based approximations to calculate the fasted route.
In the MapGeneration Project we implement such a program and the end user tools needed to access the data. At the moment we concentrate on two programs: The MapGenerator itself and the MapGeneratorGUI used to administer the generator.
The MapGenerator is a server that accepts incoming data via network and combines the received road information into one big map. As the map might become quite big a database is used as storage. The MapGeneratorGUI connects to this database and displays the map.
As the best way to understand a program is to use it we will now give a short introduction to using the program.
Enhancements:
New features
- (Server) New filter to detect gaps in the input traces.
- (Server) Calculates and outputs total length and time of processed traces.
- (Server) Added full support for more than one processing thread, 2 is default now.
Changes
- (Server) Rewrote TraceServer and TraceConnection to support commoncpp2 1.0.x.
- (Server) Server tries to bind to 127.0.0.1 if no interfaces are found.
- (Server) Added curvature as a criterion for merging -> much better merging!
- (Server) Improved avoidance of double processing of nodes.
- (Server) Moved parsing of traces into TraceFilter.
- (General) Added lots of new methods to handle distances, bearings and interpolation.
- (General) Configuration system supports boolean values.
- (Buildsys) Changed parameters to specify config files to --with-wx-config and --with-ccgnu2-config
Bugfixes
- (Server) Protected data handling between thread with mutexs.
- (GUI) Fixed some string literals for full unicode support.
- (General) Cache: Fixed all size calculations and the size handling system.
- (General) Raised requirements for wxWidgets to 2.6 (beta versions since 2.5.3 should work).
- (General) Some small fixes to build with commoncpp2 1.0.x.
<<lessNowadays gps-receivers are quite cheap and many people use them for route planning in their cars. On the other hand updated maps for the route planing systems are relativly expansive, if available at all.
The idea is to collect the data that people have recorded with their gps-receivers and combine it into one freely available road map. Besides being cheap and always current this map would also contain actual driving time information: Route planning on such a map would not have to use road type based approximations to calculate the fasted route.
In the MapGeneration Project we implement such a program and the end user tools needed to access the data. At the moment we concentrate on two programs: The MapGenerator itself and the MapGeneratorGUI used to administer the generator.
The MapGenerator is a server that accepts incoming data via network and combines the received road information into one big map. As the map might become quite big a database is used as storage. The MapGeneratorGUI connects to this database and displays the map.
As the best way to understand a program is to use it we will now give a short introduction to using the program.
Enhancements:
New features
- (Server) New filter to detect gaps in the input traces.
- (Server) Calculates and outputs total length and time of processed traces.
- (Server) Added full support for more than one processing thread, 2 is default now.
Changes
- (Server) Rewrote TraceServer and TraceConnection to support commoncpp2 1.0.x.
- (Server) Server tries to bind to 127.0.0.1 if no interfaces are found.
- (Server) Added curvature as a criterion for merging -> much better merging!
- (Server) Improved avoidance of double processing of nodes.
- (Server) Moved parsing of traces into TraceFilter.
- (General) Added lots of new methods to handle distances, bearings and interpolation.
- (General) Configuration system supports boolean values.
- (Buildsys) Changed parameters to specify config files to --with-wx-config and --with-ccgnu2-config
Bugfixes
- (Server) Protected data handling between thread with mutexs.
- (GUI) Fixed some string literals for full unicode support.
- (General) Cache: Fixed all size calculations and the size handling system.
- (General) Raised requirements for wxWidgets to 2.6 (beta versions since 2.5.3 should work).
- (General) Some small fixes to build with commoncpp2 1.0.x.
Download (0.57MB)
Added: 2005-08-02 License: GPL (GNU General Public License) Price:
1543 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above cheap airline tickets search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed