Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Storage of default settings in .cproject file

Hello Doug,

for my projects it is important to have always the same settings, even if the plugin has been updated and with new default settings.

I wonder if there is a way to go through all the settings after project creation to store them explicitly one by one.
Is it possible to do that programmatically and how can it be done?

Thanks for your support!

Sebastian


From: dschaefer@xxxxxxx
To: cdt-dev@xxxxxxxxxxx
Date: Tue, 3 Mar 2015 14:51:29 +0000
Subject: Re: [cdt-dev] Storage of default settings in .cproject file

The design intent of most property files, .cproject included, is to NOT save the defaults. That way you can change the defaults in a new version of the software and the user gets the benefits of that when they upgrade. So I doubt there is such a mechanism.

Doug.

From: Sebastian Wagner <se.wagner@xxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Tuesday, March 3, 2015 at 4:56 AM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Storage of default settings in .cproject file

My question was more how to store the already existing default values, e.g. for the compiler settings in the .cproject file. I think that the ICStorageElement is  only  created if the values are different from the default settings.
I would like to change that to store all settings in the .cproject file.



From: dmsubs@xxxxxxxxxxxxx
Date: Mon, 2 Mar 2015 08:17:05 +0000
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Storage of default settings in .cproject file

You can use ICStorageElement to store your own settings in the .cproject file. You can use something like this:

ICProjectDescriptionManager manager = CoreModel.getDefault()
.getProjectDescriptionManager();

ICProjectDescription des = manager
.getProjectDescription(project, false);
if (des != null) {
try {
// to store project-wide info use
ICStorageElement storage = des.getStorage(getPluginID(), false);
...

On 2 Mar 2015, at 08:07, Sebastian Wagner <se.wagner@xxxxxxxxxxx> wrote:

Hello Ashish,

could you give me some more details how you implemented that in your plugin?

@all
Is there no simple way to do that programmatically? Any flag for the data to force storage of the .project file?


best regards,
Sebastian


From: Ashish.Rawat@xxxxxxxx
To: cdt-dev@xxxxxxxxxxx
Date: Tue, 24 Feb 2015 03:19:07 +0000
Subject: Re: [cdt-dev] Storage of default settings in .cproject file

Hello Sebastian,

 

We also faced the similar issue in our projects. The solution that we implemented is to set the non-default values during project generation, and once the project is generated, set the default values. This will help in storing all the default values in ‘.cproject’ file.

 

We did not find any other better solution for this problem, if in case anyone else in the mailing list has better solution, please suggest.

 

Regards,
Ashish

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sebastian Wagner
Sent: 23 February 2015 15:36
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Storage of default settings in .cproject file

 

Hello,

 

is there a way to store ALL settings, including the default values in the .cproject file?
Today only settings which differ from the default values are stored in there. I would like to use the default values only when a project is created, but after all settings shall be read from the .cproject file to make it independent from the default values.

 

 

Thanks for you help!

 

Sebastian
This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails. 
_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top