Add initial support for region in launcher

[MathoMathiasCamara]

Problem

There is not support right now for region/plugin in the launcher , as it used to be in the old version.

Solution

This PR adds a region/plugin support, for that couple elements where introduced:

• LauncherPluginAttribute decorate a partial view to be used as plugin/region in the launcher.
• LauncherRegionItem describes the name (without extension) of the partial view associated to the LayoutPluginAttribute
• LauncherRegionConfig mapping class for the configuration .
• Added a new property Regions to LauncherConfig

The launcher config file could look like this:

{
  "ModuleSortIndices": [],
  "ExternalModules": [],
  "Regions":
  [
    {
     "Region": "Right",
     "PluginName": "Hydra"
    }
  ],
  "ConfigState": "Valid"
}

Here is an image of a PartialView that was defined in the Moryx.Shifts.Web project and configured in the *.Launcher.Config.json, region section, to be placed o the right.

Screenshot

[MathoMathiasCamara]

Only the right region is supported currently in the launcher layout. Other region could be added to the launcher layout in the future.

[andreniggemann]

I like this approach. It's much better than the iFrame Version we discussed.

Having searched the docs for this topic I stumbled across View Components https://learn.microsoft.com/en-us/aspnet/core/mvc/views/view-components?view=aspnetcore-10.0
They seem like a natural fit.

[1nf0rmagician]

Any thought on how routing would/could be possible in the region or what would happen if anyone used it there? Or is it, that routing cannot be part of the regions themselves?

[dbeuchler]

Any thought on how routing would/could be possible in the region or what would happen if anyone used it there? Or is it, that routing cannot be part of the regions themselves?

Routing was not supported in older WPF and there was never a requirement for it. It might be possible without changing the URL or using a custom tag for it. Problem with the current launcher is the "refresh" on module change.

[MathoMathiasCamara]

Any thought on how routing would/could be possible in the region or what would happen if anyone used it there? Or is it, that routing cannot be part of the regions themselves?

I don't tinkh we should handle routing because that would conflict the entire routing of the main view. so the idea is that the partial view that you are implementing don't need routing or you could use embed or iframe inside your partial view to point to a module if you need routing just look the external module feature.

[dbeuchler]

Any thought on how routing would/could be possible in the region or what would happen if anyone used it there? Or is it, that routing cannot be part of the regions themselves?

I don't tinkh we should handle routing because that would conflict the entire routing of the main view. so the idea is that the partial view that you are implementing don't need routing or you could use embed or iframe inside your partial view to point to a module if you need routing just look the external module feature.

The plugin can also be exported as a web component and can have their own routing without embed or iframe.

[dbeuchler]

Important missing step: Extend documentation 📄

[1nf0rmagician]

Can't you use ReflectionTool.GetPublicClasses here? I know we have some more detailed filtering on the classes in there which prevented several exceptions 🙈

[MathoMathiasCamara]

I tried but couldn't find a better way, @dbeuchler also tried i think.

[dbeuchler]

The ReflectionTool provides only public classes (exported types) and does not export internals of the assembly. The razor pages are compiled as internal types only.

[1nf0rmagician]

The razor pages are compiled as internal types only.

Ahh ok, didn't now that. Then keep it that way 👍