Free jet ducks software for linux

Duck project is a Web-based system for practice testing and quizzing.
Instructors can create multiple-choice, short answer, and extended response questions.
Unique feedback can be provided for up to 10 potential student responses.
Duck is based on constructivist teaching and learning ideals.
Enhancements:
- commented out addslashes so that it works with magic quote on.
- Probably should undo and turn magic quotes off.
- added authentication variable to duck.inc to control hard auth

Yellow Duck Framework is an object oriented framework that will help you with creating web applications. The project is implemented using the popular PHP web scripting language.
An example could be a weblog. The "post" request could take care of displaying and updating the items in the weblog. In this example, "update" would be an action as well as "display_list" and "display_item". Another request, "rss" for example could be used to generate RSS news feeds. In the "rss" request, we could for example find the actions "display_rss20" and "display_atom" which generate specific flavors of XML news feeds. Requests basically group action that are related.
By encapsulating all the programming in an object-oriented environment, you get a framework that is easy to use and understand, easy to extend and doesnt limit you in any way. If you combine this with a very feature-rich standard library that takes care of most common things that need to be programmed for a website, you have a very powerful environment available to develop web applications.
Main features:
- Structured programming environment by using requests and actions
- Clean separation of code and output
- Support for multi-langual websites by using locales
- Templates for outputting HTML easily based on Smarty
- Automatic action dispatching using URL parameters
- Object oriented form construction and validation
- Object oriented handling of authentication
- Classes for creating XML/RPC clients and servers.
- Classes for creating syndicated XML feeds such as RSS and Atom feeds.
- Easy handling of files, directories and images. For images, there are some very straightforward functions that can create thumbnails and obtain specific information about these images.
- An object oriented interface for creating and sending email messages.
- Database abstraction layer supporting MySQL, PostgreSQL, SQLite and Oracle.
- Object oriented way of creating SQL statements.
- Logging infrastructure based on plain text or XML logfiles.
- A shopping cart infrastructure that makes it easy to create webshops.
- Different smaller modules that take care of string handling, debugging, configuration settings, timers.
Enhancements:
- This release contains feature enhancements in nearly all sections.

Primate Plunge is a platform game where you help Monkey navigate his way down through treacherous jungles, canyons, towering waterfalls, into the heart of a volcano, and through the driving rain of a cold industrial city.
Monkey will find help along the way in the form of powerups, including parachutes and jet packs.
Primate Plunge originally competed in uDevGame2003, the annual Mac game competition hosted by iDevGames.com. Primate Plunge game is therefore being distributed for free.
Main features:
- Multiple scrolling layers of beautiful hand-drawn backgrounds.
- 5 worlds of intense monkey action, each uniquely challenging.
- Special powerups such as the parachute, and the jumping bean!
- Top score for each world - how deep can you go?
- Star rating for each world - can you get 5 stars in all of them?
- And lots more!

Rekall is a database front-end, somewhat in the style of MicroSoft Access. However, Rekall is not itself a database, and does not include a database.
By this we mean that data is stored somewhere else in an SQL server, and Rekall is fundementaly just a tool to extract, display and update that data (of course, it does lots more than that, it does forms and reports and scripting and .... you get the idea).
It is database agnostic, and does not have any preferred database in the sense that Access(tm) uses the Jet. database engine (although the Windows version can use the Jet database engine via an ODBC driver).
Rekall can do lots of the things that you would expect of a database front-end (or if it cant, let us know!). You can design and use forms and reports, you can construct database queries, and you can import and export data (actually, you can copy data, import is just copy file to table, and export is just copy table to file). You can also create reusable components which you can use in forms and reports, to reduce application development time.
Rekall can be scripted using the the Python language. You can arrange that a script is executed when various events occur (for instance, when the user changes the value of a control).
Scripts can be associated directly with the event, but you can also store scripts in script modules for more general use. And, of course, you have full access to all the modules that are available for Python. Plus, Rekall has an integrated Python debugger with syntax highlighting.
RekallRevealed is run as a community website to support the GPL version of Rekall. Rekall is being included by some of the Linux distributions, and commercial components and support are available from TotalRekall and from theKompany.
Enhancements:
Dynamic Layouts
- Dynamic layouts allow you to create forms where controls automatically resize depending on settings such as font sizes, and as the user resizes the form. This is based on QTs layout engine, althougn only a restricted set of functions are available.
Tool Boxes
- Personally, the author is not a fan of tool boxes, but they seem to be popular, so Rekall now supports them. If you still prefer the old context menu mechanism, you can turn tool boxes off.
Wizards
- Lots of the controls now have control wizards which prompt you for the important settings. Hopefully wizards will be avaialble for all controls by the time 2.3.x becomes 2.4.0
Stock Databases
- Stock databases. Rekall will come with some stock databases (actually there is only one at present, the demo database, but more will be added over time) which can be used to create your own database. In addition, you can download stock databases from the web. See the Rekall section on downloading the database that runs this website!
Manual
- The manual can now be accessed via a dedicated manual viewer (loosely modelled on QTs assistant program).
Other stuff
- Lots of bug fixes, lots of other smaller additions.
Enhancements:
- 2.2.6 is the now latest stable release.
- Mostly bug fixes since 2.2.4, particularly a problem related (I believe) to the default style used by Fedora Core 4

