Qt4 support

[Nicolas Castagné]

Hi there,

though I am not a developper of KDevelop nore Kde (yet ?;)).
I allow myself to say a couple of things, though.

>On 10/21/05, Amilcar do Carmo Lucas 
><<mailto:amilcar at ida.ing.tu-bs.de>amilcar at ida.ing.tu-bs.de> 
>wrote:
>Now a question for all KDevelop 3.4 developers:
>Which API should we use for KDevelop 3.4 ?
>KDE 3.2
>KDE 3.4
>or
>KDE 3.5 ?
>IMHO we should use KDE 3.4 API, because then we would remain compatible with a
>large number of user that do not want/can update to KDE 3.5


First of all, for a newcomer, let me say the 
version numbering of KDevelop is really confusing 
!

Kdevelop 3.2* was released along with KDE 3.4.
KDevelop 3.3* (currently 3.2.92) is to be relased along with KDE3.5.

Should I conclude that KDevelop 3.4 you are 
speaking about, Amilcar, is to be released allong 
with KDE... 3.6 ?
Well, never heard of a future KDE 3.6...

Basically, these differences in numbering are confusing.
It seems that KDevelop is the only K-Project that 
has such a specific version numbering (see 
http://www.kde.org/info/3.4.3.php).
I guess that there are hsitorical reasons for 
that, but it would be nice for us, users, 
downloaders, installers, etc, if it could be 
fixed one day.

Now, concerning your question Amilcar, I would 
assume that a large number of Kdevelop users 
often wanna upgrade their KDevelop without 
upgrading KDE (at least I do often !).
Consequently, there is a need to use an older KDE API.

If KDevelop 3.4 is to be released with "KDE 3.6", 
which AFAIK is not planned, then I would say, as 
a user, that using KDE 3.4 would be ok, since it 
was first released in March 2005.

A question, however : is KDE 3.* libs really 'upward compatible' ?
I mean : I have installed, for example, KDE 3.3*, 
and KDE 3.5*.. and it would be a mess if I could 
not compile KDE 3.4 because I don't have KDE 3.4* 
!

Wish these viewpoints could be of any help !

Nicolas


>I think targetting KDE-3.4 should be fine. By 
>then KDE-3.4 should be pretty well deployed and 
>it also reduces the "comptibility confusion" of 
>KDevelop. (KDE-3.4 - KDevelop-3.4)
>
>Of course, if someone wants to "backport" 
>incompatible changes to remain compatible with 
>KDE-3.2 I think we should accept those patches.
>
>// jens
>
>On 10/21/05, Amilcar do Carmo Lucas 
><<mailto:amilcar at ida.ing.tu-bs.de>amilcar at ida.ing.tu-bs.de> 
>wrote:
>
>Hi all,
>
>Matt can you move the work/kdevelop3.4 branch to kdevelop/3.4 ?
>Next time you move a branch please contact me first because otherwise the
>website breaks.
>Thanks.
>
>Now a question for all KDevelop 3.4 developers:
>Which API should we use for KDevelop 3.4 ?
>KDE 3.2
>KDE 3.4
>or
>KDE 3.5 ?
>
>IMHO we should use KDE 3.4 API, because then we would remain compatible with a
>large number of user that do not want/can update to KDE 3.5
>
>
>Regards,
>--
>Amilcar Lucas
>Current webmaster
>The KDevelop project
>
>_______________________________________________
>KDevelop-devel mailing list
><mailto:KDevelop-devel at barney.cs.uni-potsdam.de> 
>KDevelop-devel at barney.cs.uni-potsdam.de
><http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel>http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


-- 
-------------------------------------------------------------------
Dr Nicolas CASTAGNE

ACROE-ICA,
46 av. Félix Viallet
38 000 Grenoble
http://acroe.imag.fr

Tel : (33) 4 76 57 46 60
-------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20051021/4e1dd6f7/attachment.html>