Break Custom Buildsystem Plugin apart into 2 pieces.

[Sergey Kalinichev]

On Monday 10 February 2014 07:35:23 	Sven Brauch  wrote:
> On Monday 10 February 2014 22:04:48 Sergey Kalinichev wrote:
> > To the point, where to store information on the file system or in kdev4
> > file?
> 
> I would definitely vote for file system, for the reasons discussed.
> 
> For detecting and wrapping it into a GUI, I would say:
> 
>  - GUI is not a problem if we have a "one-dimensional" file format like now,
> i.e. just list of dirs separated by \n. Sounds very easy to wrap into a GUI
> with few chances to screw anything up.
> 
>  - For detecting the file, I would just keep going upwards from the source
> location and look for the file. That's what git does too and I think it
> works well enough for all non-crazy use cases.

So you suggesting showing the GUI only for the current file, which is already 
implemented, no? I was thinking more globally, i.e. showing all include 
directories for each directory in the current project. If none of projects are 
opened don't show the GUI at all. (But the include assistant will be available 
anyway)

Also what about custom defines? Should I create separate .kdev_custom_defines 
file for that?


--
Cheers