versions of winutilities history cleaner
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5855
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
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
Gnome Wave Cleaner 0.21-07
GWC is an application to do digital audio restoration on wavfile data, i.e. remove hisses and clicks. more>>
GWC is an application to do digital audio restoration on wavfile data, i.e. remove hisses and clicks. It features click repair using least squares autoregressive interpolation, and is based on the FFTW library. This is still beta code, so back up your data files first.
It is resulting of never wanting to boot to MS windows again. The only reason I had left was because I have this wonderful software to record digital audio, and the dehiss and declick using some very cool software (COOLEDIT 2000) and (Declick by M. Paar), to do the audio restoration.
I checked out some of the ongoing projects in linux, and either they crashed a lot or, didnt do what I needed, so I started this effort out of selfishness and also as a mechanism to learn the GNOME API for GUI programming . A lot of the code shows the efforts of that learning curve, and could certainly be cleaned up, but the I am personally pleased with the overall design. The goals are simple -- denoise, dehiss and amplify audio files. With the use of libsndfile, you can now do this on a multitude of audio formats, wav, au, aiff, ...
For those of you interested, I started working up a presentation describing the technical aspects of the audio restoration methods used in GWC.
Untar the source tarball (tar -xvzf )
Enter the directory created.
Run "./configure"
Run "make".
Run "make install".
"gwc" is the program file. All you have to do is run it.
Enhancements:
- BUGFIX: Ok. I messed up. The save changes stuff on exit was broken. Hopefully fixed now.
<<lessIt is resulting of never wanting to boot to MS windows again. The only reason I had left was because I have this wonderful software to record digital audio, and the dehiss and declick using some very cool software (COOLEDIT 2000) and (Declick by M. Paar), to do the audio restoration.
I checked out some of the ongoing projects in linux, and either they crashed a lot or, didnt do what I needed, so I started this effort out of selfishness and also as a mechanism to learn the GNOME API for GUI programming . A lot of the code shows the efforts of that learning curve, and could certainly be cleaned up, but the I am personally pleased with the overall design. The goals are simple -- denoise, dehiss and amplify audio files. With the use of libsndfile, you can now do this on a multitude of audio formats, wav, au, aiff, ...
For those of you interested, I started working up a presentation describing the technical aspects of the audio restoration methods used in GWC.
Untar the source tarball (tar -xvzf )
Enter the directory created.
Run "./configure"
Run "make".
Run "make install".
"gwc" is the program file. All you have to do is run it.
Enhancements:
- BUGFIX: Ok. I messed up. The save changes stuff on exit was broken. Hopefully fixed now.
Download (0.68MB)
Added: 2006-10-20 License: GPL (GNU General Public License) Price:
1105 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
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
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
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
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
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
History links 1.3
This class can be used to keep track of the pages navigated by a user, so it can generate back or next links. more>>
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".
<<lessIt 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".
Download (0.006MB)
Added: 2005-10-03 License: GPL (GNU General Public License) Price:
1482 downloads
Free Music Instrument Tuner 0.96.4
Free Music Instrument Tuner is a musical instrument tunning application. more>>
Free Music Instrument Tuner is a musical instrument tunning application.
Main features:
- Error history
- Volume history
- Wave-length shape
- Harmonics ratio (Formants)
- Microtonal tuning (with Scala file support)
- ALSA support
- JACK support
- Translations for: francais
<<lessMain features:
- Error history
- Volume history
- Wave-length shape
- Harmonics ratio (Formants)
- Microtonal tuning (with Scala file support)
- ALSA support
- JACK support
- Translations for: francais
Download (0.22MB)
Added: 2006-02-03 License: GPL (GNU General Public License) Price:
1391 downloads
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
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
Solid Of Rotation 1.3.0
Solid Of Rotation is a 3D graphic editor. more>>
There is quite a bit of history on this item. One of the assignments in a computer graphics course at the University of Victoria was to rotate a number of Bezier curves around an axis and display the result in 3D using a single light source.
This was on Sun Sparcs using X. Since then the program has mutated to match my platform preference at a given time (DOS, Windows, Linux).
The latest mutation has been to SDL/OpenGL and the result runs happily on Linux and Windows. Screenshot junkies might find the following of interest:
<<lessThis was on Sun Sparcs using X. Since then the program has mutated to match my platform preference at a given time (DOS, Windows, Linux).
The latest mutation has been to SDL/OpenGL and the result runs happily on Linux and Windows. Screenshot junkies might find the following of interest:
Download (0.30MB)
Added: 2005-09-18 License: GPL (GNU General Public License) Price:
1498 downloads
Ipanto Lite for Cisco IOS DHCP 3.0.2
Ipanto Lite for Cisco IOS DHCP provides monitoring of Cisco IOS DHCP and IP address management. more>>
IpaLite for Cisco IOS DHCP provides monitoring of Cisco IOS DHnto CP and IP address management. It has a user-friendly and intuitive Web GUI, monitoring of Cisco IOS DHCP scopes, and reporting (IP utilization and history).
Ipanto Lite is quick and easy to implement, reduces manual repetitive operations, and can replace your spreadsheet
Major Features
User-friendly and intuitive Web GUI,
1 user profile with full admin rights,
Reporting (IP utilization and history).
Major Benefits
Quick and easy implementation,
Reduce manual repetitive operations,
Replace your speadsheet.
Enhancements:
- This version is a service release that provides miscellaneous corrections and improvements.
- The Ipanto Database has been updated to provide more accurate statistics and to improve log storage usage.
- The Ipanto WebGUI has been improved to provide localized settings, DHCP hosts listing per subnet, and optimized display for large subnet/location sets.
<<lessIpanto Lite is quick and easy to implement, reduces manual repetitive operations, and can replace your spreadsheet
Major Features
User-friendly and intuitive Web GUI,
1 user profile with full admin rights,
Reporting (IP utilization and history).
Major Benefits
Quick and easy implementation,
Reduce manual repetitive operations,
Replace your speadsheet.
Enhancements:
- This version is a service release that provides miscellaneous corrections and improvements.
- The Ipanto Database has been updated to provide more accurate statistics and to improve log storage usage.
- The Ipanto WebGUI has been improved to provide localized settings, DHCP hosts listing per subnet, and optimized display for large subnet/location sets.
Download (71.3MB)
Added: 2007-05-20 License: Freeware Price:
898 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 versions of winutilities history cleaner 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
