SW Name |
Home page |
Downloaded |
GLib |
http://www.gtk.org/ |
4017x |
GLib - Library of useful routines for C programming.
|
|
AxisPHP |
http://www.axisdata.com/AxisPHP/ |
3997x |
A PHP library that includes objects for creating PostScript and PDF documents.
|
|
XMagick |
http://siag.nu/xmagick/ |
3977x |
XMagick is a library written in C, which allows integration of the ImageMagick library with any X application by providing functions which convert between the native X image format (XImage) and the native ImageMagick format (Image).
|
|
bbfinger |
http://www.geocities.com/[..]t/delta/8993/ |
3971x |
bbfinger displays the current users in a tiny X11-decorated window. It supports commandline options to set/unset transparency, foreground color, border size, display, and position. It can also be configured through a configuration file.
|
|
Tk::Text::Viewer |
http://www.raz.co.il/[..]r/Viewer.html |
3968x |
Tk::Text::Viewer is a text widget that can display text files under TK. It enable the user to search text and navigate in a Text widget.
|
|
MoreQt |
http://www.kafka-fr.net/MoreQt/ |
3962x |
MoreQt extends the Qt library, providing a range control on floating-point values instead of integers and associated widgets, a line edit that "waits" for user validation (using a timer, thefocus loss, or Enter-key press), and a units(length, temperatures, etc.) management system, including conversion between units.
|
|
Kavlon Foundation Layer |
http://kavlon.org/[..]ects/kfl.html |
3888x |
The Kavlon Foundation Layer (KFL) is designed to make producing reusable, maintainable code easy and fast. KFL builds on the strength of PHP and SQL so that experienced web application programmers do not need to learn any
new skills.
KFL works as an operating system for web applications to run on. Special
classes, called tasks, act as web programs. Each task is sepperated into
two special parts. Views are the part of the task which provide user
output. Actions are the part of the task which can make some change to the
system.
|
|
SWT |
http://www.eclipse.org/swt/ |
3880x |
The most succinct description of the Standard Widget Toolkit component is this:
The SWT component is designed to provide efficient, portable access to the user-interface facilities of the operating systems on which it is implemented.
The SWT component implementors take each of the terms in this statement to have a very specific meaning:
|
|
Ygl |
http://www.thp.uni-duisburg.de/Ygl/ |
3866x |
emulates SGI's GL routines under X11
|
|
aedGUI |
http://aedgui.sf.net |
3849x |
aedGUI is a cross-platform C++ GUI library that works with SDL.
|
|
jvider |
http://www.jvider.com |
3783x |
With jvider (Java Visual Interface Designer) you can easily design graphical user interfaces for your Java applets and applications.
|
|
paragui |
http://www.paragui.org |
3724x |
ParaGUI is a cross-platform high-level application framework and GUI (graphical user interface) library.
ParaGUI's is completely based on the Simple DirectMedia Layer.
|
|
PowerTab |
http://freshmeat.net/[..]ts/ptabtools/ |
3690x |
PowerTab Tools contains a library for accessing PowerTab Tablature files (*.ptb) and utilities for converting .ptb files to ASCII and GNU LilyPond files.
|
|
Apwal |
http://apwal.free.fr/ |
3508x |
Apwal is a simple application launcher for Linux together with a powerful editor.
|
|
JaxMe 2 |
http://ws.apache.org/jaxme/ |
3487x |
JaxMe 2 is an open source implementation of JAXB, the specification for Java/XML binding.
A Java/XML binding compiler takes as input a schema description (in most cases an XML schema but it may be a DTD, a RelaxNG schema, a Java class inspected via reflection or a database schema). The output is a set of Java classes:
* A Java bean class compatible with the schema description. (If the schema was obtained via Java reflection, then the original Java bean class.)
* An unmarshaller that converts a conforming XML document into the equivalent Java bean.
* Vice versa, a marshaller that converts the Java bean back into the original XML document.
In the case of JaxMe, the generated classes may also
* Store the Java bean into a database. Preferrably an XML database like eXist, Xindice, or Tamino, but it may also be a relational database like MySQL. (If the schema is sufficiently simple. :-)
* Query the database for bean instances.
* Implement an EJB entity or session bean with the same abilities.
In other words, by simply creating a schema and running the JaxMe binding compiler, you have automatically generated classes that implement the complete workflow of a typical web application:
|
|