The day of seperation is here

[Falk Brettschneider]

Hi,

Christoph Cullmann wrote:

>On Tuesday 26 March 2002 23:01, Roland Krause wrote:
>
>>Ooops, very sorry for sending the last email.
>>I hit the browser send button, and feel like the fool I am right now.
>>
>>Anyway, friends, the day of seperation is here, lets get it over now.
>>
>>A fork can no longer be prevented.
>>
>>We have two possibilities.
>>
>>1 Rename gideon to KDevelop, and move KDevelop under a new name to
>>kdenonbeta. The name I like to suggest is Kollide.
>>
>>2 Move gideon to kdenonbeta and leave its name.
>>
>I like the current KDevelop 2.x stuff very much (because it WORKS (mostly) and 
>compiles here) and therefor would vote for making the current 
>KDEVELOP_2_BRANCH the new HEAD. Gideon is a nice "framework" but seems to be 
>far from completion or even a stage where you can actually do something 
>usable with it (and that didn't change since more than a half year). The 
>original creator of the HEAD stuff (I think Bernd was it or ?) seems to have 
>left the stuff laying around half working and to get the stuff into a usable 
>scheme a big rework (like mhk wants to do it and has started to do it) would 
>be needed. But why put that much work into a new but broken thingy and not 
>put the work into moving parts of the good ideas from gideon to the working 
>kdevelop 2.x stuff ? The parts idea behind gideon is the great thing of it 
>and with a bit work (as robe has shown) we can adapt that for 2.x. 
>KTextEditor for 2.x is in a reachable near as the kate interfaces differ not 
>much from plain ktexteditor (some stuff is perhaps missing, but that 
>interfaces we could add for kde 3.1 to the libs).
>
>As I am not a real kdeveloper my opinion should be seen as the opinion of a 
>user/external dev ;) and it would be: tag the current head as GIDEON_BRANCH, 
>move the KDEVELOP_2_BRANCH to head and steal interesting parts/interfaces 
>from gideon for kdevelop.
>
Wise words spoken. Chris, you summarize it all in a few sentences. 
Thanks a lot.
I second this idea very well.

Furthermore I just want to add that we _need_ all current Gideon hackers 
for the united KDevelop project. Hey, if the Gideon parts are ported, 
they still can hack on them like they did before! :-)
 Maybe it's also possible to get the multi-language mechanism into 
KDevelop-2.2. And as Chris said to check if the texteditor interface is 
mighty enough for the using as the KDevelop editor. But we must care to 
not rush to much, a fast and inconsiderate port is dangerous and could 
mess up KDevelop-2.2 as well. Roland maybe can you suggest us a roadmap?

>
>
>cu
>Christoph
>
>>Roland
>>
Ciao
F at lk



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com