Local Project File [Re: Extending the IProjectFileManager interface]

Andras Mantia amantia at kde.org
Thu Jul 5 11:02:56 UTC 2007

On Tuesday 03 July 2007, Andreas Pakulat wrote:
> On 03.07.07 22:10:57, Andras Mantia wrote:
> > On Tuesday 03 July 2007, Andreas Pakulat wrote:
> > > On 03.07.07 21:10:05, Andras Mantia wrote:
> > > >  Our idea was to store such information in the project
> > > > configuration file (the "local" one if such exists now, not the
> > > > one that is shared between users).
> > >
> > > Yes, thats what the projectmanager does when importing the file.
> >
> > BTW, I couldn't find how to access the local file. It seems to be
> > commented out now.
> Uhm, you don't access that file. You access the projects
> configuration. And all changes done will be written to the local
> file. This way using remote projects is completely transparent for
> the plugins.

Maybe I wasn't clear about the local file. Of course, I shouldn't care 
if the project was remote or not, and if the file I'm writing on is 
*exactly* the project file or a local copy of it.

What I meant all above with the local file is the file that is not 
shared by developers. Do we still have this concept? I mean, in 
KDevelop3 and Quanta3 there is the project file and a project session 
file (yeah, this is a better name). Theoretically the project file 
contains only information that are relevant for all developers, while 
the session file is specific for the current developer. Propertis IMO 
can go in both files, as they might be shearable or not. 
So is such a session file now in KDevelop4? If not, I'd say we need to 
introduce one.


Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

More information about the KDevelop-devel mailing list