Free compounding pharmacy software for linux

Automated support for compound RPC calls is a project which augments RPCGEN to support NFSv4-style compound procedures.

NFSv4 specifies that the RPC calls be batched into a "compound" call. There is no support for this in RPCGEN.

By rearranging the ONC IDL for NFSv4 into AutoGen definitions, these templates will emit the original IDL *plus* all the code to package, send, distribute, collect, return, and dispatch the results.

The distributed program author merely needs to call and supply server procedures for the routines specified in the IDL.

Templates for these calls and service routines is provided, too. The NFSv4 definitions are included.

Bio::Location::CoordinatePolicyI is an abstract interface for objects implementing a certain policy of computing integer-valued coordinates of a Location.

SYNOPSIS

# get a location, e.g., from a SeqFeature
$location = $feature->location();
# examine its coordinate computation policy
print "Location of feature ", $feature->primary_tag(), " employs a ",
ref($location->coordinate_policy()),
" instance for coordinate computationn";
# change the policy, e.g. because the user chose to do so
$location->coordinate_policy(Bio::Location::NarrowestCoordPolicy->new());

Objects implementing this interface are used by Bio::LocationI implementing objects to determine integer-valued coordinates when asked for it. While this may seem trivial for simple locations, there are different ways to do it for fuzzy or compound (split) locations. Classes implementing this interface implement a certain policy, like always widest range, always smallest range, mean for BETWEEN locations, etc. By installing a different policy object in a Location object, the behaviour of coordinate computation can be changed on-the-fly, and with a single line of code client-side.

DataparkSearch Engine is a web-based search engine released under the GNU General Public License, full-featured and designed to organize search within a web-site, group of web-sites, intranet or local system.
DataparkSearch consists of two parts. The first part is indexing mechanism (indexer). Indexer walks over html hypertext references and stores found words and new references into database. The second part is web CGI front-end to provide search using data collected by indexer.
Main features:
- Support for http, https, ftp, nntp and news URL schemes.
- htdb virtual URL scheme support for indexing SQL databases.
- text/html, text/xml, text/plain, audio/mpeg (MP3) and image/gif mime types built-in support.
- External parsers support for other document types.
- Ability to index multilingual sites using content negotiation.
- Searching all of the word forms using ispell affixes and dictionaries.
- Fuzzy searching based on acronyms and abbreviations.
- Stop-words, synonyms and acronyms lists.
- Boolean query language support.
- Neural network based Popularity Rank.
- Results sorting by relevancy, popularity rank, last modified time and by importance (a multiplication of relevancy and popularity rank).
- Various character sets support.
- Accent insensitive search.
- Phrases segmenting for Chinese, Japanese, Korean and Thai languages.
- mod_dpsearch - search module for Apache web server.
- Internationalized Domain Names support.
Enhancements:
- Tags and categories are now stored in the urlinfo table and can be set on a per-document basis.
- Support for crosswords has been implemented for cache dbmode.
- Automatic phrase search has been implemented for compound words.
- The full method of relevance calculation has been modified.
- Conditional operators can now be used in the variables section of the template.
- Storing documents in stored database has been fixed for non-default values of StoredFiles.
- The -f switch has been added for cached, search, and stored: use to run them in the foreground (dont daemonize).
- Several bugs were fixed.

Cuiterm is a CUI (Composite User Interface) terminal.
CUI (Composite User Interface) is a compound type of user interface which incorporates the features of the GUI (Graphical User Interface) and the CLI (Command Line Interface) by realizing both interface in one area at the same time.
It is absolutely substantial that the CUI contains GUI elements and control language in the same area of the screen at the same time, so the incorporation is complete. CUI is not an optional, alternatively selectable combination of the two communication method but a truly new approach.
An other relevant feature of the CUI method is that it uses generated commands. When the user activated some GUI part of the user interface an automatically generated command appears to complete the task so the user can observ how the CLI part of the user interface can be used.
The cuiterm is a pilot application for the CUI methodology made to demonstrate the power of the composite user interfaces. As terminals are usually used with some shell to start simple UNIX utility programs, the Cui library can be considered as a composite user interface for the shell and some UNIX utilities. The following screenshot shows the starting screen of the cuiterm.
How to use it?
To test the composite user interface first you have to download the cuiterm and and install it. After the installation is complete the program can be started with the cuiterm command.
When the terminal emulator started it can be used the usual way by typing commands into it. Some programs and some complex commands are interpreted by the terminal and colorized (see the list below). For these commands the screen should have active areas usable with the left mouse button by double clicking on them. The output of some programs have floating menus with context sensitive functions. The menus can be accessed by the right mouse button. Some parts of the screen can be used to fire up a text entry field by holding down the left mouse button.
The following list contains some interpreted and processed commands that are worth trying.
ls -l and some variants of it
df
who
w
ps aux
stat
finger
cat /etc/fstab
Enhancements:
- This version contains new features, including an automatic GUI generator which creates dialog boxes from manual pages, a working progress bar, enhanced size bars, and some new command parsers.
- The drag and drop, the speed of the terminal, and the existing parsers were also enhanced.

