KDevelop4 API questions

[mwoehlke]

Matt Rogers wrote:
> On Thursday 17 August 2006 19:32, mwoehlke wrote:
>> Matt Rogers wrote:
>>> On Thursday 17 August 2006 10:07, mwoehlke wrote:
>>>> Matt Rogers wrote:
>>>>> On Thursday 17 August 2006 02:29, Jens Herden wrote:
>>>>>>>>> are they actually used anywhere? If not, then we can remove them
>>>>>>>>> and if we need them later, then add them then.
>>>>>>>> Please don't.  I know I need to document them, but they do have a
>>>>>>>> purpose...
>>>>>>>>
>>>>>>>> projectDirectory == the dir where the current project file is
>>>>>>>> located.
>>>>>>>>
>>>>>>>> projectsDirectory == the dir where the user holds all of his project
>>>>>>>> folders ... perhaps this can be renamed to better illustrate what it
>>>>>>>> is.
>>>>>>>>
>>>>>>>> Both of them are useful though, please don't remove.
>>>>>>> But not all project folders are in the same place, so I still don't
>>>>>>> see the point of either of these functions since projectDirectory is
>>>>>>> duplicated from KDevProject and well, right now, projectsDirectory
>>>>>>> doesn't make sense to me.
>>>>>> Oh that is new for me. I thought that project files and folders must
>>>>>> have a common base folder? But the project file can be at an arbitrary
>>>>>> location where also the hidden .kde4 folder is created. Am I wrong
>>>>>> here?
>>>>> Yes, project files and folders must reside under a particular folder.
>>>>> However, the project file can no longer be stored at an arbitrary
>>>>> location. We might change that, dunno yet, a lot of this stuff is still
>>>>> in flux.
>>>> Ok, I'll admit I don't understand entirely what's going on here, but by
>>>> "project file", are we talking about what in 3.x is 'foobar.kdevelop'?
>>>> (Private explanations welcome if you don't want to clutter the list.)
>>> yes, that is correct.
>> Ok, so I am confused... KDevelop 4 is or is not going to force all
>> projects to be in the same directory? Because that would be A Bad
>> Thing... :-) I seem to have noticed contradictory statements in this
>> very thread, although this one was "we haven't made up our minds", and
>> the other was a comfortable "no, we won't do this".
> 
> not all projects will have to be under than same directory. the project file 
> must be in the same directory as the toplevel directory for the project.

Ok, that makes sense. Thanks for clearing up my confusion. :-)

I'm fine with the project file being necessarily at the project root; I 
think most people do things that way anyway...

> The thing we haven't made up our minds about is whether to allow separation of 
> the kdevelop project file from the actual source and other things it 
> describes.

Either way works for me, though as Jens points out, I can understand why 
people would want more flexibility.

-- 
Matthew
KATE: Awesome Text Editor