Free usenet binary viewer software for linux

Scriptol to binary Compiler is a C++ native compiler.

Installation:

It is better to install Scriptol at root of a disk, for example:
c:scriptolc

Once the archive is extracted into the scriptolc directory, you have just to change to this directory to run the compiler.

To use the compiler at command line from any directory, you have to put the compiler into the path variable.

The setup script installs required file into sub-directories, or into the directory given as argument. Before to use the compiler, you have to read the licence, in the doc
directory: licence.html.

Usage:

Just type:
./solc mysource

Type "solc" only to list the options.

If your program is a multi-file project, the source given as parameter must be the main source file, the compiler will know dependencies from "include" statements and will build what is needed.

Exemples:

Type from the main scriptol directory:
./solc -bre demosfibo

Configuring:

By editing the solc.ini file, you may change the second pass compiler (you may have to rebuild the libsol library for this compiler), change the options of the compiler or add header files to include.

To add header files, just add "header=someheader.hpp" lines into the config file.

A xxx.cfg file may be written for each project main source beeing xxx, and if present, it overloads the solc.ini file.

WP Clipart now includes a viewer to expediate the use of the clipart collection. While it is true that any editor will allow you to "browse" your system for images to open or insert, the interface can often be slow, or you have to dig through the system to find the clipart, and often the display of the images (in thumbnail form) is very small.

The Clipart Viewer (CAV) is quick, has a nice size display (up to 240x240 pixels) and the images are displayed, when resized, in their original proportions. In other words, you get a real good look at the images before you pick one. CAV then lets you copy the image in original size to the clipboard to paste into your program. The preview quality and speed are the biggest advantages to using CAV, but there are a couple other advantages that are not immediately obvious.

First, you paste the saved image while keeping CAV open. This allows you to change your mind to try a different clip or copy and paste another image quickly. You dont have to block your editor with another "open" or "insert" dialog to keep going. You can also paste it into a graphics editor if you want to do a little tweaking and not have to find it again.

On Linux, you often cannot get images into the clipboard to use in apps like AbiWord or the Gimp. Simply by keeping CAV open, Abi and Gimp can be pasted into.

I programmed CAV with Python/wxPython/wxGTK. Dependencies should not be a problem on any system as I have created "stand-alone" executables for both Linux and Windows, using cxFreeze and py2exe, respectively, and included these in the downloads for WP Clipart. [They are in the "Viewer" folder.]

Below are a few screenshots. The use of the little app is fairly self-explanatory . . . by clicking on the "caviewer" in the wpclipart/viewer directory (or more easily, by making a symlink or shortcut to that file) CAV will open with its search tree open to the clipart directory.

cg is a semi-automatic newsgroup binary downloader. It assembles parts based on subject headers and then offers them in an editor for the user to choose which files he really wants.
cg is a automatic binary newsgroups downloader. It assembles parts based on subject headers and then offers them in an editor for the user to choose which files he really wants.
It supports decoding data in the following formats:
uuencode (both single- and multi-posting binaries)
MIME (multipart/mixed, message/partial; base64, quoted printable, x-uuencode) yEnc
Start it with cg somenewsgroup; `cg -h offers a short help, should you need it.
Enhancements:
- yenc support
- rename broken files to filename.broken
- CTRL-C/SIGINT handling: write rc file and quit after completely decoding current file.
- segfault fix (for postings of the type [422/7])
- ignore some uninteresting comment lines (no .desc file)
- dont assume last line before end is not allowed to contain data in uu data

GeoTIFF Viewer is a simple viewer for GeoTIFF files, which are georeferenced raster images, typically used for maps.
Ive noticed that there really arent any programs for Linux that just view maps. There are several GIS packages, but if all you want to do is look, theyre overkill. I wrote GeoTIFF Viewer to be a simple viewer of digital raster graphics.
It uses libtiff and libgeotiff for the heavy lifting of reading the TIFF and associated GeoTIFF tags, and GTK+, GDK, and GLib for the widgets and graphical utilities. As such, it should run on any platform that these do, which is to say, most modern operating systems.
Digital raster graphics for California can be freely obtained at The California Spatial Information Library. The USGS and the Tennessee Valley Authority have data for the rest of the country.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- This release fixes calculation of seconds when lat/long is being displayed.

Ekspos is platform independent Java image viewer program. Ekspos Image Viewer support most popular image format: PNG, JPEG, and GIF, where additional image format can be added through Java ImageIO plugin.
It consists of 2 parts: shell browser and viewer. Shell browser allows you to navigate your image collection and youll be able to browse images in tree, detail, list, icon and thumbnail view. The viewer provide progressive view of images with zoom and pan capability.
Main features:
- Image Format (Default): JPEG, PNG, and GIF
- Support ImageIO plugin for additional Image Format
- Support 4 views: detail, list, icon, and thumbnail
- Thumbnail caching for fast preview
- Written entirely in Java

vt52vnc is a VNC viewer which can be used on prehistoric green monochromatic terminals called vdt52s, which are capable of vectorgraphics. vt52vnc is a VNC ( http://www.uk.research.att.com/vnc ) viewer, which can be used on old, green, monochromatic, prehistoric terminals labeled vdt52s, which are capable of vector graphics.The software is functional, but incomplete for now: it does not support compression, passwords and there are many ways to optimize the output.


Mouse:
As vdt52s does not have the mouse or any other pointing device, one of three unlabeled buttons near the numeric keypad have been used to act as mouse-lock. When you depress it, you can use the numeric keypad to move the mouse, and `+, `-, `., `enter, `0, and `5 as button 1,2,3 toggle and button 1,2,3 click.

Speed:
Based on my own experiences, I recommend the speeds 38400 and higher for "real work". The screen is drawn by rectangles. This is done to improve the reaction times, when the screen changes very often.

The software uses the XOR mode to actually draw the image, which can be improved using AND and OR mode in some cases. One can also imagine another optimizations for particular shapes. I will not add those optimizations, as the decisions are very memory-consumptive and after all, I dont want to implement some kind of prolog just to
choose the right one. If you want to improve it, let me know.

Colors:
The monochromatic translation is done by some bit of green color, which can be changed at the beginning of vncproto.c. If you want to make it better (implement some dithering or (better) the shape finding algorithm), let me know.

Why and how:
The work was inspired by mine never-ending desire for an X display on the "frog". Display drawings are based on the graphics library by Marek Zelem, which is, in turn, based on the documentation for vdt52s, as my work is based on vnc protocol documentation. Coded, of course, on vdt52s terminal with wrong Enter and Control. The sources are written to be easily extended.

Installation & running
1) edit Makefile to adjust some parameters,
vi Makefile
2) run `make
make
3) optionally install:
cp vt52vnc /usr/local/bin

