hitchhikers thumb
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 47
fortune-hitchhiker 2005-06-11
fortune-hitchhiker project consists of quotes from the Hitchhikers Guide to the Galaxy. more>>
fortune-hitchhiker project consists of quotes from the "Hitchhikers Guide to the Galaxy".
"Zaphod grinned two manic grins, sauntered over to the bar
and bought most of it."
-- Zaphod in paradise.
To install these fortunes, copy the .dat file to your fortunes directory.
(possibly /usr/games/lib/fortunes)
To use it, simply type:
# fortune hitchhiker
<<less"Zaphod grinned two manic grins, sauntered over to the bar
and bought most of it."
-- Zaphod in paradise.
To install these fortunes, copy the .dat file to your fortunes directory.
(possibly /usr/games/lib/fortunes)
To use it, simply type:
# fortune hitchhiker
Download (0.011MB)
Added: 2006-12-12 License: GPL (GNU General Public License) Price:
614 downloads
MusicIP Mixer 1.6
MusicIP makes music more accessible and more enjoyable. more>>
If you use a Windows, Mac or Linux PC to listen to your digital music - whether youre grooving at your computer, piping tracks to your home stereo, or loading your iPod or MP3 player - MusicIP makes music more accessible and more enjoyable.
MusicIP Mixer a multi-million dollar MUSIC development application---and it’s yours for FREE.
Rediscover your collection.
Do you have tons of digital music, but not much time? Are you in the mood for great tunes, but dont have the patience - or the interest - in thumbing through your tracks?
MusicIP makes it simple. Pick one song. Click one button. Get one amazing playlist that includes the perfect tracks from every corner of your collection - instantly.
Discover new music that suits YOU.
Finding new music is even harder than finding your old music. The best indicator of what you like is what you already have. So why not use your old music to find new music? MusicIP gives you access to search the worlds largest collection of related tracks so that you can find new artists or songs...right now.
<<lessMusicIP Mixer a multi-million dollar MUSIC development application---and it’s yours for FREE.
Rediscover your collection.
Do you have tons of digital music, but not much time? Are you in the mood for great tunes, but dont have the patience - or the interest - in thumbing through your tracks?
MusicIP makes it simple. Pick one song. Click one button. Get one amazing playlist that includes the perfect tracks from every corner of your collection - instantly.
Discover new music that suits YOU.
Finding new music is even harder than finding your old music. The best indicator of what you like is what you already have. So why not use your old music to find new music? MusicIP gives you access to search the worlds largest collection of related tracks so that you can find new artists or songs...right now.
Download (4.1MB)
Added: 2006-07-28 License: Freeware Price:
5940 downloads
Thumbs 0.6.3
Thumbs is a Firefox extension that shows the first thumbnail from each linked gallery. more>>
Thumbs is a Firefox extension that shows the first thumbnail from each linked gallery. After installing, use Customize Toolbars to add the Thumbs toolbar button, or select some links and right-click.
The Options window requires Firefox 1.5 Beta; it doesnt work in Firefox 1.0.x. Everything else should work, and you can still use about:config to tweak the options if want.
<<lessThe Options window requires Firefox 1.5 Beta; it doesnt work in Firefox 1.0.x. Everything else should work, and you can still use about:config to tweak the options if want.
Download (0.021MB)
Added: 2007-07-09 License: MPL (Mozilla Public License) Price:
1077 downloads
GD::Image::Thumbnail 0.02
GD::Image::Thumbnail is a Perl extension for creating thumbnailed images with GD. more>>
GD::Image::Thumbnail is a Perl extension for creating thumbnailed images with GD.
SYNOPSIS
use GD::Image::Thumbnail;
my $img = GD::Image->new(100,20);
my $thm = $img->thumbnail; # same as { factor => 0.20 }
my $thm = $img->thumbnail($n); # same as { side => $n }
my $thm = $img->thumbnail({ factor => 0.25 });
my $thm = $img->thumbnail({ factor => 0.25, small => 1 });
my $thm = $img->thumbnail({ side => $n });
my $thm = $img->thumbnail({ side => $n, small => 1 });
my $thm = $img->thumbnail({ w => $w });
my $thm = $img->thumbnail({ h => $h });
my $thm = $img->thumbnail({ w => $w, h => $h });
my $thm = $img->thumbnail({ w => $w, small => 1 });
my $thm = $img->thumbnail({ h => $h, small => 1 });
my $thm = $img->thumbnail({ w => $w, h => $h, small => 1 });
thumb() ^
thumb() is shortcut for thumbnail() - useful for people who like to bite their nails :)
$img->thumbnail(@thm_args)
and
$img->thumb(@thm_args);
are doing the same thing
OPTIONS
factor => $n
This makes a thumbnail $n (0.20 by default) times the size of the original. Only a two decimal place number between 0 and 1 are allowed. If a factor is given side, h, and w are all ignored
side => $n
Makes the side that will result in a larger thumbnail $n pixels (or opposite if small => 1). If side is given then h and w are ignored.
w => $x and h => $y
You can specify one or both of these. If only one is given it makes that side that dimention. If you specify both, the side that will result in a larger thumbnail (based on the images orientation and *not* the values of w and h if different), is used (or opposite if small => 1).
small => 1
If true make the images the smallest possible. This will round down instead of up when rounding is necessary and will help decide which side gets set to the given value.
$img->thumbnail(10); # 100 x 25 image becomes 40 x 10
$img->thumbnail({ side => 10, small => 1}); # 100 x 25 image becomes 10 x 2
resample => 1
If true use copyResampled() instead of copyResized() See GDs documentation about the difference. This can also be turned on by specifying a true value as the second argument:
$img->thumbnail($n, 1);
$img->thumbnail({ factor => $n }, 1);
<<lessSYNOPSIS
use GD::Image::Thumbnail;
my $img = GD::Image->new(100,20);
my $thm = $img->thumbnail; # same as { factor => 0.20 }
my $thm = $img->thumbnail($n); # same as { side => $n }
my $thm = $img->thumbnail({ factor => 0.25 });
my $thm = $img->thumbnail({ factor => 0.25, small => 1 });
my $thm = $img->thumbnail({ side => $n });
my $thm = $img->thumbnail({ side => $n, small => 1 });
my $thm = $img->thumbnail({ w => $w });
my $thm = $img->thumbnail({ h => $h });
my $thm = $img->thumbnail({ w => $w, h => $h });
my $thm = $img->thumbnail({ w => $w, small => 1 });
my $thm = $img->thumbnail({ h => $h, small => 1 });
my $thm = $img->thumbnail({ w => $w, h => $h, small => 1 });
thumb() ^
thumb() is shortcut for thumbnail() - useful for people who like to bite their nails :)
$img->thumbnail(@thm_args)
and
$img->thumb(@thm_args);
are doing the same thing
OPTIONS
factor => $n
This makes a thumbnail $n (0.20 by default) times the size of the original. Only a two decimal place number between 0 and 1 are allowed. If a factor is given side, h, and w are all ignored
side => $n
Makes the side that will result in a larger thumbnail $n pixels (or opposite if small => 1). If side is given then h and w are ignored.
w => $x and h => $y
You can specify one or both of these. If only one is given it makes that side that dimention. If you specify both, the side that will result in a larger thumbnail (based on the images orientation and *not* the values of w and h if different), is used (or opposite if small => 1).
small => 1
If true make the images the smallest possible. This will round down instead of up when rounding is necessary and will help decide which side gets set to the given value.
$img->thumbnail(10); # 100 x 25 image becomes 40 x 10
$img->thumbnail({ side => 10, small => 1}); # 100 x 25 image becomes 10 x 2
resample => 1
If true use copyResampled() instead of copyResized() See GDs documentation about the difference. This can also be turned on by specifying a true value as the second argument:
$img->thumbnail($n, 1);
$img->thumbnail({ factor => $n }, 1);
Download (0.003MB)
Added: 2007-04-24 License: Perl Artistic License Price:
914 downloads
Time::Skew 0.1
Time::Skew is a Perl module that computes local clock skew with respect to a remote clock. more>>
Time::Skew is a Perl module that computes local clock skew with respect to a remote clock.
SYNOPISI
use Time::Skew
# Init Convex Hull and timing data
my $hull=[];
my $result={};
# Iterate data point introduction
Time::Skew::convexhull($result,$datapoint,$hull);
This module supports the computation of the skew between two clocks: the (relative) skew is the speed with which two clocks diverge. For instance, if yesterday two clocks, at the same time, showed respectively 10:00 and 10:05, while today when the former shows 10:00 the latter shows 10:04, we say that their relative skew is 1 minute/24 hours, roughly 7E-4.
The module contains one single subroutine, which accepts as input a pair of timestamps, associated to a message from host A to host B: the timestamps correspond to the time when the message was sent, and to the time when message is received. Each timestamp reflects the value of the local clock where the operation takes place: the clock of host A for the send, the clock of B for the receive.
Please note that the module does _not_ contain any message exchange facility, but only the mathematics needed to perform the skew approximation, once timestamps are known.
The subroutine takes as argument:
a reference to a hash where values related to the timing of the network path from A to B;
a 2-elems array (a data point in the sequel) containing the timestamp of the receive event, and the differece between the send timestamp and the receive timestamp for one message;
a stack containing some data points, those that form the convex hull.
The usage is very simple, and is illustrated by the following example:
#!/usr/bin/perl -w
use strict;
use Time::Skew;
# Initialize data
my $hull=[];
my $result={};
while ( 1 ) {
# Exchange message and acquire a new data point
my $datapoint = acquire();
# Call the convexhull subroutine
Time::Skew::convexhull($result,$datapoint,$hull);
# After first message some results are still undefined
( defined $result->{skewjitter} ) || next;
# here you can use the results
};
}
The data returned in the "result" hash is the following:
result->{skew} the clock skew;
result->{skewjitter} the variance of the skew estimate, used to estimate convergence;
result->{jitter} difference between the current delay and the previous delay;
result->{delay} the communication delay, decremented by a constant (yet unknown) value, used to compute communication jitter;
result->{elems} the number of data points in the convex hull;
result->{select} the index of the data point in the convex hull used to compute the skew;
result->{itimestamp} the timestamp, first element in the data point just passed to the subroutine;
result->{delta} the timestamp difference, second element in the data point just passed to the subroutine;
The data returned in the "hull" stack is a series of data points, selected from those passed to successive calls of the subroutine. The number of data points in the "hull" stack usually does not exceed 20 units.
The algorithm is very fast: each call consists in scanning at most all data points in the "hull" stack, performing simple arithmetic operations for each element.
The algorithm must be fed with a sequence of data points before returning significant results. The accuracy of the estimate keeps growing while new data points are passed to the subroutine. A rough rule of thumb to evaluate estimate accuracy is to observe the skew jitter, and assume it corresponds to the skew estimate accuracy. Paths with quite regular communication delay (small jitter) converge faster.
<<lessSYNOPISI
use Time::Skew
# Init Convex Hull and timing data
my $hull=[];
my $result={};
# Iterate data point introduction
Time::Skew::convexhull($result,$datapoint,$hull);
This module supports the computation of the skew between two clocks: the (relative) skew is the speed with which two clocks diverge. For instance, if yesterday two clocks, at the same time, showed respectively 10:00 and 10:05, while today when the former shows 10:00 the latter shows 10:04, we say that their relative skew is 1 minute/24 hours, roughly 7E-4.
The module contains one single subroutine, which accepts as input a pair of timestamps, associated to a message from host A to host B: the timestamps correspond to the time when the message was sent, and to the time when message is received. Each timestamp reflects the value of the local clock where the operation takes place: the clock of host A for the send, the clock of B for the receive.
Please note that the module does _not_ contain any message exchange facility, but only the mathematics needed to perform the skew approximation, once timestamps are known.
The subroutine takes as argument:
a reference to a hash where values related to the timing of the network path from A to B;
a 2-elems array (a data point in the sequel) containing the timestamp of the receive event, and the differece between the send timestamp and the receive timestamp for one message;
a stack containing some data points, those that form the convex hull.
The usage is very simple, and is illustrated by the following example:
#!/usr/bin/perl -w
use strict;
use Time::Skew;
# Initialize data
my $hull=[];
my $result={};
while ( 1 ) {
# Exchange message and acquire a new data point
my $datapoint = acquire();
# Call the convexhull subroutine
Time::Skew::convexhull($result,$datapoint,$hull);
# After first message some results are still undefined
( defined $result->{skewjitter} ) || next;
# here you can use the results
};
}
The data returned in the "result" hash is the following:
result->{skew} the clock skew;
result->{skewjitter} the variance of the skew estimate, used to estimate convergence;
result->{jitter} difference between the current delay and the previous delay;
result->{delay} the communication delay, decremented by a constant (yet unknown) value, used to compute communication jitter;
result->{elems} the number of data points in the convex hull;
result->{select} the index of the data point in the convex hull used to compute the skew;
result->{itimestamp} the timestamp, first element in the data point just passed to the subroutine;
result->{delta} the timestamp difference, second element in the data point just passed to the subroutine;
The data returned in the "hull" stack is a series of data points, selected from those passed to successive calls of the subroutine. The number of data points in the "hull" stack usually does not exceed 20 units.
The algorithm is very fast: each call consists in scanning at most all data points in the "hull" stack, performing simple arithmetic operations for each element.
The algorithm must be fed with a sequence of data points before returning significant results. The accuracy of the estimate keeps growing while new data points are passed to the subroutine. A rough rule of thumb to evaluate estimate accuracy is to observe the skew jitter, and assume it corresponds to the skew estimate accuracy. Paths with quite regular communication delay (small jitter) converge faster.
Download (0.044MB)
Added: 2007-04-10 License: Perl Artistic License Price:
927 downloads
i.File 0.2 Alpha
i.File is a file manager for Linux written for the Windows refugees that are arriving in Linux. more>>
i.File is a file manager for Linux written for the Windows refugees that are arriving in Linux only to find that the state of the user interface is rather poor. I personally somewhat fall into this catagory, although more as a power user than the average Joe.
Both the leading file managers for KDE and Gnome are well... not to put too fine a point on it: crap. There are just not ready for everyday use by normal people, because of the untold number of bugs in the usability and function that are STILL there 3 years after they first infested Linux desktops.
Not that this project will start off any better, but my hope is that itll end far more successfully than the aforementioned software. i.File project is targetted at other developers in an attempt to get some help with bringing it up to speed. Enough of the basic code layout and implementation is done so that the user can see how things should work. And now its just time to fill in the blanks and bust those bugs.
Main features:
- Be fast. i.File doesnt load icons for every file by its mime type. Because that takes too long. All the algorithms are designed to make it fast. The use of hashtables is pervasive. At no point should "eye candy" ever take precedence over speed. Startup/shutdown time should be sub-second. Drag and drop should have latencies around 100ms at most.
- All views of the same inode (file/dir/etc) point back to the same object, thus when the object changes, all views of that automatically update.
- Network accesses and all other tasks that can take time should be threaded. There is no excuse for locking up the GUI thread while the application goes off to get some data.
- Be minimal. i.File is not a thumb nail viewer, or any other type of viewer. Applications do the viewing, not the file manager. Viewing tasks bloat up the file manager.
- Every file is typed with a mime type. This is marginally better than using a files extension to associate it with an application.
- The Win2k implementation of Windows Explorer is the basis for some of the user interface because it works, people are used to it, and its "the standard". And no the experiments with file manager UI in Linux didnt work. They suck badly, thats why there is i.File in the first place.
<<lessBoth the leading file managers for KDE and Gnome are well... not to put too fine a point on it: crap. There are just not ready for everyday use by normal people, because of the untold number of bugs in the usability and function that are STILL there 3 years after they first infested Linux desktops.
Not that this project will start off any better, but my hope is that itll end far more successfully than the aforementioned software. i.File project is targetted at other developers in an attempt to get some help with bringing it up to speed. Enough of the basic code layout and implementation is done so that the user can see how things should work. And now its just time to fill in the blanks and bust those bugs.
Main features:
- Be fast. i.File doesnt load icons for every file by its mime type. Because that takes too long. All the algorithms are designed to make it fast. The use of hashtables is pervasive. At no point should "eye candy" ever take precedence over speed. Startup/shutdown time should be sub-second. Drag and drop should have latencies around 100ms at most.
- All views of the same inode (file/dir/etc) point back to the same object, thus when the object changes, all views of that automatically update.
- Network accesses and all other tasks that can take time should be threaded. There is no excuse for locking up the GUI thread while the application goes off to get some data.
- Be minimal. i.File is not a thumb nail viewer, or any other type of viewer. Applications do the viewing, not the file manager. Viewing tasks bloat up the file manager.
- Every file is typed with a mime type. This is marginally better than using a files extension to associate it with an application.
- The Win2k implementation of Windows Explorer is the basis for some of the user interface because it works, people are used to it, and its "the standard". And no the experiments with file manager UI in Linux didnt work. They suck badly, thats why there is i.File in the first place.
Download (0.78MB)
Added: 2006-01-18 License: Freeware Price:
1378 downloads
GD::Thumbnail 1.01
GD::Thumbnail is a thumbnail maker for GD. more>>
GD::Thumbnail is a thumbnail maker for GD.
SYNOPSIS
use GD::Thumbnail;
my $thumb = GD::Thumbnail->new;
my $raw = $thumb->create(test.jpg, 80, 2);
my $mime = $thumb->mime;
warn sprintf "Dimension: %sx%sn", $thumb->width, $thumb->height;
open IMG, ">thumb.$mime" or die "Error: $!";
binmode IMG;
print IMG $raw;
close IMG;
or
use CGI qw(:standard);
use GD::Thumbnail;
my $thumb = GD::Thumbnail->new;
my $raw = $thumb->create(test.jpg, 80, 2);
my $mime = $thumb->mime;
binmode STDOUT;
print header(-type => "image/$mime");
print $raw;
This a thumbnail maker. Thumbnails are smaller versions of the original image/graphic/picture and are used for preview purposes, where bigger images can take a long time to load. They are also used in image galleries to preview a lot of images at a time.
This module also has the capability to add information strips about the original image. Original images size (in bytes) and resolution & mime type can be added to the thumbnails upper and lower parts. This feature can be useful for web software (image galleries or forums).
This is a Yet Another type of module. There are several other thumbnail modules on CPAN, but they simply dont have the features I need, so this module is written to increase the thumbnail population on CPAN.
The module can raise an exception if something goes wrong. So, you may have to use an eval block to catch them.
<<lessSYNOPSIS
use GD::Thumbnail;
my $thumb = GD::Thumbnail->new;
my $raw = $thumb->create(test.jpg, 80, 2);
my $mime = $thumb->mime;
warn sprintf "Dimension: %sx%sn", $thumb->width, $thumb->height;
open IMG, ">thumb.$mime" or die "Error: $!";
binmode IMG;
print IMG $raw;
close IMG;
or
use CGI qw(:standard);
use GD::Thumbnail;
my $thumb = GD::Thumbnail->new;
my $raw = $thumb->create(test.jpg, 80, 2);
my $mime = $thumb->mime;
binmode STDOUT;
print header(-type => "image/$mime");
print $raw;
This a thumbnail maker. Thumbnails are smaller versions of the original image/graphic/picture and are used for preview purposes, where bigger images can take a long time to load. They are also used in image galleries to preview a lot of images at a time.
This module also has the capability to add information strips about the original image. Original images size (in bytes) and resolution & mime type can be added to the thumbnails upper and lower parts. This feature can be useful for web software (image galleries or forums).
This is a Yet Another type of module. There are several other thumbnail modules on CPAN, but they simply dont have the features I need, so this module is written to increase the thumbnail population on CPAN.
The module can raise an exception if something goes wrong. So, you may have to use an eval block to catch them.
Download (0.025MB)
Added: 2006-08-25 License: Perl Artistic License Price:
1158 downloads
chaplin 1.10
chaplin is a dvd chapter tool for Linux (and all other *ixes with libdvdread support). more>>
chaplin is a dvd chapter tool for Linux (and all other *ixes with libdvdread support).
The tool parses a DVD disc or image and extracts the exact duration for each chapter of a given title. Then the total list of chapters is split into a user-selectable number of subsets. Each subset should have approximately the same duration.
This is a very useful approach for multi-cd rips. You no longer simply split the movie in the middle of the frame count but you choose two sets of chapters for both parts which both have (almost) the same length. Then the disc-break is not at a rather random point (concering the story telling of the movie) but at the end of a dvd-chapter.
The chapter timings and the split sets are also very useful for chapter navigation (even on a single disc). The normal output mode of chaplin thus prints the chapters relative beginning time and the duration in a wide number of formats, ranging from seconds, frame counts to timestamps.
For S/VCD mastering chaplin can also produce vcdimager XML files for each disc. There a complete sequence structure with chapter entry points is defined. Also the full navigation setup for chapter hopping is provided. Additionally you can add chapter menus and automatically create the necessary menu pages out of thumbnails extracted directly from the DVD.
Installation:
You will need the libdvdread library for this tool. Specify its installation path in the provided Makefile. Then a simple call to "make" should build the chaplin binary. Copy the binary into your PATH. It is very useful to have transcode and vcdimager installed. The chaplin-genmenu tool needs transcode, ImageMagick and the mjpegtools.
Usage
Simple Usage
Just call chaplin the following way:
chaplin -d < dvd_path > -t < title >
This will display a chapter summary and places all chapters into a single subset (the default). This is useful for a single cd transfer. For multi-cd targets you specify the number of subsets with the -p option:
chaplin -d < dvd_path > -t < title > -p 2
This will divide the chapters up into 2 subsets. They should have almost the same size (this depends largely on the granularity of the provided chapters). Now you know which chapters fit on the first disc, know the exact frame count and you can calculate the exact bitrate for this part and finally transcode each part.
Chapter Info
Detailed info on the chapters is also available. Just add the -c option and per chapter info is printed:
chaplin ... -c
The standard output mode prints the relative offset of each chapter in the part. With the -l option you can replace this display with the length of each chapter.
S/VCD Mastering
If your target is a set of S/VCDs then the -x option is very useful:
chaplin ... -x MYMOVIE
MYMOVIE is the basename of the VCDs.
This option generates a XML S/VCD description for vcdimager which contains the exact chapter setup found by chaplin. The XML files are called "vcdNN.xml" and are created in the current directory. Name the MPEG files made from each subset "partNN.mpg" and place them in the same directory (NN=part number). Now a call to:
vcdxbuild vcdNN.xml
should generate a SVCD image with chapters and navigation information.
You can control the XML generation by passing suboptions to -x:
chaplin ... -x MYMOVIE,vcd,my%02d.xml,movie%02.mpg
This will generate VCD 2.0 XML files called myNN.xml and refers to MPEG movie files called movieNN.mpg. Do not forget to include a "%d" expression in the XML and MPEG file patterns. This will be replaced by the current part number. Numbering starts with one by default. Chaplin will begin with zero if you pass the -z option.
The second argument defines the type of the disc: vcd or svcd.
S/VCD Chapter Menus
Since version 1.9 chaplin also supports the creation of XML mastering files for S/VCDs with chapter menus. Add the -m option to -x to enable menu creation. You have to specify how many chapters are selectable on each menu page. chaplin will then create a menu page set for each of the selected parts and each menu page will contain at most the given number of entries:
chaplin ... -x MYMOVIE,svcd,my%02d.xml,movie%02.mpg,menu%02d-%d.mpg -m 6
In this example menu pages with up to six entries are created and labeled menu%02d-%d.mpg. Note the two %d replacement tags in the menu file name. The first one is replaced with the current part number and the second one counts the menu pages for this part. The generated XML will create a SVCD that shows the first menu page and allows to select the first six chapters with the numeric buttons. Furthermore you can switch to the next menu page.
The referenced menu pages are MPEG files containing still images. Each menu page should depict the chapters that can be selected on this page. The menu pages can be rendered automatically with the chaplin-genmenu tool.
Automatic Chapter Menu Generation
The chaplin-genmenu script creates the chapter menu still image MPG files that are referenced in the S/VCD chapter menus. To guide this tool what should be rendered on each menu page, you have to create a chapling menu description with the -g command:
chaplin ... -x ... -m < n > -g menu.txt
Now have a look a the created menu description text file. Its splitted into blocks for each menu page:
chaplin-menu 9
dvd "/dev/dvd" title 10 PAL 4:3
menu01-1.mpg 9 Part 1 Menu 1
01 0 Chapter 1
02 0 Chapter 2
03 0 Chapter 3
04 0 Chapter 4
05 0 Chapter 5
06 0 Chapter 6
07 0 Chapter 7
08 0 Chapter 8
09 0 Chapter 9
menu01-2.mpg 6 Part 1 Menu 2
10 0 Chapter 10
11 0 Chapter 11
12 0 Chapter 12
13 0 Chapter 13
14 0 Chapter 14
15 0 Chapter 15
The description contains the menu files to create and the chapters that are referenced on each page. You can edit this file to change the sample frame for each chapter that will be extracted to get the thumbnail image on the menu page: change the 0 value in the second column to the requested frame number. Finally you can edit the text that gets rendered on the menu pages: The title of each menu page is given in the title line (e.g.: "Part 1 Menu 1") and the chapter description after each frame number (e.g.: "Chapter 1").
Now run the menu page creator:
chaplin-genmenu menu.txt
This sets the dvd input device and title similar to the chaplin call and pass the generated chaplin menu description. This will create the MPG still images needed for S/VCD creation out of the XML file.
Specify -n NTSC if creating a NTSC and not a PAL S/VCD. Use -v if creating a VCD and not a SVCD.
With -o you can set a global offset for each chapter sample frame number. The -u option cleans up all temporary files created during program call. -x will display all external command calls to debug the tool.
With -b, -l and -f you can adjust the rendering of the menu pages.
Note that chaplin-genmenu is an incremental tool that only creates files that are not yet existing in the current path. So you can first call the tool (without -u) to create all intermediate files. Then you can retouch or repaint the menu PNG files and call the tool again to build MPG files. If you pass the -c switch then all files are recreated always.
Enhancements:
- fixed crash in some parts calculations
- output some video attributes in verbose mode
- new menu.txt format now passes all important parameters
- (dvd device, title, tvnorm and aspect ratio) automatically
- chaplin-genmenu:
- improved menu layout creation (hinted by S. Stordal)
- manual layout setup with -m option
- now reads all important parameters from chaplin directly
- thumbs now have correct aspect ratio
- default frame offset is now 16 (to skip partial gops)
- new switch -c allows to always recreate files
- new switch -s sets the font size
- renamed switches to be more consistent
<<lessThe tool parses a DVD disc or image and extracts the exact duration for each chapter of a given title. Then the total list of chapters is split into a user-selectable number of subsets. Each subset should have approximately the same duration.
This is a very useful approach for multi-cd rips. You no longer simply split the movie in the middle of the frame count but you choose two sets of chapters for both parts which both have (almost) the same length. Then the disc-break is not at a rather random point (concering the story telling of the movie) but at the end of a dvd-chapter.
The chapter timings and the split sets are also very useful for chapter navigation (even on a single disc). The normal output mode of chaplin thus prints the chapters relative beginning time and the duration in a wide number of formats, ranging from seconds, frame counts to timestamps.
For S/VCD mastering chaplin can also produce vcdimager XML files for each disc. There a complete sequence structure with chapter entry points is defined. Also the full navigation setup for chapter hopping is provided. Additionally you can add chapter menus and automatically create the necessary menu pages out of thumbnails extracted directly from the DVD.
Installation:
You will need the libdvdread library for this tool. Specify its installation path in the provided Makefile. Then a simple call to "make" should build the chaplin binary. Copy the binary into your PATH. It is very useful to have transcode and vcdimager installed. The chaplin-genmenu tool needs transcode, ImageMagick and the mjpegtools.
Usage
Simple Usage
Just call chaplin the following way:
chaplin -d < dvd_path > -t < title >
This will display a chapter summary and places all chapters into a single subset (the default). This is useful for a single cd transfer. For multi-cd targets you specify the number of subsets with the -p option:
chaplin -d < dvd_path > -t < title > -p 2
This will divide the chapters up into 2 subsets. They should have almost the same size (this depends largely on the granularity of the provided chapters). Now you know which chapters fit on the first disc, know the exact frame count and you can calculate the exact bitrate for this part and finally transcode each part.
Chapter Info
Detailed info on the chapters is also available. Just add the -c option and per chapter info is printed:
chaplin ... -c
The standard output mode prints the relative offset of each chapter in the part. With the -l option you can replace this display with the length of each chapter.
S/VCD Mastering
If your target is a set of S/VCDs then the -x option is very useful:
chaplin ... -x MYMOVIE
MYMOVIE is the basename of the VCDs.
This option generates a XML S/VCD description for vcdimager which contains the exact chapter setup found by chaplin. The XML files are called "vcdNN.xml" and are created in the current directory. Name the MPEG files made from each subset "partNN.mpg" and place them in the same directory (NN=part number). Now a call to:
vcdxbuild vcdNN.xml
should generate a SVCD image with chapters and navigation information.
You can control the XML generation by passing suboptions to -x:
chaplin ... -x MYMOVIE,vcd,my%02d.xml,movie%02.mpg
This will generate VCD 2.0 XML files called myNN.xml and refers to MPEG movie files called movieNN.mpg. Do not forget to include a "%d" expression in the XML and MPEG file patterns. This will be replaced by the current part number. Numbering starts with one by default. Chaplin will begin with zero if you pass the -z option.
The second argument defines the type of the disc: vcd or svcd.
S/VCD Chapter Menus
Since version 1.9 chaplin also supports the creation of XML mastering files for S/VCDs with chapter menus. Add the -m option to -x to enable menu creation. You have to specify how many chapters are selectable on each menu page. chaplin will then create a menu page set for each of the selected parts and each menu page will contain at most the given number of entries:
chaplin ... -x MYMOVIE,svcd,my%02d.xml,movie%02.mpg,menu%02d-%d.mpg -m 6
In this example menu pages with up to six entries are created and labeled menu%02d-%d.mpg. Note the two %d replacement tags in the menu file name. The first one is replaced with the current part number and the second one counts the menu pages for this part. The generated XML will create a SVCD that shows the first menu page and allows to select the first six chapters with the numeric buttons. Furthermore you can switch to the next menu page.
The referenced menu pages are MPEG files containing still images. Each menu page should depict the chapters that can be selected on this page. The menu pages can be rendered automatically with the chaplin-genmenu tool.
Automatic Chapter Menu Generation
The chaplin-genmenu script creates the chapter menu still image MPG files that are referenced in the S/VCD chapter menus. To guide this tool what should be rendered on each menu page, you have to create a chapling menu description with the -g command:
chaplin ... -x ... -m < n > -g menu.txt
Now have a look a the created menu description text file. Its splitted into blocks for each menu page:
chaplin-menu 9
dvd "/dev/dvd" title 10 PAL 4:3
menu01-1.mpg 9 Part 1 Menu 1
01 0 Chapter 1
02 0 Chapter 2
03 0 Chapter 3
04 0 Chapter 4
05 0 Chapter 5
06 0 Chapter 6
07 0 Chapter 7
08 0 Chapter 8
09 0 Chapter 9
menu01-2.mpg 6 Part 1 Menu 2
10 0 Chapter 10
11 0 Chapter 11
12 0 Chapter 12
13 0 Chapter 13
14 0 Chapter 14
15 0 Chapter 15
The description contains the menu files to create and the chapters that are referenced on each page. You can edit this file to change the sample frame for each chapter that will be extracted to get the thumbnail image on the menu page: change the 0 value in the second column to the requested frame number. Finally you can edit the text that gets rendered on the menu pages: The title of each menu page is given in the title line (e.g.: "Part 1 Menu 1") and the chapter description after each frame number (e.g.: "Chapter 1").
Now run the menu page creator:
chaplin-genmenu menu.txt
This sets the dvd input device and title similar to the chaplin call and pass the generated chaplin menu description. This will create the MPG still images needed for S/VCD creation out of the XML file.
Specify -n NTSC if creating a NTSC and not a PAL S/VCD. Use -v if creating a VCD and not a SVCD.
With -o you can set a global offset for each chapter sample frame number. The -u option cleans up all temporary files created during program call. -x will display all external command calls to debug the tool.
With -b, -l and -f you can adjust the rendering of the menu pages.
Note that chaplin-genmenu is an incremental tool that only creates files that are not yet existing in the current path. So you can first call the tool (without -u) to create all intermediate files. Then you can retouch or repaint the menu PNG files and call the tool again to build MPG files. If you pass the -c switch then all files are recreated always.
Enhancements:
- fixed crash in some parts calculations
- output some video attributes in verbose mode
- new menu.txt format now passes all important parameters
- (dvd device, title, tvnorm and aspect ratio) automatically
- chaplin-genmenu:
- improved menu layout creation (hinted by S. Stordal)
- manual layout setup with -m option
- now reads all important parameters from chaplin directly
- thumbs now have correct aspect ratio
- default frame offset is now 16 (to skip partial gops)
- new switch -c allows to always recreate files
- new switch -s sets the font size
- renamed switches to be more consistent
Download (0.023MB)
Added: 2006-05-26 License: GPL (GNU General Public License) Price:
1246 downloads
rdigikam 0.2
rdigikam is a flickr like interface to Digikam. more>>
rdigikam is a flickr like interface to Digikam.
Main features:
- tags navigation
- album navigation
- date navigation with a calendar page
- cool iPhoto like zooming effect
To install follow these steps:
as root, you need to run:
gem install sqlite3-ruby
gem install rmagick
gem install calendar_grid
calendar_grid can be found here http://rubyforge.org/frs/?group_id=786
Once youve got all that installed:
uncompress the tarball, that should give you another tarball and a bash script script
run the script ./setup.sh as normal user
Ok now youre almost done:
edit the file rdigikam/app/helpers/application_helper.rb
edit the two variables on top. You might have something like:
@rdigikampath="/home/user/rdigikam-0.1/rdigikam" if you uncompressed the original tarball in your home.
and @mydigikampath="/home/user/Pictures"
Usage:
cd rdigikam
script/server
then open your browser to http://localhost:3000/tags
Enhancements:
- small UI improvement on Mozilla, now the tag list appear below the two navigation thumbs just like in konq
<<lessMain features:
- tags navigation
- album navigation
- date navigation with a calendar page
- cool iPhoto like zooming effect
To install follow these steps:
as root, you need to run:
gem install sqlite3-ruby
gem install rmagick
gem install calendar_grid
calendar_grid can be found here http://rubyforge.org/frs/?group_id=786
Once youve got all that installed:
uncompress the tarball, that should give you another tarball and a bash script script
run the script ./setup.sh as normal user
Ok now youre almost done:
edit the file rdigikam/app/helpers/application_helper.rb
edit the two variables on top. You might have something like:
@rdigikampath="/home/user/rdigikam-0.1/rdigikam" if you uncompressed the original tarball in your home.
and @mydigikampath="/home/user/Pictures"
Usage:
cd rdigikam
script/server
then open your browser to http://localhost:3000/tags
Enhancements:
- small UI improvement on Mozilla, now the tag list appear below the two navigation thumbs just like in konq
Download (0.068MB)
Added: 2006-09-03 License: GPL (GNU General Public License) Price:
1146 downloads
Image Tree 1.0
Image Tree is a complete and versatile photo publishing system in less than 200 lines of code. more>>
Image Tree is a complete and versatile photo publishing system in less than 200 lines of code.
ImgTree is based only on three files:
index php : contains all the php and html code. Must be put, unmodified in every folder of the directory tree.
data.php : contains the specific settings of every folder
style.css : the css style sheet
Every folder of the folder tree must contain the three files. Clearly index.php and style.php should be simply linked:
imgtree/
|-- data.php
|-- index.php
|-- style.css
|-- Section-A
| |-- data.php
| |-- index.php -> ../index.php
| |-- style.css -> ../style.css
| |-- 01-thumb.jpg
| |-- 01.jpg
| |-- 02-thumb.jpg
| |-- 02.jpg
| `-- ...
`-- Section-B
|-- data.php
|-- index.php -> ../index.php
|-- style.css -> ../style.css
|-- 00.jpg
|-- Subsection-B1
| |-- data.php
| |-- index.php -> ../index.php
| `-- style.css -> ../style.css
| |-- cover.jpg
`-- Subsection-B2
|-- data.php
|-- index.php -> ../index.php
|-- style.css -> ../style.css
|-- 01-thumb.jpg
|-- 01.jpg
|-- 02-thumb.jpg
|-- 02.jpg
`-- ...
Every folder act as a section and the behaviour can be choose between:
index : Contains a list of links to every subfolder of the current folder. For every section an image and a description are shown.
thumb : Thumbnails page. Shows every image file of the folder. Thumbnail must be named "xxx-thumb.jpg" for the xxx.jpg file. Ex: 01-thumb.jpg -> 01.jpg ; tramonto-thumb.jpg -> tramonto.jpg ; ecc.
cover : Cover page. Shows an image, a text and an associated link
The file data.php contin the settings specific for every section:
$gallerystart : is the gallery start to generate the back-menu. The path must be relative to the starting folder of the site
$name : name used to link the current section in the menus
$title : page title
$description: description, used as subtitle and for brief description in index pages
$indeximage : image used in index pages to link this section
$type : type of the page (cover|thumb|index)
$imgtitle : associtive array of the images descriptions. Used only by "thumb" pages
$coverimage : image used by "cover" pages
$covertext : text used by "cover" pages
$coverlink= : link used by "cover" pages
$covertitle : title used by "cover" pages
NEEDS a web server (Apache or similar) with PHP support
<<lessImgTree is based only on three files:
index php : contains all the php and html code. Must be put, unmodified in every folder of the directory tree.
data.php : contains the specific settings of every folder
style.css : the css style sheet
Every folder of the folder tree must contain the three files. Clearly index.php and style.php should be simply linked:
imgtree/
|-- data.php
|-- index.php
|-- style.css
|-- Section-A
| |-- data.php
| |-- index.php -> ../index.php
| |-- style.css -> ../style.css
| |-- 01-thumb.jpg
| |-- 01.jpg
| |-- 02-thumb.jpg
| |-- 02.jpg
| `-- ...
`-- Section-B
|-- data.php
|-- index.php -> ../index.php
|-- style.css -> ../style.css
|-- 00.jpg
|-- Subsection-B1
| |-- data.php
| |-- index.php -> ../index.php
| `-- style.css -> ../style.css
| |-- cover.jpg
`-- Subsection-B2
|-- data.php
|-- index.php -> ../index.php
|-- style.css -> ../style.css
|-- 01-thumb.jpg
|-- 01.jpg
|-- 02-thumb.jpg
|-- 02.jpg
`-- ...
Every folder act as a section and the behaviour can be choose between:
index : Contains a list of links to every subfolder of the current folder. For every section an image and a description are shown.
thumb : Thumbnails page. Shows every image file of the folder. Thumbnail must be named "xxx-thumb.jpg" for the xxx.jpg file. Ex: 01-thumb.jpg -> 01.jpg ; tramonto-thumb.jpg -> tramonto.jpg ; ecc.
cover : Cover page. Shows an image, a text and an associated link
The file data.php contin the settings specific for every section:
$gallerystart : is the gallery start to generate the back-menu. The path must be relative to the starting folder of the site
$name : name used to link the current section in the menus
$title : page title
$description: description, used as subtitle and for brief description in index pages
$indeximage : image used in index pages to link this section
$type : type of the page (cover|thumb|index)
$imgtitle : associtive array of the images descriptions. Used only by "thumb" pages
$coverimage : image used by "cover" pages
$covertext : text used by "cover" pages
$coverlink= : link used by "cover" pages
$covertitle : title used by "cover" pages
NEEDS a web server (Apache or similar) with PHP support
Download (0.033MB)
Added: 2006-09-11 License: GPL (GNU General Public License) Price:
1139 downloads
PhreakPic Beta
PhreakPic project is a Web gallery designed for any kind of content that can be displayed visually. more>>
PhreakPic project is a Web gallery designed for any kind of content that can be displayed visually.
The content can be sorted into multiple (sub)cateogries.
Thumbnails are generated automatically, and it has several methods to add new content.
Every function can be managed through an access-control system, and all functions are accessible through the Web interface.
It uses the userbase of an existing phpBB2 installation and the Smarty template system.
Main features:
- Categories and unlimited sub-categories
- Detailed Rightsmanagment
- Categories and Subcategories
- Threaded Comments for every category, content and serie
- Template System (Smarty)
- It can log how long someone stays at a picture (BigBrother Feature)
- Its easy to implement other filetypes (e.g. Movies)
- You can create almost unlimited possibilities of searches, through costumizalbe sql queries (e.g. New Pictures/Comments, Most viewed pictures,...)(No Admin interface yet)
- PhreakPic uses the phpBB2 usermanagement, so you have no redundant userdatabase (it should be possible to use other userbases as well)
- And standard stugg like generating thumbnails
Enhancements:
- Added recursive change of groups
- Merged catand contentgroups
- Cleaned up ACP
- Date at comments now follow the dateformat of phpBB
- Added current picture and thread to the write comment page
- Added Thumbs per page selector
- Added content basket
- Added download for content basket
- Added user profile configuration
- Added basket page
- Child content amount now saved in db (for performance)
- Comments amount saved in db (for performace)
- added phpBB avatars to the comments
- fixed problem when a picture was in thumb view several times
- made nav bar an include
- added phpBB2 avatar to comments
- added possibility the change parent cat of cat
- change group of a cat
- edit comments
- some exif informations
- added rights management for adding and removing user to usergroups
- created UCP
<<lessThe content can be sorted into multiple (sub)cateogries.
Thumbnails are generated automatically, and it has several methods to add new content.
Every function can be managed through an access-control system, and all functions are accessible through the Web interface.
It uses the userbase of an existing phpBB2 installation and the Smarty template system.
Main features:
- Categories and unlimited sub-categories
- Detailed Rightsmanagment
- Categories and Subcategories
- Threaded Comments for every category, content and serie
- Template System (Smarty)
- It can log how long someone stays at a picture (BigBrother Feature)
- Its easy to implement other filetypes (e.g. Movies)
- You can create almost unlimited possibilities of searches, through costumizalbe sql queries (e.g. New Pictures/Comments, Most viewed pictures,...)(No Admin interface yet)
- PhreakPic uses the phpBB2 usermanagement, so you have no redundant userdatabase (it should be possible to use other userbases as well)
- And standard stugg like generating thumbnails
Enhancements:
- Added recursive change of groups
- Merged catand contentgroups
- Cleaned up ACP
- Date at comments now follow the dateformat of phpBB
- Added current picture and thread to the write comment page
- Added Thumbs per page selector
- Added content basket
- Added download for content basket
- Added user profile configuration
- Added basket page
- Child content amount now saved in db (for performance)
- Comments amount saved in db (for performace)
- added phpBB avatars to the comments
- fixed problem when a picture was in thumb view several times
- made nav bar an include
- added phpBB2 avatar to comments
- added possibility the change parent cat of cat
- change group of a cat
- edit comments
- some exif informations
- added rights management for adding and removing user to usergroups
- created UCP
Download (MB)
Added: 2006-09-14 License: GPL (GNU General Public License) Price:
1136 downloads
ROX-Filer 2.6.1
ROX-Filer is a drag-and-drop based filemanager. more>>
ROX-Filer is a fast and powerful graphical file manager for the X Window System.
You can use ROX-Filer as a small and fast filer within your current desktop......or get it to manage your pinboard, panels and applications.
Main features:
- Fast scanning of directories (in the background),
- Uncluttered display (popup menus are used throughout),
- Background file operations (copy, move, link, delete, permissions, find),
- Powerful expression-based find feature with on-line quick reference (eg mtime after 2 days ago and size > 10Mb finds files based on their modification time and size)
- Mounts and unmounts filesystems (just Shift-Click on the mount point),
- Supports the XDND protocol, which provides for drag-and-drop file loading, and the new XDS extension which allows drag-and-drop saving,
- VfS support allows browsing around inside zip files (and other types of archive),
- Fully configurable from the Options dialog box,
- User-defined key bindings for all menu entries,
- A pop-up minibuffer allows navigating the filesystem using shell-style tab completion,
- The minibuffer can also be used for quickly entering shell commands,
- Full manual provided (HTML format),
Other features:
XDND
A common drag-and-drop protocol used, for example, by the GNOME desktop[GNOME]. This allows data to be loaded into an application by dragging it from a filer window to a program. The full specification is given in [DND].
XDS
An extension to XDND that allows applications to save data by dragging an icon back to a filer window. The full specification is given in [XDS].
Choices
A simple, but flexible, system for managing user choices. See [Choices] for details.
Application directories
Self contained relocatable applications, where installation is as simple as copying it to where you want it and uninstalling it is just a matter of deleting a directory. Described later in this documentation.
Thumbnails
The filer can be made to display image files by using the image itself for the icon, instead of a generic `this-is-an-image icon. Very useful for organising a directory full of photos! See [Thumbs] for details (spec is still in developement).
Shared MIME Info Database
In the past, each desktop had its own database of rules for determining the type of files. The Shared MIME Info Database[SharedMIME] unifies these into a single system shared by all desktops.
Icon Themes
Collections of file icons, called themes, can be installed (eg, to `~/.icons). You can switch between themes in the Options box. Once other desktops support this fully, themes will be sharable between desktops.
DNotify support (Linux only)
If used with a recent Linux kernel (2.4.x series), the filer will notice changes to directories automatically. On other systems, directories will update when the pointer is moved over them.
Enhancements:
- Some problems with session management were fixed.
- This makes it easier to use ROX-Filer with gnome-session and similar software.
- When creating thumbnails, this release can use a thumbnail embedded in an EXIF image, which speeds things up.
- A couple of build problems were fixed.
<<lessYou can use ROX-Filer as a small and fast filer within your current desktop......or get it to manage your pinboard, panels and applications.
Main features:
- Fast scanning of directories (in the background),
- Uncluttered display (popup menus are used throughout),
- Background file operations (copy, move, link, delete, permissions, find),
- Powerful expression-based find feature with on-line quick reference (eg mtime after 2 days ago and size > 10Mb finds files based on their modification time and size)
- Mounts and unmounts filesystems (just Shift-Click on the mount point),
- Supports the XDND protocol, which provides for drag-and-drop file loading, and the new XDS extension which allows drag-and-drop saving,
- VfS support allows browsing around inside zip files (and other types of archive),
- Fully configurable from the Options dialog box,
- User-defined key bindings for all menu entries,
- A pop-up minibuffer allows navigating the filesystem using shell-style tab completion,
- The minibuffer can also be used for quickly entering shell commands,
- Full manual provided (HTML format),
Other features:
XDND
A common drag-and-drop protocol used, for example, by the GNOME desktop[GNOME]. This allows data to be loaded into an application by dragging it from a filer window to a program. The full specification is given in [DND].
XDS
An extension to XDND that allows applications to save data by dragging an icon back to a filer window. The full specification is given in [XDS].
Choices
A simple, but flexible, system for managing user choices. See [Choices] for details.
Application directories
Self contained relocatable applications, where installation is as simple as copying it to where you want it and uninstalling it is just a matter of deleting a directory. Described later in this documentation.
Thumbnails
The filer can be made to display image files by using the image itself for the icon, instead of a generic `this-is-an-image icon. Very useful for organising a directory full of photos! See [Thumbs] for details (spec is still in developement).
Shared MIME Info Database
In the past, each desktop had its own database of rules for determining the type of files. The Shared MIME Info Database[SharedMIME] unifies these into a single system shared by all desktops.
Icon Themes
Collections of file icons, called themes, can be installed (eg, to `~/.icons). You can switch between themes in the Options box. Once other desktops support this fully, themes will be sharable between desktops.
DNotify support (Linux only)
If used with a recent Linux kernel (2.4.x series), the filer will notice changes to directories automatically. On other systems, directories will update when the pointer is moved over them.
Enhancements:
- Some problems with session management were fixed.
- This makes it easier to use ROX-Filer with gnome-session and similar software.
- When creating thumbnails, this release can use a thumbnail embedded in an EXIF image, which speeds things up.
- A couple of build problems were fixed.
Download (1.8MB)
Added: 2007-06-10 License: GPL (GNU General Public License) Price:
869 downloads
Inferno Operating System 20060303
Inferno is a compact operating system designed for building distributed and networked systems on a wide variety of devices. more>>
Inferno is a compact operating system designed for building distributed and networked systems on a wide variety of devices and platforms.
Inferno was originally developed at Bell Labs (the research division of Lucent Technologies).
Inferno Operating System is a well-designed, economical operating system particularly suitable for use in networked devices such as advanced telephones, hand-held devices, TV set-top boxes, and many other embedded applications.
Inferno can run in native mode on an embedded system or in emulation mode under many different operating systems. Inferno has many features in common with Plan 9.
Cross-Platform Portability
Inferno can run as a user application on top of an existing operating system or as a stand alone operating system. Most of the popular operating systems and processor architectures are supported:
Host Operating Systems:
- Windows NT/2000/XP
- Irix
- Linux
- MacOS X
- FreeBSD
- Solaris
- Plan 9
Supported Architectures:
- Intel x86 (386 & higher)
- Intel XScale
- IBM PowerPC
- ARM StrongARM (ARM & Thumb)
- Sun SPARC
Inferno also runs as a plug-in under Internet Explorer version 4 and higher. Each Inferno system presents an identical environment to the applications, irrespective of the underlying host OS or architecture, allowing the developer to work with a truly homogeneous environment across multiple different platforms.
Portable Applications
Inferno applications are written in Limbo, a modern, safe, modular, concurrent programming language with C-like syntax. It is more powerful than C but considerably easier to understand and debug than C++ or Java. Limbo code is compiled into architecture independent byte code which is then interpreted (or compiled on the fly) on the target processor. This means that any Inferno application will run identically on all Inferno platforms.
Transparent Resources
Inferno offers complete transparency of resources and data using a simple but powerful namespace system. By representing resources as files and having one standard communication protocol, resources such as data stores, services and external devices can easily be shared between Inferno systems. A resource interface may be imported to the local system and used by the applications without them knowing, or needing to know, whether it is local or remote.
Security
High level security is an important part of the Inferno system. By using one standard protocol for all network communication, security can be focused on one point and provided at a system level. Inferno offers full support for authenticated, encrypted connections using a certificate based user identification scheme and variety of algorithms including:
- IDEA, 56 bit DES, 40, 128 and 256 bit RC4 encryption algorithms
- MD4, MD5 and SHA secure hash algorithms
A Complete Solution
Inferno is not only an operating system, it is also a complete development environment, providing all the tools necessary for creating, testing and debugging the applications that run within it.
- Acme IDE: includes editor, shell, advanced pattern matching tools & more
- Fast Compiler: with full syntax and compile time type checking
- Graphical Debugger: with full stack trace for currently executing threads
- Powerful Shell: with sophisticated scripting capabilities
- UNIX like commands: including bind, grep, gzip, mount, ps, tar, yacc...
Enhancements:
- New licence terms (a `dual licence scheme allowing use as Free Software)
- Styx revision based on 9P2000, and consequent changes to Sys
- Authentication changes
- Improved colour graphics support, including compositing
- Scalable fonts using Freetype
- Revamped Tk implementation
- Window management moved out of Tk to a separate window manager in Limbo
- Limbo: exception handling and fixed-point
- Limbo: other possible changes
- Dis VM changes
- More commands and library modules
- Better network service configuration
- /net/dns served by host and native DNS resolver
- Hosted kernels configured from a parts list as for native kernels
- Signed modules
- Internet Explorer plug-in revised and in source form
- Expanded documentation
<<lessInferno was originally developed at Bell Labs (the research division of Lucent Technologies).
Inferno Operating System is a well-designed, economical operating system particularly suitable for use in networked devices such as advanced telephones, hand-held devices, TV set-top boxes, and many other embedded applications.
Inferno can run in native mode on an embedded system or in emulation mode under many different operating systems. Inferno has many features in common with Plan 9.
Cross-Platform Portability
Inferno can run as a user application on top of an existing operating system or as a stand alone operating system. Most of the popular operating systems and processor architectures are supported:
Host Operating Systems:
- Windows NT/2000/XP
- Irix
- Linux
- MacOS X
- FreeBSD
- Solaris
- Plan 9
Supported Architectures:
- Intel x86 (386 & higher)
- Intel XScale
- IBM PowerPC
- ARM StrongARM (ARM & Thumb)
- Sun SPARC
Inferno also runs as a plug-in under Internet Explorer version 4 and higher. Each Inferno system presents an identical environment to the applications, irrespective of the underlying host OS or architecture, allowing the developer to work with a truly homogeneous environment across multiple different platforms.
Portable Applications
Inferno applications are written in Limbo, a modern, safe, modular, concurrent programming language with C-like syntax. It is more powerful than C but considerably easier to understand and debug than C++ or Java. Limbo code is compiled into architecture independent byte code which is then interpreted (or compiled on the fly) on the target processor. This means that any Inferno application will run identically on all Inferno platforms.
Transparent Resources
Inferno offers complete transparency of resources and data using a simple but powerful namespace system. By representing resources as files and having one standard communication protocol, resources such as data stores, services and external devices can easily be shared between Inferno systems. A resource interface may be imported to the local system and used by the applications without them knowing, or needing to know, whether it is local or remote.
Security
High level security is an important part of the Inferno system. By using one standard protocol for all network communication, security can be focused on one point and provided at a system level. Inferno offers full support for authenticated, encrypted connections using a certificate based user identification scheme and variety of algorithms including:
- IDEA, 56 bit DES, 40, 128 and 256 bit RC4 encryption algorithms
- MD4, MD5 and SHA secure hash algorithms
A Complete Solution
Inferno is not only an operating system, it is also a complete development environment, providing all the tools necessary for creating, testing and debugging the applications that run within it.
- Acme IDE: includes editor, shell, advanced pattern matching tools & more
- Fast Compiler: with full syntax and compile time type checking
- Graphical Debugger: with full stack trace for currently executing threads
- Powerful Shell: with sophisticated scripting capabilities
- UNIX like commands: including bind, grep, gzip, mount, ps, tar, yacc...
Enhancements:
- New licence terms (a `dual licence scheme allowing use as Free Software)
- Styx revision based on 9P2000, and consequent changes to Sys
- Authentication changes
- Improved colour graphics support, including compositing
- Scalable fonts using Freetype
- Revamped Tk implementation
- Window management moved out of Tk to a separate window manager in Limbo
- Limbo: exception handling and fixed-point
- Limbo: other possible changes
- Dis VM changes
- More commands and library modules
- Better network service configuration
- /net/dns served by host and native DNS resolver
- Hosted kernels configured from a parts list as for native kernels
- Signed modules
- Internet Explorer plug-in revised and in source form
- Expanded documentation
Download (57CrossPlMB)
Added: 2006-05-23 License: GPL (GNU General Public License) Price:
1258 downloads
Bookmarks Scrollbar 1.0.5
Bookmarks Scrollbar is an extension which adds a scrollbar to the bookmarks menu. more>>
Bookmarks Scrollbar is an extension which adds a scrollbar to the bookmarks menu.
A scrollbar is a graphical widget in a GUI with which continuous text, pictures or anything else can be scrolled including time in video applications, i.e., viewed even if it does not fit into the space in a computer display, window, or viewport.
Usually designed as a long rectangular area on one or two sides of the viewing area, containing a bar (or thumb) that can be dragged along a trough to move the body of the document as well as two arrows on either end for precise adjustments. The "thumb" has different names in different environments: on the Macintosh it is called a "thumb" on the Java platform it is called "thumb" or "knob"; Microsofts .NET documentation refers to it as "scroll box" or "scroll thumb"; in other environments it is called "elevator", "puck" or "wiper". Additional functions may be found, such as zooming in/out or various application-specific tools.
The thumb can also sometimes be adjusted by dragging its ends. In this case it would adjust both the position and the zooming of the document, where the size of the thumb represents the degree of zooming applied. A thumb that completely fills the trough, or "track" represents viewing the entire document, at which point the scrollbar may temporarily become hidden.
<<lessA scrollbar is a graphical widget in a GUI with which continuous text, pictures or anything else can be scrolled including time in video applications, i.e., viewed even if it does not fit into the space in a computer display, window, or viewport.
Usually designed as a long rectangular area on one or two sides of the viewing area, containing a bar (or thumb) that can be dragged along a trough to move the body of the document as well as two arrows on either end for precise adjustments. The "thumb" has different names in different environments: on the Macintosh it is called a "thumb" on the Java platform it is called "thumb" or "knob"; Microsofts .NET documentation refers to it as "scroll box" or "scroll thumb"; in other environments it is called "elevator", "puck" or "wiper". Additional functions may be found, such as zooming in/out or various application-specific tools.
The thumb can also sometimes be adjusted by dragging its ends. In this case it would adjust both the position and the zooming of the document, where the size of the thumb represents the degree of zooming applied. A thumb that completely fills the trough, or "track" represents viewing the entire document, at which point the scrollbar may temporarily become hidden.
Download (0.001MB)
Added: 2007-04-11 License: MPL (Mozilla Public License) Price:
931 downloads
Vinetto 0.07 Beta
Vinetto project is a forensics tool to examine Thumbs.db files. more>>
Vinetto project is a forensics tool to examine Thumbs.db files. The project is a command line python script that works on Linux, Mac OS X and Cygwin(win32).
Usage:
Usage: vinetto [OPTIONS] [-s] [-U] [-o DIR] file
options:
--version show programs version number and exit
-h, --help show this help message and exit
-o DIR write thumbnails to DIR
-H write html report to DIR
-U use utf8 encodings
-s create symlink of the image realname to the numbered name in
DIR/.thumbs
Metadata list will be written on standard output.
<<lessUsage:
Usage: vinetto [OPTIONS] [-s] [-U] [-o DIR] file
options:
--version show programs version number and exit
-h, --help show this help message and exit
-o DIR write thumbnails to DIR
-H write html report to DIR
-U use utf8 encodings
-s create symlink of the image realname to the numbered name in
DIR/.thumbs
Metadata list will be written on standard output.
Download (0.015MB)
Added: 2007-06-19 License: GPL (GNU General Public License) Price:
859 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above hitchhikers thumb search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
