First of all, I've talked a bit in irc with pv2b already and created #kirssi
channel in OPN IRC network if anyone's interested joining there.
The very first thing to do would be to figure out how to use irssi's signals
easily inside C++ without horrible extern "C" { .. } hacks for each signal
handler. pv2b figured out some way to convert irssi's signals to QT's moc
signals. I think that would work pretty well :) It'd just need a perl script
to generate all the known signals from docs/signals.txt file. Sending
signals would still happen with irssi's signal_emit() function.
> - Modifications to konsole widget to allow mouse wheel scrollbacks and
> better copy & paste etc.
I don't think konsole would be good for it. Many people want GUI especially
for the proportional fonts, konsole can probably do only fixed size? Also
unicode support would be very good to have (irssi will have utf8 support).
> - Clickable tabs for channels
Some people like the MDI thing too .. and the separate windows. Would be
nice if users were able to choose whichever they want.
> - Ability to detach the IRC client from it's X display and run it text
> based and vice versa. (Now we're talking. :)
irssi-proxy kind of does that, but yes, it would be nice to have some
separate process which would automatically run when irssi is started and
contain all the information of server connections. it could by default stay
alive for 10 mins after the connection to kirssi client was lost for some
reason before shutting down completely. If the kirssi is started again
within 10 mins, it could ask if user wants to resume the previous session.
Of course the same feature would work with the irssi-text and you could
switch between irssi-text and kirssi. ..but this isn't very high priority at
the start i think :)
