Bernd-Gehrmann at gmx.de
Sun Jun 30 10:20:04 UTC 2002
On Sunday 30 June 2002 00:14, you wrote:
> On Saturday 29 June 2002 2:59, Bernd Gehrmann wrote:
> > On Saturday 29 June 2002 23:00, you wrote:
> > > John Firebaugh wrote:
> > > >Why not save the UI state as part of the project file instead, and
> > > > restore it after the project gets restored?
> > >
> > > Imagine, users want to put project files in cvs.
> > Project files do not belong in cvs, they are exclusively for user
> > preferences.
> > > Gideon should really try to look more often at KDevelop-2 mechanisms.
> > Falk should really try to look more often at Gideon mechanisms ;-)
> No, he has a valid point. Some settings you will want to share (build
> configurations, run options, file templates, file groups, etc.), others you
> will want per-developer.
Build configurations are a user preference, as they contain the developer-
dependent build directory or even options like --host (note that build
configurations are automake specific; in contrast to other IDEs, the end
result of a project is not a binary package with installer, but a .tar.gz
package which still has to be compiled for the target system). Run options
also depend on the developer's testing environment. These are typical
things to be stored in the project file. Shared things like file templates or
the Doxygen configuration are not part of the project file (and have never
More information about the KDevelop-devel