This commit is contained in:
@@ -48,8 +48,11 @@ TODO: FILTER AT CLIENT
|
|||||||
|
|
||||||
Sort / filter / select return columns all in one!
|
Sort / filter / select return columns all in one!
|
||||||
- This combined is a "view" or DataListView (fucking renaming again here we come! :)
|
- This combined is a "view" or DataListView (fucking renaming again here we come! :)
|
||||||
- Each list has default template for fields to return user can add more but they are built in lesser (only a few fields)
|
- Each list has 2 default templates for fields to return etc, a table view and a picklist view
|
||||||
- When user opens a data table they see for the first time the default view and sort order and filter (no filter, sort by id, a few key fields)
|
- Server dataList can accept either Default=true or sort filter json
|
||||||
|
- Mini format or table format default
|
||||||
|
- Or is default when there is no sort/filter/columns to show?
|
||||||
|
- When user opens a data table they see for the first time the default table view and sort order and filter (no filter, sort by id, a few key fields)
|
||||||
- they can make a new view which shows all the fields and they can set props on each one:
|
- they can make a new view which shows all the fields and they can set props on each one:
|
||||||
- Filter (with filter code)
|
- Filter (with filter code)
|
||||||
- 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
|
||||||
@@ -68,11 +71,22 @@ TODO: FILTER AT CLIENT
|
|||||||
|
|
||||||
- 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?
|
|
||||||
|
- MINI code is not right:
|
||||||
|
- right now it produces a single column header but can contain multiple columns of data
|
||||||
|
- this is bad because the client doesn't know the underlying type so can't co-erce each column into locale format
|
||||||
|
- I'm thinking ditch mini at server and make it a client display issue instead
|
||||||
|
- There does still need to be a MINI default format though for all lists, hard coded so user can revert or start with a solid PickList
|
||||||
|
- MINI just same as regular DataListView however Client would display differently munged into one column so up to user what columns in what order!!
|
||||||
|
- So we need two default views for each datalist, one for grid display and one for picklist display that can be reverted to and are permanent
|
||||||
|
- User can at any time use the default view or pick a custom DataListView
|
||||||
|
- All users start with default view and can modify as they see fit
|
||||||
|
- each form with each picklist would have it's own view possibly?
|
||||||
|
- IS MINI options 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
|
||||||
|
|||||||
Reference in New Issue
Block a user