Free browsing history software for linux

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

CVS History is a Web application for searching the history of CVS actions. It parses the output of the CVS history command and imports it into a MySQL database for ease of manipulation by the PHP front-end.
Its advantage over other CVS history viewing applications is that it only needs anonymous CVS access to the repository.
Main features:
- Tested on Firefox and IE
- XHTML and CSS validated code
- RSS feed of the search query results
- Export the output of search query to other formats (e.g. CSV file)
- Searches can be bookmarked
- History entries can be linked to a ViewVC installation of the same repository

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.

Netscape::History is a Perl object class for accessing Netscape history database.

SYNOPSIS

use Netscape::History;

$history = new Netscape::History();
while (defined($url = $history->next_url() ))
{
}

The Netscape::History module implements an object class for accessing the history database maintained by the Netscape web browser. The history database keeps a list of all URLs you have visited, and is used by Netscape to change the color of URLs which you have previously visited, for example.

With this module, you can get at the URLs stored in a Netscape history file, delete URLs, and add new ones. With the associated Netscape::HistoryURL module you can access the information which is associated with each URL.

Please Note: the database format for the browser history was changed with Netscape 4. Previously only the time of most recent visit was available; now you can also get at the time of your first visit, the number of visits, the title of the referenced page, and another value.

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.

Improved offline web browsing package contains:
- improved / bug-fixed offline browsing for Konqueror and other application that use kde http io slaves.
- Improved / bug-fixed web browsing for low-bandwidth connections.
- Improved / bug-fixed detection of cross-domain requests
- Referer-Urls are not send cross-domain (configurable)
Requires sources for kdelibs, kdebase and kdeaddons. If you use German localization, you will probably want sources for kde-i18n-de, too.
Webpages with enabled javascript may not work 100% when browsing offline completely.
Version restrictions:
- None that are not present in the original http slave.
- Webpages with javascript enabled may not work with offline browsing.

The purpose of this project is to provide a simple, generic GUI database browsing frontend. The tool is a very simple aggregation of the Qt database classes.
The database abstraction is provided by the Qt database drivers. So far, the drivers for PostgreSQL and MySQL have been found to work well.
In principle, there is no reason why ODBC drivers for popular databases such as Oracle, DB2, Informix as well as Firebird and SAP/DB shouldnt work via the Qt ODBC3 abstraction layer.
However, some preliminary tests with these have not been promising. It may be that the only way to get some of these working is to create a native Qt database driver. This is something Ill be looking into much later.
At the moment, it is only possible to build the system on Unix and similar systems. Since Trolltech have released a version of Qt for OSX under the GPL and have announced their intention to do likewise for Win32, it should be possible to provide ports for both of these platforms. For the moment though, I just provide the source.
Main features:
- Tree browser for databases and tables
- Display of table descriptions
- Display of table contents in main window
- Execution of ad-hoc SQL queries in the query tab
- Command line history in the query tab
- Retrieval of database connection details from XML config file
- Retrieval of other configuration parameters from XML config file
- Prompting for connection password
- Addition of new connections via GUI to the running application and the config file
- Display database views with a separate icon
- Create a connection name independent of the database name
- A "Test" button when creating a new connection
- Dynamically generate a list of available drivers
- Configuration via autoconf
- Fixed bug with executing updates/inserts twice
- Refreshing of a DB connection
- Deleting of connections via the GUI
- Editting of connections via the GUI
- Check for the existence of ~/.qtsql
- Creation of skeleton config file
- Auto saving/restoring of history
- Loading of queries
- Saving of results
- Keyboard shortcuts

Puppet::VcsTools::History provides a TK GUI for VcsTools::History.
This class provides a GUI to the VcsTools::History class.
It contains a GraphWidget to draw the history tree and some key bindings to read the log informations from the tree drawing .
Main features:
- A canvas to draw a revision tree.
- A revision list. If you double click on a revision of this list, History will draw the revision tree starting from this revision.
- A text window to display informations related to the revision tree.