Free view update history software for linux

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

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.

kio_history is a protocol to access Konquerors browsing history. It is mostly experimental in nature.

Known bugs:

-Cannot delete entries / clear history.
-Does not receive real-time updates, must be refreshed.
-Folder URLS (e.g. svn://anonsvn.kde.org/home/kde) do not open correctly.

Ideas for the future?

-All of the above bugs could be fixed by modifying KonqHistoryManager.
-Display favicons.
-Store previews of all history entries?

Update Scanner provides an extension which monitors web pages for updates.

Right-click on any page, and select "Scan Page for Updates".

You can choose how often the site will be checked for changes, and whether to ignore minor updates.

When a change is detected, a notification window is displayed. Click the blue up-arrow on the bottom status bar to show the Update Scanner sidebar. Webpages that have been updated are shown in bold.

Double-click any item to open the website.

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.

RPM Delta Compression Virtual Update Repository is an experiment to explore the possibility of significantly reducing the bandwidth required to apply updates to a Fedora installation.
This software includes a server which provides a virtual update repository to clients such as yum, up2date, or other update tools. RPM Delta Compression Virtual Update Repository also includes a utility to create and maintain a RPM delta repository.
The server will attempt to generate the update RPM from a small delta file applied to a locally stored RPM from the original distribution.
Enhancements:
- This version utilizes the SuSE deltarpm tool as the underlying delta generator.
- It features both HTTP virtual update of the RPM repository (using Tomcat servlet container) and command line tools for generating update RPMs from a delta repository.

This class can be used to keep track of the pages navigated by a user, so it can generate back or next links providing a similar effect to the use of the Javascript history.go() function.
It uses sessions to store an array variable that holds the URL of each page of a site that the user accesses. It can limit the number of pages that are kept in the history array.
It may also ignore pages accessed with the POST method or with certain URLs based on options that define exclusion regular expressions. The class can generate links to go back to the last page or the first page that was recorded.
Enhancements:
- The class is completely changed.
- This release adds creation of several objects of a class, a predefined start page, an expanded list of exceptions, and the methods get_history_back, get_history_next, is_history_back (check back one page), is_history_next (check the next page), get_history_backs (go to the first page), get_history_nexts (go to the last page), and get_history_header (go to the previous and next pages using external parameters).
- It adds history "always", and has more compatibility with javascript:history.go() (no checking previous and next pages).
- New methods have been added for the manipulation of history "always".