Re: [anjuta-devel] Vala and the new code-assistance architecture

[Moritz Lüdecke <ritze skweez net>]

Hi Sébastien,

I've made ​​a few thoughts how we can realise this.

The first option is to integrate this in each plugin. So we only have 
to adapt the Vala plugin. As you already said the user will only change 
the options, if the plugin is loaded. And this will only the case, if 
the user has opened the language specific document. In my opinion this 
is bad.

The second option is to move all option widgets to the new 
parser-engine plugin. In this case we can merge some code. The user can 
set his language specific settings in one option widget. For example we 
show a table of checkboxes. The rows stand for the setting and the 
columns stand for the language. If the language doesn't support the 
setting, the checkbox will be disabled or not available. The negative 
side is the same point as above. We have to load the plugin so that the 
user can set his preferences.

Another option is to write a new plugin, which single purpose is to 
show the option widget. But this is my worst idea.

> > And
> > it's not clear if all users really want the same settings for C and
> > Python, some projects use quite different settings there.
>
> I don't know neither if the users want the same settings or not. I 
> think it
> could be better to have something even project specific.

Saving the settings in the project file is a good idea. Maybe we can 
update the standard settings for a new project each time the user change 
the preferences. And this preferences will be load, if the user create a 
new project.

Regards,
Moritz