Juha Kiviluoma

I didn't remember it. Which begs the question how do we make stuff more apparent for the user (I think the approach suggested here would do that in this case)....

> If we don't want to use the datapackage connector I think we should just remove the datapackage functionality we have implemented, as it's becoming almost pointless? I would agree...

Great! Yes, seems logical. We could later add more elaborate rendering - e.g. if entity is active in one selected alternative and inactive in another, it could show the 'conflict'...

It looks really great and useful. Like this:  The issue I have is that when choosing something from the entity_tree (without ctrl-pressed), the alternative remains chosen. This should happen...

I think this is ready to be merged after that. A review by @soininen?

I'd like to have only necessary tools. I don't quite understand the use case here. When @SilkeJo runs the workflow, it could presumably have multiple scenarios. If you save them...

I suppose you could timestamp/scenario-name output files, but it can become unwieldy with exporters/tools that produce many files per scenario.

I'm not 100% sure how we will make the tutorials happen - are they just Toolbox projects or will there be some animation and stuff to guide the user to...

Would it be best if the tutorials were just a web-page in our documentation? I mean, doing it with animations in the workflow editor would be great, but maybe we...

Good plan Suvayu, let's proceed with that. I would just leave #3 optional in mopo - I think we will likely have other things of higher value to do within...