Main

Documentation

Projects using SmartIrc4net

Powered by

log4net

Finally I released SmartIrc4net 0.4.0, which contains some interesting features and of course some outstanding bugfixes. The last release (0.3.5) was 2 years ago, and today I thought it's a nice day to make a release tongue.png Actually I have 2 weeks holydays starting today, means I have a lot of time for my projects. I focus on smuxi (the cross-platform graphical IRC client I am hacking) but as smuxi uses SmartIrc4net (what else) I wanted SmartIrc4net polished and bug-free before prime time face-smile.png most features I added in 0.4.0 was actually for smuxi, the reason why I kept delaying the release so much.
OK, enough gibberish, here the changelog, and here the download.

meebey | General | 6 04 2007 - 23:16 | 6 comments

I just upgraded this Jaws install to version 0.6.1, now you can comment on blog posts again. I had to disable comments because bastard spammers added 10,000 spams to my comments. Luckily a simple "DELETE FROM comments WHERE id > 2" was enough to get rid of them. With Jaws 0.6.1 CAPTCHAs are supported, thus the spammers will have now hard time to add spam here face-wink.png
Happy commenting tongue.png

meebey | General | 25 05 2006 - 14:53 | 1 comments

Finally SmartIrc4net is getting some documentation, part's are written by myself and most of it is contributed by Benjamin Hall (aka Blindspot). I uploaded a generated HTML view of the documentation (it's also linked on the left menu), take a look if you like. More documentation will follow with time. Soon the 0.4.0 version of SmartIrc4net will be released, hopefully together with Smuxi (the IRC client which I am developing), that's it for now.

meebey | General | 19 06 2005 - 21:19 | -1 comments

As you already know probably, the webview at http://svn.qnetp.net was offline duo berkley database corruption, caused by locking problems with subversion and viewcvs (the webview script for svn I use). I converted all subversion repository to the relative new "fsfs" backend, this means no berkley database and of course no berkley database corruption face-wink.png . By the way... you probably didn't notice but the server of SmartIrc4net changed, it's now a dedicated server for my projects, should be somewhat faster than before... happy source code browsing!

meebey | General | 27 03 2005 - 15:05 | 3 comments

Here we go again... SmartIrc4net v0.3.5 now available and ready for public use.
This release fixes some key bugs reported by SmartIrc4net users (thanks to those)! The release also contains some new features like non-RFC support for halfop, syncing the motd, tracking channel sync time. The auto-reconnect and auto-relogin code is now implemented. More details you can find in the changelog.
Although not common, some IRC servers violate the RFC in various ways, this is now handled with several sanity checks. I tested this release against one such IRC server for about 24 hours with channel sync activated in a channel with ~4000 users without error. Some better examples have also been added to this release including a benchmark.
This release is a big step forward at getting us closer to a stable and fully functional irc class.

What are you waiting for?
Get SmartIrc4net 0.3.5 now!

meebey | General | 29 01 2005 - 03:18 | 4 comments

Good news for all people that need non-RFC features like HalfOp, I finally decided how to implementate them. I didn't want to violate the RFC on the normal version of SmartIrc4net because I don't like to support such things (thats my own oppinion...). Anyhow, I respect my users needs so here it is, HalfOp support is commited to the SVN HEAD trunk. Thats the only non-RFC feature so far I added, but I may add more on feature requests basis. This means if you need anything special which is not covered by the RFC, please drop a feature request on the sourceforge project page, thanks!
How to use those non-RFC features like HalfOp?
Pretty simple, when you create an instace of the IrcClient class just set the SupportNonRfc property to true, then the object will allow/use NonRfcChannel and NonRfcChannelUser classes.
Here an short example (using GetChannelUser()):

IrcClient irc = new IrcClient();
irc.SupportNonRfc = true;
// ... Connect() Login() and so on...
NonRfcChannelUser nuser = (NonRfcChannelUser)GetChannelUser("#channel", "nick");
System.Console.WriteLine("user: "+nuser.Nick+" has halfop status: "+nuser.Halfop);
or another example (using GetChannel()):
IrcClient irc = new IrcClient();
irc.SupportNonRfc = true;
// ... Connect() Login() and so on...
NonRfcChannel nchan = (NonRfcChannel)GetChannel("#channel");
foreach (nuser as NonRfcChannelUser in nchan.Halfops.Values) {
        System.Console.WriteLine("user: "+nuser.Nick+" has halfop status: "+nuser.Halfop);
}
pretty forward I think, other non-RFC feature within channels and users will work the same way...

meebey | General | 1 12 2004 - 12:35 | Comment on this

Finally the 0.3.0 version of SmartIrc4net is released. This release contains a big API change (for being conform with the .NET library standards), many bugfixes and full feature support of all RFC commands, see changelog for more details:

Changelog:
http://sourceforge.net/project/shownotes.php?release_id=280984

Download:
http://sourceforge.net/project/showfiles.php?group_id=114302&package_id=123768&release_id=280984

meebey | General | 7 11 2004 - 23:43 | Comment on this

The documentation part is not taken much process lately, I am working alot on feature-completion. All RFC commands are now implemented with all overloads! Yes, it was alot of work! Also some bugs in the channel sync code are fixed, added some sanity-checks. What I will do soon, is move all RFC commands to its own property, this step is required to distinguish between IRC API and RFC commands, e.g. irc.Protocol.Version(); will request the version of the IRC server. All commands that are in IrcClient class will be API calls. This means IrcClient will not extend the IrcCommands class anymore, it will keep an instance of the class in a property called "Protocol" for all RFC commands. It is required because some RFC commands have names that I need for the SmartIRC API, like Quit() was not clear if its an API quit or just an IRC quit, or Connect() what about the IRC admin command "CONNECT" for linking IRC servers? There are some conflicts and sometimes it was not clear if the command is an API feature and does something special or just the plain IRC command is send. So this issue is finally solved!

meebey | General | 24 10 2004 - 01:42 | Comment on this

Since I released 0.2.0 to the public, I am working on 0.3.0. My focus is that SmartIrc4net is CLS and .NET standards conform. This included major changes in the events part (now everything is packed into EventArgs objects). I hope this will be the last major API change, so it's one step further to the API freeze. Also what I am working on for the 0.3.0 release is documentation! Yes, you read right, documentation face-wink.png It's one of the worst part of development (at least for me) but it's required and I do it for all SmartIrc4net users! The best IRC library wouldn't help much if nobody knows how to use it, makes sense I guess. You can see on the subversion repository the changes going on if you want. Allrights, thats all for now.

meebey | General | 27 09 2004 - 22:44 | 2 comments

As you can see, SmartIrc4net project has a nice homepage now. It's a Jaws project based page, check their page out, great project!
I will use this page for giving more details about SmartIrc4net like documenation, examples, howtos, faq etc. For now I have to find out how to use this cool jaws, but up to now it was very easy to install, setup and writing this blog entry face-wink.png
Allright you will see when things on this page change, keep an eye on it!

meebey | General | 26 09 2004 - 18:22 | Comment on this