[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: qextmdi
From:       "F () lk Brettschneider" <falk ! brettschneider () gmx ! de>
Date:       2003-05-16 22:09:53
[Download RAW message or body]

Hi,
In KDevelop cvs (lib/qextmdi), I've renamed all classes and files from 
prefix QextMdi to KMdi.
Only the lib target name is still the old one.
Waldo, David, now you can copy it to kdelibs/whereever!

Ciao
F@lk


Roberto Raggi wrote:

>On Friday 16 May 2003 16:31, David Faure wrote:
>  
>
>>On Friday 16 May 2003 15:57, Roberto Raggi wrote:
>>    
>>
>>>On Friday 16 May 2003 14:35, falk.brettschneider@gmx.de wrote:
>>>      
>>>
>>>>David, it was just a thought. It's OK with kdelibs/kutils. Cheers, F@lk
>>>>        
>>>>
>>>falk, as you know kdevelop must be compatible with kde 3.0 and 3.1 too,
>>>for this reason we must have a copy of qextmdi in our repository too..
>>>so, what do you think to change the API in kdevelop repository and then
>>>"copy" it into kdelibs?
>>>      
>>>
>>If you do that (including renaming the classes in the kdevelop tree),
>>kdevelop will have symbols that will conflict with kdelibs-cvs-head...
>>    
>>
>
>you're right! but, we can add it as a "compat" library, so kdevelop build it 
>only for kde < 3.2, or the other option could be to require kde head for 
>kdevelop... i like the idea to use cvs head and qt 3.2 for kdevelop 
>development, but i'm not sure that the other developers agree :)
>
>ciao robe
>
>
>  
>



[prev in list] [next in list] [prev in thread] [next in thread]