KDev4 SDK Single or Multiple Projects?

[Paulo Moura Guedes]

On Tuesday 30 January 2007 20:42, Alexander Dymo wrote:
> On Tuesday 30 January 2007 22:14, Matt Rogers wrote:
> > Why do you think that? What can you provide to back up your statement
> > that it "is more trouble than it's worth"?
> >
> > So far, the arguments against multiple projects is unconvincing.
>
> May I give one argument that I think would sound convincing for multiple
> projects support for KDevelop developers and maybe for Quanta too.
>
> We're going to have separate module with our "unnamed" platform.
> Imagine how good would be to click "build" once and build
> platform + kdevelop or "platform" + quanta.

:)

I think I never had though of this but maybe the needs of open source 
development vs the needs of developers working in corporate projects are 
completely different.

If I look at myself, while working in KDE, I wouldn't have the need for 
several projects in one instance. At work though an IDE that wouldn't have 
this feature seems completely ridiculous and unusable to me.

Of course we have to deal with multiple projects and it's vital to do it in 
the same window. There is a tree with project higher level nodes, going down 
the way to the lower level ones like class methods, resource properties, 
libraries used, etc. One can right click and do beautiful things like build 
stuff, VCS, find by project, etc. The projects can depend on each one, i.e., 
build one before another.

IMHO, IDEs tend to be unique instances with multi-projects, some times with 
different nature, i.e., not necessarily code but UML projects, etc.

It's funny that this is even being discussed :)

Paulo