Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
GENLIB_FLATTEN_ALL_LOINS(3)
flatten all instances in the current netlist figure
GENLIB_FLATTEN_ALL_PHINS(3)
flatten all instances in the current layout figure
GENLIB_FLATTEN_LOFIG(3)
flatten an instance in the current netlist figure
GENLIB_FLATTEN_PHFIG(3)
flatten an instance in the current layout figure
GENLIB_UNFLATTEN_LOFIG(3), UNFLATTEN_LOFIG(3)
creates a hierarchy level from instances in the current logical figure
POLYTYPE_FLAT(3)
Polygon rendering mode type Allegro game programming library
PS_setflat(3)
Sets flatness
Tcl_ZlibAdler32.tcl86(3), Tcl_ZlibAdler32(3), Tcl_ZlibCRC32(3), Tcl_ZlibDeflate(3), Tcl_ZlibInflate(3), Tcl_ZlibStreamChecksum(3), Tcl_ZlibStreamClose(3), Tcl_ZlibStreamEof(3), Tcl_ZlibStreamGet(3), Tcl_ZlibStreamGetCommandName(3), Tcl_ZlibStreamInit(3), Tcl_ZlibStreamPut(3)
compression and decompression functions
Tcl_ZlibAdler32.tcl87(3), Tcl_ZlibAdler32(3), Tcl_ZlibCRC32(3), Tcl_ZlibDeflate(3), Tcl_ZlibInflate(3), Tcl_ZlibStreamChecksum(3), Tcl_ZlibStreamClose(3), Tcl_ZlibStreamEof(3), Tcl_ZlibStreamGet(3), Tcl_ZlibStreamGetCommandName(3), Tcl_ZlibStreamInit(3), Tcl_ZlibStreamPut(3)
compression and decompression functions
advdef(1)
AdvanceCOMP Deflate Compression Utility
asn2ff(1)
convert ASN.1 biological data to a flat format (old version)
asn2gb(1)
convert ASN.1 biological data to a GenBank-style flat format
ext2sim(1)
convert hierarchical ext|(5) extracted-circuit files to flat sim|(5) files
ext2spice(1)
convert hierarchical ext|(5) extracted-circuit files to flat spice| files
ffe(1)
flat file extractor
flatablexpr(3)
merges the operators of an expression man1/alc_origin.1
flatbeh(1)
Synthetize a behavioral description from a structural description
flatboob(1)
search for housing
flatlo(1)
FLATen LOgical figure man1/alc_origin.1
flatph(1)
FLATen PHysical figure man1/alc_origin.1
flattenlofig(3)
flatten a instance in a logical figure man1/alc_origin.1
flattenphfig(3), flatenphfig(3)
flatten a instance in a figure man1/alc_origin.1
glShadeModel(3), "glShadeModel(3)
select flat or smooth shading
latex(1), pdflatex(1), lualatex(1), dvilualatex(1), xelatex(1), lamed(1)
structured text formatting and typesetting
libowfat_fmt_ip6_flat(3), fmt_ip6_flat(3)
write a formatted ASCII representation of an IPv6 number
libowfat_scan_ip6_flat(3), scan_ip6_flat(3)
parse an IPv6 number in flat ASCII representation
map_db(1)
read a FASTA (0), GENBANK flat file (1) PIR/VMS (5) or GCG binary (6) sequence database and produce the offsets necessary for efficient memory mapping
qflatboob(1)
search for housing
rdf2bin(1), rdf2com(1)
convert an RDOFF object file to flat binary
rflattenlofig(3)
recursivly flatten a figure man1/alc_origin.1
rflattenphfig(3)
recursivly flatten a figure man1/alc_origin.1
sane-abaton(5)
SANE backend for Abaton flatbed scanners
sane-agfafocus(5)
SANE backend for AGFA Focus flatbed scanners
sane-apple(5)
SANE backend for Apple flatbed scanners
sane-artec(5)
SANE backend for Artec flatbed scanners
sane-avision(5)
SANE backend for original Avision and Avision OEM scanners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film scanners
sane-canon630u(5)
SANE backend for the Canon 630u USB flatbed scanner
sane-canon_lide70(5)
SANE backend for the Canon LiDE 70 USB flatbed scanner
sane-fujitsu(5)
SANE backend for Fujitsu flatbed and ADF scanners
sane-genesys(5)
SANE backend for GL646, GL841, GL843, GL847 and GL124 based USB flatbed scanners
sane-gt68xx(5)
SANE backend for GT-68XX based USB flatbed scanners
sane-hs2p(5)
SANE backend for Ricoh SCSI flatbed/ADF scanners
sane-ibm(5)
SANE backend for IBM and Ricoh SCSI flatbed scanners
sane-kodak(5)
SANE backend for big Kodak flatbed and ADF scanners
sane-mustek(5)
SANE backend for Mustek SCSI flatbed scanners (and some other devices)
sane-mustek_usb(5)
SANE backend for Mustek USB flatbed scanners
sane-mustek_usb2(5)
SANE backend for SQ113 based USB flatbed scanners
sane-pie(5)
SANE backend for PIE, Devcom and AdLib SCSI flatbed scanners
sane-plustek(5)
SANE backend for LM983[1/2/3] based USB flatbed scanners
sane-plustek_pp(5)
SANE backend for Plustek parallel port flatbed scanners
sane-ricoh(5)
SANE backend for Ricoh flatbed scanners
sane-ricoh2(5)
SANE backend for Ricoh flatbed scanners
sane-s9036(5)
SANE backend for Siemens 9036 flatbed scanners
sane-snapscan(5)
SANE backend for AGFA SnapScan flatbed scanners
sane-sp15c(5)
SANE backend for Fujitsu ScanPartner 15C flatbed scanner
sane-st400(5)
SANE backend for Siemens ST/Highscan flatbed scanners
sane-tamarack(5)
SANE backend for Tamarack flatbed scanners
sane-u12(5)
SANE backend for Plustek USB flatbed scanners, based on older parport designs
sane-umax_pp(5)
SANE backend for Umax Astra parallel port flatbed scanners
unflatablexpr(3)
unflats the operators of an expression man1/alc_origin.1
unflatten(1)
adjust directed graphs to improve layout aspect ratio
unflattenlofig(3)
creates a hierarchy level from instances of a figure man1/alc_origin.1
xyflat(3)
compute hierarchical coordinates man1/alc_origin.1
zlib-flate(1)
raw zlib compression program
Bio::DB::Flat(3)
Interface for indexed flat files
Bio::DB::Flat::BDB(3)
Interface for BioHackathon standard BDB-indexed flat file
Bio::DB::Flat::BDB::embl(3)
embl adaptor for Open-bio standard BDB-indexed flat file
Bio::DB::Flat::BDB::fasta(3)
fasta adaptor for Open-bio standard BDB-indexed flat file
Bio::DB::Flat::BDB::genbank(3)
genbank adaptor for Open-bio standard BDB-indexed flat file
Bio::DB::Flat::BDB::swiss(3)
swissprot adaptor for Open-bio standard BDB-indexed flat file
Bio::DB::Flat::BinarySearch(3)
BinarySearch search indexing system for sequence files
Bio::DB::Taxonomy::flatfile(3)
Use the NCBI taxonomy from local indexed flat files
Bio::Index::Abstract(3)
Abstract interface for indexing a flat file
Bio::Index::EMBL(3)
Interface for indexing (multiple) EMBL/Swissprot .dat files (i.e. flat file EMBL/Swissprot format)
Bio::Index::GenBank(3)
Interface for indexing one or more GenBank files (i.e. flat file GenBank format)
Bio::Ontology::OBOEngine(3)
An Ontology Engine for OBO style flat file format from the Gene Ontology Consortium
Bio::OntologyIO::dagflat(3)
a base class parser for GO flat-file type formats
Bio::OntologyIO::goflat(3)
a parser for the Gene Ontology flat-file format
Bio::OntologyIO::obo(3)
parser for OBO flat-file format
Bio::OntologyIO::soflat(3)
a parser for the Sequence Ontology flat-file format
Bio::SeqFeature::Tools::Unflattener(3)
turns flat list of genbank-sourced features into a nested SeqFeatureI hierarchy
Bio::Variation::IO::flat(3)
flat file sequence variation input/output stream
CAD::Drawing::IO::FlatYAML(3)
Fast distributed YAML file methods
CGI::Expand(3)
convert flat hash to nested data using TT2's dot convention
Class::DBI::LazyInflate(3)
Defer Inflating Of Columns Until They Are Used
Class::Inflate(3)
Inflate HASH Object from Values in Database
DBIx::Class::DateTime::Epoch(3)
Automatic inflation/deflation of epoch-based columns to/from DateTime objects
DBIx::Class::Helper::ResultClass::Tee(3)
Inflate to multiple result classes at the same time
DBIx::Class::InflateColumn(3)
Automatically create references from column data
DBIx::Class::InflateColumn::Authen::Passphrase(3)
Inflate/deflate columns to Authen::Passphrase instances
DBIx::Class::InflateColumn::DateTime(3)
Auto-create DateTime objects from date and datetime columns
DBIx::Class::InflateColumn::FS(3)
Inflate/deflate columns to Path::Class::File objects
DBIx::Class::InflateColumn::FS::ResultSet(3)
FS columns resultset class
DBIx::Class::InflateColumn::File(3)
DEPRECATED (superseded by DBIx::Class::InflateColumn::FS)
DBIx::Class::InflateColumn::IP(3)
Auto-create NetAddr::IP objects from columns
DBIx::Class::InflateColumn::Serializer(3)
Inflators to serialize data structures for DBIx::Class
DBIx::Class::InflateColumn::Serializer::JSON(3)
JSON Inflator
DBIx::Class::InflateColumn::Serializer::Storable(3)
Storable Inflator
DBIx::Class::InflateColumn::Serializer::YAML(3)
YAML Inflator
DBIx::Class::MooseColumns::Meta::Role::Attribute::DBICColumn(3)
Attribute metaclass trait for DBIx::Class::MooseColumns for attributes that are inflated DBIC columns
DBIx::Class::MooseColumns::Meta::Role::Attribute::DBICColumn(3)
Attribute metaclass trait for DBIx::Class::MooseColumns for attributes that are non-inflated DBIC columns
DBIx::Class::ResultClass::HashRefInflator(3)
Get raw hashrefs from a resultset
DBIx::Class::Schema::PopulateMore::Inflator(3)
Base Class for keyword Inflators
DBIx::Class::Schema::PopulateMore::Inflator::Date(3)
Returns A DateTime object
DBIx::Class::Schema::PopulateMore::Inflator::Env(3)
inflated via the %ENV hash
DBIx::Class::Schema::PopulateMore::Inflator::Find(3)
Inflate via ResultSet->find
DBIx::Class::Schema::PopulateMore::Inflator::Index(3)
Coerce DateTime from Strings
DBIx::Skinny::InflateColumn::DateTime(3)
DateTime inflate/deflate settings for DBIx::Skinny
DBIx::Skinny::InflateColumn::DateTime::Auto(3)
DateTime inflate/deflate and auto insert update time for DBIx::Skinny
Dancer::RPCPlugin::FlattenData(3), Dancer::RPCPlugin::DataFlatten(3)
Simple routine to flatten (blessed) data
Data::URIEncode(3)
Allow complex data structures to be encoded using flat URIs
File::Flat(3)
Implements a flat filesystem
GIS::Distance::Polar(3)
Polar coordinate flat-earth distance calculations
Gantry::Conf::FAQ(3)
Frequently Asked Questions regarding Gantry::Conf "Why should I use Gantry::Conf at all?" 4 Item "Why should I use Gantry::Conf at all?" There are many reasons why we feel Gantry::Conf is helpful both during development and after deployment. The next two entries should hopefully answer this question for you as they outline a few common scenarios programmers and system administrators often face. "How is Gantry::Conf helpful during development?" 4 Item "How is Gantry::Conf helpful during development?" "Easy separation of development configs from production configs" 4 Item "Easy separation of development configs from production configs" Often programmers have a separate development environment from their production environment. By using <shared> blocks and dev instances you can avoid spending any serious time setting up your application in the development environment. Take this configuration example: <shared dev> dbuser nobody dbpass secret dbconn "dbi:Pg:dbname=dev" </shared> <shared production> dbuser apache dbpass secret2 dbconn "dbi:Pg:dbname=production" </shared> <instance app1> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use production </instance> <instance app1-dev> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use dev </instance> By separating out our production and dev database information into shared blocks we can essentially switch between our production and dev environments by simply changing the instance we are using. If you were working on a script this would be a simple matter of running: $ script.pl --instance=app1-dev instead of: $ script.pl --instance=app1 "How is Gatnry::Conf helpful in production?" 4 Item "How is Gatnry::Conf helpful in production?" Gantry::Conf has several advantages in a production environment. First, it provides a single place for all config information, if you commit to it. Even if you don't commit to it for all apps, it still provides control to the installing admin over how and where conf information is stored. For instance, the admin could put the config information directly into /etc/gantry.conf, or into a separate file in /etc/gantry.d. She could even set up a secure web server where all boxes would go to get their conf. The short answer is, Gantry::Conf is flexible and production environments benefit from flexibility. "How do I pass my instance information into my application?" 4 Item "How do I pass my instance information into my application?" There are many possible ways to do this a few of which are: "Command line arguments" 4 Item "Command line arguments" If your application accepts arguments on the command line we suggest adding an --instance option to pass in the instance's name. "PerlSetVar" 4 Item "PerlSetVar" In a mod_perl environment you could use a PerlSetVar, possibly named GantryConfInstance, to pull in this value for your application. "ModPerl::ParamBuilder" 4 Item "ModPerl::ParamBuilder" Again in a mod_perl environment, another option would be to use ModPerl::ParamBuilder to pass the instance name. "Hard coded" 4 Item "Hard coded" We include this for the sake of completeness, but advise against it. You could always simply hard code your instance information into your application, but this will greatly reduce the flexibility you have. "How do I add a different provider for an existing ConfigVia method?" 4 Item "How do I add a different provider for an existing ConfigVia method?" Place your provider module in the Gantry::Conf::Provider::Method::* namespace. Make sure your public API matches the existing providers which use the same method. For instance the flat file providers all implement a config method which is called as a class method and receives a file name. "How do I add to the ConfigVia methods?" 4 Item "How do I add to the ConfigVia methods?" If none of the existing provider methods will do, you need to work in Gantry::Conf. In particular, you need to augment the dispatch hash with the name of your provisioning method and a sub name which will handle it. Then you need to implement the method you put in %dispatch
Gantry::Conf::Provider::FlatFile::Config::General(3)
-- Uses Config::General to configure your Gantry application
Gantry::Conf::Provider::FlatFile::Config::Tiny(3)
-- Uses Config::Tiny to configure your Gantry application
HTML::FormFu::Deflator(3)
Deflator Base Class
HTML::FormFu::Deflator::Callback(3)
Callback deflator
HTML::FormFu::Deflator::CompoundDateTime(3)
CompoundDateTime deflator
HTML::FormFu::Deflator::CompoundSplit(3)
CompoundSplit deflator
HTML::FormFu::Deflator::FormatNumber(3)
Format a number for a locale
HTML::FormFu::Deflator::PathClassFile(3)
Deflator for Path::Class::File objects
HTML::FormFu::Deflator::Strftime(3)
Strftime deflator
HTML::FormFu::Exception::Inflator(3)
Inflator exception
HTML::FormFu::Inflator(3)
Inflator Base Class
HTML::FormFu::Inflator::Callback(3)
Callback inflator
HTML::FormFu::Inflator::CompoundDateTime(3)
CompoundDateTime inflator
HTML::FormFu::Inflator::DateTime(3)
DateTime inflator
HTML::FormFu::Inflator::Imager(3)
Imager HTML::FormFu inflator
HTML::FormHandler::Manual::InflationDeflation(3)
inflation and deflation of field values
HTML::Shakan::Inflator::DateTime(3)
inflate field value to DateTime instance
Hash::Flatten(3)
flatten/unflatten complex data hashes
IO::Compress::Deflate(3)
Write RFC 1950 files/buffers
IO::Compress::RawDeflate(3)
Write RFC 1951 files/buffers
IO::Uncompress::AnyInflate(3)
Uncompress zlib-based (zip, gzip) file/buffer
IO::Uncompress::Inflate(3)
Read RFC 1950 files/buffers
IO::Uncompress::RawInflate(3)
Read RFC 1951 files/buffers
Jifty::Plugin::Deflater(3)
Handles Accept-Encoding and compression
List::Flatten(3)
Interpolate array references in a list
Mojolicious::Command::Author::inflate(3)
Inflate command
Net::Twitter::Role::InflateObjects(3)
Inflate Twitter API return values to Moose objects
Plack::Middleware::Deflater(3)
Compress response body with Gzip or Deflate
Pod::Elemental::Flat(3)
a content-only pod paragraph
Rose::HTML::Form::Field::Date(3)
Text field that inflates valid dates into DateTime objects
Rose::HTML::Form::Field::DateTime(3)
Text field that inflates valid dates and times into DateTime objects
SVN::Notify::Filter::EmailFlatFileDB(3)
Converts account names to email address based on a flat-file database
Tk::TableEdit(3)
A simple flat-file DBMS editor using Tk::SplitFrame, Tk::TabbedForm, and Tk::Columns
bp_bioflat_index(1), bp_bioflat_index.pl(1)
index sequence files using Bio::DB::Flat
bp_process_sgd(1), bp_process_sgd.pl(1)
Massage SGD annotation flat files into a version suitable for the Generic Genome Browser
bp_unflatten_seq(1)
unflatten a genbank or genbank-style feature file into a nested SeqFeature hierarchy
dtdflatten(1)
Flatten an SGML/XML DTD
flate(3), deflateinit(3), deflate(3), deflatezlib(3), deflateblock(3), deflatezlibblock(3), inflateinit(3), inflate(3), inflatezlib(3), inflateblock(3), inflatezlibblock(3), flateerr(3), mkcrctab(3), blockcrc(3), adler32(3)
deflate compression
stag-flatten.pl(1), stag-flatten(1)
turns stag data into a flat table
text2table(1)
flat text conversion to OpenDocument spreadsheet
tree-inflate(1)
transform a one-tree-per-line treebank into something human-readable
txt2man(1)
convert flat ASCII text to man page format
v.extrude(1), v.extrude (1)
Extrudes flat vector features to 3D vector features with defined height. Optionally the height can be derived from sampling of elevation raster map
home | help