nextcloud-libraries
Create MenuBar-Component
I think it would be a good idea to have a MenuBar-Component like the nextcloud text app has.
We already have the Actions-Component, but that one hides all the elements behind a threedot menu. It also allows elements that do not make sense in such a situation, like textfields or checkboxes.
Therefore it would be good if we had a MenuBar component that only accepts ActionButton-, ActionLink- or ActionSeperator-components. This way apps can quickly create toolbars that are responsive and good looking, without having to resort to reimplementing this functionality.
So from texts perspective we need the ability to have a flexible width and move items to a three dot menu at the end of the menubar. At the same time we currently have submenus that cannot be moved into the threedot because we want to prevent subsubmenus. I understand that this would also be useful in notes... not sure about other uses though. But maybe sharing code between two apps is already good enough?
The first time i encountered this was when i tried using the actionGroup, when i wanted to have a single button next to the actiongroup instead of in it. That alone would be beneficial. If we would then allow multiple buttons fixed "outside", we have the same behaviour than the notes app.
And i guess there are quite a few apps that could benefit from that: The deck app (Top left, threedot menu, search, tag and add buttons could be such a group) Maybe talk, in the chat window there is a cogwheel-button next to the start call button obviously notes&text
I don't know if it is worth the time and effort it takes to implement this, but i can see it beeing useful. Especially since such a group would automatically be mobile-friendly, which i have a hard time with sometimes
@raimund-schluessler This is not nesessarily a duplicate. The other issue wants to allow any ActionComponent to be renderable in such a toolbar, my proposed component would be specifically limited to a subset of that.
Technically it could be done in the same component, but i feel it comes with a lot of drawbacks and problems for actually handling such lists. Could you reevaluate with this in mind and reopen accordingly?
Hm, having just a subset doesn’t seem much different to me. The technical challenges would be (nearly) the same, I think. But I am fine with reopening.