Tabs visibility #156
Merged
Tabs visibility #156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
javascript functions to translate visible tab indexes to indexes of the full set of tabs
the ordered keys of the maps are used by the transpose js functions, while the translated tabtitles will be used by the user UI later on.
a column for holding a list of tab names is added to the user table. one for each module (visible_inventory_tab_list, visible_staff_tab_list, ...)
this time all db changes are completed by auto-ddl.
expose hashsets only, in preparation for the user UI additions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
a database module's UI tabs visibility can finally be predefined per user.
For example hiding some of the inventory tabs eg.:
... will look as below.
this way it is possible to make the UI look less complex, or restrict certain tabs to dedicated users only.