This commit is contained in:
@@ -50,37 +50,44 @@ SHELL / NAV / MENUS / LAYOUT
|
|||||||
TODO: LOCALIZATION
|
TODO: LOCALIZATION
|
||||||
- TODO ACTIONS
|
- TODO ACTIONS
|
||||||
|
|
||||||
- Relative time filters need to be removed from server and replaced with a single BETWEEN filter
|
- Remove relative time token filter integration tests
|
||||||
- Then they need to be re-implemented at the client where the client will send the between date/times to the server based on the user's chosen relative token
|
- Keep the ones that rely on filtering dates between values because that's how the client will be sending the relative filters
|
||||||
- This fixes a bad design decision to involve the server in time zone shit when in fact the server should never operate in anything but UTC
|
|
||||||
- Time zones are a client issue and should never be a server issue
|
|
||||||
- When the filter code and processor is written it should calc the dates based on token and user's local time , then conver to between filter on the fly
|
|
||||||
- system is written with static filters saved to server so maybe need to turn it around and instead of providing a filterid, provide the filter json instead?
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- Make functional user settings form with all overrides so can test shit out
|
- DataTable, make bools display as checkboxes instead of text (could just use icons instead of actual checkbox)
|
||||||
- Need a browser check on opening the login page that will check to ensure the browser can do the date conversions properly etc and tell user browser is unsuitable if it isn't
|
|
||||||
|
|
||||||
|
- Determine best way to handle filters at client then code it
|
||||||
|
- Modify datalist server code to alternatively accept a json filter string instead of a filter ID (post?)
|
||||||
|
- Actually, this is jsut for relative dates so, instead how about optional start and stop date parameters to go with filterid that contains relative filter?
|
||||||
|
- Mayve need to actually make the filter client code and that will trigger the right design?
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
TODO: CUSTOMIZE not working on widget edit form
|
|
||||||
TODO: CUSTOM DATE FIELD NOT SETTING NOW??
|
|
||||||
|
|
||||||
TODO: toolbar above grid for filters, refresh etc (make it a standard component?)
|
|
||||||
TODO: main.js filters need to be finished
|
|
||||||
TODO: SEARCH UI
|
|
||||||
TODO: FILTER UI
|
TODO: FILTER UI
|
||||||
- Show current filter summary or text name of filter at top of filter
|
- Show current filter summary or text name of filter at top of filter
|
||||||
- going to need filter name and also a summarized fragment of text showing criteria for reporting so also could purpose that list to show current filter?
|
- going to need filter name and also a summarized fragment of text showing criteria for reporting so also could purpose that list to show current filter?
|
||||||
- Filter picklist will show name for the current filter and sb at top of filter right up front
|
- Filter picklist will show name for the current filter and sb at top of filter right up front
|
||||||
|
- Relative time filters need to be removed from server and replaced with a single BETWEEN filter
|
||||||
|
- Then they need to be re-implemented at the client where the client will send the between date/times to the server based on the user's chosen relative token
|
||||||
|
- This fixes a bad design decision to involve the server in time zone shit when in fact the server should never operate in anything but UTC
|
||||||
|
- Time zones are a client issue and should never be a server issue
|
||||||
|
- When the filter code and processor is written it should calc the dates based on token and user's local time , then conver to between filter on the fly
|
||||||
|
- system is written with static filters saved to server so maybe need to turn it around and instead of providing a filterid, provide the filter json instead?
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Make functional user settings form with all overrides so can test shit out
|
||||||
|
- Need a browser check on opening the login page that will check to ensure the browser can do the date conversions properly etc and tell user browser is unsuitable if it isn't
|
||||||
|
|
||||||
|
TODO: CUSTOMIZE not working on widget edit form
|
||||||
|
TODO: CUSTOM DATE FIELD NOT SETTING NOW??
|
||||||
|
- Retest every kind of custom field
|
||||||
|
|
||||||
|
TODO: toolbar above grid for filters, refresh etc (make it a standard component?)
|
||||||
|
TODO: main.js filters need to be finished
|
||||||
|
TODO: SEARCH UI
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
TODO: Make sure scroll position is respected and saved when editing a widget and coming back to the list
|
TODO: Make sure scroll position is respected and saved when editing a widget and coming back to the list
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -471,7 +471,7 @@ function buildRecords(listData, columndefinitions, filters) {
|
|||||||
);
|
);
|
||||||
break;
|
break;
|
||||||
// case 6: //bool
|
// case 6: //bool
|
||||||
// display = filters.boolastext(display);
|
// change to checkboxes??
|
||||||
// break;
|
// break;
|
||||||
case 7: //decimal
|
case 7: //decimal
|
||||||
display = window.$gz.locale.decimalLocalized(display, languageName);
|
display = window.$gz.locale.decimalLocalized(display, languageName);
|
||||||
|
|||||||
Reference in New Issue
Block a user