Re: CenterIM Update + Roadmap Proposal
Mark Pustjens <[email protected]> Fri, 2 Mar 2007 21:06:42 +0100 (CET)
| Newsgroups | gmane.network.centericq |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 1 Mar 2007, Stéphane Bisinger wrote: > Hi David, > > On 01/03/07, David Riebenbauer <[email protected]> wrote: >> Yesterday I requested the creation of a project called CenterIM at >> Sourceforge. I hope that my request will be approved in the course of >> this week. That also means that the name under which our development of >> Centericq will continue will also be CenterIM. > > That's great! > >> I think a name change isn't so bad after all, because this project >> involves new people and will possibly go into a different direction than >> Konst would have taken it. > > I agree with that. Also it underlines that we do not only support ICQ > as a protocol, but many many other protocols. > >> I would like to thank Konst for all the effort he has put into >> developing Centericq. It is an excellent program and very worthy to >> continue it's development. > > You have my thankfullness too, Konst. It's a great app, that's why > we're here talking about it! Yeah Konst, great app if i ever saw one. > >> In the git repository there is a new branch called libgaim now. It >> contains some changes where I started experimenting with the use of >> libgaim in CenterIM. It doesn't do much yet. Essentially it breaks the >> account dialog and makes it display a list of the protocol plugins of >> libgaim. > > I think that this is our best option, well done. > >> And here comes the roadmap proposal: >> >> 4.22.0 >> ====== >> >> The first release of CenterIM. This should be done soonish. Basically a release >> of the current git head as soon as the following points are solved. >> [...] > > Agree > Yes, but lets wait until some of the tasks mentioned in `Help wanted: simple tasks' are done (locating the patches mainly). >> 4.22.1 - 4.22.x >> =============== >> >> These should be released as the need arises, especially when important fixes >> become available. The points to focus on for these should be: >> [...] >> - Stabilization > > Maybe into this point we can include a revisiting of all the build > process. For now we should just focus on "making it work", but after > that we need to update everything to the latest (stable) autoconf, > automake, etc. and clean everything. > Another point to discuss: include libraries in the codebase, or as seperate packages, lets start a thread about that. >> 4.23.0 >> ====== >> [...] > > Ok for libgaim > > I would definitely add this: > - Fix visualizations with UTF-8 > > This doesn't mean UTF-8 support, but at least make it so that we can > display UTF-8 characters nicely. Maybe it could be possible to do that > with some iconv functions. > >> 4.24.0 >> ====== >> >> Multiple accounts per protocol >> ------------------------------ >> [...] > > Agree > >> 4.25.0 >> ====== >> >> UTF-8 support in the user interface >> ----------------------------------- > > This is one of the issues I care most about. It has some major > difficulties, though: if we are to introduce the use of wchar_t > instead of char, all the interfaces are going to change. So we need to > redesign the kkconsui and kkstrtext from scratch. Same functionality, > better code. I would not say `same' functionality. I would say `enhanced' (and then i do not mean utf8). What I mean is that more flexibility would be nice. Eg, i heard someone mention fullscreen chat. Another example would be multiple chat windows. During a redesign this can all be abstracted and be taken care of. But be aware: it seems that a lot of the current protocol hooks are very tightly intergrated with the ui. > > -- "Seems I can't get me 'ead down these days without rescuin' people or foilin' robbers or sunnink." -- It's a wonder dog's life (Terry Pratchett, Moving Pictures) _______________________________________________ Cicq mailing list Cicq-xGejAJT2w6wWP6gT/[email protected] http://mailman.linuxpl.org/mailman/listinfo/cicq Questions? Check the FAQ first: http://centericq.de/faq/