diff --git a/devdocs/specs/core-main-grids.txt b/devdocs/specs/core-main-grids.txt index 5da1e48f..963f7f2e 100644 --- a/devdocs/specs/core-main-grids.txt +++ b/devdocs/specs/core-main-grids.txt @@ -16,13 +16,26 @@ None that are intrinsically grid related really, just 3 or so regarding specfic REQUIREMENTS Client - - Client needs to tell the server which form of list is required, i.e. it's client window size when fetching a list - - viewport="XS" I think would be sufficient + - Client needs to tell the server which form of list is required, i.e. it's client window size when fetching a list + - HYBRID BIMODAL: XS or LARGE (for now but consider maybe a medium down the road in planning) + - in XS mode + - the client sends "viewport=xs" to the client with the grid data request + - Client receives two field list back (id and display field), displays the single field + - in large mode + - the client sends no viewport= parameter as it's optional and understood to be full size + - the list comes back as an object with not only the actual columns but also a separate property listing the set of columns in order to be displayed + - Also their data type + - Also need to handle links of what type of object and or ID to open maybe for each column + - Client expects an arbitrary set of columns in an arbitrary order defined by server so doesn't have a pre-ordained set of things. + - HMMM... Maybe I only need a single list object that adapts to the data being sent back Server - Server needs to accept a parameter from the client when a grid list is fetched that tells it if it needs to send a single column templated list - viewport="XS" I think would be sufficient - Grid lists need to know what their template is as more than one list might use the same template? + - SERVER SENDS LIST OF COLUMNS + - The server needs to tell the client which columns are coming back with the list and what types etc so the client can just adapt to any template setting + Back AND front end \ No newline at end of file