search

bigbluebutton / bigbluebutton-html-plugin-sdk

BigBlueButton Plugin SDK
GNU Lesser General Public License v3.0
6 stars 5 forks source link

Content-component as extensible area - Auxiliary and main content #76

Closed GuiLeme closed 2 months ago

GuiLeme commented 4 months ago

Context

After some discussion, and requests to add the side-bar pannel as a possible extensible-area to play around, we came to the conclusion that a good way to make it happen is to add it as a type of the generic-component extensible-area, but with that, it would be necessary to refactor the generic-component and even rename it.

Suggestions:

Maybe we could rename the generic component to content-component and allow the user to specify its type, which they could choose between:

Just as we already do with ActionButtonDropdown(Separator or Option).

As for the auxiliary-content type, it would be rendered within the user-list pannel (the one in the far left edge of the UI) as a clickable option like the shared-notes button, which will render the content right beside it as the chat does or the shared-notes even. See screenshots ahead for better understanding:

image

The red-squared area is what I refer to as "user-list pannel", and the arrow points to where we could add another option for when the user clicks it, the auxiliary-content renders right beside it.

So on that regards, we are open for suggestions as we can improve the UI and the developer's experience even better. Just comment what you think of, and let's discuss!

gustavotrott commented 4 months ago

I don't know why, but I didn't like the name "auxiliary-content".

What about "Sidekick Panel"?

TiagoJacobs commented 4 months ago

Having "side" in the name was not our first choice, because we can decide to show it on another place in screen.

The word sidekick helps in this matter, however, calling it as panel is not good, because panel is where it's displayed, in the plugin we define what is being displayed.

So I think we could have:

And these would be rendered into:

Does it make sense?

gustavotrott commented 4 months ago

Having "side" in the name was not our first choice, because we can decide to show it on another place in screen.

The word sidekick helps in this matter, however, calling it as panel is not good, because panel is where it's displayed, in the plugin we define what is being displayed.

So I think we could have:

  • main content

  • sidekick content

And these would be rendered into:

  • main panel

  • sidekick panel

Does it make sense?

sounds good!