savIRC Graphical IRC Client

File Release Notes and Changelog

Release Name: 2.0

Notes: Well, it has been a long year. Sander has left the project, phobie has joined the project, and I must say if it were not for him, savIRC would still be limping along if it were only me working on it. If you have been using 1.99 or earlier versions we urge you to upgrade. This is by far, the most polished version of savIRC. Lots of bugs have been fixed, several new features have been implemented, and the code has and still is going through a major transformation. What this means is that developers should have an easier time understanding how savIRC works, but not only that, they will only need to learn a small part of the code base, since it is becoming more modular. It isn't there yet, but we are well on our way. Please read the INSTALL.txt for installation instructions. And remember, help from everyone counts, no matter how small you may think it is. We're always looking for more developers, testers, and doc writers.

---

Changes: The main features of the 2.0 release are: * Faster GUI-handling * Better multi-server support * New DCC subsystem * New Channel Settings window * A Text-High-Lighter * A new /server-command. As all commands, just type the command name without arguments for a short instruction. * You can now select a port-range for DCC SEND and CHAT. * Select how savIRC detects your IP address with 3 options: A) IP Detection php scripts (Web) B) Using dyndns.com, or other similar service (You must have an account) C) IRC Server * Clicking the Help, menu item now launches a web browser to the Docs on savirc.com * Tab complete now works in chats and queries * Save Session (on *nix). If you log out of your desktop with savIRC still running, and you log back in, savIRC will start automatically. * You can finally select multiple nicks and mass op/voice * Bluefish encryption - Compatible http://fish.sekure.us/ * Connect to servers with SSL support (usage: /server -i ServerName -e ssl) We have fixed numerous bugs, although some have not always been recorded. However visiting our bug tracker you can get an idea. http://www.savirc.com/bugs/changelog_page.php For a complete list of commited changes use subversion: svn log -r235:624 http://svn.savirc.com/savirc