nicolas.alvarez at gmail.com
Fri Jul 28 17:44:06 UTC 2017
> El 28 jul 2017, a las 12:32, Aleix Pol <aleixpol at kde.org> escribió:
> Dear KDevelopers,
> During the BoF we were discussing whether it would make sense to merge
> kdev-python and kdev-php like we did with kdev-clang and kdev-qmljs.
I would say no but I don't have a good justification ^^ I'll think about it.
> Furthermore, we discussed whether it would make sense to merge
> kdevplatform into kdevelop because:
> - nobody is using the abstraction
> - will definitely simplify the steps to take by new contributors
I think a separate kdevplatform is not particularly useful in its current form. In practice it's not easy to make a new IDE based on kdevplatform, for many reasons.
For example, how do you make your own IDE that loads the common plugins that come with kdevplatform, but doesn't load the plugins that come with KDevelop? They are both in the same install directory, and I don't think there is anything in the plugin JSON to distinguish them.
There is also a lot of code in KDevelop, especially for startup (main() is pretty long!), that an alternative IDE would have to replicate.
We should either do a real effort to make kdevplatform usable and good as a "framework to make an IDE", or stop pretending it is. And I think the former is too much work for little gain (how many people would want to make separate IDEs like that?).
In conclusion, I agree with merging kdevplatform and kdevelop. But it will be quite some work too :)
More information about the KDevelop-devel