Ports Search

CTWM is an extension to twm, that support multiple virtual screens, and a lot of other goodies. You can use and manage up to 32 virtual screens called workspaces. You swap from one workspace to another by clicking on a button in an optionnal panel of buttons (the workspace manager) or by invoking a function. You can custom each workspace by choosing different colors, names and pixmaps for the buttons and background root windows. Main features are : - Optional 3D window titles and border (ala Motif). - Shaped, colored icons. - Multiple icons for clients based on the icon name. - Windows can belong to several workspaces. - A map of your workspaces to move quickly windows between different workspaces. - Animations : icons, root backgrounds and buttons can be animated. - Pinnable and sticky menus. - etc...

fluxter is a newer incarnation of bbpager, which is like the name suggests a pager tool for Blackbox. The major changes to bbpager are: - Accesses fluxbox configuration files, e.g. in ~/.fluxbox, rather than in blackbox directories. - Default styles come from the fluxbox configuration. Without customization it will track the look of the current theme. - The configuration files have been renamed to fluxter.bb (used in a fluxbox environment) and fluxter.nobb (used in a non-fluxbox environment). These files should go in fluxbox configuration directories, such as ~/.fluxbox. - The X resource entries in the configuration files use fluxter as a label, rather than bbpager. - Per-workspace wallpaper changing is supported by the addition of per-workspace rootCommand configuration entries. For example: fluxter.workspace0.rootCommand: Esetroot /usr/share/pixmaps/bg1.png fluxter.workspace1.rootCommand: Esetroot /usr/share/pixmaps/bg2.png fluxter.workspace2.rootCommand: Esetroot /usr/share/pixmaps/bg3.png

This qjail version only supports the RELEASE-10.x series of releases. Qjail [ q = quick ] is a 4th generation wrapper for the basic chroot jail system that includes security and performance enhancements. Plus a new level of "user friendliness" enhancements dealing with deploying just a few jails or large scale jail environments consisting of 100's of jails. Qjail uses the jail(8) jail.conf method. This provides the ability to enable the following options on a per-jail basis. exec.fib, securelevel, allow.sysvipc, devfs_rulesets, allow.raw_sockets, allow.quotas, allow.mount.nullfs, allow.mount.tmpfs, allow.mount.zfs, vnet.interface, and vnet. The vnet option gives a jail its own network stack using the experimental vimage kernel module. The vnet option has only been tested on i386 and amd64 equipment. Qjail requires no knowledge of the jail command usage. It uses "nullfs" for read-only system executables, sharing one copy of them with all the jails. Uses "mdconfig" to create sparse image jails. Sparse image jails provide a method to limit the total disk space a jail can consume, while only occupying the physical disk space of the sum size of the files in the image jail. Ability to assign ip address with their network device name, so aliases are auto created on jail start and auto removed on jail stop. Ability to create "ZONE"s of identical qjail systems, each with their own group of jails. Ability to designate a portion of the jail name as a group prefix so the command being executed will apply to only those jail names matching that prefix. Qjail has been incorporated into the Finch open source project, see http://dreamcat4.github.io/finch/ for details.

This qjail version only supports RELEASE-11.0 and newer. Qjail [ q = quick ] is a 4th generation wrapper for the basic chroot jail system that includes security and performance enhancements. Plus a new level of "user friendliness" enhancements dealing with deploying just a few jails or large scale jail environments consisting of 100's of jails. Qjail uses the jail(8) jail.conf method. This provides the ability to enable the following options on a per-jail basis. exec.fib, securelevel, allow.sysvipc, devfs_rulesets, allow.raw_sockets, allow.quotas, allow.mount.nullfs, allow.mount.tmpfs, allow.mount.zfs, vnet.interface, and vnet. The vnet option gives a jail its own network stack using the experimental vimage kernel module. The vnet option has only been tested on i386 and amd64 equipment. Qjail requires no knowledge of the jail command usage. It uses "nullfs" for read-only system executables, sharing one copy of them with all the jails. Uses "mdconfig" to create sparse image jails. Sparse image jails provide a method to limit the total disk space a jail can consume, while only occupying the physical disk space of the sum size of the files in the image jail. Ability to assign ip address with their network device name, so aliases are auto created on jail start and auto removed on jail stop. Ability to create "ZONE"s of identical qjail systems, each with their own group of jails. Ability to designate a portion of the jail name as a group prefix so the command being executed will apply to only those jail names matching that prefix. Qjail has been incorporated into the Finch open source project, see http://dreamcat4.github.io/finch/ for details.

