On Friday 18 August 2006 15:13, Jens Herden wrote:
> On Saturday 19 August 2006 02:30, Matt Rogers wrote:
> > On Friday 18 August 2006 12:39, Jens Herden wrote:
> > > Hi,
> > >
> > > KDevelop is using the default value for the
"Project Management" entry
> > > in the project file every time a local
project file under .kdev4
> > > exists. I saw this because we are using a
Quanta project manager and it
> > > gets only loaded when there is not file under
.kdev4!
> > > I think KDevelop will do this for all entries
that are in the project
> > > file but not in the local one under .kdev4
when you use
> > > KDevConfig::standard().
> > >
> > > Is this supposed to be a bug in kdelibs or is
it how it should work?
> > >
> > > Jens
> >
> > I'm not sure what you mean by this. Are you
saying that there is a local
> > project file in your hidden .kdev4 directory and
that's messing up the
> > project loading?
>
> Yes, that is what I mean.
> I have this line in a *.kdev4 file:
> Project Management=KDevQuantaProject
>
> This is supposed to load our Quanta specific
implementation of KDevProject.
> This is working fine when I do not have a file in the
.kdev4 folder. But
> once I have opened the project I will get this file in
.kdev4 but there is
> no line with "Project Managment" inside.
Next time I open the same project
> the framework will not take the Quanta project but the
default one. So I
> suspect that the access to this configuration entry
does not take in
> account the global project file but just returns the
default value when it
> can not find the value in the local project file.
> I addmit that I did not really debug this, so if you
say this is wrong I
> will look into it deeper.
>
> > Does your project manager (i assume you mean file
manager here) have a
> > desktop file with the appropriate entries in it?
It needs to have all the
> > various KDevelop entries that are defined in
kdevfilemanager.desktop and
> > also X-KDE-PluginName as well.
>
> Everything is fine the first time so it is not an issue
with the *.dektop
> file I guess.
>
> Jens
ok, so i took a look at this. IMHO, you don't need to
reimplement the view for
the project manager part like you're doing in
quantaprojectmanager.{h,cpp}
but that's not the main problem. The file manager, which
appears to in
quantafilemanager.{h,cpp}, will need to be its own plugin.
You will need to
split the two. Also, be sure that an X-KDE-PluginInfo-Name
key is in all
the .desktop files for file managers since that's how
they're looked up in
kdevelop's project manager part by default. Whatever value
you put in
the .desktop file for the file manager is what will need to
go on the
'Project Management' line. See kdevelop.kdev4 in
trunk/KDE/kdevelop for the
example.
If you really want to replace the project manager, it may
not be possible at
this point in time.
hope this helps, or at least provides a bit of answers
--
Matt
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
|