Convert::Binary::C is a Binary Data Conversion using C Types.

SYNOPSIS

Simple
use Convert::Binary::C;

#---------------------------------------------
# Create a new object and parse embedded code
#---------------------------------------------
my $c = Convert::Binary::C->new->parse( DEC, day => 24 };

my $packed = $c->pack( Date, $date );
Advanced
use Convert::Binary::C;
use Data::Dumper;

#---------------------
# Create a new object
#---------------------
my $c = new Convert::Binary::C ByteOrder => BigEndian;

#---------------------------------------------------
# Add include paths and global preprocessor defines
#---------------------------------------------------
$c->Include( /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/include,
/usr/include )
->Define( qw( __USE_POSIX __USE_ISOC99=1 ) );

#----------------------------------
# Parse the time.h header file
#----------------------------------
$c->parse_file( time.h );

#---------------------------------------
# See which files the object depends on
#---------------------------------------
print Dumper( [$c->dependencies] );

#-----------------------------------------------------------
# See if struct timespec is defined and dump its definition
#-----------------------------------------------------------
if( $c->def( struct timespec ) ) {
print Dumper( $c->struct( timespec ) );
}

#-------------------------------
# Create some binary dummy data
#-------------------------------
my $data = "binaryteststring";

#--------------------------------------------------------
# Unpack $data according to struct timespec definition
#--------------------------------------------------------
if( length($data) >= $c->sizeof( timespec ) ) {
my $perl = $c->unpack( timespec, $data );
print Dumper( $perl );
}

#--------------------------------------------------------
# See which member lies at offset 5 of struct timespec
#--------------------------------------------------------
my $member = $c->member( timespec, 5 );
print "member( timespec, 5 ) = $membern";

Convert::Binary::C is a preprocessor and parser for C type definitions. It is highly configurable and should support arbitrarily complex data structures. Its object-oriented interface has pack and unpack methods that act as replacements for Perls pack and unpack and allow to use the C types instead of a string representation of the data structure for conversion of binary data from and to Perls complex data structures.

Actually, what Convert::Binary::C does is not very different from what a C compiler does, just that it doesnt compile the source code into an object file or executable, but only parses the code and allows Perl to use the enumerations, structs, unions and typedefs that have been defined within your C source for binary data conversion, similar to Perls pack and unpack.

Beyond that, the module offers a lot of convenience methods to retrieve information about the C types that have been parsed.

Search::Binary is a Perl module for generic binary search.

SYNOPSIS

use Seach::Binary;
$pos = binary_search($min, $max, $val, $read, $handle, [$size]);

binary_search implements a generic binary search algorithm returning the position of the first record whose index value is greater than or equal to $val. The search routine does not define any of the terms position, record or index value, but leaves their interpretation and implementation to the user supplied function &$read(). The only restriction is that positions must be integer scalars.

During the search the read function will be called with three arguments: the input parameters $handle and $val, and a position. If the position is not undef, the read function should read the first whole record starting at or after the position; otherwise, the read function should read the record immediately following the last record it read. The search algorithm will guarantee that the first call to the read function will not be with a position of undef. The read function needs to return a two element array consisting of the result of comparing $val with the index value of the read record and the position of the read record. The comparison value must be positive if $val is strictly greater than the index value of the read record, 0 if equal, and negative if strictly less. Furthermore, the returned position value must be greater than or equal to the position the read function was called with.

The input parameters $min and $max are positions and represents the extent of the search. Only records which begin at positions within this range (inclusive) will be searched. Moreover, $min must be the starting position of a record. If present $size is a difference between positions and determines when the algorithms switches to a sequential search. $val is an index value. The value of $handle is of no consequence to the binary search algorithm; it is merely passed as a convenience to the read function.