Jalview is a multiple alignment editor written in Java. It is used widely in a variety of web pages (e.g. the EBI Clustalw server and the Pfam protein domain database) and is also available as a general purpose alignment editor. o Reads and writes alignments in a variety of formats o Gaps can be inserted/deleted using the mouse. o Group editing (insertion deletion of gaps in groups of sequences). o Removal of gapped columns. o Align sequences using Web Services (Clustal, Muscle...) o Amino acid conservation analysis similar to that of AMAS. o Alignment sorting options (by name, tree order, percent identity, group). o UPGMA and NJ trees calculated and drawn based on percent identity distances. o Sequence clustering using principal component analysis. o Removal of redundant sequences. o Smith Waterman pairwise alignment of selected sequences. o Web based secondary structure prediction programs (JNet). o User predefined or custom colour schemes to colour alignments or groups. o Sequence feature retrieval and display on the alignment. o Print your alignment with colours and annotations. o Output alignments as HTML pages, images (PNG) or postscript (EPS). If you use Jalview in your work, please quote this publication. Clamp, M., et al. (2004), The Jalview Java Alignment Editor. Bioinformatics, 12, 426-7

The EAGLE Layout Editor is an easy to use, yet powerful tool for designing printed circuit boards (PCBs). The name EAGLE is an acronym, which stands for Easily Applicable Graphical Layout Editor. The program consists of three main modules: o Layout Editor o Schematic Editor o Autorouter which are embedded in a single user interface. Therefore there is no need for converting netlists between schematics and layouts. This is a Light Freeware Edition. It has the following limitations: o The useable board area is limited to 100 x 80 mm (4 x 3.2 inches). o Only two signal layers can be used (Top and Bottom). o The schematic editor can only create one sheet. o Support is only available via email or through our forum (no fax or phone support). o Use is limited to non-profit applications or evaluation purposes. Apart from these limitations the EAGLE Light Edition can do anything the Professional Edition can do. You can even load, view and print drawings that exceed these limits!

Sqitch is a database change management application. What makes it different from your typical migration-style approaches? A few things: ## No opinions Sqitch is not integrated with any framework, ORM, or platform. Rather, it is a standalone change management system with no opinions about your database engine, application framework, or development environment. ## Native scripting Changes are implemented as scripts native to your selected database engine. Writing a PostgreSQL application? Write SQL scripts for psql. Writing a MySQL-backed app? Write SQL scripts for mysql. ## Dependency resolution Database changes may declare dependencies on other changes -- even on changes from other Sqitch projects. This ensures proper order of execution, even when you've committed changes to your VCS out-of-order. ## No numbering Change deployment is managed by maintaining a plan file. As such, there is no need to number your changes, although you can if you want. Sqitch doesn't much care how you name your changes. ## Iterative development Up until you tag and release your application, you can modify your change deployment scripts as often as you like. They're not locked in just because they've been committed to your VCS. This allows you to take an iterative approach to developing your database schema. Or, better, you can do test-driven database development.

pgloader imports data from a flat file and inserts it into one or more PostgreSQL database tables. It uses a flat file per database table, and you can configure as many Sections as you want, each one associating a table name and a data file. Data are parsed and rewritten, then given to PostgreSQL COPY command. Parsing is necessary for dealing with end of lines and eventual trailing separator characters, and for column reordering: your flat data file may not have the same column order as the database table has. pgloader is also able to load some large objects data into PostgreSQL, as of now only Informix UNLOAD data files are supported. This command gives large objects data location information into the main data file. pgloader parse it add the text or bytea content properly escaped to the COPY data. pgloader issues some timing statistics every "commit_every" commits. At the end of processing each section, a summary of overall operations, numbers of rows copied and commits, time it took in seconds, errors logged and database errors is issued.

This module provides perl access to Glib and GLib's GObject libraries. GLib is a portability and utility library; GObject provides a generic type system with inheritance and a powerful signal system. Together these libraries are used as the foundation for many of the libraries that make up the Gnome environment, and are used in many unrelated projects. This wrapper attempts to provide a perlish interface while remaining as true as possible to the underlying C API, so that any reference materials you can find on using GLib may still apply to using the libraries from perl. Where GLib's functionality overlaps perl's, perl's is favored; for example, you will find perl lists and arrays in place of GSList or GList objects. Some concepts have been eliminated; you need never worry about reference-counting on GObjects or GBoxed structures. Other concepts have been converted to a perlish analogy; the GType id will never be seen in perl, as the package name serves that purpose. [FIXME link to a document describing this stuff in detail.]

InlineX::C2XS - create an XS file from an Inline C file. The C file that InlineX::C2XS needs to find would contain only the C code. InlineX::C2XS looks for the file in ./src directory - expecting that the filename will be the same as what appears after the final '::' in the module name (with a '.c' extension). ie if the module is called My::Next::Mod it looks for a file ./src/Mod.c, and creates a file named Mod.xs. Also created, is the file 'INLINE.h' - but only if that file is needed. The generated xs file (and INLINE.h) will be written to the cwd unless a third argument (specifying a valid directory) is provided to the c2xs() function. The created XS file, when packaged with the '.pm' file, an appropriate 'Makefile.PL', and 'INLINE.h' (if it's needed), can be used to build the module in the usual way - without any dependence upon the Inline::C module.