Free the view software for linux

Bagel View project is a lightweight image viewer for looking at pXm images. Here pXm means Portable Pixmap (ppm), Portable Bitmap (pbm), and Portable Graymap (pgm) in both RAW and ASCII format. Sample files are included in the samples directory.

UF-View provides a Gnome-based User Friendly comic viewer.
uf-view is a calendar-based User Friendly comic viewer for Gnome.
It also supports:
Calvin and Hobbes
Little Gamers
Angst Technology
Penny Arcade
FoxTrot
It doesnt support anymore:
MegaTokyo
Warp9 To Hell.
Enhancements:
- Misc bug fixes
- Removed Dilbert
- Added Little Gamers
- Added Angst Technology
- Added Swedish translation
- Added .spec file

GO::View is a Perl module that creates a gif or png image for visualizing the GO DAG.

This perl module generates a graphic that displays the parent and child relationships of a selected GO term. It also provides the visualization for the GO::TermFinder perl module created by the Stanford Microarray Database (SMD). This module is useful when analyzing experimental or computational results that produce a set of gene products that may have a common function or process.

SYNOPSIS

use GO::View;

my $goView =

GO::View->new(-goid => $goid,
-ontologyProvider => $ontology,
-annotationProvider => $annotation,
-termFinder => @pvalues,
-aspect => P,
-configFile => $confFile,
-imageDir => "/tmp",
-imageUrlRoot => "http://www.ABC.com/tmp",
-imageName => "GOview.88.png",
-tree => up,
-nodeUrl => $goUrl,
-geneUrl => $geneUrl,
-pvalueCutOff => 0.01,
-imageLabel => "SGD");


argument required expect data and type
-------------------------------------------------------------------------
-goid No A gene ontology ID (GOID).
If nothing is passed in, the module
will use the top goid of each ontology
branch (i.e, goid for
molecular_function, biological_process,
or cellular_component)

-ontologyProvider Yes An ontology provider instance.

-annotationProvider No An annotation provider instance. It is
required for creating tree for GO Term
Finder result.

-termFinder No An array of hash references returned
from findTerms method of
GO::TermFinder module. It is required
for creating tree for GO Term Finder
result.

-aspect No . The aspect of the ontology
provider. It is required for creating
tree for GO Term Finder result.

-configFile Yes The configuration file for setting the
general variables for the graphic
display.

-imageDir Yes The directory for storing the newly
created image file. It must be
world (nobody) readable and writable
if you want to display the image to
the web.

-imageUrlRoot No The url root for the -imageDir. It is
required if you want to display the
image to the web.

-imageName No The image file name. By default, the
name will be something like
GOview.xxxx.png. The xxxx will be
the process id. A suffix for the image (.png
or .gif) should not be provided, as that will
be determined at run time, depending on the
capabilities of the GD library.

-treeType No . The tree type.

1. up => display the ancestor tree
for the given goid.
2. down => display the descendant tree
for the given goid.
By default, it will display the
descendant tree.

-geneUrl No The URL for each Gene to link to.
It needs to have the text in
the url which will be substituted
by the real goid for a node.

-nodeUrl No The url for each GO node to link to.
It needs to have the text in
the url which will be substituted
by the real goid for a node.

-pvalueCutOff No The p-value cutoff for displaying
the graphic for GO Term Finder.
The default is 0.01

-imageLabel No The image label which will appear at
the left bottom corner of the map.
------------------------------------------------------------------------

To display the image on the web:

$goView->showGraph;

To create and return image file name with full path:

my $imageFile = $goView->createImage;

Template::Manual::Views is a template toolkit views (experimental).

This section describes dynamic views: a powerful but experimental new feature in version 2.01 of the Template Toolkit.

A view is effectively a collection of templates and/or variable definitions which can be passed around as a self-contained unit. This then represents a particular interface or presentation style for other objects or items of data.

You can use views to implement custom "skins" for an application or content set. You can use them to help simplify the presentation of common objects or data types. You can even use then to automate the presentation of complex data structures such as that generated in an XML::DOM tree or similar. You let an iterator do the walking, and the view does the talking (or in this case, the presenting). Voila - you have view independant, structure shy traversal using templates.

In general, views can be used in a number of different ways to achieve several different things. They elegantly solve some problems which were otherwise difficult or complicated, and make easy some things that were previously hard.

At the moment, theyre still very experimental. The directive syntax and underlying API are likely to change quite considerably over the next version or two. Please be very wary about building your multi-million dollar e-commerce solutions based around this feature.

Euchre project is an Euchre game.
Euchre is a spades or bridge-like card game played with four players (3 computer players and 1 human).
The game is played via a GTK+ interface and allows customization of the computer skill level, aggression level, and many of the other game parameters. There are three levels of AI skill (easy, medium, and hard).
The medium and hard levels are good enough to give you a decent challenge.
Enhancements:
- Fixed bug where pass markers are not cleared after an all-pass event (thanks to an unknown euchre lover on sourceforge...)
- Added previous tricks dialog and the view menu items to access it

Tree::Simple::View::DHTML is a Perl class for viewing Tree::Simple hierarchies in DHTML.

SYNOPSIS

use Tree::Simple::View::DHTML;

## a simple example

# use the defaults (an unordered list with no CSS)
my $tree_view = Tree::Simple::View::DHTML->new($tree);

## more complex examples

# using the CSS properties
my $tree_view = Tree::Simple::View::DHTML->new($tree => (
list_type => "ordered",
list_css => "list-style: circle;",
list_item_css => "font-family: courier;",
expanded_item_css => "font-family: courier; font-weight: bold",
link_css => "text-decoration: none;"
));

# using the CSS classes
my $tree_view = Tree::Simple::View::DHTML->new($tree => (
list_css_class => "myListClass",
list_item_css_class => "myListItemClass",
expanded_item_css_class => "myExpandedListItemClass",
link_css_class => "myListItemLinkClass"
));

# mixing the CSS properties and CSS classes
my $tree_view = Tree::Simple::View::DHTML->new($tree => (
list_css => "list-style: circle;",
list_item_css => "font-family: courier;",
expanded_item_css_class => "myExpandedListItemClass",
link_css_class => "myListItemLinkClass"
# format complex nodes with a function
node_formatter => sub {
my ($tree) = @_;
return "" . $tree->getNodeValue()->description() . "";
},
# add a radio button element to the tree
# with the name of tree_id
radio_button => tree_id
));

# print out the javascript nessecary for the DHTML
# functionality of this tree
print $tree_view->javascript();

# print out the tree fully expanded
print $tree_view->expandAll();

# print out the tree expanded along a given path (see below for details)
print $tree_view->expandPath("Root", "Child", "GrandChild");