Posted on 07/10/2024 12:01:15
Hi Karol,
I agree that the documentation is lacking, but we're continually working to improve it.
Screens are only shown when navigating to them. They do not have anywhere special they live. To show a screen, you need to create a NavigateScreenAction and show that in the UI. All buttons, tree nodes and links can take a navigate action -- or any of the built-in actions for that matter.
You can either create your own area, add a new section to an existing tree or inject new elements -- including buttons -- onto existing screens. Which is correct depends on the situation you're trying to solve.
There is an example on our GitHub, but the current version doesn't work on newer versions of DynamicWeb 10. I'm currently in the process of updating it. It does however show some of the concepts even if the code doesn't currently compile. Among other things, it shows
- Adding to an existing tree
- Injecting something on a screen
- Creating screens, queries, commands and models
- Creating custom components with custom UI
- Using existing components
You can find it here: https://github.com/dynamicweb/Summit2022_ExtendingTheUI
- Jeppe