ui
ui copied to clipboard
nexus-js
As a User, I'd like to see labels per row on a sequencer so that I can...
...easily identify what sound I will be triggering.
I found closed issue https://github.com/nexus-js/ui/issues/48 and was curious was there anymore development on this or work planned in the near future?
It would be helpful to be able to label individual sequencer rows. It does get confusing from a User perspective if you begin to have a lot of rows, and need to guess what is what. That said, that is just one example. Optional labels on all components in the library could be beneficial for the User (sliders, dials, etc), especially as a interface gets more and more complex.
Labels are left up to the user to write in their HTML.
We did add a label option to NexusUI at one point but the amount of customization required for them (font, size, style, location, alignment, text wrap, etc) made it a pretty bloated and cumbersome feature. I think it is really better left up to the user to create text that matches their site design.
For the sequencer, could you add a row of fixed-width divs beneath the matrix that had labels for each column?
@taylorbf thanks, this makes sense. I can see your point about customization bloating the core library. That said, it could be helpful to have that as an optional dependency like a nexus-js/ui-label (ie. script).
Anyway, thanks for the answer and context, just something I thought I'd bring up. I'll try to play around with labels when I have some time. Cheers
If you find a good solution for creating labels that would make a good starting point for an optional dependency, please share. There are a number of things like this that would be good options that shouldn’t be in the core code. This might make a good test case to iron out how it may function.
-Jesse
On Oct 13, 2017, at 9:30 AM, Jonah Bitautas <[email protected] mailto:[email protected]> wrote:
@taylorbf https://github.com/taylorbf thanks, this makes sense. I can see your point about customization bloating the core library. That said, it could be helpful to have that as an optional dependency like a nexus-js/ui-label (ie. script).
Anyway, thanks for the answer and context, just something I thought I'd bring up. I'll try to play around with labels when I have some time. Cheers
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nexus-js/ui/issues/99#issuecomment-336469767, or mute the thread https://github.com/notifications/unsubscribe-auth/AANNCOOJQtmNvbJhE21G6DQqoMtO-_Uuks5sr3QggaJpZM4Px4zD.
https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png https://github.com/nexus-js/ui https://github.com/nexus-js/ui/issues/99#issuecomment-336469767
