how do i change my name
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 7207
Gnome Desktop Change 0.2.1
Gnome Desktop Change is a daemon that changes randomly your GNOME desktop background. more>>
Gnome Desktop Change is a daemon that changes randomly your GNOME desktop background.
Gnome Desktop Change is a daemon that changes randomly your GNOME desktop background. Its totally written in C++, it uses FAM (File Alteration Monitor) to detect changes into directory that contains picture files, and its multithread.
<<lessGnome Desktop Change is a daemon that changes randomly your GNOME desktop background. Its totally written in C++, it uses FAM (File Alteration Monitor) to detect changes into directory that contains picture files, and its multithread.
Download (0.10MB)
Added: 2005-08-02 License: GPL (GNU General Public License) Price:
1555 downloads
Gtk+ 2.0 Change Theme 0.3.1
Gtk+ 2.0 Change Theme is a tiny GUI application that aims to make theme preview and selection as slick as possible. more>>
As the name suggests, this little program lets you change your Gtk+ 2.0 theme. The aim is to make theme preview and selection as slick as possible.
Themes installed on the system are presented for selection and previewed on the fly. For a comprehensive demonstration theres a large variety of widgets.
It was originally derived from Gtk Theme Switch, but what started out as a hack to remove various nuisances now shares no code whatsoever anymore with the original.
Enhancements:
- Fixes for a number of a packaging glitches.
<<lessThemes installed on the system are presented for selection and previewed on the fly. For a comprehensive demonstration theres a large variety of widgets.
It was originally derived from Gtk Theme Switch, but what started out as a hack to remove various nuisances now shares no code whatsoever anymore with the original.
Enhancements:
- Fixes for a number of a packaging glitches.
Download (0.02MB)
Added: 2005-04-21 License: GPL (GNU General Public License) Price:
1654 downloads
mod_urlscheme
mod_urlscheme is a small Apache 1.3/2.0/2.2 module that allows the Apache configuration author control over the scheme. more>>
mod_urlscheme is an Apache 1.3/2.0/2.2 module that allows the Apache configuration author control over the scheme to use when constructing self-referential URLs.
Please note that this module is different from mod_scheme, which embeds the Tinyscheme interpreter into Apache. You can find that module here. I changed the name from mod_scheme to mod_urlscheme to avoid confusion.
The original module was only written to work on Apache 2.0. There is now also a version for Apache 1.3 + EAPI, although it wont work with stock 1.3. Please see the "Apache 1.3" section at the bottom of this page for details. The 2.0 module will work almost unchanged on Apache 2.2. There is a small naming change in the API that requires a slightly different version.
In several situations, Apache will attempt to construct a URL that will point to itself and will deliver the result to the client. The most notable occasion for this is when Apache is constructing a client redirect. This can for example happen when the client requests a URL that maps to a directory but doesnt include a trailing slash: Apache will send back a redirect to the same URL, but with a trailing slash appended. Other occasions include Redirect directives in the Apache configuration, or mod_proxy rewriting redirects coming from a backend server (when mod_proxy is functioning as a reverse proxy).
A self-referential URL has four distinct major components: the scheme, the hostname, the port number and the request URI, the latter including perhaps a query string and a fragment identifier. The combination of ServerName, UseCanonicalName and the use of the clients HTTP Host header allows an Apache administrator full control over the hostname and port number part of the generated URLs, but the scheme is up to Apache itself.
Normally, the scheme is always "http". A module such as mod_ssl will override this and set the scheme to "https" for those locations where it is active. But that doesnt help you when the Apache server is behind another server that will handle the HTTPS traffic for you. Imagine the following layered approach:
- The clients HTTPS request comes in to the first machine on port 443 (the default port for HTTPS). The first machine, which perhaps has dedicated hardware to speed up SSL processing, accepts the connection and provides for all the encryption/decryption. It forwards the decrypted request as a regular HTTP request to port 81 on the next machine.
- The second machine runs Apache. It will be listening on ports 80 and 81. It will receive the request from the first machine on port 81. The fact that its coming in on that port establishes the request as being secure, and Apache may provide different processing rules depending on whether the request is secure or not. (Of course, the Apache server should be behind a firewall, so a client cant connect to port 81 directly and circumvent the access controls.)
Now, if Apache for some reason needs to generate a redirect, the scheme on the redirect URL will be "http", because thats what Apache is serving. But that URL isnt valid on the outside: the scheme should be "https", so that the client will proceed to get the new URL from the same secure location.
One solution is to let the machine that handles the SSL work do the rewrite from http://www.example.com:81/ to https://www.example.com/. But that doesnt help you if the first machine is (for example) a dumb SSL tunnel that doesnt understand HTTP. In that case, Apache will need to be convinced its scheme is actually "https", not "http".
Thats where mod_urlscheme comes in.
Installation:
These instructions assume a Unix installation. For other systems, please consult the Apache documentation. mod_urlscheme is a very simple module that requires no special treatment. Simply put, if you can build mod_example from the stock Apache tree, then you can build mod_urlscheme as well.
Put the downloaded mod_urlscheme.c file in a temporary directory somewhere where you will compile it.
If you want to include mod_urlscheme as a static module in your Apache server, prepare your Apache source directory as per the Apache build instructions. When calling the ./configure command, include the option --with-module=experimental:/path/to/mod_urlscheme.c (for Apache 1.3: --add-module=/path/to/mod_urlscheme.c). You need to specify the full path to the source file after the colon. Then, proceed with the build instructions as you would normally. The module will be included in your Apache binary as a static module.
For a dynamic module, first install a full Apache distribution, including the apxs tool and the C headers. If you install from pre-packaged bundles, such as RPMs, you may need to separately install the development package. On RPM-based systems that usually means you need to have the httpd-devel package installed. You will also need a fully functional compiler suite installed.
Go to the directory where you put the mod_urlscheme.c file and run apxs -c mod_urlscheme.c. Refer to the Apache documentation to see if you need to specify more command line options for your system.
If the compile succeeded, you will now have a dynamic Apache module ready to use. You may need to look in the .libs subdirectory to find the actual mod_urlscheme.so file (under Unix, that is). Copy the module to the Apache module directory, which is the modules subdirectory of the server root (for Apache 1.3: the libexec subdirectory). Alternatively, you can put it in any other location; just make a note of where you put it, so you can refer to the location later on.
<<lessPlease note that this module is different from mod_scheme, which embeds the Tinyscheme interpreter into Apache. You can find that module here. I changed the name from mod_scheme to mod_urlscheme to avoid confusion.
The original module was only written to work on Apache 2.0. There is now also a version for Apache 1.3 + EAPI, although it wont work with stock 1.3. Please see the "Apache 1.3" section at the bottom of this page for details. The 2.0 module will work almost unchanged on Apache 2.2. There is a small naming change in the API that requires a slightly different version.
In several situations, Apache will attempt to construct a URL that will point to itself and will deliver the result to the client. The most notable occasion for this is when Apache is constructing a client redirect. This can for example happen when the client requests a URL that maps to a directory but doesnt include a trailing slash: Apache will send back a redirect to the same URL, but with a trailing slash appended. Other occasions include Redirect directives in the Apache configuration, or mod_proxy rewriting redirects coming from a backend server (when mod_proxy is functioning as a reverse proxy).
A self-referential URL has four distinct major components: the scheme, the hostname, the port number and the request URI, the latter including perhaps a query string and a fragment identifier. The combination of ServerName, UseCanonicalName and the use of the clients HTTP Host header allows an Apache administrator full control over the hostname and port number part of the generated URLs, but the scheme is up to Apache itself.
Normally, the scheme is always "http". A module such as mod_ssl will override this and set the scheme to "https" for those locations where it is active. But that doesnt help you when the Apache server is behind another server that will handle the HTTPS traffic for you. Imagine the following layered approach:
- The clients HTTPS request comes in to the first machine on port 443 (the default port for HTTPS). The first machine, which perhaps has dedicated hardware to speed up SSL processing, accepts the connection and provides for all the encryption/decryption. It forwards the decrypted request as a regular HTTP request to port 81 on the next machine.
- The second machine runs Apache. It will be listening on ports 80 and 81. It will receive the request from the first machine on port 81. The fact that its coming in on that port establishes the request as being secure, and Apache may provide different processing rules depending on whether the request is secure or not. (Of course, the Apache server should be behind a firewall, so a client cant connect to port 81 directly and circumvent the access controls.)
Now, if Apache for some reason needs to generate a redirect, the scheme on the redirect URL will be "http", because thats what Apache is serving. But that URL isnt valid on the outside: the scheme should be "https", so that the client will proceed to get the new URL from the same secure location.
One solution is to let the machine that handles the SSL work do the rewrite from http://www.example.com:81/ to https://www.example.com/. But that doesnt help you if the first machine is (for example) a dumb SSL tunnel that doesnt understand HTTP. In that case, Apache will need to be convinced its scheme is actually "https", not "http".
Thats where mod_urlscheme comes in.
Installation:
These instructions assume a Unix installation. For other systems, please consult the Apache documentation. mod_urlscheme is a very simple module that requires no special treatment. Simply put, if you can build mod_example from the stock Apache tree, then you can build mod_urlscheme as well.
Put the downloaded mod_urlscheme.c file in a temporary directory somewhere where you will compile it.
If you want to include mod_urlscheme as a static module in your Apache server, prepare your Apache source directory as per the Apache build instructions. When calling the ./configure command, include the option --with-module=experimental:/path/to/mod_urlscheme.c (for Apache 1.3: --add-module=/path/to/mod_urlscheme.c). You need to specify the full path to the source file after the colon. Then, proceed with the build instructions as you would normally. The module will be included in your Apache binary as a static module.
For a dynamic module, first install a full Apache distribution, including the apxs tool and the C headers. If you install from pre-packaged bundles, such as RPMs, you may need to separately install the development package. On RPM-based systems that usually means you need to have the httpd-devel package installed. You will also need a fully functional compiler suite installed.
Go to the directory where you put the mod_urlscheme.c file and run apxs -c mod_urlscheme.c. Refer to the Apache documentation to see if you need to specify more command line options for your system.
If the compile succeeded, you will now have a dynamic Apache module ready to use. You may need to look in the .libs subdirectory to find the actual mod_urlscheme.so file (under Unix, that is). Copy the module to the Apache module directory, which is the modules subdirectory of the server root (for Apache 1.3: the libexec subdirectory). Alternatively, you can put it in any other location; just make a note of where you put it, so you can refer to the location later on.
Download (0.014MB)
Added: 2006-04-18 License: The Apache License 2.0 Price:
1284 downloads
Not A Commander 1.0-SNAP-051109
Not A Commander is an X11 file manager. more>>
Not A Commander is yet another file manager modeled after the Norton Commander. Good integration with the command line is the primary goal.
This project is using the technology of Natural Stupidity for development: first get something working at all, then gradually improve it. My primary targets are the features that I personally would use. The features that I wont use anyway are not planned to be implemented at all (though if someone would contribute an implementation I would gladly accept it - as long as it does not break any of the things that I use).
Build
Run `make. That should build all the binary parts. The X11 headers are required for build. You may need to modify the Makefile for peculiarities of your particular system (directory names, libraries etc.).
Installation
Run `make install. By default the `nac binary is instaled into /usr/local/bin and the rest of files is installed into /usr/local/lib/nac (which is referred further as "the NAC directory").
These directory names can be changed in the Makefile. If the configuration file nac.sysrc was present in the NAC directory before installation, it will be moved into nac.sysrc.old.
Configuration
The default configuration of NAC can be changed with rc files. There are two rc files:
per system - nac.sysrc in the NAC directory per user - .nacrc in the users home directory
These files are common Tcl scripts that can be used to change the tunable values. NAC first sets the built-in values, then loads the system-wide rc file (if present), then loads the users rc file (if present). Thus the system-wide script can examine the built-in values and modify them was neccessary, and the users script can do the same thing with the result
of the system-wide script.
Be careful with the syntax, in case of an error in the rc scripts NAC wont start.
The list of the supported tunables and their values can be found at the top of tune.tcl. For now (the alpha phase of development) its expected to be quite liquid and change between snapshot releases. Probably some sort of versioning will be added after it stabilizes.
The sample system rc file included in a release contains only one setting - the name of font to use (most probably you dont have the font "koi9x16" which is the built-in default).
The default initial size of the window is defined by panel dimensions, variables named set panel:filespercolumn (number of rows in panels), panel:ncolumns (number of columns in panels), panel:columnwidth (width of a column in dots). The internal xterm is automatically resized to fit these dimensions. Alternative size in pixels or xterm characters can be
selected with command line options.
Enhancements:
- Various bugs were fixed and workarounds were included for bugs in glibc and Tk.
<<lessThis project is using the technology of Natural Stupidity for development: first get something working at all, then gradually improve it. My primary targets are the features that I personally would use. The features that I wont use anyway are not planned to be implemented at all (though if someone would contribute an implementation I would gladly accept it - as long as it does not break any of the things that I use).
Build
Run `make. That should build all the binary parts. The X11 headers are required for build. You may need to modify the Makefile for peculiarities of your particular system (directory names, libraries etc.).
Installation
Run `make install. By default the `nac binary is instaled into /usr/local/bin and the rest of files is installed into /usr/local/lib/nac (which is referred further as "the NAC directory").
These directory names can be changed in the Makefile. If the configuration file nac.sysrc was present in the NAC directory before installation, it will be moved into nac.sysrc.old.
Configuration
The default configuration of NAC can be changed with rc files. There are two rc files:
per system - nac.sysrc in the NAC directory per user - .nacrc in the users home directory
These files are common Tcl scripts that can be used to change the tunable values. NAC first sets the built-in values, then loads the system-wide rc file (if present), then loads the users rc file (if present). Thus the system-wide script can examine the built-in values and modify them was neccessary, and the users script can do the same thing with the result
of the system-wide script.
Be careful with the syntax, in case of an error in the rc scripts NAC wont start.
The list of the supported tunables and their values can be found at the top of tune.tcl. For now (the alpha phase of development) its expected to be quite liquid and change between snapshot releases. Probably some sort of versioning will be added after it stabilizes.
The sample system rc file included in a release contains only one setting - the name of font to use (most probably you dont have the font "koi9x16" which is the built-in default).
The default initial size of the window is defined by panel dimensions, variables named set panel:filespercolumn (number of rows in panels), panel:ncolumns (number of columns in panels), panel:columnwidth (width of a column in dots). The internal xterm is automatically resized to fit these dimensions. Alternative size in pixels or xterm characters can be
selected with command line options.
Enhancements:
- Various bugs were fixed and workarounds were included for bugs in glibc and Tk.
Download (0.20MB)
Added: 2005-11-10 License: BSD License Price:
1445 downloads
Workspace Name Applet 0.0.2
Workspace Name Applet is a Gnome panel applet to display and edit the name of the current workspace. more>>
Workspace Name Applet is a Gnome panel applet to display and edit the name of the current workspace.
<<less Download (0.088MB)
Added: 2006-08-01 License: GPL (GNU General Public License) Price:
1181 downloads
Powered by Linux
Powered by Linux is a KDM theme created after a wallpaper of the same name. more>>
Powered by Linux is a KDM theme created after a wallpaper of the same name. It was tested on KDE 3.5.6.
<<less Download (0.70MB)
Added: 2007-03-16 License: GPL (GNU General Public License) Price:
953 downloads
Domain Name Portfolio 0.8.0
Domain Name Portfolio is a PHP and MySQL based application to help domain owners better organize their portfolio. more>>
Domain Name Portfolio is a PHP and MySQL based application to help domain owners better organize their portfolio.
It allows you to list your domains with their expiry, registrar, and a price.
Also allows visitors to your portfolio to contact you about a given domain.
Main features:
- Script features
Enhancements:
- This release brings support for MySQLi, along with minor bugfixes and several function improvements.
<<lessIt allows you to list your domains with their expiry, registrar, and a price.
Also allows visitors to your portfolio to contact you about a given domain.
Main features:
- Script features
Enhancements:
- This release brings support for MySQLi, along with minor bugfixes and several function improvements.
Download (0.15MB)
Added: 2007-07-30 License: GPL (GNU General Public License) Price:
822 downloads
Recursively create M3U playlists 1.1
Recursively create M3U playlists is a service menu which can create a file called playlist.m3u in each directories. more>>
Recursively create M3U playlists is a service menu which can create a file called playlist.m3u in each directories and sub directories.
You can edit recursively_create_M3U_playlist.py to change the name of playlist.m3u
To install, simply put recursively_create_M3U_playlist.py and recursively_create_M3U_playlist.desktop in ~/.kde/share/apps/konqueror/servicemenus
You need the package fapg installed.
Dont hesitate giving feedbacks or improvements.
Enhancements:
NEW FEATURES :
- 001 ==> Ask the name of the m3u playlist file
- 002 ==> Tell when its finished
BUGS FIXES :
- 001 ==> Much faster
<<lessYou can edit recursively_create_M3U_playlist.py to change the name of playlist.m3u
To install, simply put recursively_create_M3U_playlist.py and recursively_create_M3U_playlist.desktop in ~/.kde/share/apps/konqueror/servicemenus
You need the package fapg installed.
Dont hesitate giving feedbacks or improvements.
Enhancements:
NEW FEATURES :
- 001 ==> Ask the name of the m3u playlist file
- 002 ==> Tell when its finished
BUGS FIXES :
- 001 ==> Much faster
Download (0.001MB)
Added: 2007-03-18 License: GPL (GNU General Public License) Price:
960 downloads
nodoze 2.0
nodoze is a Perl script to repair websites built with MS Windows so that they will work properly on a UNIX server. more>>
nodoze is a Perl script to repair websites built with MS Windows so that they will work properly on a UNIX server.
It changes all file and directory names, and all relative URLS in the html, to lower case, and it changes all .htm extensions to .html.
When websites are built on on computers running Microsoft Windows, the case of file and directory names is often ignored.
Other "widowsizms" are also introduced (such as ending files with .htm instead of .html). This causes BIG problems if the site is served under unix.
What nodoze Changes
".htm" extensions in file names and in Relative URLs are changed to ".html"
< img src="document.htm" > becomes < img src="document.html" >
All files are renamed to lower case. All Relative URLs are changed to lower case
< img src="http:/Images/my.JPG" > becomes < img src="http:/images/my.jpg" >
"Dangerous" characters in URLs are escaped
< img src="a space.jpg" > becomes < img src="a%20space.jpg" >
"" characters in URLs become "/"
< img src="http:www.server.com" > becomes < img src="http://www.server.com" >
URLs are quoted
< img src=picture.jpg > becomes < img src="picture.jpg" >
Javascript: URLs are not changed by nodoze (i.e. the above doesnt apply to them)
Relative URLs (a.k.a Local URLs)
In a Relative URL the server is not named
< img src="http:/Local.JPG" > becomes < img src="http:/local.jpg" >
An Absolute URL is a mailto:, or a javascript:, or names a server
example: < img src="http://www.server.com/absolute.jpg" >
<<lessIt changes all file and directory names, and all relative URLS in the html, to lower case, and it changes all .htm extensions to .html.
When websites are built on on computers running Microsoft Windows, the case of file and directory names is often ignored.
Other "widowsizms" are also introduced (such as ending files with .htm instead of .html). This causes BIG problems if the site is served under unix.
What nodoze Changes
".htm" extensions in file names and in Relative URLs are changed to ".html"
< img src="document.htm" > becomes < img src="document.html" >
All files are renamed to lower case. All Relative URLs are changed to lower case
< img src="http:/Images/my.JPG" > becomes < img src="http:/images/my.jpg" >
"Dangerous" characters in URLs are escaped
< img src="a space.jpg" > becomes < img src="a%20space.jpg" >
"" characters in URLs become "/"
< img src="http:www.server.com" > becomes < img src="http://www.server.com" >
URLs are quoted
< img src=picture.jpg > becomes < img src="picture.jpg" >
Javascript: URLs are not changed by nodoze (i.e. the above doesnt apply to them)
Relative URLs (a.k.a Local URLs)
In a Relative URL the server is not named
< img src="http:/Local.JPG" > becomes < img src="http:/local.jpg" >
An Absolute URL is a mailto:, or a javascript:, or names a server
example: < img src="http://www.server.com/absolute.jpg" >
Added: 2005-10-10 License: Artistic License Price:
1476 downloads
Autocomplete Manager 1.6
Autocomplete Manager is an extension which provides advanced features for the address Autocomplete component in Firefox. more>>
Autocomplete Manager is an extension which provides advanced features for the address Autocomplete component in Firefox.
This extension provides advanced features for the address Autocomplete component in Firefox. It has been tested on Windows XP and Vista, Linux (Fedora Core 4), and Mac OS X.
Main features:
- searching bookmark addresses
- matching against page titles and bookmark names
- changing the sorting criterion to alphabetical, most-often-visited, most-recently-visited, or top-level pages first
- opening a suggestion from the popup in a new tab
- excluding local pages and pages containing search results
- matching any part of the domain
- popup appearance fine-tuning, including hiding page titles, changing the number of visible entries, and setting the truncation method for long addresses and page titles
In addition, one can switch between the default and the enhanced Autocomplete component, or turn it off altogether. The extension includes numerous fixes for Autocomplete-related bugs, as well as a rudimentary history manager, which can be used to view, add, and delete history entries.
<<lessThis extension provides advanced features for the address Autocomplete component in Firefox. It has been tested on Windows XP and Vista, Linux (Fedora Core 4), and Mac OS X.
Main features:
- searching bookmark addresses
- matching against page titles and bookmark names
- changing the sorting criterion to alphabetical, most-often-visited, most-recently-visited, or top-level pages first
- opening a suggestion from the popup in a new tab
- excluding local pages and pages containing search results
- matching any part of the domain
- popup appearance fine-tuning, including hiding page titles, changing the number of visible entries, and setting the truncation method for long addresses and page titles
In addition, one can switch between the default and the enhanced Autocomplete component, or turn it off altogether. The extension includes numerous fixes for Autocomplete-related bugs, as well as a rudimentary history manager, which can be used to view, add, and delete history entries.
Download (0.069MB)
Added: 2007-05-21 License: MPL (Mozilla Public License) Price:
909 downloads
Mp3dings 1.0 / 2.0 Beta 1
Mp3dings is a small, powerful and easy-to-use program allowing you to change the names and edit the meta-information of mp3s. more>>
Mp3dings is a small, powerful and easy-to-use program that allows you to change the names and edit the meta-information of a large number of mp3 files at the same time.
Main features:
- transfer information from filenames to ID3 tags and vice versa
- consistently name and/or tag your mp3 files
- reorganize the directory structure of your mp3 collection
Programs with similar scope usually lack the ability to process a large number of ID3 tags at the same time. Mp3dings is written in Java and can thus be used on every platform for which there is a Java Runtime Environment.
ID3 is a standard to store meta-information (author, title etc.) inside an audio file. An ID3v1 tag takes up a fixed number of bytes at the end of the file. This makes ID3v1 easy to implement but also severely limits the kind and amount of data such a tag can contain.
ID3v2 tags on the other hand can be arbitrarily large and can be used to store just about any kind of data. Naturally, this makes it quite hard to implement routines that read and write these tags. Mp3dings fully supports ID3v1 tags and a core set of ID3v2 frames (which will be extended gradually).
<<lessMain features:
- transfer information from filenames to ID3 tags and vice versa
- consistently name and/or tag your mp3 files
- reorganize the directory structure of your mp3 collection
Programs with similar scope usually lack the ability to process a large number of ID3 tags at the same time. Mp3dings is written in Java and can thus be used on every platform for which there is a Java Runtime Environment.
ID3 is a standard to store meta-information (author, title etc.) inside an audio file. An ID3v1 tag takes up a fixed number of bytes at the end of the file. This makes ID3v1 easy to implement but also severely limits the kind and amount of data such a tag can contain.
ID3v2 tags on the other hand can be arbitrarily large and can be used to store just about any kind of data. Naturally, this makes it quite hard to implement routines that read and write these tags. Mp3dings fully supports ID3v1 tags and a core set of ID3v2 frames (which will be extended gradually).
Download (1.0MB)
Added: 2007-07-27 License: GPL (GNU General Public License) Price:
819 downloads
MySpace Friend Renamer .86
MySpace Friend Renamer provides an extension that allows you to rename your MySpace Friends. more>>
MySpace Friend Renamer provides an extension that allows you to rename your MySpace Friends.
This adds a right click option to Myspace Pages and allows you to change the display name for any of your friends. Handy if your friends change names often, or pick strange and obscure names.
Also in response to comments. If a tab is not in focus when the page loads, the extension will not rename.
I believe that the extension will conflict with other extensions that change pages when they load. If I find a better way to do it, I will change it.
<<lessThis adds a right click option to Myspace Pages and allows you to change the display name for any of your friends. Handy if your friends change names often, or pick strange and obscure names.
Also in response to comments. If a tab is not in focus when the page loads, the extension will not rename.
I believe that the extension will conflict with other extensions that change pages when they load. If I find a better way to do it, I will change it.
Download (0.004MB)
Added: 2007-04-05 License: MPL (Mozilla Public License) Price:
934 downloads
Ubuntu Live Chat Support 0.3.14-7
UbuntuLiveChatSupport aims to provide an interface to communicate to other ubuntu users with the same language & location. more>>
The UbuntuLiveChatSupport aims to provide an interface to communicate to other ubuntu users with the same language & location, as well as to connect to the official ubuntu channel in Freenode.org. Ubuntu Live Chat Support also aims to get live chat support from ubuntu users right into the desktop menu, via "System > Help > Live Chat Support".
Rationale
People who dont speak english and want local support in their language will face a challenge to gain help in existing documentations, specially when there are just a few documentations for their language. But if they speak to someone that can understand their language, they can talk to an experienced user to provide them with answers. It might as well be positive, because there might be a good chance that they will collaborate on translation of documentations and software for their language, as well as contributing to the Ubuntu work.
Another problem with the current way of getting help in Ubuntu requires the user to read and browse documentations, but what most users really want is getting the right answers to the questions straight. Browsing and reading documentations sometimes require one to research on a particular problem. But to get the right answer from an experience user is the most easiest way.
Scope
This will use Gaim as an IRC client, but will not alter the main Gaim configurations. It will add the IRC channels defined in InternetRelayChat in Gaim buddy list, namely, Localized Channels, Support Channels, and Team Collaboration Channels.
Enhancements:
- Change the name "Auto-Join Default" to "Default"
- Overhaul the Local Channel names
- A new channel will be autojoined based on language.
- Added the language to "Local Languages" group
- Change the name of "Local Ubuntu Channels" to "Local Channels"
- UI improvements, in Nick registration, add a "Passwords do not match" warning.
- Impliment a settings in login page to choose from 2 different layout, the default top channels tab and alternative left channels tab. The static xchat-gnome look is removed.
- Add a new checkbox for privacy, when registration.
- Impliment registration privacy when the checkbox is toggled.
<<lessRationale
People who dont speak english and want local support in their language will face a challenge to gain help in existing documentations, specially when there are just a few documentations for their language. But if they speak to someone that can understand their language, they can talk to an experienced user to provide them with answers. It might as well be positive, because there might be a good chance that they will collaborate on translation of documentations and software for their language, as well as contributing to the Ubuntu work.
Another problem with the current way of getting help in Ubuntu requires the user to read and browse documentations, but what most users really want is getting the right answers to the questions straight. Browsing and reading documentations sometimes require one to research on a particular problem. But to get the right answer from an experience user is the most easiest way.
Scope
This will use Gaim as an IRC client, but will not alter the main Gaim configurations. It will add the IRC channels defined in InternetRelayChat in Gaim buddy list, namely, Localized Channels, Support Channels, and Team Collaboration Channels.
Enhancements:
- Change the name "Auto-Join Default" to "Default"
- Overhaul the Local Channel names
- A new channel will be autojoined based on language.
- Added the language to "Local Languages" group
- Change the name of "Local Ubuntu Channels" to "Local Channels"
- UI improvements, in Nick registration, add a "Passwords do not match" warning.
- Impliment a settings in login page to choose from 2 different layout, the default top channels tab and alternative left channels tab. The static xchat-gnome look is removed.
- Add a new checkbox for privacy, when registration.
- Impliment registration privacy when the checkbox is toggled.
Download (0.077MB)
Added: 2006-05-15 License: GPL (GNU General Public License) Price:
1258 downloads
Mantaray Console 2.0
Mantaray Console is a distributed, peer-to-peer, server-less communication & messaging solution for JAVA (JMS), C++ and .NET app more>>
Mantaray Console is a distributed, peer-to-peer, server-less communication & messaging solution for JAVA (JMS), C++ and .NET app. Offers guaranteed delivery, security and transactions. It supports TCP, SSL & HTTP protocols.
Basic Installation Instructions
-------------------------------
1. Extract the MantaRay file under a directory of your choice.
From now on, this directory will be called MANTA_HOME.
2. Set the VM argument.
This argument should hold the path (full/relative) to the MantaRay configuration file.
The default name of the MantaRay configuration file is default_config.xml, and it is
located in config directory.
To set the argument add the following text in the VM execution command:
-DmantaConfig=
Example:
java -DmantaConfig=c:/mantaray1.9/default_config.xml MyApp
For further information on how to set the mantaConfig argument, see the MantaRay User Guide.
3. Optional: Set a name for the MantaRay domain.
The domain name is the name of the group to which the peer will be related.
Setting this parameter prevents collisions between peers that dont share the group.
To change the domain name, set the value of the tag MY-PEER.DOMAIN in the MantaRay
configuration file.
For further information about the domain parameter, see the MantaRay User Guide.
4. Optional: Set MantaRay peer name in the configuration file of MantaRay.
Each MantaRay peer needs to have a unique name. To change the peer name, set the
value of the tag MY-PEER.NAME in the MantaRay configuration file.
By default, MantaRay sets the peer name according to the following format:
m
Example:
Local resolved IP: 192.168.1.44
Free port (in port range): 6600
The name of the MantaRay peer: m192.168.1.446600
For further information about the peer name parameter, see the MantaRay User Guide.
5. Optional: Change the mulicast IP address and multicast port.
These parameters are used when one enables the MantaRay Auto Discovery plugin (default).
Changing this parameter for each MantaRay peer in the same domain assures that all
the peers in the same domain are discovered, and that peers that dont belong to that
domain will not be discovered and will not interfere.
<<lessBasic Installation Instructions
-------------------------------
1. Extract the MantaRay file under a directory of your choice.
From now on, this directory will be called MANTA_HOME.
2. Set the VM argument.
This argument should hold the path (full/relative) to the MantaRay configuration file.
The default name of the MantaRay configuration file is default_config.xml, and it is
located in config directory.
To set the argument add the following text in the VM execution command:
-DmantaConfig=
Example:
java -DmantaConfig=c:/mantaray1.9/default_config.xml MyApp
For further information on how to set the mantaConfig argument, see the MantaRay User Guide.
3. Optional: Set a name for the MantaRay domain.
The domain name is the name of the group to which the peer will be related.
Setting this parameter prevents collisions between peers that dont share the group.
To change the domain name, set the value of the tag MY-PEER.DOMAIN in the MantaRay
configuration file.
For further information about the domain parameter, see the MantaRay User Guide.
4. Optional: Set MantaRay peer name in the configuration file of MantaRay.
Each MantaRay peer needs to have a unique name. To change the peer name, set the
value of the tag MY-PEER.NAME in the MantaRay configuration file.
By default, MantaRay sets the peer name according to the following format:
m
Example:
Local resolved IP: 192.168.1.44
Free port (in port range): 6600
The name of the MantaRay peer: m192.168.1.446600
For further information about the peer name parameter, see the MantaRay User Guide.
5. Optional: Change the mulicast IP address and multicast port.
These parameters are used when one enables the MantaRay Auto Discovery plugin (default).
Changing this parameter for each MantaRay peer in the same domain assures that all
the peers in the same domain are discovered, and that peers that dont belong to that
domain will not be discovered and will not interfere.
Download (2.1MB)
Added: 2006-06-15 License: MPL (Mozilla Public License) Price:
1228 downloads
WebPageIndexer 0.3.0
WebPageIndexer is a small utility that allows you to organize your html collections. more>>
WebPageIndexer is a small utility that allows you to organize your html collections, indexes and renames html files according to theirs titles.
In the past WebPageIndexer application was known as KHTMLOrganizer, but Ive changed its name.
There are many changes to program in interface, functions and features.
It uses ENCA library to detect charsets,if you have non-english html pages.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes a while. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Type `make install to install the programs and any data files and documentation.
4. You can remove the program binaries and object files from the source code directory by typing `make clean.
Enhancements:
- new interface
- new indexing mechanism
- new renaming mechanism
- new scripts to build debian fedara binary packages
- and etc...
<<lessIn the past WebPageIndexer application was known as KHTMLOrganizer, but Ive changed its name.
There are many changes to program in interface, functions and features.
It uses ENCA library to detect charsets,if you have non-english html pages.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes a while. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Type `make install to install the programs and any data files and documentation.
4. You can remove the program binaries and object files from the source code directory by typing `make clean.
Enhancements:
- new interface
- new indexing mechanism
- new renaming mechanism
- new scripts to build debian fedara binary packages
- and etc...
Download (0.48MB)
Added: 2006-01-04 License: GPL (GNU General Public License) Price:
1388 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 how do i change my name 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