Free crossplatform software for linux

DVDStyler is a crossplatform DVD Authoring System.
DVDStyler project is free software distributed under GNU General Public License (GPL).
Main features:
- drag and drop MPEG files directly
- import image file for background
- create NTSC/PAL menus
- place text and images anywhere on the menu screen
- change font/color
- put basic text buttons, change font/color and background color
- copy and paste any menu object
- set chapters for each movie
- change post command for each movie

QPVCalendarWidget is an extremely useful widget. With dependancy only on Qt4 no other libraries are needed inorder to use this widget; no depenancies means totally crossplatform for you the developer.

Unlike other Mini-Calendar widgets seen in Qt software such as the clock widget in the KDE Desktop, QPVCalendarWidget does not depend and never will on external libraries such as kdelibs which is hard to keep cross-platform especially when developing for Win32.

QPVCalendarWidget depends only on Qt4.

The goal of this project is to allow you to have a mini calendar for allowing users to select dates. Originating from PracticeVisions own need of a mini calendar LimeSG has opensourced this part of PracticeVision so you to can enjoy the ease of a simple calendar/graphical date selector in your application. Since Trolltech only supplies text based widgets for date, QPVCalendarWidget is the perfect solution for graphical date selection.

BibleStudy is one of many frontends to the Sword project. The sword project is a library which provides access to many religious works.

Almost 100% of which are Christian. There are dozens of translations of the bible in many languages, as well as commentaries, dictionaries and some various books.

BibleStudy is written using the wxWidgets crossplatform API. It is currently available for Microsoft Windows and Linux, but it is possible to make a MacOS build. If anyone is interested please let me know.

SMM++ Mud Client project is a client with mapping functionality and lots of other features.
SMM++ Mud Client is a mud client with extended and unique features.
Aside from all standard mud client functionality like ANSI color support, aliases, action triggers, and tab-completion, SMM++ features a highly-customizable user interface (labels, buttons, and menus) and unique and powerful mapping capabilities, and SMM++ is the only mapping crossplatform (Tcl/Tk based) mud client available.
Enhancements:
- ::smm::action replaced with ::smm::reaction (pretty stable)
Added:
- ::smm::pasteok hook (not tested extensively, yet)

LWJGL (Lightweight Java Game Library) is a solution aimed directly at professional and amateur Java programmers alike to enable commercial quality games to be written in Java.
LWJGL provides developers access to high performance crossplatform libraries such as OpenGL (Open Graphics Library) and OpenAL (Open Audio Library) allowing for state of the art 3D games and 3D sound. Additionally LWJGL provides access to controllers such as Gamepads, Steering wheel and Joysticks.
All in a simple and straight forward API. LWJGL is not meant to make writing games particularly easy; it is primarily an enabling technology which allows developers to get at resources that are simply otherwise unavailable or poorly implemented on the existing Java platform.
We anticipate that the LWJGL will, through evolution and extension, become the foundation for more complete game libraries and "game engines" as they have popularly become known, and hide some of the new evils we have had to expose in the APIs.
LWJGL is available under a BSD license, which means its open source and freely available at no charge.
Please visit us on the Freenode IRC Network: #LWJGL. Do idle if there is no one to answer any of your questions, we are on different timezones.
In response to everything here Id like to state our goals with LWJGL:
- Speed
- Simplicity
- Ubiquity
- Smallness
- Security
- Robustness
- Minimalism
and this will help explain how we got to where we are today and more importantly where were going and where were not going.
Speed
The whole point of LWJGL was to bring the speed of Java rendering into the 21st century. This is why we have:
Thrown out methods designed for efficient C programming that make no sense at all in java, such as glColor3fv.
Made the library throw an exception when hardware acceleration is not available on Windows. No point in running at 5fps is there?
Ubquity
Our library is designed to work on devices as small as phones right the way up to multiprocessor rendering servers. Just because there arent any phones or consoles yet with fast enough JVMs and 3d acceleration is neither here nor there - there will be, one day. Were carefully tailoring the library so that when it happens well have OpenGL ES support in there just like that. This means that:
We had to have a very small footprint or itll never catch on in the J2ME space at all. Thats why the binary distribution is under half a meg, and that takes care of 3d sound, graphics, and IO.
Even under desktop environments having a 1-2mb download just to call a few 3D functions is daft.
Weve worked to a lowest common denominator principle rather than attempting to design for all possibilities, but weve made sure that 99% of required uses are covered. Thats why weve only got one window, and why we dont guarantee that windowed mode is even supported (its officially a debug mode and hence we dont even supply some very basic windowy abilities that youd get in AWT) and why we dont allow multiple thread rendering contexts.
Simplicity
LWJGL needed to be simple for it to be used by a wide range of developers. We wanted relative newbies to be able to get on with it, and professionals to be able to use it professionally, maybe typically coming from a C++ background. We had to choose a paradigm that actually fits with OpenGL, and one that fits with our target platforms which ranges from PDA to desktop level. This is why:
We arent catering for single-buffered drawing
We dont require that an instance of GL is passed around all over the place but we do not prevent this style of coding. See below for why.
We removed a lot of stuff that 99% of games programmers need to know nothing about
We have decided that consistency is better than complexity. Rather than allowing multiple ways to call the same methods and bloating the library weve just said, "Right, no arrays. Theyre slower anyway. Get used to buffers, as this is what buffers are meant to be used for."
Smallness
See ubiquity above. We had to be small.
Small == simple. The less ways there are to do something, the easier it is to learn the only way that works or is allowed.
Small == our code is less buggy. Wouldnt you rather be hunting for bugs in your own code, not ours?
Small == downloadable. No version nightmares. LWJGL is small enough to download with every application that uses it.
Small == J2ME.
Security
We realised a few months ago that no-one was going to take us seriously if we couldnt guarantee the security of the LWJGL native libraries. This is why we:
No longer use pointers but exclusively use buffers instead
Are gradually adding further checks to buffer positions and limits to ensure that the values are within allowed ranges to prevent buffer attacks
Robustness
Similarly to security we have now realised that a reliable system is far more useful than a fast system. When we actually had a proper application to benchmark finally we had some real data. Many of our original design decisions were based on microbenchmarks - well, you have to start somewhere! But with a real application to benchmark we now know we can throw out asserts and replace them with a proper if (...) check and a thrown exception. We know also that we can move all that GL error checking out of native code and into Java code and we will no longer need a separate DLL for debug mode.
As for runtime exceptions, they have their place. Theres not a reasonably well defined argument as to when you should use a runtime exception and when you should use a checked exception. When I made OpenGLException a checked exception all it did was end up littering my code with try {} catch {} sections - except that if youve got an OpenGLException there is very little sensible you can do to rectify it because it should never have occurred in the first place.
Thats why its a runtime exception. You should simply not write code than can throw it because it is generally not recoverable nicely. However for robustness (and security) we are required to throw an exception if something is amiss. It falls, I believe, into exactly the same category of trouble as NPEs, ArrayIndexOOBs and ClassCastExceptions: should never occur but needs to be trapped somewhere.
Minimalism
This is another critical factor in our design decisions. If it doesnt need to be in the library, its not in the library. Our original aim was to produce a library that provided the bare minimum required to access the hardware that Java couldnt access, and by and large were sticking to this mantra.
The vector math code in the LWJGL is looking mighty scared at the moment because its probably for the chop - well, at least, from the core library - as its not an enabling technology at all, and there are numerous more fully featured alternatives. We chucked out GLU because its mostly irrelevant to game developers except for a few functions that we really need to get redeveloped in pure Java - but basically, GLU is just a library of code built on top of the enablement layer.