-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jon Keating wrote: > On Fri, Mar 31, 2006 at 05:36:44AM +0200, QnD [Joachim Staib] wrote: >
> >>- Things seem to be so unorganized. There are big steps to do, for example >>better plugin integration, video support, bug hunting .... and what comes >>in? A new error source: a third method of encryption (this is NO "attack" of >>the programmer of OTR. It is propably a good thing and important, but is it >>really the right time?), messing up the source more and more by making it >>bigger and bigger (and for the points below). > > > It is really nice to be able to support other forms of encryption. But as you > can see, I'm holding off on integrating the patch. I'd like to implement it > "properly"... working with a nice GUI and interfaces well with the source. Of > course the patch writer cannot interface it well with the source, because the > source is a mess and needs to be re-ordered. Have you ever added new features > to icqd-srv.cpp? It is over 4000 lines which is too big to manage. I spend > more time searching for the part to modify than modifying the code. First I thought about implementing the encryption as plugin. But later I saw that this is not possible. So I needed to make the changes in the base code. The encryption code as plugin would be very good. The aim should be to minimize the base licq code as much as possible. That's the only way improving of code is possible. > > And because of a lack of documentation, there aren't many people willing to > help out. It's like a vicious circle. A new documentation must be done with reoganizing the code. > > >>- The new web site is not bad from an ergonomic and stylistic standpoint but >>the content is (for someone like me who really likes licq and always gets >>butterflies in his stomach when a new version comes out) somehow >>embarrassing ... half of the plugins arn't working anymore, the themes are >>unorganized, just listed, and so on and so on > > I have spent some time working on the website, I created a blog to try and > get more opinions and see what people were interested in. And then I created > the Wiki to try and get documentation for end users working. But like most > other things, I am diong most of the work. There have been some user > contributions, thank you! A wiki is a good idea but I think many people don't know what to write there. What were the reasons to create this wiki? What should be organised there? > > >>The question is what to do? >>- create a REAL roadmap which is not based on sticky notes on Jons desktop >>but on a real serious list on the licq page > > > Yes, I created the Wiki with hopes of doing this. But then, I'm the only > programmer it seems... Ok then let's do it. Hey people out there, ADD SOMETHING USEFULL TO THE WIKI. Here we have the problem which QnD addressed with community project. What are the other developers doing at this time. (-> new wiki entry :) Are there people who add new features or plan to add except Jon? Don't misunderstand me. I don't think that Jon is the only one here but I only see Jon adding or changing code in svn. In IRC nearly all discussions must be with Jon because no other knows. Or am I wrong? Hopefully with reorganizing the code and better documentation more people understand the code and can comment questions on it. > >>- REALLY do everything together with a community, plan areas, plan dead >>lines (which still can cope with the "spare time project"-factor) > > > Hmm.. not to be sarcastic, but who is together? I'd love to have other people > helping out with the daemon or qt-gui.. but no ne has really stepped up. > Recently Martin has sent a few patches though. > > >>- tidy the site, ditch everytihng that isn't working > > > If anyone wants access to the modify the site, let me know. Maybe make a todo list in the wiki. > >>Sounds easy but is hard, I know too well. But (to say it again) Licq ran the >>wrong way. The code is in some parts too messed up. Do a rework, at lease >>40% can still be used. > > > Perhaps reorganization is a better phrase. Doing a rework sounds a bit too > much ;) ... and can be discouraging. > The planing can only be done by someone who knows the programm and the protocol in detail. The following rewriting shouldn't be done by only one person. If many people do rewriting many people understand the code. > > > Well, if you want to help it out, it would make things much better. Perhaps > we should start co-ordinating to get the reset button pressed. There are many > things to do, below is my list of things that I think should be done first: > > * Create a better plugin API > First we have to decide what information needs to be passed to plugins and > how the information is passed. Currently we use CICQSignal and ICQEvent > classes and pass them through a pipe to the listening plugins. Perhaps having > the plugin export a function, and then we call the function with specified > parameters is a better way. That way the same object won't be used for _all_ > different types of information. If that structure isn't enough, we create a > new member to the class and then all events require that extra member (even > if we don't use, it is taking up memory). > > * Create a better API for the protocol plugins > See above... > > * Strip out ICQ and make it be a protocol plugin > * Cleanup the new ICQ plugin's structure by: > * Removing unused code > * Organizing the source code layout in a logical way > We should make a todo-list/roadmap in the wiki with these points. After creating a list with what to do we should give it priorities and who can/wants to do it. regards rsLeo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFELZYfuFcJvHsEu9gRApVUAJ4mVFveFiHdVKYUl1IshSzEJFFuZwCghFnu YP7aBYWQ7E2CsQAV9s318LQ= =/gX+ -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
