This commit is contained in:
@@ -4,14 +4,29 @@ PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route chang
|
||||
=-=-=-=-
|
||||
|
||||
|
||||
todo: remember scroll position in lists when returning, make sure it is working, will be a pain if not
|
||||
|
||||
todo: OPS routes CLIENT UI
|
||||
- Backup, restore https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3369
|
||||
view files
|
||||
view last backup date
|
||||
download files UNTESTED YET< NEED UI FOR THIS
|
||||
adjust settings
|
||||
|
||||
Is this two forms or one form?
|
||||
A good philosophy should probably be one form for one task, however people hate naving around too much, however this is not a common thing to much with
|
||||
Viewing backup is a very common and seeing list etc
|
||||
Triggering backup and adjusting settings is very less common
|
||||
maybe it's two forms seperately, not like workorder where it's critical how to move around in hierarchy
|
||||
|
||||
Lists all backup files
|
||||
with download links
|
||||
Backup NOW button triggers backup somehow tied to list, in header or worst case scenario in menu but like to expose it directly
|
||||
Are you sure prompt, will lock server until backup is completed
|
||||
|
||||
Shows backup settings in editable form
|
||||
can update and save this is the editable content of the form
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- JOBS
|
||||
view, and work with, whatever that means
|
||||
|
||||
|
||||
Reference in New Issue
Block a user