EgS's blog http://quassel-irc.org/blog/3/atom/feed 2008-02-08T11:43:00+01:00 Mac OS X nightlys back on track http://quassel-irc.org/node/80 2008-06-28T16:40:03+02:00 2008-06-28T16:40:03+02:00 EgS After all the hazzle that came with the switch from svn to git and qmake to cmake, I'm glad to tell you, that the nightly builds for Mac OS X are available again. Currently there are only Mac OS X nightlys for 0.2 but that is about to change soonish. Get them as usual at http://quassel-irc.org/nightly/macosx/

]]> After all the hazzle that came with the switch from svn to git and qmake to cmake, I'm glad to tell you, that the nightly builds for Mac OS X are available again. Currently there are only Mac OS X nightlys for 0.2 but that is about to change soonish. Get them as usual at http://quassel-irc.org/nightly/macosx/

]]> alpha2 soon to come http://quassel-irc.org/node/60 2008-02-27T18:28:58+01:00 2008-02-27T18:35:21+01:00 EgS It's always amazing how easily one can be destracted from learning...
Despite having an exam next tuesday I've spent most of this day on fixing bugs and tweaking things for -alpha2. Sput's already fixed one of the major bugs: the client crash during first run network setup. So what to expect from -alpha2? Actually not much more than from -alpha1. :) Find a list of the fixes and features after the jump.

]]> It's always amazing how easily one can be destracted from learning...
Despite having an exam next tuesday I've spent most of this day on fixing bugs and tweaking things for -alpha2. Sput's already fixed one of the major bugs: the client crash during first run network setup. So what to expect from -alpha2? Actually not much more than from -alpha1. :) Find a list of the fixes and features after the jump.

- fixed a bug where the client crashes during first run network setup
- fixed a bug where the encoding was not correctly applied to /me-style messages
- fixed "ghost" buffers showing up in the "All Network" view.
- Notices and Messages like "no such nick or channel" can now be displayed in the status buffer, the current buffer or still the original target buffer (have a look at the general settings of your client)
- some cosmetic improvements (uncluttered the default client layout a bit and fixed widths of the Nicklist and Buffer Views)
- one can now switch buffers with the mousewheel while hovering over a bufferview (thanks to Ian "eean" Monroe for the patch)

We've added some more infos to the FAQ-Section, like some of the cool undocumented features of quassel, that came to our mind.

If you have any questions or suggestions, feel invited to join #quassel or #quassel.de on Freenode.

]]> Universal Binary Build available now for Mac OS X http://quassel-irc.org/node/54 2008-02-26T15:28:13+01:00 2008-02-26T15:28:13+01:00 EgS I just switched to universal binaries, so the Mac Client will be able to run on PPC Macs as well as on the new intel ones. Get it in the "Get Quassel!" section or right here.
Currently there is only the Client build. If you're interessted in precompiled Mac builds for the Quassel Core or the Monolithic Quassel, then please let me know.

]]> I just switched to universal binaries, so the Mac Client will be able to run on PPC Macs as well as on the new intel ones. Get it in the "Get Quassel!" section or right here.

Currently there is only the Client build. If you're interessted in precompiled Mac builds for the Quassel Core or the Monolithic Quassel, then please let me know.

]]> My First Blog Post http://quassel-irc.org/node/23 2008-01-17T15:32:38+01:00 2008-02-08T11:43:00+01:00 EgS This is not only my first post on Quassel IRC but my very first blog post at all.
I have to say that I'm pretty excited about what's happening in the last few weeks. The improvements on Quassel have been enormous. There've been already more than 50 commmits this month. Having just checked in Revision 353 and waiting for Sput's next big commit (which hopefully doesn't break anything - I'm always scared if someone says: dude I'm just reorganizing the multithreading in the core...), I'm having some leisure time, which I want to use tell you a bit about the current state of Quassel IRC.

]]> This is not only my first post on Quassel IRC but my very first blog post at all.

I have to say that I'm pretty excited about what's happening in the last few weeks. The improvements on Quassel have been enormous. There've been already more than 50 commmits this month. Having just checked in Revision 353 and waiting for Sput's next big commit (which hopefully doesn't break anything - I'm always scared if someone says: dude I'm just reorganizing the multithreading in the core...), I'm having some leisure time, which I want to use tell you a bit about the current state of Quassel IRC.

So where are we at and what does that mean for you? The first public release of Quassel IRC obviously comes closer and closer and just seems to be a footsetp away. More and more items are being removed from our Roadmap leaving only a few, not very difficult things to be done. So when Sput is done with is current work, we'll have a better organized core with lesser threads resulting in less overhead for keeping things threadsafe. In addition the setup process will be more intuitive (at least we think so), as some of our pre-alpha-whatchamacallait version pointed out that it's a bit confusing.

And the state of this blog? You might wonder, why this is the first Blog Post about Quassel though the development of Quassel has already been going on for quite some time. Well it's basically because due to the fact that we're more about coding and bringing Quassel IRC to you and less about blogging.

I hope we can keep you a bit more informed in the future here. Meanwhile you're invited to join #quassel on Freenode to keep up with the very latest news.

Cheers,
EgS

]]>