Ports Search

DBIx::Class::Schema::Loader automates the definition of a DBIx::Class::Schema by scanning database table definitions and setting up the columns, primary keys, and relationships. DBIx::Class::Schema::Loader currently supports only the DBI storage type. It has explicit support for DBD::Pg, DBD::mysql, DBD::DB2, and DBD::SQLite. Other DBI drivers may function to a greater or lesser degree with this loader, depending on how much of the DBI spec they implement, and how standard their implementation is. Patches to make other DBDs work correctly welcome. See DBIx::Class::Schema::Loader::DBI::Writing for notes on writing your own vendor-specific subclass for an unsupported DBD driver. This module requires DBIx::Class 0.06 or later, and obsoletes the older DBIx::Class::Loader. This module is designed more to get you up and running quickly against an existing database, or to be effective for simple situations, rather than to be what you use in the long term for a complex database/project.

The target of the game is to reach the target door of each of the 8 towers in currently 2 missions with this little green animal. This door is usually at the very top of the tower. But finding the way by using elevators and walking trough a maze of doors and platforms is not the only problem you have to solve. There is a bunch of other creatures living on the tower that will hinder you to reach your target by pushing you over the edge of the platforms. The only weapon of defence you have is to throw a little snowball. But most of the other creatures just don't care about this. So you must avoid them.

CVS Monitor is an CVS repository browser. It provides visibility of activity in CVS to developers, management, and the general public. Features: * Look at any repository anywhere - CVS Monitor can act on any repository that has at least a public read-only account, even if you don't own the repository * Aggressive Caching - all statistics, and most pages, are generated purely from the cached information * ChangeSet Visibility - present changes to the repository in ChangeSets, a single change involves new revisions on multiple files * Tracker Integration - CVS Monitor can be easily integrated with your Bug tracking or Request tracking systems

The C++ Portable Components currently consist of four libraries. The Foundation library contains a platform abstraction layer (including classes for multithreading, file system access, logging, etc.), as well as a large number of useful utility classes, such various stream buffer and stream classes, URI handling, and many more. The Net library contains network classes (sockets, HTTP, etc.) The XML library contains an XML parser with SAX2 and DOM interfaces, as well as an XMLWriter. The Util library contains classes for working with configuration files and command line arguments, as well as various utility classes.

ASL can generate code for totally different processors. These are implemented: Motorola 68000..68030,683xx including math co-processor and MMU; DSP56000; Motorola/IBM MPC601/MPC505/PPC403; 6800, 6805, 6809, 68(HC)11 and Hitachi 6301 Hitachi 6309, H8 and SH7000/7600 Rockwell 6502 and 65(S)C02 CMD 65816 Mitsubishi MELPS-740; MELPS-7700; MELPS-4500 and M16 Intel MCS-48/41, MCS-51, MCS-96 and 8080/8085 AMD 29K Siemens 80C166/167 Zilog Z80, Z180, Z380 and Z8 Toshiba TLCS-900(L), TLCS-90, TLCS-870, TLCS-47 and TLCS-9000 Microchip PIC16C54..16C57, PIC16C84/PIC16C64 and PIC17C42 SGS-Thomson ST62xx and 6804 Texas Instruments TMS32010/32015, TMS3202x, TMS320C3x and TMS370xxx NEC uPD 78(C)1x and uPD 75xxx (a.k.a. 75K0)

This module tries to find middle ground between one at a time and all at once processing of data sets. The purpose of this module is to avoid the overhead of implementing an iterative api when this isn't necessary, without breaking forward compatibility in case that becomes necessary later on. The API optimizes for when a data set typically fits in memory and is returned as an array, but the consumer cannot assume that the data set is bounded. The API is destructive in order to minimize the chance that resultsets are leaked due to improper usage.

omniORBpy is an object request broker (ORB) for Python which implements specification 2.6 of the Common Object Request Broker Architecture (CORBA). omniORBpy is implemented as a Python extension module (written in C++) to provide bindings for omniORB4, a high performance C++ ORB. Some features of omniORB4: - Support for GIOP and IIOP 1.0, 1.1 and 1.2. - Fully multithreaded runtime. - TypeCode and type Any. - CORBA 2.6 DynAny interfaces. - Dynamic Invocation and Dynamic Skeleton interfaces. - Complete Naming Service, omniNames. - Support for wchar, wstring and code set negotiation. - Full long long, long double, fixed point support. - PortableServer::Current. - Unix domain socket transport. - Bidirectional GIOP. - Interoperable Secure Socket Layer transport. - Flexible thread management. - Interceptors. - Fully interoperable with other CORBA ORBs.

A program that looks superficially like the minesweeper program that comes supplied with MS Windows (and is also available in other versions). Runs under X Windows on the UNIX operating system. Features -------- There are a number of features that make this version different from the others available (that I have seen). 3 Grid Tile options Hexagonal - Easy (the endgame can be difficult). Square - Traditional. Triangular - Difficult. 3 Grid sizes Small - 8x8 with 10 bombs Medium - 16x16 with 40 bombs Large - 30x16 with 99 bombs Highscore table 10 entries for the fastest times for each of the 3 levels of each of the 3 grid shapes.

This plugin uses the blog change interface in FullBlogPlugin to send out email notifications for: * new posts * updated posts * comment added * deleted posts Email notifications are sent to the user who made the change. Notifications can also be sent to other users or a distribution list by specifying the smtp_always_cc option. The emails are sent in plain text using a template that was modeled after Trac's ticket_notify_email template. If you are using the AnnouncerPlugin, you should use its FullBlogPlugin rather than the FullBlogNotificationPlugin.

A "recipe" specifies a number of branches to combine in a certain way. This plugin will take the recipe and give you the resulting branch. It also has a command to then build a source package from the resulting branch and optionally upload it somewhere.