Creation of the table base class for application

[Neketek]

I'm trying to generalize tables logic.
Table Base class should simplify implementation of the tables which will have next features:

• Multiselection
• Loading
• Standard entity (row) base class

[Neketek]

@Dubbinary @jerichofs @vsmysle @ddnomad Any ideas about table UI which will have optional multi-selection just like zen hub issues but mobile friendly?

[jerichofs]

@Neketek What do you mean by optional multi-selection? If you want to accommodate the section Boards with subsections (Labels, Milestones, Assignees, Releases etc.) for mobile screens. Maybe we should take a look at how it's built in FastHub and make customization. For instance, we could add the Boards section to the pull down menu (where you have: Home, Profile, Organizations etc.). In this section like in FastHub instead of Created, Assigned, Mentioned etc. sections we can put those subsections from ZenHub i mentioned above (those are kind of filters for your issues). Then instead of a simple list of issues we can have the system of posts where a post is an issue itself (something like a facebook post). Also, a post can consist of 1. the tilte of an issue 2. the list of related issues included in the post. Also those subsections (Labels, Milestones etc.) allow you to filter these posts. I think issues would be much reasonable represent as posts especially for mobile screens and those subsections allow you to tweak them easily. But drawing a sketch of this thing would be much more clear

[Neketek]

@jerichofs You are right about sketch, it's essential for explaining your idea. You can use Pencil and draw one which will show what you have in mind. As a programmer I'm writing code which adds syntax sugar for you, so I'm really interested in the things which come to your mind as implementation ideas for the components. About optional multi selection. This is a feature which allows selection of the several table entities which can be used to perform specific action simultaneously without repeating that action on each desired entity. This functionality can be implemented in many ways, but generally this feature turns table entity component to component which have options of the button component which gives an ability to click on it and to checkbox which gives an ability to select it and store this selection in the component state.

[Neketek]

@jerichofs Tables are most complex input components of the application so you can try to start experimenting with them. Tables should have rich functionality and if you are interested in that experiment I'll explain you details.