Crisis of a marriage?

[Victor Röder]

Hi, August, Falk and all the others!

> if it is possible for "several" plugins
>  * which ones are "several" ?

In Robe's screenshot I saw the FileSelectorPart :-).

>  * if roberto did them in very short time, it should be possible to
>    do the others, too -- or is there something that prevents this

Hmmm, that depends on the parts. Some are (I think so) easier to 'plug-in', 
e.g. the FileSelPart - others are very hard to plug-in: the language support 
parts for example. (But I read that KDevelop 2.2 should only support C/C++(?))

> looking some time into the future: so, there are kdevelop and gideon
> and the FAQ includes:
>  * what is the difference ?

I think the UI: 	KDevelop => VS C++
		Gideon => IntelliJ IDEA :-)?

>  * which user should use which one ?

That would be in the sphere of influence of the user :-).

> suggestion:
> lets define targets to reach and then talk about how to reach them,
> and if we need two different tools
> kdevelop has come a long way and it is the best ide around - there
> is no place for "the two best" ides - and it seems that there arent't
> enough developers for two ides (look at the development of gideon)

Agreed, but let me emphasize my following opinion: I'm neither for nor 
against a fork. I have no preference. I think both would have advantages and 
disadvantages.Only a few words to the two options (the proceeding - in my 
eyes):
1) No fork: Gideon (the framework) get's some polish and everything it need's 
- even the functionality of KDevelop in the long run. All KDevelop developers 
(with united effectivity) are concentrated on Gideon in the long run (I DO 
understand that "giving up" KDevelop2 development would be very brutal for 
its users :-) and Gideon becomes a stable and solid IDE.
But: We have accept compromises :-)

2) Fork: KDevelop keeps a C/C++ IDE and Gideon becomes a multi-language IDE. 
These two IDE's have differences maybe in their look and feel - but are more 
or less compatible (How? I don't know :-) so that the C/C++ parts of KDevelop 
are working in Gideon (that would be desirable). Both teams could implement 
their ideas in two projects
But: Forking the projects = forking the developers :-)

> No. Even now there seems to a real beginning of a merging of both worlds
> as Robe proved that today.

Hmmm, I talked to Roland and his goals are clear: In his eyes it's better to 
fork and/or make Gideon obsolete. It's a little bit dangerous and tricky at 
the moment, I think: No one knows what the other wants to do. Even in the 
"old" team :-).

> The main aim is to provide KDevelop users with good and stable releases,
> now we get a chance to profit from the KDevelop2 usuability and
> stability married with Gideon features.

Hmmm, but why can KDevelop now load Gideon plug-ins, so that Gideon becomes 
obsolete?

> I don't understand what result you want in the end. Another 'K' menu
> entry 'Development'-->'TheOtherAlmostTheSameKDevelopAkaGideon'? Does
> that make KDE programmers more happy?

No, not really. I'm not adamant that KDevelop and Gideon go different ways. I 
listened to Roland's reasons (pro fork) and they sounded quite serious.
I thought that "everybody" of you share his opinion. That you (Falk) are 
against a fork, is suprising for me...

> Victor, you're good programmers, keep in the boat, At the moment we're
> trying to overcome the divided world, please, support that, too.

Never fear and no ceremony!  ;-P

Bye,
	Victor