Export / Import configs from Boot Dashboard

[qzmarco]

I miss an option to export / import the configs of boot dashboard. This is very useful when you need to configure projects on other computers.

[martinlippert]

Great suggestion, thanks for that.

Would you prefer to have support for this via something like an "Export Settings..." action that you could invoke and then save settings to a file (same for import) or would you prefer some metadata file to be stored in the projects themselves (like .project or .settings) that you could check into version control?

[qzmarco]

Thank you for accepting my suggestion. I believe the first option is satisfactory.

[kdvolder]

Trying to understand what it is you want to export. For example, you can already export / save local app's launch configuration to a file via the standard Eclipse UI on the 'common' tab. That is follow these steps:

1. Select an app
2. Click the 'pencil icon' to open a launch configuration
3. Select the 'common' tab.
4. In the 'save as' section. Switch from 'local file' to 'shared file'.

This will allow saving the launch configuration into the project (or anywhere in the workspace really). Then this file can be shared, for example, by committing into source control, or whatever way you want to. If the file is in the project, then any workspace where you import the project to will automatically pick up on that launch configuration.

Does this do what you want? If not please comment and provide a bit more details on why this is not what you want and what exactly you had in mind instead.

[qzmarco]

It would be something exactly at this level that I would like to be able to export the settings for that project.

What I imagined was something simpler than the whole process. Something like right clicking on the project in the boot dashboard and the export / import option appears, just like in order to be able to import / export projects in Eclipse.

[kdvolder]

What I imagined was something simpler than the whole process.

I hear you, Eclipse UI design can be a bit mind bogling at times. We can probably come up with something a little more intuitive that achieves a similar functionality.

Just as long as we understand that what you are trying to do is basically the same thing as that but without so many required button clicks. So it would be really helpful if you tried this method for a bit and make sure that it works. Then we can put some thought into making the whole 'share/save' launch.configuration a bit more direct.

Just want to make sure we are sure saving/sharing the launch configuration is really you are after so we don't spend a bunch of time implementing it only to find its not quite right.

BTW: While I do agree with you that it takes far too many ui actions to setup the 'shared config'. One nice touch of the way this works in Eclipse is that the launch configurations don't need to be imported. Any launch configuration that is in your workspace is somehow magically found/imported by Eclipse, so as long as you saved them in your project one time, from that point onward, you wouldn't need to do anything at all. So I think that aspect of how it works now is actually kind of nice.