Ports Search

bsdproxy is a generic, event-driven proxy designed specifically for the BSD platform. It uses the kqueue()/kevent() system calls to determine when to relay data from one side of the connection to the other. It also uses GLib (http://www.gtk.org) data structures and memory management functions to optimize steady-state performance (minimize unnecessary memory allocation/deallocation). bsdproxy has been used to proxy HTTP, HTTPS, telnet, and mysql without any problems. It should be able to serve as a transparent proxy for anything over a TCP/IP connection.

KMFL aims to bring Tavultesoft Keyman functionality to *nix operating systems. KMFL is being jointly developed by SIL International (http://www.sil.org) and Tavultesoft (http://www.tavultesoft.com). SCIM KMFL IMEngine allows you to use KMN keyboards (compiled with textproc/kmflcomp) through standard SCIM interface. The powerful KMN keyboard language supports contextual deadkeys, pre- and post-processing of keystrokes, rules grouping, 'storing' of character classes for use in similar rules, custom and Unicode character constants, SIL Ethnologue language codes, etc. Official Tavultesoft repository contains keyboards that cover more than 220 languages. Significant number of them are open source. The keyboards ports are textproc/kmfl-*.

A Python utilities collection for building WSGI applications. Werkzeug does not try to be a framework, and instead started as a simple collection of various utilities useful for building WSGI applications. It has since become one of the most advanced collections of its kind. It includes a powerful debugger, fully featured request and response objects, HTTP utilities to handle entity tags, cache control headers, HTTP dates, cookie handling, file uploads, a powerful URL routing system and a bunch of community contributed add-on modules.

This is Business::OnlinePayment::LinkPoint, an Business::OnlinePayment backend module for LinkPoint. It is only useful if you have a merchant account with LinkPoint: http://www.linkpoint.com/ and the "LinkPoint Perl Wrapper":

DBIx::Admin::DSNManager manages a file of DSNs, for both testing and production. The INI-style format was selected, rather than, say, using an SQLite database, so that casual users could edit the file without needing to know SQL and without having to install the command line program sqlite3. Each DSN is normally for something requiring manual preparation, such as creating the database named in the DSN. In the case of SQLite, etc, where manual intervention is not required, you can still put the DSN in dsn.ini. One major use of this module is to avoid environment variable overload, since it is common to test Perl modules by setting the env vars $DBI_DSN, $DBI_USER and $DBI_PASS. But then the problem becomes: What do you do when you want to run tests against a set of databases servers? Some modules define sets of env vars, one set per database server, with awkward and hard-to-guess names. This is messy and obscure. DBIx::Admin::DSNManager is a solution to this problem.

XML::Compile::WSDL11 understands WSDL version 1.1. An WSDL file defines a set of messages to be send and received over (SOAP) connections. This involves encoding of the message to be send into XML, sending the message to the server, collect the answer, and finally decoding the XML to Perl. As end-user, you do not have to worry about the complex details of the messages and the way to exchange them: it's all simple Perl for you. Also, faults are handled automatically. The only complication you have to worry about is to shape a nested HASH structure to the sending message structure. XML::Compile::Schema::template() may help you. When the definitions are spread over multiple files you will need to use addWSDL() (wsdl) or importDefinitions() (additional schema's) explicitly. Usually, interreferences between those files are broken. Often they reference over networks (you should never trust). So, on purpose you must explicitly load the files you need from local disk! (of course, it is simple to find one-liners as work-arounds, but I will to tell you how!)

fv is an HDRI viewer. Currently supported formats are the followings: * Greg Ward's HDR (also known as Radiance/PIC/RGBE). See http://www.graphics.cornell.edu/~bjw/rgbe.html for details. * Paul Debevec's PFM (Portable Float Map). See http://netpbm.sourceforge.net/doc/pfm.html for details. fv reads data from the standard input or files specified as arguments. In the latter case, each file may be compressed one with gzip or bzip2. The file may also change after fv is invoked, except its header part. fv checks whether the file changes and updates the display if necessary. This feature is useful for checking intermediate outputs from renderers.

Tgif is an interactive drawing tool that allows the user to draw and manipulate objects in the X Window System. It's also a hyper-graphics (or hyper-structured-graphics) browser on the World-Wide-Web. Its hyper-text home page is http://bourbon.usc.edu:8001/tgif/ and its hyper-graphics home page is http://bourbon.usc.edu:8001/tgif/index.obj. Tgif drawings can be converted to a variety of formats, including GIF, encapsulated PostScript and XBM. Version 4 has a completely revamped 3-D user interface, as well as a host of new features.

http://www.linuxtv.org/vdrwiki/index.php/Xineliboutput-plugin X11 and Linux framebuffer front-end for VDR. Plugin displays video and OSD in X/Xv/XvMC/VAAPI/VDPAU window, Linux framebuffer/DirectFB/vidixfb or DXR3 card. Support for local and remote frontends. Built-in image and media player supports playback of most known media files (avi/mp3/divx/jpeg/...), DVDs and radio/video streams (http, rtsp, ...) directly from VDR. FreeBSD Note: If you want to use VAAPI/VDPAU make sure the ffmpeg and libxine ports are (re)built with the corresponding knobs turned on! (make config in their port dirs.)

LinkChecker can check HTML documents for broken links. Features : * recursive checking * multithreaded * output can be colored or normal text, HTML, SQL, CSV or a sitemap graph in XML or GML format. * additionally reports download time for HTML pages * HTTP/1.1 and 1.0, HTTPS, FTP, mailto:, news:, nntp:, Gopher, Telnet and local file links are supported Javascript links are currently ignored * restrict link checking with regular expression filters for URLs * proxy support * give username/password for HTTP and FTP authorization * robots.txt exclusion protocol support * i18n support * command line interface * (Fast)CGI web interface