Hi to all the main developers (Jon,Denis,Thomas, and anyone i'm forgeting), I'm just wondering if you guys have a feature roadmap for licq?
It would be great to see a push for a version 2 revamp, and because of the number of alternative clients now, i'm wondering if using some of their existing code would be a good move? kopete.kde.org is probably the biggest candidate since it's uses a qt native interface and is in it's intfancy (and is more aimed at kde integration that as a defacto client). And of course there is gaim. -- An Open Call for comments -- I think we have a great project here, and the stability and maturity of the project means we have a large user base, and a well integrated market in terms of distrobutions which ship licq. If we are to continue to keep that it would be a good move, LICQ primarily is a cross-desktop product, and i'd like to see that kept as the main concern as it seems to be a good neiche. The other neiche which LICQ operates in is it's integration with the underlying network tools, (in form of command scripts etc). Pushing these two point as drivers in design might work out, building features around automated responses, speaker bots, command line feed access to external programs, and security, and CURSES based interface.These are all features which make LICQ stand out from the other clients available. However the criticisms (as a lay user) I have are with it's lack of completeness when it comes to standard protocol options and compatibility with other clients extended features. i.e a) lack of voice call capability (could be implemented through open h.xxx(i forget the number) b) Contact info is incomplete and somewhat buggy (interface wise anyway), (does not display hobbies/interests, should allow for a more flexible contact system with extended info,and be modular for allowing plugins to add own tabs/pages for each contact) c) Modular protocol system ---> I know licq was developed as an ICQ client, but using existing modular systems, to implement in LICQ would be a great boon to it's user base. Still push licq as the main protocol but adding a unified messaging platform would be great (i.e jabber) d) Integration with other clients ssl type auth, I.e miranda's ssl plugin(gpl). Something small but it seems stupid not to have this feature, and also opens windows based computers as potential compatriots. these are the main things I think would be good for a version 2 push, how these would be implemented within the current prog is something which would need to be discussed. Perhaps moving to an XML format for contacts and history would be a good way of doing the second. This is an open call. I apologise if this is the wrong list to post too, but hopefully something constructive will come of this. Or if i'm off the spot on some of these issues. Kind regards Joel Wiramu Pauling
signature.asc
Description: This is a digitally signed message part
