windows versions history
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5738
browser-history 2.8
Browser-history is a small and efficient daemon that keeps your browser history, independent of the browser you use. more>>
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
<<lessBrowser-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
Download (0.019MB)
Added: 2006-06-22 License: Freeware Price:
698 downloads
Browser History Viewer 0.0.10
Browser History Viewer allows you to examine the contents of web browser history files and export the data. more>>
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).
<<lessCurrently 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).
Download (MB)
Added: 2006-06-26 License: GPL (GNU General Public License) Price:
1239 downloads
CVS History 0.8.0
CVS History is a Web application for searching the history of CVS actions. more>>
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
<<lessIts 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
Download (0.10MB)
Added: 2005-11-29 License: GPL (GNU General Public License) Price:
1425 downloads
Sort::Versions 1.5
Sort::Versions is a Perl 5 module for sorting of revision-like numbers. more>>
Sort::Versions is a Perl 5 module for sorting of revision-like numbers.
SYNOPSIS
use Sort::Versions;
@l = sort { versioncmp($a, $b) } qw( 1.2 1.2.0 1.2a.0 1.2.a 1.a 02.a );
...
use Sort::Versions;
print lower if versioncmp(1.2, 1.2a) == -1;
...
use Sort::Versions;
%h = (1 => d, 2 => c, 3 => b, 4 => a);
@h = sort { versioncmp($h{$a}, $h{$b}) } keys %h;
Sort::Versions allows easy sorting of mixed non-numeric and numeric strings, like the version numbers that many shared library systems and revision control packages use. This is quite useful if you are trying to deal with shared libraries. It can also be applied to applications that intersperse variable-width numeric fields within text. Other applications can undoubtedly be found.
For an explanation of the algorithm, its simplest to look at these examples:
1.1 < 1.2
1.1a < 1.2
1.1 < 1.1.1
1.1 < 1.1a
1.1.a < 1.1a
1 < a
a < b
1 < 2
1.1-3 < 1.1-4
1.1-5 < 1.1.6
More precisely (but less comprehensibly), the two strings are treated as subunits delimited by periods or hyphens. Each subunit can contain any number of groups of digits or non-digits. If digit groups are being compared on both sides, a numeric comparison is used, otherwise a ASCII ordering is used. A group or subgroup with more units will win if all comparisons are equal. A period binds digit groups together more tightly than a hyphen.
Some packages use a different style of version numbering: a simple real number written as a decimal. Sort::Versions has limited support for this style: when comparing two subunits which are both digit groups, if either subunit has a leading zero, then both are treated like digits after a decimal point. So for example:
0002 < 1
1.06 < 1.5
This wont always work, because there wont always be a leading zero in real-number style version numbers. There is no way for Sort::Versions to know which style was intended. But a lot of the time it will do the right thing. If you are making up version numbers, the style with (possibly) more than one dot is the style to use.
USAGE
The function versioncmp() takes two arguments and compares them like cmp. With perl 5.6 or later, you can also use this function directly in sorting:
@l = sort versioncmp qw(1.1 1.2 1.0.3);
The function versions() can be used directly as a sort function even on perl 5.005 and earlier, but its use is deprecated.
<<lessSYNOPSIS
use Sort::Versions;
@l = sort { versioncmp($a, $b) } qw( 1.2 1.2.0 1.2a.0 1.2.a 1.a 02.a );
...
use Sort::Versions;
print lower if versioncmp(1.2, 1.2a) == -1;
...
use Sort::Versions;
%h = (1 => d, 2 => c, 3 => b, 4 => a);
@h = sort { versioncmp($h{$a}, $h{$b}) } keys %h;
Sort::Versions allows easy sorting of mixed non-numeric and numeric strings, like the version numbers that many shared library systems and revision control packages use. This is quite useful if you are trying to deal with shared libraries. It can also be applied to applications that intersperse variable-width numeric fields within text. Other applications can undoubtedly be found.
For an explanation of the algorithm, its simplest to look at these examples:
1.1 < 1.2
1.1a < 1.2
1.1 < 1.1.1
1.1 < 1.1a
1.1.a < 1.1a
1 < a
a < b
1 < 2
1.1-3 < 1.1-4
1.1-5 < 1.1.6
More precisely (but less comprehensibly), the two strings are treated as subunits delimited by periods or hyphens. Each subunit can contain any number of groups of digits or non-digits. If digit groups are being compared on both sides, a numeric comparison is used, otherwise a ASCII ordering is used. A group or subgroup with more units will win if all comparisons are equal. A period binds digit groups together more tightly than a hyphen.
Some packages use a different style of version numbering: a simple real number written as a decimal. Sort::Versions has limited support for this style: when comparing two subunits which are both digit groups, if either subunit has a leading zero, then both are treated like digits after a decimal point. So for example:
0002 < 1
1.06 < 1.5
This wont always work, because there wont always be a leading zero in real-number style version numbers. There is no way for Sort::Versions to know which style was intended. But a lot of the time it will do the right thing. If you are making up version numbers, the style with (possibly) more than one dot is the style to use.
USAGE
The function versioncmp() takes two arguments and compares them like cmp. With perl 5.6 or later, you can also use this function directly in sorting:
@l = sort versioncmp qw(1.1 1.2 1.0.3);
The function versions() can be used directly as a sort function even on perl 5.005 and earlier, but its use is deprecated.
Download (0.005MB)
Added: 2007-05-22 License: Perl Artistic License Price:
885 downloads
Program Version Switch 1.03
Program Version Switch is a program to easily switch between different interpreter versions. more>>
pvswitch is a very tiny program which makes it possible to use different program installations on one machine flawlessly.
Its flexibility is intended for people who need to run programs against different interpreter versions.
But it can also be used for different purposes like switching the version of a compiler, text editor, mail reader, browser, whatever.
It is most useful for developers of interpreter based programs which are started via a hash-bang line (#!).
The following example explains the usage for perl programs, but the very same is true for all other interpreter languages.
If you install two or more different perl versions on your machine, you could just call the respective perl binary you want to use..
perl myscript.pl
/path/to/another/perl myscript.pl
This works fine, although it isnt very convenient. However if you are starting your program using the hash-bang line like
#! /usr/bin/perl
and then just start it by
./myscript.pl
you would need to change the file itself to use another perl version. Again it is possible, but not very convenient.
And here comes pvswitch: its purpose is to make such situations convenient. Further it solve some problems which come up if multiple people want to use different perl versions. pvswitch allows even to run one program in two shells with different perl versions.
This is possible because pvswitch uses a environment variable to select the interpreter version to use. This environment variable can be set in different sessions independently.
pvswitch is installed as new program binary (e.g. perl) the old one will be renamed to program.pvswitch.
Now every time you execute a this program (e.g. perl), pvswitch is executed. It doesnt matter how you start the program...
perl myscript.pl
./myscript.pl # if it has a hash-bang #! /usr/bin/perl
for both cases the pvswitch binary will be executed, pvswitch will than check for the environment variable PVSWITCH_PERL_BINARY (if you are running perl), if it is found it tries to find this key in the configuration file pvswitch.conf and execute the program which is configured for the version configured set in the environment variable (e.g. perl.pvswitch).
So it just executes the real program (e.g. perl interpreter). Depending on the environment a different version might be selected.
There are some convenient tools (e.g. perlver, pvconfig) to configure this.
Enhancements:
- Fixed a bug which could cause segmentation violation.
<<lessIts flexibility is intended for people who need to run programs against different interpreter versions.
But it can also be used for different purposes like switching the version of a compiler, text editor, mail reader, browser, whatever.
It is most useful for developers of interpreter based programs which are started via a hash-bang line (#!).
The following example explains the usage for perl programs, but the very same is true for all other interpreter languages.
If you install two or more different perl versions on your machine, you could just call the respective perl binary you want to use..
perl myscript.pl
/path/to/another/perl myscript.pl
This works fine, although it isnt very convenient. However if you are starting your program using the hash-bang line like
#! /usr/bin/perl
and then just start it by
./myscript.pl
you would need to change the file itself to use another perl version. Again it is possible, but not very convenient.
And here comes pvswitch: its purpose is to make such situations convenient. Further it solve some problems which come up if multiple people want to use different perl versions. pvswitch allows even to run one program in two shells with different perl versions.
This is possible because pvswitch uses a environment variable to select the interpreter version to use. This environment variable can be set in different sessions independently.
pvswitch is installed as new program binary (e.g. perl) the old one will be renamed to program.pvswitch.
Now every time you execute a this program (e.g. perl), pvswitch is executed. It doesnt matter how you start the program...
perl myscript.pl
./myscript.pl # if it has a hash-bang #! /usr/bin/perl
for both cases the pvswitch binary will be executed, pvswitch will than check for the environment variable PVSWITCH_PERL_BINARY (if you are running perl), if it is found it tries to find this key in the configuration file pvswitch.conf and execute the program which is configured for the version configured set in the environment variable (e.g. perl.pvswitch).
So it just executes the real program (e.g. perl interpreter). Depending on the environment a different version might be selected.
There are some convenient tools (e.g. perlver, pvconfig) to configure this.
Enhancements:
- Fixed a bug which could cause segmentation violation.
Download (0.075MB)
Added: 2005-04-15 License: GPL (GNU General Public License) Price:
1661 downloads
kio_history 0.1
kio_history is a protocol to access Konquerors browsing history. more>>
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?
<<lessKnown 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?
Download (0.38MB)
Added: 2006-11-06 License: GPL (GNU General Public License) Price:
1082 downloads
Rails History Plugin 0.2
Rails History Plugin is a Ruby on Rails plugin that stores user actions (i.e. URLs that the user has recently visited). more>>
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.
<<lessIt 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.
Download (0.011MB)
Added: 2006-06-29 License: MIT/X Consortium License Price:
1213 downloads
Module::Versions 0.02
Module::Versions is a Perl module to handle versions of loaded modules with flexible result interface. more>>
Module::Versions is a Perl module to handle versions of loaded modules with flexible result interface.
SYNOPSIS
use Module::Versions;
# Simple Interface
list Module::Versions; # prints formatted results to STDOUT
Module::Versions->list; # prints formatted results to STDOUT
# Shortcuts
$vers = get Module::Versions; # retrieves loaded modules
$vers = Module::Versions->get; # retrieves loaded modules
$array = Module::Versions->ARRAY; # returns array with version infos
$hash = Module::Versions->HASH; # returns hash with version infos
$list = Module::Versions->SCALAR; # returns text list with version infos
$csv = Module::Versions->CSV; # returns csv list with version infos
$xml = Module::Versions->XML; # returns xml struct with version infos
$xsd = Module::Versions->XSD; # returns xml schema of version infos
$dtd = Module::Versions->DTD; # returns DTD of version infos
# Individual Parameters
$vers = Module::Versions # retrieves mods and vars as defined
->new($mods,$vars)
->get($criteria);
$vers->list($fd,$mask); # prints formatted results to file
$vers->list($fd,$preform); # prints preformatted results to file
$vers->list($fd,&cb); # prints serialied results as handled
# in callback routine
$vers->data(&cb); # returns transformed results as
# defined in callback routine
# Individual formatted output
list Module::Versions(*LOG, %5d %1s %-20s %10s %-16s);
# prints individually formatted
# results to LOG
list Module::Versions(*DBIMPORT, %s|%s|%s);
# prints individually formatted
# results to Database Import file
list Module::Versions(*FD, SCALAR);# prints text list results to file
list Module::Versions(*FD, CSV); # prints csv list results to file
list Module::Versions(*FD, XML); # prints xml struct results to file
list Module::Versions(*FD, XSD); # prints xml schema to file
list Module::Versions(*FD, DTD); # prints DTD to file
list Module::Versions(*FD, ARRAY); # prints serialized results to file
list Module::Versions(*FD, HASH); # prints serialized results to file
Module::Versions->list(*LOG); # prints formatted results to LOG
# Pretty Compact
Module::Versions->list # prints formatted results on STDOUT
->list(*XML,XML); # prints xml struct results to XML file
Module::Versions->list # prints formatted results on STDOUT
->list(*XSD,XSD) # prints xml schema to XSD file
->list(*XML,XML); # prints xml struct results to XML file
Module::Versions->list # prints formatted results on STDOUT
->list(*DTD,DTD) # prints DTD to DTD file
->list(*XML,XML); # prints xml struct results to XML file
Module::Versions handles versions of loaded modules with a flexible result interface. The main goal is to get as much version informations as possible about a module or module list with a simple call interface and an absolutely flexible result interface. Module::Versions handles *loaded* and *loadable* modules.
The motivation for writing this module was the need for better support facilities to get informations about the used modules and versions in the productivity environment. Module::Versions allows shipping applications basically with something like a -version option (See Getopt::Long) but with expanded functions.
Module::Versions tries to read the loaded/loadable modules $VERSION. For extended purposes any private project version variables can be fetched ($_VERSION, $version, $REV, etc.).
Module::Versions has a flexible result interface to satisfy different needs: results can be lists and data structures with different formats - pre-formed ARRAY, HASH, SCALAR, CSV, XML/XSD/DTD and a full flexible user callback interface.
It is for example very simple to print a good formatted version list to the console and save a version.xml file (in conjunction with an xsd-schema) at the same time with an absolutely minimum of coding (SYNOPSIS, Pretty Compact) .
Module::Versions tries to load version.pm to support Perl 5.10.0s $VERSION formatting.
<<lessSYNOPSIS
use Module::Versions;
# Simple Interface
list Module::Versions; # prints formatted results to STDOUT
Module::Versions->list; # prints formatted results to STDOUT
# Shortcuts
$vers = get Module::Versions; # retrieves loaded modules
$vers = Module::Versions->get; # retrieves loaded modules
$array = Module::Versions->ARRAY; # returns array with version infos
$hash = Module::Versions->HASH; # returns hash with version infos
$list = Module::Versions->SCALAR; # returns text list with version infos
$csv = Module::Versions->CSV; # returns csv list with version infos
$xml = Module::Versions->XML; # returns xml struct with version infos
$xsd = Module::Versions->XSD; # returns xml schema of version infos
$dtd = Module::Versions->DTD; # returns DTD of version infos
# Individual Parameters
$vers = Module::Versions # retrieves mods and vars as defined
->new($mods,$vars)
->get($criteria);
$vers->list($fd,$mask); # prints formatted results to file
$vers->list($fd,$preform); # prints preformatted results to file
$vers->list($fd,&cb); # prints serialied results as handled
# in callback routine
$vers->data(&cb); # returns transformed results as
# defined in callback routine
# Individual formatted output
list Module::Versions(*LOG, %5d %1s %-20s %10s %-16s);
# prints individually formatted
# results to LOG
list Module::Versions(*DBIMPORT, %s|%s|%s);
# prints individually formatted
# results to Database Import file
list Module::Versions(*FD, SCALAR);# prints text list results to file
list Module::Versions(*FD, CSV); # prints csv list results to file
list Module::Versions(*FD, XML); # prints xml struct results to file
list Module::Versions(*FD, XSD); # prints xml schema to file
list Module::Versions(*FD, DTD); # prints DTD to file
list Module::Versions(*FD, ARRAY); # prints serialized results to file
list Module::Versions(*FD, HASH); # prints serialized results to file
Module::Versions->list(*LOG); # prints formatted results to LOG
# Pretty Compact
Module::Versions->list # prints formatted results on STDOUT
->list(*XML,XML); # prints xml struct results to XML file
Module::Versions->list # prints formatted results on STDOUT
->list(*XSD,XSD) # prints xml schema to XSD file
->list(*XML,XML); # prints xml struct results to XML file
Module::Versions->list # prints formatted results on STDOUT
->list(*DTD,DTD) # prints DTD to DTD file
->list(*XML,XML); # prints xml struct results to XML file
Module::Versions handles versions of loaded modules with a flexible result interface. The main goal is to get as much version informations as possible about a module or module list with a simple call interface and an absolutely flexible result interface. Module::Versions handles *loaded* and *loadable* modules.
The motivation for writing this module was the need for better support facilities to get informations about the used modules and versions in the productivity environment. Module::Versions allows shipping applications basically with something like a -version option (See Getopt::Long) but with expanded functions.
Module::Versions tries to read the loaded/loadable modules $VERSION. For extended purposes any private project version variables can be fetched ($_VERSION, $version, $REV, etc.).
Module::Versions has a flexible result interface to satisfy different needs: results can be lists and data structures with different formats - pre-formed ARRAY, HASH, SCALAR, CSV, XML/XSD/DTD and a full flexible user callback interface.
It is for example very simple to print a good formatted version list to the console and save a version.xml file (in conjunction with an xsd-schema) at the same time with an absolutely minimum of coding (SYNOPSIS, Pretty Compact) .
Module::Versions tries to load version.pm to support Perl 5.10.0s $VERSION formatting.
Download (0.021MB)
Added: 2007-05-03 License: Perl Artistic License Price:
904 downloads
Tie::HashHistory 0.03
Tie::HashHistory can track history of all changes to a tied hash. more>>
Tie::HashHistory can track history of all changes to a tied hash.
SYNOPSIS
my $hh = tie %hash => Tie::HashHistory, PACKAGE, ARGS...;
@values = $hh->history(KEY);
Tie::HashHistory interposes itself between your program and another tied hash. Fetching and storing to the hash looks completely normal, but Tie::HashHistory is keeping a record of all the changes to the each key, and can Tie::HashHistory will give you a list of all the values the key has ever had, in chronological order.
The arguments to the tie call should be Tie::HashHistory, and then the arguments that you would have given to tie to tie the hash without the history feature. For example, suppose you wanted to store your hash data in an NDBM file named database. Normally, you would say:
tie %hash => NDBM_File, database, $flags, $mode;
to get this history feature, just add Tie::HashHistory before NDBM_File:
my $hh = tie %hash => Tie::HashHistory,
NDBM_File, database, $flags, $mode;
The data will still be stored in database, and it will still be an NDBM file. All the fetching and storing will look the same, but the change history of each key will be available.
The tie call will return an object; to find out the history of a key, use the history method on this object. It takes one argument, which is a key string. It will return a list of all the values that have ever been associated with the key, in chronological order, starting with the most recent. For example:
$hash{a} = first;
$hash{b} = second;
$hash{a} = third; # Overwrites old value
# Prints "third second" as you would expect
print "$hash{a} $hash{b}n";
@values = $hh->history(a);
# @values now contains (third, first)
@values = $hh->history(b);
# @values now contains (second)
At present, if called in scalar context, the history() method will return the number of items in the history. This behavior may change in future versions.
The underlying hash can be any tied hash class at all. To use a regular in-memory hash, use Tie::StdHash (distributed with Perl) as the underlying implementation:
use Tie::Hash; # *NOT Tie::StdHash*
my $hh = tie %hash => Tie::HashHistory, Tie::StdHash;
This is not as efficient as it could be because fetches and stores on %hash still go through two layers of tieing. I may fix this in a future release.
<<lessSYNOPSIS
my $hh = tie %hash => Tie::HashHistory, PACKAGE, ARGS...;
@values = $hh->history(KEY);
Tie::HashHistory interposes itself between your program and another tied hash. Fetching and storing to the hash looks completely normal, but Tie::HashHistory is keeping a record of all the changes to the each key, and can Tie::HashHistory will give you a list of all the values the key has ever had, in chronological order.
The arguments to the tie call should be Tie::HashHistory, and then the arguments that you would have given to tie to tie the hash without the history feature. For example, suppose you wanted to store your hash data in an NDBM file named database. Normally, you would say:
tie %hash => NDBM_File, database, $flags, $mode;
to get this history feature, just add Tie::HashHistory before NDBM_File:
my $hh = tie %hash => Tie::HashHistory,
NDBM_File, database, $flags, $mode;
The data will still be stored in database, and it will still be an NDBM file. All the fetching and storing will look the same, but the change history of each key will be available.
The tie call will return an object; to find out the history of a key, use the history method on this object. It takes one argument, which is a key string. It will return a list of all the values that have ever been associated with the key, in chronological order, starting with the most recent. For example:
$hash{a} = first;
$hash{b} = second;
$hash{a} = third; # Overwrites old value
# Prints "third second" as you would expect
print "$hash{a} $hash{b}n";
@values = $hh->history(a);
# @values now contains (third, first)
@values = $hh->history(b);
# @values now contains (second)
At present, if called in scalar context, the history() method will return the number of items in the history. This behavior may change in future versions.
The underlying hash can be any tied hash class at all. To use a regular in-memory hash, use Tie::StdHash (distributed with Perl) as the underlying implementation:
use Tie::Hash; # *NOT Tie::StdHash*
my $hh = tie %hash => Tie::HashHistory, Tie::StdHash;
This is not as efficient as it could be because fetches and stores on %hash still go through two layers of tieing. I may fix this in a future release.
Download (0.004MB)
Added: 2007-08-21 License: Perl Artistic License Price:
794 downloads
Netscape::History 3.01
Netscape::History is a Perl object class for accessing Netscape history database. more>>
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.
<<lessSYNOPSIS
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.
Download (0.009MB)
Added: 2007-03-24 License: Perl Artistic License Price:
949 downloads
Superversion 2.0 Beta 8
Superversion is a multi-user distributed version control system based on change sets. more>>
Superversion is a multi-user distributed version control system based on change sets. It aims to be an industrial-strength, open source alternative to commercial solutions that is equally easy to use (or even easier) and similarly powerful. In fact, intuitive and efficient usability has been one of the top priorities in Superversions development from the very beginning.
If youre frustrated with CVS - as so many developers before you - and dont want to spend money on a version management software, try Superversion today! Superversion is ublished under the GPL and free to use even in commercial environments.
Main features:
- Very easy download, installation and setup in just a few clicks
- Platform-independent; supported on Windows, Linux, OS/2, OpenVMS (should run on Macs too - feedback welcome!)
- Graphical user interface for all operations
- Fully transactional internal database - very strong protection against data loss
- Can be used with any editor or file-based IDE
- Compressed diff view for every file accessible in just one click
- Instant overview of all new/changed/deleted files in work area
- Changes can be collected in a buffer before being committed to repository
- Branching
- Branch merging
- All file changes stored as diffs (low space consumption even for binary files)
- Report functions: fulltext search, state comparison, file history
- Support for multiple work areas per project (simultaneous work on different versions)
- Graphical project history view
- Keyword replacement (analogous to CVS)
- Convenient selection of files and directories to be ignored
- Marker system to assign human-readable labels to versions
- Comments assignable to every version, every file
- Export of any recorded version as zip file, complete directory or file-wise
- File type (binary/text) detected automatically (manual override possible)
- Help text in most dialogs
Enhancements:
- The user interface is faster and more responsive in many places.
- There is a new dialog for adding work areas.
<<lessIf youre frustrated with CVS - as so many developers before you - and dont want to spend money on a version management software, try Superversion today! Superversion is ublished under the GPL and free to use even in commercial environments.
Main features:
- Very easy download, installation and setup in just a few clicks
- Platform-independent; supported on Windows, Linux, OS/2, OpenVMS (should run on Macs too - feedback welcome!)
- Graphical user interface for all operations
- Fully transactional internal database - very strong protection against data loss
- Can be used with any editor or file-based IDE
- Compressed diff view for every file accessible in just one click
- Instant overview of all new/changed/deleted files in work area
- Changes can be collected in a buffer before being committed to repository
- Branching
- Branch merging
- All file changes stored as diffs (low space consumption even for binary files)
- Report functions: fulltext search, state comparison, file history
- Support for multiple work areas per project (simultaneous work on different versions)
- Graphical project history view
- Keyword replacement (analogous to CVS)
- Convenient selection of files and directories to be ignored
- Marker system to assign human-readable labels to versions
- Comments assignable to every version, every file
- Export of any recorded version as zip file, complete directory or file-wise
- File type (binary/text) detected automatically (manual override possible)
- Help text in most dialogs
Enhancements:
- The user interface is faster and more responsive in many places.
- There is a new dialog for adding work areas.
Download (1.9MB)
Added: 2005-08-21 License: GPL (GNU General Public License) Price:
1526 downloads
Netscape::HistoryURL 3.01
Netscape::HistoryURL is a URI::URL subclass with Netscape history information. more>>
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.
<<lessSYNOPSIS
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.
Download (0.008MB)
Added: 2007-03-24 License: Perl Artistic License Price:
945 downloads
Puppet::VcsTools::History 1.004
Puppet::VcsTools::History provides a TK GUI for VcsTools::History. more>>
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.
<<lessThis 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.
Download (0.007MB)
Added: 2007-03-30 License: Perl Artistic License Price:
938 downloads
Computer History Graphing Project 0.9.2
Computer History Graphing Project is a computer family tree. more>>
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.
<<lessThe 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.
Download (MB)
Added: 2006-10-04 License: GPL (GNU General Public License) Price:
1115 downloads
Convulsion 0.0.5
Convulsion is a drop-in CVS repository browser for PHP. more>>
Convulsion is a drop-in CVS repository browser for PHP. It makes use of the libraries developed for the Chora module of the Horde project, but does not require that Horde be installed and working to be used.
You can browse directories and files, view a files revision history, compare two versions, and retrieve its ChangeLog. Convulsion also supports automatic obfuscation of e-mail addresses and syntax highlighting of most common languages.
Convulsions output is standards-compliant, accessible, and customisable by means of CSS.
Using Convulsion with Apache 2.x
Please note that in order to use Convulsion with the 2.x series of the Apache web server, you will need to set the value of the "AcceptPathInfo" directive to a value other than "Off". This can be done in the main Apache config, in the < VirtualHost > section for your site or using a .htaccess file.
<<lessYou can browse directories and files, view a files revision history, compare two versions, and retrieve its ChangeLog. Convulsion also supports automatic obfuscation of e-mail addresses and syntax highlighting of most common languages.
Convulsions output is standards-compliant, accessible, and customisable by means of CSS.
Using Convulsion with Apache 2.x
Please note that in order to use Convulsion with the 2.x series of the Apache web server, you will need to set the value of the "AcceptPathInfo" directive to a value other than "Off". This can be done in the main Apache config, in the < VirtualHost > section for your site or using a .htaccess file.
Download (0.018MB)
Added: 2005-09-28 License: GPL (GNU General Public License) Price:
1487 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 windows versions history 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