This commit is contained in:
@@ -31,10 +31,11 @@ Client
|
||||
- Each row contains a bunch of row objects
|
||||
- Each column from the db is converted to an object and is formatted like this:
|
||||
- {v:[field value],id:42[optional id value if openable]}, {v:[field value],id:42[optional id value if openable]}...etc
|
||||
- df First column object is ALWAYS the Default "df" object and is not intended for display
|
||||
- First column contains the same format as a normal column but doesn't display and is intended for the client to know what type and ID of object to open
|
||||
- This is necessary in cases where they have made selections that preclude knowing what link to open, so if there is no links in the row this is the default for the entire row
|
||||
- This also saves bandwidth as a list that has no other types can not bother setting the type or id for any other columns
|
||||
- rid flag: (was df)
|
||||
- A column with a flag of rid:true means it's the RowId column or IsRowId and must be visible to user at client
|
||||
- rid is not required because some datalists won't need one to open a record or have a practical row id due to the nature of the data
|
||||
- for example ones used for REPORTING
|
||||
|
||||
|
||||
- COLUMNS 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
|
||||
@@ -52,10 +53,8 @@ Server
|
||||
- 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
|
||||
- column list has type of object behind each column if applicable and user has rights to open so client can make hyperlinks
|
||||
- FIRST column in column list is always the DEFAULT column corresponding to the first "default" column in the data row
|
||||
- cm value is always "df"
|
||||
- dt value is always 0 (dt:0)
|
||||
- AyaType is always the default type to open, if it's nothing there is nothing to open (not likely)
|
||||
- RID flagged column in column list is always the default RowID column corresponding to the underlying object and ID in the datalist
|
||||
- rid column must have an id and an object type to be valid rid column
|
||||
- SERVER SENDS DATA
|
||||
- Data in a standard format all grid lists json format, not based on set objects (I think I can do that, probably a hybrid object with JSON data)
|
||||
- Each row has each column as a object comprising of:
|
||||
@@ -64,7 +63,7 @@ Server
|
||||
- To save bandwidth abbreviations are used in the column definitions:
|
||||
- ColumnsJSON=@"""columns"":[ {""cm"":""Widget"",""dt"":""text"",""ay"":"+ AyaType.Widget.ToString()+ "}]";
|
||||
- cm=column name locale key, dt=AyDataType, ay=AyaType to open on click of that column field (optional, not present if not openable)
|
||||
- First column in each row is *ALWAYS* the DEFAULT column that corresponds to the df column specified in objectfields with it's sql attributes
|
||||
- rid flagged column in each row is *ALWAYS* the rowID column specified in objectfields with it's sql attributes
|
||||
- For example (wide list):
|
||||
data:{
|
||||
columns:{[ {cm:"lt_client_name",dt:text,ay:2},{cm:"lt_client_notes",dt:text},{cm:"lt_last_workorder",dt:number,ay:workorder}]}
|
||||
|
||||
Reference in New Issue
Block a user