Free matches history software for linux

Rails History Plugin is a Ruby on Rails plugin that stores user actions (i.e. URLs that the user has recently visited).
It avoids storage of POST and AJAX requests, and it provides a manual way to specify which actions not to store.
Installation:
Unpack into the vendor/plugin and that should be it.
Usage:
In your app/controllers/application_controller.rb, add a history line like this:
class ApplicationController < ActionController::Base
history :default => "http://default.url.com/",
:max => 10
end
The history function accepts a hash of options
:default, the default URL to redirect
:max, the maximum locations to remember (five by defaults).
None of the parameters are required. If somebody knows of a better way to obtain the default URL, he is welcomed to tell me how.
You can use the method history_skip in your controller if you want to avoid certain location to be stored in the history. By default, action resulting from a POST, PUT, DELETE request or an Ajax request are not stored in the history.
class FooController < ApplicationController
history_skip :action_to_skip
def action_to_skip
# I will not be stored in the history
end
end
In your actions, you can then use the following methods:
last_location: returns the last visited location, can be used with one numeric argument precising how many locations to go back in the history (1 by default),
peek_last_location: like last_location but dont remove it from the history,
redirect_back: redirect the user to the last location in history, it takes the same arguments as last_location,
store_location(force = false): stores the current location in the history, set force parameter to true to store location even if it would be skipped.
Note that if you want to use the plugin to create a "back" link on a page, you must go back two times. For example, using this controller
class HistoryController < ApplicationController
def foo
end
def bar
end
def back
redirect_back(2)
end
end
Ill try to explain clearly why. Lets say that in your bar view, you create a back link wich links to the back action. Now a user visits foo then bar. What you want is your user being redirected to foo when clicking your "back" link. Now your user hits the link. The controller will call the back action. From its point of view, you are in the back action so going back one time would take you to the bar action.
Enhancements:
- This release fixes a bug where a user variable was stored in a class variable instead of a session one, so a user going back would make another one skip a page in its history.
- The plugin no longer stores PUT and DELETE requests.
- A peek_last_location method was added to look at the history without modifying it, and a "force" parameter was added to the store_location method to force storing of a location even if it would normally be skipped.

Browser-history is a small and efficient daemon that keeps your browser history, independent of the browser you use.
Browser-history came from the will to overcome a Netscape bug: there was no global history, and if you close a window, its whole history is lost. For people browsing lots of sites, having a possibility to track back where one has been before means that you dont have to put everything in your bookmarks file. If you are not sure if a site may be worth remebering, dont add it in your bookmarks. If you need it later, just browse your history files.
Later, it came to our minds that this also could be a valuable add-on to people writing experimental browsers, so they dont have to add this functionality to their browser itself, and to users able thus to track their web history regardless of the browser they used.
Browser-history is a small and efficient daemon. Real user services could be built on top of the log files it maintains for more possibilities (graphical representation, advanced search options, collective histories). It can be seen as a quick-and-dirty hack wrt to the general solution of using a personal proxy to provide this history and housekeeping facilities. For now, it is easy to use and it works very good.
And now that Netscape has a semi-decent history, browser-history is still valuable, as it is difficult to search in the netscape history, its file format is not defined, and entries expire after some time.
Enhancements:
- bugfix: since 2.6, internal links of default generated headers were false

Netscape::HistoryURL is a URI::URL subclass with Netscape history information.

SYNOPSIS

use Netscape::HistoryURL;

$url = new Netscape::HistoryURL(http://foobar.com/,
LAST, FIRST, COUNT, EXPIRE, TITLE);

The Netscape::HistoryURL module subclasses URI::URL to provide a URL class with methods for accessing the information which is stored in Netscapes history database.

The history database is used to keep track of all URLs you have visited. This is used to color previously visited URLs different, for example. The information stored in the history database depends on the version of Netscape being used.

Browser History Viewer allows you to examine the contents of web browser history files and export the data.

Currently it supports Internet Explorer and Mozilla/Firefox.

Browser History Viewer meant to be a forensics tool. It meant to be a forensics tool.

BHV is licensed under the terms of the GNU General Public License (GPL).

Computer History Graphing Project is a computer family tree.

The Computer History Graphing Project is an attempt to graph every computer standard, every piece of hardware, every OS, and every computer language in one big family tree.

Games::Mastermind is a simple framework for MasterMind games.

SYNOPSIS

use Games::Mastermind;

# the classic game
$mm = Games::Mastermind->new;

# make a guess
$marks = $game->play(qw( Y C W R ));

# results
print "You win!n" if $marks->[0] == $mm->holes();

# the game history is available at all times
$history = $mm->history();
$last_turn = $mm->history()->[-1];

# reset the game
$mm->reset();

Games::Mastermind is a very simple framework for running Mastermind games.

Daath provides a searchable knowledge base.
Daath is an organized, easy to use, in-depth search tool using MySQL full-text searching.
This allows searching for error messages, select words, phrases, or null searches, to produce a relevant search result from searching all fields of importance. It supports full administration of creating, editing, authorizing, and deleting solutions.
There is full-text searching using a MySQL database based on title, summary and solution with filter options.
It supports alternative searches through the Google and ask.com search engines. Logging and syslog is supported for tracking.
There is a version history for all solutions, and a directory tree view for a quick overview of all solutions.
Main features:
- Null search for all matches in a category.
- Built on PHP and MySQL for fast search results and page display.
- FULLTEXT search of title, summary, and solution fields.
- Search supports filters for company name, type, and category.
- Search string supports phrase, quoted, and priority words.
- All results have a relevance rating based on the search string.
- Search results have brief description or solution with search words in bold.
- Administration page for easy creation and editing of solutions.
- Cookie authentication for administration page security.
- User access control levels.
- Printer-friendly articles.
- Auto Print function for each solution.
- Solutions have version control number and edit history.
- Support for unlimited solutions.
- Ability to upload images and other files into solutions.
- Syslog logging support.
- Support mysql master slave design for redundancy.
- Directory tree view of all solutions.
- Alternate search options through Google and others.
- Supports categorization for multiple customer or companies.
- Support web site themes.