1 of 1 people found this helpful
Not out of the box. But I was thinking about that before.
Would you like to propose a solution or even extend workspaces and send a patch?
I do appreciate a contribution like this.
It would definitly be nice if I could define the general page structure with an own widget and insert the workspace within it.
Extending the login box is also interesting to provide "password forgotten" and "more informations" links and such. So there should be two different widgets, marked by @LoginFrame and @WorkspaceFrame or something similar which can use <errai:Workspace/> and <errai:Loginbox/>. In the end I would define two UIBinder widget with content like that:
Depending on the two states (loggedin, not loggedin) the frames would be loaded by errai.
Having predefined slots is another solution and is less intrusive to the existing code I think. I can imagine a WidgetProvider annotation like this:
@ExtensionWidget(location = ExtensionLocation.TOP)
@ExtensionWidget(location = ExtensionLocation.BOTTOM, loggedOff = true, loggedIn = false)
@ExtensionWidget(location = ExtensionLocation.BOTTOM, priority = 4)
I will try to hack something around in the workspace code and will send you a patch.
I think I would prefer the @ExtensionWidget opposed to the UIBinder approach. There aren't really so much places
where you want to place custom widgets. Top, bottom and maybe embedded within the lefthand navigation.
Looking forward to your solution.
Let me know if you need help with the meta data processing. But there should be plenty of examples how to use the MetaDataScanner to look for @ExtensionWidget