Antti Soininen

> Should we do this only in v0.8? I think we do not need to back port it to 0.7. We have been missing this feature for years now and...

Currently, Exporter does not know which scenario the live preview should show, especially when there is more than one scenario selected. We could add a combo box in the Specification...

I took the liberty to move this issue here because Spine-Toolbox issue tracker is also used for issues in spine-items. It is just to keep the number of relevant issue...

Should we move the plugin bars to the vertical position as well? When I open Toolbox I get this:  Would this make more sense? 

> I didn't intend to put those two on the left, actually... was just an accident. I see. Sorry about the noise, then!

I have a few plugins installed and when opening a project with multiple specifications (a few exporters, importers and tools, nothing special), I get quite a few icons on the...

Frankly, I'm unsure what's the motivation here? Keep a database in text format to make it 'nicer' for `git`?

I think this is most critical for `spinedb_api` for development of tools/scripts that use Spine databases. Toolbox API is not that interesting unless you're actually developing the Toolbox itself.

Writing everything as strings in Excel files sounds like an oversight in Exporter. I believe we can write the correct types automatically without additional options in the UI.

We indeed prevent the completion of rows in the parameter tables that would break database integrity because once the row is completed, it gets integrate into the 'machinery' as a...