Free flying tickets software for linux

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.

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.

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)

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.

The FlightGear flight simulator project is an open-source, multi-platform, cooperative flight simulator development project. Source code for the entire project is available and licensed under the GNU General Public License.

The goal of the FlightGear project is to create a sophisticated flight simulator framework for use in research or academic environments, for the development and pursuit of other interesting flight simulation ideas, and as an end-user application. We are developing a sophisticated, open simulation framework that can be expanded and improved upon by anyone interested in contributing.

There are many exciting possibilities for an open, free flight sim. We hope that this project will be interesting and useful to many people in many areas.

FlightGear is a free flight simulator project. It is being developed through the gracious contributions of source code and spare time by many talented people from around the globe. Among the many goals of this project are the quest to minimize short cuts and "do things right", the quest to learn and advance knowledge, and the quest to have better toys to play with.

The idea for Flight Gear was born out of a dissatisfaction with current commercial PC flight simulators. A big problem with these simulators is their proprietariness and lack of extensibility. There are so many people across the world with great ideas for enhancing the currently available simulators who have the ability to write code, and who have a desire to learn and contribute. Many people involved in education and research could use a spiffy flight simulator frame work on which to build their own projects; however, commercial simulators do not lend themselves to modification and enhancement. The Flight Gear project is striving to fill these gaps.

There are a wide range of people interested and participating in this project. This is truly a global effort with contributors from just about every continent. Interests range from building a realistic home simulator out old airplane parts, to university research and instructional use, to simply having a viable alternative to commercial PC simulators.

Flight Dynamics Models

With FlightGear it is possible to choose between three primary Flight Dynamics Models. It is possible to add new dynamics models or even interface to external "proprietary" flight dynamics models:

1. JSBSim: JSBSim is a generic, 6DoF flight dynamics model for simulating the motion of flight vehicles. It is written in C++. JSBSim can be run in a standalone mode for batch runs, or it can be the driver for a larger simulation program that includes a visuals subsystem (such as FlightGear.) In both cases, aircraft are modeled in an XML configuration file, where the mass properties, aerodynamic and flight control properties are all defined.

2. YASim: This FDM is an integrated part of FlightGear and uses a different approach than JSBSim by simulating the effect of the airflow on the different parts of an aircraft. The advantage of this approach is that it is possible to perform the simulation based on geometry and mass information combined with more commonly available performance numbers for an aircraft. This allows for quickly constructing a plausibly behaving aircraft that matches published performance numbers without requiring all the traditional aerodynamic test data.

3. UIUC: This FDM is based on LaRCsim originally written by the NASA. UIUC extends the code by allowing aircraft configuration files instead and by adding code for simulation of aircraft under icing conditions.

UIUC (like JSBSim) uses lookup tables to retrieve the component aerodynamic force and moment coefficients for an aircraft... and then uses these coefficients to calculate the sum of the forces and moments acting on the aircraft.

Extensive and Accurate World Scenery Data Base

Over 20,000 real world airports included in the full scenery set.
Correct runway markings and placement, correct runway and approach lighting.
Taxiways available for many larger airports (even including the green center line lights when appropriate.)
Sloping runways (runways change elevation like they usually do in real life.)
Directional airport lighting that smoothly changes intensity as your relative view direction changes.
World scenery fits on 3 DVDs. (Im not sure thats a feature or a problem!) But it means we have pretty detailed coverage of the entire world.
Accurate terrain worldwide, based on the most recently released SRTM terrain data.) 3 arc second resolution (about 90m post spacing) for North and South America, Europe, Asia, Africa, and Australia.
Scenery includes all vmap0 lakes, rivers, roads, railroads, cities, towns, land cover, etc.
Nice scenery night lighting with ground lighting concentrated in urban areas (based on real maps) and headlights visible on major highways. This allows for realistic night VFR flying with the ability to spot towns and cities and follow roads.
Scenery tiles are paged (loaded/unloaded) in a separate thread to minimize the frame rate hit when you need to load new areas.

Accurate and Detailed Sky Model

FlightGear implements extremely accurate time of day modeling with correctly placed sun, moon, stars, and planets for the specified time and date. FlightGear can track the current computer clock time in order to correctly place the sun, moon, stars, etc. in their current and proper place relative to the earth. If its dawn in Sydney right now, its dawn in the sim right now when you locate yourself in virtual Sidney. The sun, moon, stars, and planets all follow their correct courses through the sky. This modeling also correctly takes into account seasonal effects so you have 24 hour days north of the arctic circle in the summer, etc. We also illuminate the correctly placed moon with the correctly placed sun to get the correct phase of the moon for the current time/date, just like in real life.

Flexible and Open Aircraft Modeling System

FlightGear has the ability to model a wide variety of aircraft. Currently you can fly the 1903 Wright Flyer, strange flapping wing "ornithopters", a 747 and A320, various military jets, and several light singles. FlightGear has the ability to model those aircraft and just about everything in between.

FlightGear has extremely smooth and fluid instrument animation that updates at the same rate as your out-the-window view updates (i.e. as fast as your computer can crank, and not artificially limited and chunky like in some sims.)