Whups provides a ticket and bug tracking system.
It is designed to be extremely flexible in letting users define kinds of tickets, different life cycles (sets of states) and priorities for each kind of ticket, and mixing types of tickets into sets of queues.
This design allows for very general and sophisticated multi-purpose uses.
Main features:
- Support for multiple "Queues" (aka Projects).
- Custom ticket types, states, priorities per Queue.
- Create, Assign, Close tickets.
- Search for tickets matching specific criteria.
- A complex query building for building and saving/storing custom searches.
- A reporting facility include graphs.
- Guest access (in addition to login access).
- E-mail notification of changes to tickets.
- Some groups/permisions support (more to come).
Enhancements:
- Ensure that a due date in a prior year doesnt make the EditTicketForm invalid (Bug #4763).
- Remove saved searches (Request #4897).
- Calculate ticket date attributes when they change instead of on every access (php@ideacode.com, Request #4893).
- Queries are now managed as shares, but the serialized bits are stored and managed by Whups in their own dedicated table.
- Allow guest access to query page.
- Smarter word wrapping in string representations of tickets (Request #4510).
- Add a Queue Summary block showing queues with the number of open tickets in each (Request #4628).
- Combine the People tab with the Update tab.
- Allow changing ticket queues as long as the user has DELETE permissions on the current queue and EDIT permissions on the new queue (tmerritt@email.arizona.edu, Request #4268).
- Add hours and minutes to due dates.
- Always use Summary for the ticket summary field label.
- Add Slovenian translation (Duck ).
- Show the requester in search results (rodion (at) nezna (dot) com, Bug #2820).
- Show either the Comment or Update tabs depending on permissions, but not both.
- Report the last-updated date for tickets (Bug #2396).
- Tickets now have an optional due date field.
- New updateTicket API call (Ben Klang , Bug #4101).
- Check permissions when setting ticket attributes through an API call (Ben Klang , Bug #4098).
- If guests can add tickets but not view them, dont tell them adding failed (Bug #3630).
- Add Unassigned Tickets Horde_Block (Request #766).
- [mas] Fix sorting in summary page to better handle dates. (Bug #2930)
- Add CAPTCHA support to the Add Comment and Create Ticket forms.
- Deliver RSS feeds in a way that supports USM (http://www.kbcafe.com/rss/usm.html, Request #2593).
- processMail() now ignores emails that were generated by Whups (Bug #3398).
- [ben] Better support for MS-SQL.
- Add Norwegian (Bokmal) translation (Torbjorn Grindhaug ).
- "My Bugs" page is now a Horde_Block layout (Request #3202).
- Fix permissions checking for ticket comments when an admin user is the one making the comment (Bug #2673).
- Delete searches by getvars string, not by name (Bug #3197).
- Allow to assign tickets to foreign groups

Openchange project intends to provide an Open-Source implementation of Microsoft Exchange Server 2003 under Unix Platforms.
The Openchange Project is developed in C language under the BSD license, and will primary work on NetBSD, OpenBSD, FreeBSD and Linux platforms. The project time line has been defined to approximatively one year, and we believe the project will be in a complete stable state at this time.
Openchange wishes to integrate the enterprise working environment and to substitute to an Exchange Server in a transparent way, so final users may continue to use Outlook, or any other mail client.
We also intend to provide to network administrators an easy solution to migrate Exchange databases into Openchange ones and reversely. And last but not least, we work so developers may reuse our sources in a smart way.
The project is divided into 4 parts :
- The OpenChange Library
- The OpenReverse Library
- The Documentation Framework
- The Openchange specifications
The OpenChange Library
This library includes all the requests managing the identification process, the data flow, and all the other requirements needed to permit the communication between an Outlook client and an Exchange Server. It can be used either to develop another Exchange-like server or client.
The OpenReverse Library
Due to legal restriction, the Openchange Server wont reuse the Microsoft Jet Database file format. Instead, we provide a library making easy to parse headers, retrieve the data, calculate checksum and more generally to offer a abstract migration tool to other user defined backends. This library can also be used for basics to develop a repair database tool.
The Documentation Framework
In the documentation framework, you will find all our research results. The subjects may concern the Exchange Internals or treat of a related subject. We wants to provide the most valuable information so our work can be shared with developers community.
The OpenChange Specifications
At last, we will provide the complete specifications of OpenChange in a printable way. This major document of the OpenChange team will help new developers to understand how Exchange Server works, how we implemented our APIs to make OpenChange, Exchange compatible. Around this main development, you will find several modules:
- OpenUtils Library
- OpenSniff
- OpenEDB
Enhancements:
- This release fixes limitations from the previous release (0.2) and adds a set of new features.
- Sending email messages to external recipients is now possible.
- It can also fetch and create appointments, contacts, and tasks in their respective default folder.
- Experimental NEWMAIL notification support is also available.
- The openchangeclient command line messaging tool has been improved and exchange2mbox has been introduced.
- It provides a way to synchronize an Exchange mailbox with an mbox file, supports MIME types, and is able to reflect changes back to Exchange.

The MDB Tools project is a effort to document the MDB file format used in Microsofts Access database package, and to provide a set of tools and applications to make that data available on other platforms.

Specifically, MDB Tools includes programs to export schema and data to other databases such as MySQL, Oracle, Sybase, PostgreSQL, and others.

Also, included is a SQL engine for performing simple SQL queries. The 0.5 release includes an updated GUI interface (screenshot is available here). A sparse but functional ODBC driver is included as well.

MDB Tools currently has read-only support for Access 97 (Jet 3) and Access 2000/2002 (Jet 4) formats. Access 2000 support is a recent addition and may not be as complete as Jet 3 support.

Write support is currently being worked on and the first cut is expected to be included in the 0.6 release.

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.