Menu
▾
▴
icqlib-dev
You can subscribe to this list here.
| 2000 |
Jan
(16) |
Feb
(6) |
Mar
(1) |
Apr
(5) |
May
(8) |
Jun
(12) |
Jul
(19) |
Aug
(4) |
Sep
(2) |
Oct
(5) |
Nov
(2) |
Dec
(13) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(22) |
Feb
(12) |
Mar
(23) |
Apr
(3) |
May
(10) |
Jun
(26) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: FigBug <rr...@gu...> - 2000-01-24 15:49:57
|
>And what is the best way: leave icqlib implemented with plain C and add C++ >wrapper to it or switch icqlib to the C++ language? What are all of you >guys thinking? My vote is for C, but that is because my client is written in C. If you do switch to C++, I could always figure out a way to put C wrapper around it, so it's not a big deal. |
|
From: Bill S. <we...@os...> - 2000-01-24 14:20:58
|
On Mon, 24 Jan 2000, Denis V. Dmitrienko wrote: > Vadim Zaliva <lo...@cr...> writes: > > > Hi! > > By they way, as part of my other projec, I am finishing now tiny C++ > > wrapper around ICQLIB. Once it will be ready (within a week) I will send > > you description. Maybe we can provide it as optional part of ICQLIB. > > And what is the best way: leave icqlib implemented with plain C and add C++ > wrapper to it or switch icqlib to the C++ language? What are all of you > guys thinking? I know from my work on the tcp section of the lib I think it's _very_ clear that they implemented the real ICQ protocol in C++, almost all of my tcp code is very OO-like. Especially by the way the tcp hello and tcp packets work- the more specialized packets are simply copies of existing packets with extra information tacked on the end, indicating to me in the real ICQ they probably used inheritance, etc. I think it would be a good change, but I also don't know anything about portability so I can't comment. We'd really need to use STL I think- but is this portable now? It seems most C++ implementations have at least a basic STL now, and we could always try to stick to the simple types (especially since that's all we really need anyway) like lists and queues. I also think it would _significanly_ clean up the library interface. ex: ICQ::Contact denis( DENIS_ICQ_NUMBER ); ICQ::Link *link = new ICQ::Link; link->contactList.add( denis ); link->setStatus( ICQ::Online ); ICQ::Message message( "C++ icqlib!" ); link.sendEvent( message ); delete link; Either way we're going to need to make an interface change soon I think. So I say go for it, as long as it maintains portability (if that's still one of your design goals Denis). Bill |
|
From: Denis V. D. <de...@nu...> - 2000-01-24 13:55:59
|
Vadim Zaliva <lo...@cr...> writes: > Hi! > By they way, as part of my other projec, I am finishing now tiny C++ > wrapper around ICQLIB. Once it will be ready (within a week) I will send > you description. Maybe we can provide it as optional part of ICQLIB. And what is the best way: leave icqlib implemented with plain C and add C++ wrapper to it or switch icqlib to the C++ language? What are all of you guys thinking? -- Denis V. Dmitrienko | E-mail: de...@nu... | ICQ#: 5538614 Home page: http://www.cn.ua/~denis |
|
From: Vadim Z. <lo...@cr...> - 2000-01-23 05:35:05
|
Hi! By they way, as part of my other projec, I am finishing now tiny C++ wrapper around ICQLIB. Once it will be ready (within a week) I will send you description. Maybe we can provide it as optional part of ICQLIB. Vadim ;;----------------------------------+-----------------------------------+ ;; Vadim Zaliva + Those who do not understand Unix + ;; mailto:lo...@cr... + are condemned to reinvent it, + ;; http://www.crocodile.org + poorly. (H. Spencer) + ;;----------------------------------+-----------------------------------+ |
|
From: Denis V. D. <de...@nu...> - 2000-01-20 20:37:47
|
Hi. Please take a look at this: http://www.linuxsupportline.com/~pgp/linux/icq/ Please pay attention to the libicq library and its API. -- Denis V. Dmitrienko | E-mail: de...@nu... | ICQ#: 5538614 Home page: http://www.cn.ua/~denis |
|
From: Bill S. <we...@os...> - 2000-01-20 20:37:47
|
2000-01-20 Bill Soudan <so...@kd...>
Worked more on file send implementation. icqlib will now also
handle sending file requests to clients.
* icqlib/filesession.c, filesession.h, icq.h.in, stdpackets.c
stdpackets.h, tcp.c, tcpfilehandle.c, tcphandle.c:
first implementation of sending file requests
* icqlib/tcplink.c: fixed bug in icq_TCPLinkConnect that caused
file/chat connection attempts to go to the wrong port
|
|
From: Denis V. D. <de...@nu...> - 2000-01-19 18:14:32
|
kicq-0.4.0-0.snap19991212.src.rpm 510164 kicq-0.4.0-0.snap19991212rh61.i386.rpm 453575 Download locations and build machine information listed below. RPMs are built with rpm version 3.0.3. Required programs listed are either updates or are not in the default RedHat 6.1 installation. Name : kicq Relocations: (not relocateable) Version : 0.4.0 Vendor: Denis V. Dmitrienko <de...@nu...> Release : 0.snap19991212 Build Date: Tue 18 Jan 2000 06:07:21 PM CST Install date: Tue 18 Jan 2000 06:08:16 PM CST Build Host: hellstone.infohwy.com Group : Applications/Internet Source RPM: kicq-0.4.0-0.snap19991212.src.rpm Size : 958601 License: GPL Distribution: Freshmeat RPMs Packager : Ryan Weaver <ry...@in...> URL : http://kicq.sourceforge.net/kicq.shtml Summary : ICQ clone for KDE. Based on ICQ library icqlib 0.1.3 Description : kicq is an ICQ (I seek you) client. It's beta code and you may use it at your own risk. This program was made without any help from Mirabilis or there consent. Not reverse engineering or decompilation of any Mirabilis code took place to make this program. Core Developers --------------- Denis V. Dmitrienko <de...@nu...> Nikita I. Makeev <wh...@ni...> Bill Soudan <so...@kd...> Secondary Developers -------------------- Markus Goetz <gu...@gm...> Kyle Smith <ky...@13...> Requires: -------------------------------------------------------------------- Package Distribution (Or Url) ==================================================================== icqlib-0.2.0-0.snap19991212 Freshmeat RPMs kdelibs-1.1.2-9 KDE qt1x-1.44-4 KDE -------------------------------------------------------------------- %CHANGELOG * Tue Jan 18 2000 Ryan Weaver <ry...@in...> [kicq-0.4.0-0.snap19991212] - ReWrote Specfile (again). . Spec will look for and use KDEDIR environment variable. . Requires qt-1.44. Spec will look for QTDIR if it is set to /usr/lib/qt-2* ( ie: RedHat-6.1 ) it sets it to /usr/lib/qt-1.44. If not set like this and is qt >= 2.0 build will fail, even if qt = 1.44 is installed. - Upgraded to 0.4.0 snapshot 19991212. - See ChangeLog for details. * Mon Dec 14 1998 Ryan Weaver <ry...@in...> [kicq-0.3.0-2] - ReWrote Specfile. - Version 0.3.0 (08 Dec 1998) ! New Messages/URLs set blinking icons rather than popups immediatly. ! View Message History on each user in Contact List. ! SOCKS5 proxy support. ! Send/Receive URLs. ! Docking in kpanel. Rename user ability. Beep on new Messages/URLs. Alert/Accept Modes popup menu with Online Alert and Visible to User items. Reconnect on disconnect. Preferences for sound and SOCKS5 proxy. Main window remember position, size, desktop and other properties. Info fields like ICQ# and message body can be scrolled and copied by mouse. Changed empty lines in Info window to "Not Entered". Message body size limit. Popup menu focus grabbing with Qt-1.41+ fixed. Enabled already implemented search by ICQ# feature. Fixed "wide" Info button in Windows style of KDE. Login password stripped to 8 symbols. Many many other bug-fixes and improvements... * Wed Dec 09 1998 Ryan Weaver <ry...@in...> - Updated to Version 0.3.0 * Wed Oct 28 1998 Sorin Lingureanu <so...@dn...> - first rpm version ================================================================== RPMs are built on a Pentium II 450mhz w/98megs RAM with RedHat 6.1 plus updates from ftp://updates.redhat.com installed. These files are also available on the following sites ftp://ftp.falsehope.com/pub/kicq ftp://ftp.tux.org/pub/sites/ftp.falsehope.com/kicq ftp://ftp.freshmeat.net/pub/rpms/kicq PGP Key can be found at ftp://ftp.falsehope.com/pub/Ryan_Weaver.pgp.key GPG Key can be found at ftp://ftp.falsehope.com/pub/Ryan_Weaver.gpg.key -- ,------------------------------------.,------------------------------------. | Ryan Weaver || email: ry...@in... | | Unix Systems Administrator || phone: (281) 447-7025 | | InfoHighway International Inc. || web : http://www.infohwy.com | `------------------------------------'`------------------------------------' |
|
From: Bill S. <we...@ri...> - 2000-01-16 21:49:27
|
Got the date right this time. :)
2000-01-16 Bill Soudan <so...@kd...>
Exported icq_FileSession structure to library clients;
fixed a serious list bug. Oops. :)
* icqlib/filesession.c, filesession.h: added new public functions,
icq_FileSessionSetSpeed, icq_FileSessionClose,
icq_FileSessionSetWorkingDir, moved icq_FileSession interface to
icq.h.in
* icqlib/icq.h.in: added definition for icq_FileSession and new
public functions
* icqlib/list.c: fixed serious bug in list_remove
* icqlib/tcp.c: renamed icq_TCPAcceptFileReq to
icq_AcceptFileRequest, moved file request functions to new
file session code
* icqlib/tcpfilehandle.c: added code so icq_FileSessions now
keep track of the tcplink to which they are attached
* icqlib/tcplink.h: removed list_node from icq_TCPLink
|
|
From: Bill S. <we...@ri...> - 2000-01-16 04:07:36
|
Should have done it this way in the first place. Now that I want to
export the file and chat session structures, I realized it wasn't a good
idea to put the list_node in the item structure. Plus it also got rid of
the strlist code.
1999-01-15 Bill Soudan <so...@kd...>
Reworked list routines so list_node's don't need to be
inside item structures. Note this made the strlist code
unnecessary - strlist code was replaced with generic list
commands.
* icqlib/Makefile.am: strlist.c, strlist.h removed
* chatsession.c, chatsession.h, contacts.c, contacts.h,
filesession.c, filesession.h, icqlib.c, icqpacket.c, icqpacket.h,
list.c, list.h, queue.c, queue.h, tcp.c, tcplink.c, tcplink.h,
udphandle.c: reworked list code, removed strlist code
* strlist.c, strlist.h: removed
|
|
From: Denis V. D. <de...@nu...> - 2000-01-11 17:02:08
|
Hi. Congratulations! CVS repositories have been successfully moved to the SourceForge. I recommend you to checkout sources from scratch with new CVSROOT to avoid any problems. -- Denis V. Dmitrienko | E-mail: de...@nu... | ICQ#: 5538614 Home page: http://www.cn.ua/~denis |
|
From: Denis V. D. <de...@nu...> - 2000-01-06 18:54:28
|
Vadim Zaliva <lo...@cr...> writes: > Hi! > I just checked icqlib RPM from file area on sourceforge and > it does have some strange dependencies: I didn't package any of them. But since previous stable versions of icqlib+kicq I got some experience in RPM packaging. So I can and will write spec files for next versions of them. > Unfortunatly I do not have spec file for either and > not RPM expert to build new one. > Could somebody please help me with these RPMs? Meanwhile I uploaded RPMS/SRPMS packages to the SF download area. They were taken from the BlackCat 6.02 distribution. kicq-0.3.0-5bc.i386.rpm: http://sourceforge.net/download.php?fileid=1215 kicq-0.3.0-5bc.src.rpm: http://sourceforge.net/download.php?fileid=1216 icqlib-0.1.3-4bc.i386.rpm: http://sourceforge.net/download.php?fileid=1217 icqlib-0.1.3-4bc.src.rpm: http://sourceforge.net/download.php?fileid=1218 -- Denis V. Dmitrienko | E-mail: de...@nu... | ICQ#: 5538614 Home page: http://www.cn.ua/~denis |
|
From: Vadim Z. <lo...@cr...> - 2000-01-04 06:57:02
|
Hi!
I just checked icqlib RPM from file area on sourceforge and
it does have some strange dependencies:
[root@r90 lord]# rpm -Uvh icqlib-0.1.3-4.i386.rpm
error: failed dependencies:
qt-egcs-10x is needed by icqlib-0.1.3-4
kdesupport-rh5x is needed by icqlib-0.1.3-4
kdelibs-rh5x is needed by icqlib-0.1.3-4
[root@r90 lord]# rpm -Uvh icqlib-0.1.3-4.i386.rpm
(I have hand compiled KRASH release of KDE and gcc-2.95.2)
I do not think it should depend from KDE and QT.
In fact version 0.1.3 does not, it is just the way RPM
have being built.
There is another RPM somebody made while ago:
ftp://ftp.crocodile.org/pub/icqlib-0.1.3-1.i386.rpm
which does not have such dependency.
Unfortunatly I do not have spec file for either and
not RPM expert to build new one.
Could somebody please help me with these RPMs?
Sincerely,
Vadim
;;----------------------------------+-----------------------------------+
;; Vadim Zaliva + Those who do not understand Unix +
;; mailto:lo...@cr... + are condemned to reinvent it, +
;; http://www.crocodile.org + poorly. (H. Spencer) +
;;----------------------------------+-----------------------------------+
|
3 messages has been excluded from this view by a project administrator.