FlightGear has the infrastructure to allow aircraft designers to build fully animated, fully operational, fully interactive 3d cockpits (which even update and display correctly from external chase plane views.)

FlightGear realistically models real world instrument behavior. Instruments that lag in real life, lag correctly in FlightGear, gyro drift is modeled correctly, the magnetic compass is subject to aircraft body forces -- all those things that make real world flying a challenge.

FlightGear also accurately models many instrument and system failures. If the vacuum system fails, the HSI gyros spin down slowly with a corresponding degradation in response as well as a slowly increasing bias/error.

Moderate Hardware Requirements

The intention of FlightGear is to look nice, but not at the expense of other aspects of a realistic simulator. Our focus is not on competing in the "game" market and not on the ultra-flashy graphic tricks.

The result is a simulator with moderate hardware requirements to run at smooth frame rates. You can be reasonably happy on a $500-1000 (USD) machine (possibly even less if you are careful) and dont necessarily need $3000 (USD) worth of new hardware like you do with the many of the newest games.

That said, the more hardware you throw at FlightGear, the better it looks and runs, so dont feel like you have to chuck your expensive new hardware if you just purchased it. :-)

Internal Properties EXPOSED!

FlightGear allows users and aircraft designers access to a very large number of internal state variables via numerous internal and external access mechanisms. These state variables are organized into a convenient hierarchal "property" tree.

Using the properties tree it is possible to monitor just about any internal state variable in FlightGear. Its possible to remotely control FlightGear from an external script. You can create model animations, sound effects, instrument animations and network protocols for about any situation imaginable just by editing a small number of human readable configuration files. This is a powerful system that makes FlightGear immensely flexible, configurable, and adaptable.

Networking options

A number of networking options allow FlightGear to communicate with other instances of FlightGear, GPS receivers, external flight dynamics modules, external autopilot or control modules, as well as other software such as the Open Glass Cockpit project and the Atlas mapping utility.

A generic input/output option allows for a user defined output protocol to a file, serial port or network client.

A multi player protocol is available for using FlightGear on a local network in a multi aircraft environment, for example to practice formation flight or for tower simulation purposes.

The powerful network options make it possible to synchronize several instances of FlightGear allowing for a multi-display, or even a cave environment. If all instances are running at the same frame rate consistently, it is possible to get extremely good and tight synchronization between displays.

Flight Gear and its source code have intentionally been kept open, available, and free. In doing so, we are able to take advantage of the efforts of tremendously talented people from around the world. Contrast this with the traditional approach of commercial software vendors, who are limited by the collective ability of the people they can hire and pay. Our approach brings its own unique challenges and difficulties, but we are confident (and other similarly structured projects have demonstrated) that in the long run we can outclass the commercial "competition."

Contributing to Flight Gear can be educational and a lot of fun. A long time developer, Curtis Olson, had this to say about working on Flight Gear:

Personally, Flight Gear has been a great learning experience for me. I have been exposed to many new ideas and have learned a tremendous amount of "good stuff" in the process of discussing and implementing various Flight Gear subsystems. If for no other reason, this alone makes it all worth while.

xplanets shows a simulation of a spacecraft flying through the solar system. With the controls next to the simulation screen you can control the simulation and steer the spacecrafts flight.
The following planets are visible:
- the Sun (yellow)
- mercury (gray38)
- venus (burlywood2)
- earth (blue2)
- mars (LightSalmon3)
Note that the sizes of the sun and planets are not to scale, though their distances are. Showing the planets to scale would mean that they wouldnt be visible. The solar system is rather big, after all.
The planet nearest to the spaceship is indicated with a red circle around it. Its relative speed and distance are shown in the data display.
The xplanets program uses the GTK+ toolkit. It has been built with version 2.2.1, so it should work with any version >2.0.0. It does not work with GTK+ 1.x anymore.

Intellidiscs is a Remake of Tron: Deadly Discs for the classic Intellivision console. Its also one of the few, if not the first, Tron freeware games that has nothing to do with light-cycles.

Basically, you run around in an arena fighting off bad guys with your disc. There are four different varieties of bad guy, and one of them has three different varieties of disc. More difficult enemies appear as your score increases, with the most difficult showing up if you can reach 1,000,000 points.

Bad guys enter through doors on the sides of the arena. You can jam these doors open by either hitting them with your disc, or by running into them. If you jam open doors that are opposite each other, you can run in one side and come out the other. This is very important to your survival.

If you jam enough doors, eventually a recognizer will be dispatched to fix them. If you can hit the recognizer when its eye is open, it will stop fixing the doors and leave the arena. Plus, you get lots of points for this.

You can take three hits before you die, and every hit makes you slower! You will eventually recover from damage, regaining your speed as well. Touching the recognizer kills you instantly, so dont do it.

Default controls are the familiar WASD to move, and the outer keys of numpad (1, 2, 3, 4, 6, 7, 8, 9, non-Mac users turn Num Lock on!) throw your disc in any of eight directions. If you press one of the throw keys while your disc is in flight, it will return to you. Discs are harmless when returning. If you move away from your disc as it is flying back, it will never catch up to you, you must stop and catch it. All of the controls can be changed from the main menu.