Free bindings software for linux

octave-g2 bindings is an Octave interface to G2 library.

INSTALL:

1: ./autogen.sh
2: ./configure
3: make
4: make install
#test the package by
5: cd ./examples && ./simple_x11.m #you must see a 45degree line on X11 window.

Java VideoLan Client Binding lets you use the VideoLan multimedia player in any Java software.
Main features:
- displays an original VideoLan Client
- using JVLCCanvas (extends java.awt.Canvas) or JVLCPanel (extends javax.swing.JPanel) is possible to embed VLC output in any application.
Enhancements:
- This release has a cleaner classes layout, and is more intuitive to use.
- Parts of the native interface have been rewritten, some memory leaks corrected.
- Upgrading is recommended.

Redland RDF Library Language Bindings provides high-level language bindings for the Redland RDF C libraries, allowing full access to the C APIs along with enhancements for individual languages. Redland RDF Library Language Bindings currently provides bindings in C#, Java, Perl, Python, Ruby, PHP and Tcl.
Configuring and building
Redland bindings uses the GNU automake and autoconf to handle system dependency checking. It is developed and built on x86 Linux (Redhat), but is also used extensively locally on various versions of sparc Sun Solaris 2.x. I also test it via SourceForges compile farm and it builds on Debian Linux (x86, Alpha, PPC and Sparc, IA64), FreeBSD (x86) and Apple OSX.
Configure tries very hard to find several programs and libraries that the Redland bindings need. These include the binding binaries: perl, python, etc., headers for the bindings such as the JDK, Python etc. and various others. A summary of the parts found is given at the end of the configure run. Several options to configure given below can be used to point to locations or names of dependencies that cannot be automatically determined.
Enhancements:
- All the bindings were synchronised with the Redland RDF Library release 1.0.6, adding a transactions API.
- Many updates and fixes were made to the Python and Ruby bindings, and other bugs were also fixed.

Tk::bindtags can determine which bindings apply to a window, and order of evaluation.

SYNOPSIS

$widget->bindtags([tagList]); @tags = $widget->bindtags;

When a binding is created with the bind command, it is associated either with a particular window such as $widget, a class name such as Tk::Button, the keyword all, or any other string. All of these forms are called binding tags. Each window has a list of binding tags that determine how events are processed for the window. When an event occurs in a window, it is applied to each of the windows tags in order: for each tag, the most specific binding that matches the given tag and event is executed. See the Tk::bind documentation for more information on the matching process.

By default, each window has four binding tags consisting of the the windows class name, name of the window, the name of the windows nearest toplevel ancestor, and all, in that order. Toplevel windows have only three tags by default, since the toplevel name is the same as that of the window.

Note that this order is different from order used by Tcl/Tk. Tcl/Tk has the window ahead of the class name in the binding order. This is because Tcl is procedural rather than object oriented and the normal way for Tcl/Tk applications to override class bindings is with an instance binding. However, with perl/Tk the normal way to override a class binding is to derive a class. The perl/Tk order causes instance bindings to execute after the class binding, and so instance bind callbacks can make use of state changes (e.g. changes to the selection) than the class bindings have made.

The bindtags command allows the binding tags for a window to be read and modified.

If $widget->bindtags is invoked without an argument, then the current set of binding tags for $widget is returned as a list. If the tagList argument is specified to bindtags, then it must be a reference to and array; the tags for $widget are changed to the elements of the array. (A reference to an anonymous array can be created by enclosin the elements in [ ].) The elements of tagList may be arbitrary strings or widget objects, if no window exists for an object at the time an event is processed, then the tag is ignored for that event. The order of the elements in tagList determines the order in which binding callbacks are executed in response to events. For example, the command

$b->bindtags([$b,ref($b),$b->toplevel,all])

applies the Tcl/Tk binding order which binding callbacks will be evaluated for a button (say) $b so that $bs instance bindings are invoked first, following by bindings for $bs class, followed by bindings for $bs toplevel, followed by all bindings.

If tagList is an empty list i.e. [], then the binding tags for $widget are returned to the perl/Tk default state described above.

The bindtags command may be used to introduce arbitrary additional binding tags for a window, or to remove standard tags. For example, the command

$b->bindtags([TrickyButton,$b->toplevel,all])

replaces the (say) Tk::Button tag for $b with TrickyButton. This means that the default widget bindings for buttons, which are associated with the Tk::Button tag, will no longer apply to $b, but any bindings associated with TrickyButton (perhaps some new button behavior) will apply.

Libconfig is a simple library for parsing structured configuration files, like this one: test.cfg.

This file format is more compact and more readable than XML. And unlike XML, it is type-aware, so it is not necessary to do string parsing in application code.

libconfigduo library includes bindings for both the C and C++ languages.

SwigSword library is a branch of the SWORD bible software library with enhanced SWIG bindings. This software will periodically be merged with the SWORD trunk.
Example code for using the SharpSword API:
SharpSword.MarkupFilterMgr markup = new SharpSword.MarkupFilterMgr();
markup.Encoding(SharpSword.Sword.ENC_HTML);
markup.Markup(SharpSword.Sword.FMT_HTML);
SharpSword.SWMgr mgr = new SharpSword.SWMgr(null, null, true, markup);
int mgrcount = mgr.moduleCount();
for (int i = 0; i < mgr.moduleCount(); i++)
{
SharpSword.SWModule mod = mgr.getModuleAt(i);
mod.SetKey(new SharpSword.VerseKey("John 3:16"));
string text = mod.text();
//do something with mod
Enhancements:
- Support for functions which use stl maps was added.

PitaCard is a program for creating and reviewing flashcards. PitaCard was initially designed for aiding language study and has strong multi-language support.

PitaCard is written in python using the PyGTK bindings to the GTK+ library.

Gst-Python provides Python bindings for the GStreamer project. These bindings provide access to almost all of the GStreamer C API through an object oriented Python API.