PicoStorage allows you to store hierarhical information (similar to "files and directories") inside a single file. The functionality offered is largely equivalent to the one offered by any filesystem, or by the Structured Storage and Compound Files.

PicoStorage can efficiently handle huge numbers of small files, with very economical disk usage; it also allows you to keep open (in RAM) simultaneously a large number of files. Transaction support guarantees data integrity.

Learn more about the distinctive advantages of PicoStorage. or look at the benchmark.

The library is available on a dual-license basis: under GPL for free, and under a commercial license for use in closed-source applications.

Using

The library contains the classes File and Dir to represent files and directories. On a File you can read or write a number of bytes from a given offset, and set/get the file size. On a Dir you can create entries (either files or subdirectories), open entries, delete entries, and iterate over the directorys content.

The storage itself (i.e. the whole hierarchical structure, contained in a filesystem file) is represented by the class Storage. Using this class, you can create or open a storage, obtain the root directory of the storage, close the storage and do commit or rollback.

Font::TTF::Glyph is a Perl module that holds a single glyphs information.

This is a single glyph description as held in a TT font. On creation only its header is read. Thus you can get the bounding box of each glyph without having to read all the other information.

INSTANCE VARIABLES

In addition to the named variables in a glyph header (xMin etc.), there are also all capital instance variables for holding working information, mostly from the location table.

The standard attributes each glyph has are:

numberOfContours
xMin
yMin
xMax
yMax

There are also other, derived, instance variables for each glyph which are read when the whole glyph is read (via read_dat):

instLen

Number of bytes in the hinting instructions (Warning this variable is deprecated, use length($g-{hints})> instead).

hints

The string containing the hinting code for the glyph
In addition there are other attribute like instance variables for simple glyphs:

For each contour there is:

endPoints

An array of endpoints for each contour in the glyph. There are numberOfContours contours in a glyph. The number of points in a glyph is equal to the highest endpoint of a contour.

There are also a number of arrays indexed by point number

flags

The flags associated with reading this point. The flags for a point are recalculated for a point when it is updated. Thus the flags are not very useful. The only important bit is bit 0 which indicates whether the point is an on curve point, or an off curve point.

x

The absolute x co-ordinate of the point.

y

The absolute y co-ordinate of the point

For composite glyphs there are other variables

metric

This holds the component number (not its glyph number) of the component from which the metrics for this glyph should be taken.

comps

This is an array of hashes for each component. Each hash has a number of elements:

glyph

The glyph number of the glyph which comprises this component of the composite.

args

An array of two arguments which may be an x, y co-ordinate or two attachment points (one on the base glyph the other on the component). See flags for details.

flag

The flag for this component

scale

A 4 number array for component scaling. This allows stretching, rotating, etc. Note that scaling applies to placement co-ordinates (rather than attachment points) before locating rather than after.

numPoints

This is a generated value which contains the number of components read in for this compound glyph.

The private instance variables are:

INFILE (P)

The input file form which to read any information

LOC (P)

Location relative to the start of the glyf table in the read file

BASE (P)

The location of the glyf table in the read file

LEN (P)

This is the number of bytes required by the glyph. It should be kept up to date by calling the update method whenever any of the glyph content changes.

OUTLOC (P)

Location relative to the start of the glyf table. This variable is only active whilst the output process is going on. It is used to inform the location table where the glyphs location is, since the glyf table is output before the loca table due to alphabetical ordering.

OUTLEN (P)

This indicates the length of the glyph data when it is output. This more accurately reflects the internal memory form than the LEN variable which only reflects the read file length. The OUTLEN variable is only set after calling out or out_dat.