Table, Dropdown & Input Features

[achatzi78]

Hi.

I have a few features, that some can be accomplished with adding css classes and some by publishing the templates.

The problem with the first solution is that I must copy and paste the classes to the same component every time I use it (for example bordered table) and for the second solution I prefer not to do it because it could be break functionality in future upgrades.

So here is my wishlist

1. Bordered table. Self explanatory, I think. Right now I add classes to the table but I have to copy paste them everytime. Of course can publish the template but like I said I would rather not
2. Slim table. In case space is an issue, a variant that reduces padding and spacing to occupy smaller space would be welcomed
3. Multiple rows in thead. I know this is not frequent but there are case that in thead we need more than one tr. The columns template onl allows 1 and in my case I had to use a thead directly and copy paste the classes that flux uses
4. Sticky headers and columns. I have made that already (and I found a very nice solution here 351) but having it incorporated in the flux wold be much better
5. Top pagination, as requested in 350
6. Loader for pagination and sorting. When the user sorts the table or navigates the pages, it would be helpful to show some kind of loader
7. Sort icon always visible. I believe that the sorting icon should always be visible to the user, so it is easier to know which columns can be sorted and which cannot. Now the user has to hover each columns to determine which is which
8. Link as a dropdown trigger. I use the dropdown as a popover as well and sometimes I don't want to use a button for the trigger, just a simple link. For example I have the description of an item and in the dropdown/popover I show the image of it. Now I use a button with the photo icon next to the description
9. Add classes to the label of an input. Many times I want to add classes to the label of the input and I have to use the field to component instead of the much shorter input. I think that another prop (like the new class:input, kudos for that by the way) class:label would be much appreciated.

I know that these are a lot, of course I do not expect for all of them to be implemented. None the less, I believe that these features would make flux even better. Also, I know that most of these can be solved by us, I have done it already, but like I said, I believe that the less you publish templates the less chances you have missing or breaking functionality in the future.

Either way I love flux and these came from my first experience creating an app with it.

Keep up the good work!