This commit is contained in:
@@ -55,20 +55,34 @@ TODO: FILTER AT CLIENT
|
|||||||
- in v7 users can set more than one condition per column by selecting "custom" so we need to support that
|
- in v7 users can set more than one condition per column by selecting "custom" so we need to support that
|
||||||
- Maybe a row of all columns then each one has a expandable list of conditions under it for setting multi filters?
|
- Maybe a row of all columns then each one has a expandable list of conditions under it for setting multi filters?
|
||||||
- Like a card with top part all static info, then filters below as a collection that can expand the card vertically with ADD and REMOVE buttons for each one
|
- Like a card with top part all static info, then filters below as a collection that can expand the card vertically with ADD and REMOVE buttons for each one
|
||||||
|
- In v7 user can set AND or OR query for custom more than one condition (but it applies to teh whole group, not both and and or individually)
|
||||||
- Sort
|
- Sort
|
||||||
- Need to be able to set order for sorting
|
- Need to be able to set order for sorting
|
||||||
|
- Can view order also be sort order?
|
||||||
|
- Or maybe since viewing and querying are decoupled it makes sense that sort order and view order are also decoupled?
|
||||||
|
- Or, maybe it should always be visible if it's sorted or filtered so the user can't be like "what the fuck, why am I seeing it like this?"
|
||||||
|
- also simplicity for the ui
|
||||||
|
|
||||||
- Visible
|
- Visible
|
||||||
- Checkbox if visible which means the server returns it or not, visible maybe not correct word here
|
- Checkbox if visible which means the server returns it or not, visible maybe not correct word here
|
||||||
|
|
||||||
- This way the user can customize the grid all in one savable setting
|
- This way the user can customize the grid all in one savable setting
|
||||||
- Grid defaults to last "View" that was in use
|
- Grid defaults to last "View" that was in use
|
||||||
- Also has MINI options or is that a different UI?
|
- Also has MINI options or is that a different UI?
|
||||||
- Maybe it *is* different because selects are a kind of unique situation with thier own requirements.
|
- Maybe it *is* different because selects are a kind of unique situation with thier own requirements.
|
||||||
- Can default but also would be hellish if it's customizable user by user since there is probably a company standard for selecting parts for example
|
- Can default but also would be hellish if it's customizable user by user since there is probably a company standard for selecting parts for example
|
||||||
- Maybe the "Default" can be set by an admin and users can either select default or go off the books to their own custom
|
- Maybe the "Default" can be set by an admin and users can either select default or go off the books to their own custom
|
||||||
|
- MINI view is really just regular view but with all columns jumbled together...no? INVESTIGATE
|
||||||
- Reports are a special circumstance, a report really would go with a specfic filter wouldn't it? INVESTIGATE THAT
|
- Reports are a special circumstance, a report really would go with a specfic filter wouldn't it? INVESTIGATE THAT
|
||||||
- View filter set with report? Report needs all fields sometimes but view may not have so what happens then?"
|
- View filter set with report? Report needs all fields sometimes but view may not have so what happens then?"
|
||||||
- Show text filter sort fragment at bottom of grid in footer
|
- Show text filter sort fragment at bottom of grid in footer
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- PickList of filters for dataListKey (DO I have a server route for that?)
|
- PickList of filters for dataListKey (DO I have a server route for that?)
|
||||||
- ListOptions editor
|
- ListOptions editor
|
||||||
- OWN PAGE NOT combined with data table
|
- OWN PAGE NOT combined with data table
|
||||||
|
|||||||
Reference in New Issue
Block a user