partselector

Bernd Gehrmann bernd at physik.hu-berlin.de
Thu May 10 21:08:02 UTC 2001


The more parts we get, the more it becomes clear that the current way of
selecting them isn't sufficient. For example, when I develop a C++
application, I want to use a native debugger, when I develop Java
I want to use the java debugger. You normally don't want to use both
at the same time (unless your're Richard ;-) This is only most obvious
example since other parts are more 'hidden'.

So I think we need configuration on a per-project basis. But maybe
for some parts it makes sense to be present always, and not only
when a project is loaded. What is the best way to implement this?
Offer both a global and a per-project part selector? Let the parts
decide themselves whether they are global or not? Any other
possibilities?

Bernd.


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop-devel mailing list