Relative positions in the buildset

[Olivier J. G.]

There are a couple problems with the buildset:
1. The order of the BuildItems isn't preserved, they are simply added as
soon as the project is finished loading
2. The "automatically add loaded projects to buildset" option doesn't care
if you have previously removed a project

Considering that the purpose of the buildset is to be able to build a list
of specified projects in order, those two bugs are rather annoying.
Since the only place where build item changes are stored is in the project
where the build item originates, it would be a bit hackish and error prone
for the project to store its items positions relative to the other project's
items positions.
It seems that the best way to fix this would be to save all the build items
in the buildset to the session config, as well as keep a blacklist of
removed items, so that when a project is loaded, the buildset model can
check if it has any build items for that project, and add it (or not add it,
in the case of blacklisted items), accordingly.

The only draw-back I can see with that is that a blacklisted project may be
deleted, but the buildset wouldn't know about it. The worst-case scenario
there is that a project of the same name later gets recreated and you'll
have to add it to the buildset manually... seems a little esoteric a problem
to stop progress with though.

Does anyone else see any drawbacks to this approach? Or does anyone have
another suggestion for fixing this?

-Olivier JG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100101/a0b3df4b/attachment.html>