Am Dienstag, 2. Februar 2010 schrieb Justin B Rye: > Jonathan Nieder wrote: > > For what it’s worth, I like this. I would leave out the > > “cross-platform” (what is more relevant is that it is graphical, and > > most software packaged for Debian is cross-platform these days). > > The question is, can you use the Debian quassel-front-end with a > quassel-back-end on a Windows box? > This is possible and intended. Due to that I'd leave cross-platform in here - because it truely it. > (Indeed, can multiple users, perhaps following different channels, > connect to one core? I'm assuming not; if so, it's worth saying.) > Multiuser support is planned for 0.6.0 > > Though probably it is worth mentioning that it works well on a cell > > phone. > > > > The use may still wonder “why?”, so I think you should mention the use > > for logs. > > > > When no clients are connected to the core, it stores messages in a > > database so they can be read later. > > That's more or less what I was thinking of as the "same advantages > as using screen[...]". Perhaps instead of "a connection to the IRC > server" it ought to say something about maintaining a presence on > the IRC channels. > > >> Maybe with the word "channels" in there somewhere. And surely > >> there's a label somewhere that describes this design... modular? > >> Master/slave? Or perhaps it's an IRC multiplexer... > > We should not go too far away from the upstream description by inventing new attributes. At http://www.quassel-irc.org/about upstream explains why quassel is modern, cross-platform and distributed > > Maybe: > > > > graphical multiplexing IRC client - core > > graphical multiplexing IRC client - Qt front-end > > And presumably: > quassel: > graphical multiplexing IRC client - Qt core+front-end we shall keep monolithic or mono - its upstream wording. > quassel-data: > graphical multiplexing IRC client - Qt data files > quassel-client-kde4: > graphical multiplexing IRC client - KDE front-end > quassel-kde4: > graphical multiplexing IRC client - KDE core+front-end > quassel-data-kde4: > graphical multiplexing IRC client - KDE data files > > If we do use these terms in the synopses we have to make sure that > the long descriptions bridge the gap back to the terminology assumed > in the upstream docs. Hang on, _are_ there any upstream docs? Even > the man page is a Debian addition... > Well - there is a wiki: http://bugs.quassel-irc.org/wiki/quassel-irc > >> So what advantage does it have over any other graphical IRC client? > > > > It looks like the layout is roughly based on WeeChat’s, so it might be > > comfortable for WeeChat veterans that want something graphical. > > > > Comparing <http://quassel-irc.org/node/104> with the screenshots from > > <http://lwn.net/Articles/216456/>, one benefit seems to be that it > > displays multiple channels at once in a single window, rather than > > using the insane tabbed layout some others use. But that is only my > > quick and uninformed impression. > > Putting WeeChat back in and reshuffling a bit: WeeChat must be within the desc - I decided to use: ... as WeeChat or irssi, but graphical. > > Quassel is a cross-platform IRC client made up of a "core" component, > which maintains a presence on IRC (and can store channel logs), and > one or more client front-ends, which can attach to and detach from a > local or remote core. It's like WeeChat combined with screen, but > graphical. > Take care -- Thomas Müller (Thomas Mueller) E-Mail: thomas.mueller@tmit.eu Packages: http://qa.debian.org/developer.php?login=thomas.mueller@tmit.eu Powered by Debian
Attachment:
signature.asc
Description: This is a digitally signed message part.