[Licq-devel] Some GUI patches

Hi,

here is bunch of patches for the Qt4-GUI that fix session handling and
global shortcuts on KDE and make the display of remote user time less
intrusive.

ciao
  Jörg

From e096c0f979863f911097cc380f06389da6332e14 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=B6rg=20Mensmann?= <joerg_ml <at> bitplanet.de>
Subject: [PATCH 1/3] kde4-gui: Fix command line handling for plugin.

The plugin would interpret a "-session" argument as a request to set
the skin (-s). When restored by the session manager, it would
therefore try to load a non-existent skin file and fall back to the
default one, ignoring the skin selected by the user.

In addition, there is a workaround for handling "licq -- --help" and
argument parse errors gracefully. Since KCmdLineArgs::parsedArgs()
calls exit() directly in these cases, the Licq daemon would not be
shut down and the application would hang. The workaround installs an
atexit-handler that shuts down the daemon before calling parsedArgs().
---
 qt4-gui/src/core/licqgui.cpp |   32 +++++++++++++++++++++++++++++---
 qt4-gui/src/core/plugin.cpp  |   42 ++++++++++++++++++++++++++++++++++++++----
 2 files changed, 67 insertions(+), 7 deletions(-)

[Licq-devel] Licq 1.6.0 Released

The final release of Licq 1.6.0 is here.

Licq 1.6.0 contains both bugfixes and new features.

Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.6.0/

The Licq Team

[Licq-devel] Licq 1.6.0-rc1

The first release candidate for Licq 1.6.0 is ready for download.

Licq 1.6.0 contains both bugfixes and new features.

Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.6.0/

If you find any bugs, please notify us by creating an Issue in github:
https://github.com/licq-im/licq/issues?sort=created&direction=desc&state=open

The Licq Team

[Licq-devel] Migrating trac tickets [help needed]

I have gone through the list of tickets that we had in trac and tried to 
figure out what to do with them. The following is my suggestion on how 
to migrate them but I would appreciate feedback on this, especially on 
some of the tickets that I'm not sure about.

I've divided the tickets into 6 groups:
1) Tickets that have been fixed since trac was closed
2) Tickets I personally know are bugs
3) Bugs that I cannot confirm and/or don't have enough information on to 
understand - Please help me with these!!
4) Enhancements that are realistic to be implemented
5) Enhancements that will take more time and/or effort but might be 
worth remembering
6) Tickets that should probably just be forgotten

Suggested actions:
Group 2 and (partially) group 3 needs to be moved to some new ticket 
system. I will attempt to add them as Issues in github unless anyone has 
a better suggestion.
Group 4 and group 5 will be listed on an enhancement page on 
www.licq.org. (Probably the split between these two groups will not be 
kept.)
Group 1 and group 6 won't be migrated.

Below is a list of the tickets as I've grouped them and my comments on 
them. Please let me know if there are other opinions on the groupings.
(Some descriptions are a bit vague, full tickets are available in the 
trac.sql dump Jon posted to licq-dev in May or if needed in discussions 
I can post more details for specific tickets.)

[Licq-devel] Licq 1.5.1 Released

We are happy to announce the final release of Licq 1.5.1.

Licq 1.5.1 is bugfix release to fix some things found since the release 
of Licq 1.5.0. It also adds support for away messages in the jabber 
protocol.

Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.5.1/

If you find any bugs, please notify us through the licq-users mailing 
list. (Due to the move from trac to github we currently don't have any 
ticket system for Licq.)

The Licq Team

[Licq-devel] Licq 1.5.1-rc1

The first release candidate for Licq 1.5.1 is ready for download.

Licq 1.5.1 is bugfix release to fix some things found since the release 
of Licq 1.5.0. It also adds support for away messages in the jabber 
protocol.

Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.5.1/

If you find any bugs, please notify us through the licq-users mailing 
list. (Due to the move from trac to github we currently don't have any 
ticket system for Licq.)

The Licq Team

[Licq-devel] Trac server

Hey guys,

I have kept the Trac server in a read-only state for awhile, is it
ready to be taken offline yet?

Jon

[Licq-devel] Auto refuse

I asked this question on the official ICQ site. But if anything, it
was counter productive.

I have all the contacts I am ever going to have already. But I
constantly get requests from other contacts. Those are mainly in
languages I don't understand, empty, or full of advertisements I don't
care to be bothered by.

Is there a possibility to quite simply quietly just disregard incoming
requests? If, at the same time as I am not bothered, an offensive
response to the offending part is sent, that would be ok too.

Best regards!
Wed

Re[4]: [Licq-devel] Licq build on Mac

cmake output is in attach.

Tue, 28 Dec 2010 08:25:16 +0100 письмо от Erik Johansson <erik <at> ejohansson.se>:

> 2010/12/28 Andrey Danin <danindrey <at> mail.ru>:
> > I used cmake -G "Unix Makefiles". I guess this is a reason that
> lisq is x11 application.
> 
> No, I wouldn't think so. I build it like that. Can you please post the
> output from running cmake?
> 
> // Erik
> 
> -- 
> Erik Johansson
> Home Page: http://ejohansson.se/
> PGP Key: http://ejohansson.se/erik.asc

15:15 % cmake -G "Unix Makefiles" . -DCMAKE_INSTALL_PREFIX=/Applications/Licq.app
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Checking whether C compiler has -isysroot
-- Checking whether C compiler has -isysroot - yes
-- Checking whether C compiler supports OSX deployment target flag
-- Checking whether C compiler supports OSX deployment target flag - yes
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info

[Licq-devel] Licq build on Mac

[Licq-devel] Licq domains

Hi all,

As we are now moving to github we must decided what to do with the
licq.org domain. I have some suggestions:

licq.org and www.licq.org
Change these to point to http://licq-im.github.com/ in the way
described on http://pages.github.com/ under "Custom Domains". I have
created the CNAME file so the only thing left to do is change the DNS.

trac.licq.org
It would be very good if this could stay accessible for some time
(months?) to give us time to move stuff to GitHub.

svn.licq.org
I would like this to always stay up and serve the svn repo in a read-only mode.

Did I miss any domain?

Jon, since you are the admin of trac and svn, what do you say? If you
can't host them anymore maybe someone else can?

// Erik

--

-- 
Erik Johansson
Home Page: http://ejohansson.se/
PGP Key: http://ejohansson.se/erik.asc