Defining the KDevelop Platform

[Andras Mantia]

On Friday 07 April 2006 00:04, Alexander Dymo wrote:
> Ok, one by one.
>
> On Thursday 06 April 2006 17:09, Matt Rogers wrote:
> > IMHO, We need to answer the following questions about the KDevelop
> > platform in concrete terms. Right now, we don't really have a clear
> > cut idea of what the platform actually is. In order to move forward
> > with the idea of the platform, i think we need to give it a bit of
> > formal definition.
> >
> > 1. What will the platform encompass? (don't just say the current
> > kdevelop lib dir)
>
> All stuff necessary to build and run common plugins (interfaces,
> support libs, shell to load a plugin, profile engine).
>
> > 2. What should the platform be used for?
>
> Quanta, KDevAssistant, specialized (commercial?) IDEs
>
> > 3. What can developers who want to use the platform do with it?
>
> Use the plugin framework to easily build plugins and easily reuse
> existing plugins to combine their own applications.
>
> > 4. Why should developers use the platform?
> > 5. What advantages would the platform give them?
>
> Development speed and more ways to reuse existing functionality
> (software).
>
> > 6. What's in it for us?
>
> PR, more developers, well-defined, well-tested architecture.

I sent my comments (similar to this one), but it is waiting for 
approval. ;-) Shortly: code share, common libraries, we will also care 
much more about those libraries = more developers, smaller 
applications.

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/20060407/be54d403/attachment.sig>