Finishing my personal crusade against Buffer. Note: this was heavy surgery... please let me know if I did cut the guts or any other innards...
Continuing my personal crusade against Buffer. - activity changes are now handled purely in the NetworkModel - Sput: I can only hope for you that there are no conflicts with your local repo :)
Post-merge cleanups, remove the old message handling
Bring back lastSeen support. Buffer has been hacked even closer to death now.
Bring back activity levels. I think Buffer has to go soon, since this is all that it does now.
Fix warnings from GCC 4.3 about suggested parentheses. In GCC 4.3 there are further cases that are suggested to be given parentheses, to make sure that the result is the actuall behaviour looked for. Fix the cases so that warnings are not reported for these. Signed-off-by: Manuel Nickschas <sputnick@quassel-irc.org>
performance++
CTCP ACTION (/me style messages) are now treated like regular messages regarding activity updates
switching from timestamps to msgid regarding lastseen states
own messages no longer update the activity status
Fix client crash at core disconnect.
This should fix duplicate messages that would occur when new messages arrived while the backlog was still being requested. Breaks core protocol, because somebody *cough* forgot to serialize the MsgId of Message objects...
Now activity sync should work... and yes, I did accidentally stop the core _again_... -_-
(Hoperfully) fixing activity syncing. We really shouldn't refuse to update invalid lastSeen timestamps...
Buffer activity levels are now synced between clients, meaning that seeing a buffer in one client will clear activity for that buffer in other clients too. NOTE: Activity state is not yet remembered between core restarts, since there are still some database issues. Client/core protocol updated, distclean mandatory.
replaced Client::fakeInput() with Client::userInpt() (now static but no longer a slot) if you need sig/slot usage: connect your SIGNAL directly to Client::instance(), SIGNAL(sendInput(BufferInfo, QString))
Features come and features go... - the Buffer object is stripped down as possible but still exists in as a Hash in the Client. This will be changed once the Auth Process is redone. - the client lib no longer depends on QtGui \o/ - channel activities are no longer shown (will be fixed soon) :( - networks and channels are now once again greyed out when not in use \o/ - basic tabcompletion works again \o/
As preparation for revamping the whole networking stuff, I did two renames: Server -> NetworkConnection NetworkInfo -> Network Quite a disrupting change, hope everything still works. GUI Protocol version increased to 5, distclean advised.
Fix license headers: Quassel IRC Team -> Quassel Project, 2007 -> 2008
Making Quassel slowly ready for its first release... - Fixed all license headers so that they look consistent; we also now allow GPL v2 and v3 (but no blank "or later" option) - Added new and edited old READMEs and INSTALLs and stuff - Added the texts of the GPL v2 and v3 as required Ok, so that should take care of the legalese, now we have to polish the code... :)