interfaces / implementations separation (was Let's discuss KDevelop4 interfaces and shell)

[Andras Mantia]

On Fri Jan 19 2007, Alexander Dymo wrote:
> There're two goals:
> 1) to make sure all old plugins load in new versions of KDevelop
>   and Quanta (let's call this plugin architecture BC).
>   We need this to support third-party plugins and plugins from
>   (not yet created) kdevelop-extragear
This is very important.

> 2) to make sure Quanta application can use the same shell.
>   Here we don't really need a BC. Quanta and KDevelop usually
>   have the same release cycle so they will most likely end up
>   installing the same version of shell. So no BC-keeping is necessary
> at all.


I think both KDevelop and Quanta right now have a policy to run under 
previous KDE versions as well (e.g. KDevelop 3.4 runs on KDE 3.4.x as 
well, right?). 

>   Alternatively we can keep BC between minor releases (like
>   allow updating Koncrete (platform) and KDevelop to 4.0.6 while
> still working with Quanta 4.0.0.

At least this is a must. Not being able to run KDevelop 4.1 and Quanta 
4.0 together might be also somewhat problematic, but I can live with 
that and if it's an absolutely must, it is always possible to install a 
Quanta version of the platform if the one on the system is BIC. But 
between . .x releases we should keep full compatibility

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20070120/6b0ef9f7/attachment.sig>