This commit is contained in:
@@ -1,11 +1,8 @@
|
||||
# TODO (J.F.C. - Just fucking code it already)
|
||||
|
||||
Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTQ0NTU5NzAwIiwiZXhwIjoiMTU0NzE1MTcwMCIsImlzcyI6ImF5YW5vdmEuY29tIiwiaWQiOiIxIiwiYXlhbm92YS9yb2xlcyI6IjMyNzY3In0.fMq_8Dvia63rzN_U2zjczPvUNM40OEAeI4VOeV6ulGw
|
||||
# CLIENT TODO (J.F.C. - Just fucking code it already)
|
||||
|
||||
|
||||
## IMMEDIATE ITEMS
|
||||
|
||||
|
||||
Need a sprint to get to a fully testable client with entry form, list and as much as possible all features from COMMON-* specs list
|
||||
|
||||
-----------------------
|
||||
@@ -13,19 +10,24 @@ Need a sprint to get to a fully testable client with entry form, list and as muc
|
||||
///
|
||||
TODO CLIENT STUFF
|
||||
|
||||
#### A PHONE IS PROBABLY NOT THE MOST COMMON SIZE FORM FACTOR THAT WILL BE USED SO SUPPORT IT, YES, BUT DON'T GET HUNG UP ON IT TO THE POINT WHERE IT RUINS THE EXPERIENCE ON A FULL COMPUTER OR TABLET
|
||||
|
||||
- CUSTOM FIELDS?!
|
||||
- This wasn't worked out and needs to be done now
|
||||
- main docs and specs in server project and core-custom-fields.txt specifications doc where I will work it out
|
||||
|
||||
- LIST
|
||||
- Overall list menu toolbar at top with following icons:
|
||||
- Add new item
|
||||
- Filter list
|
||||
- Refresh
|
||||
- Ellipsis submenu with mass ops options and other list wide options appear there
|
||||
- Print / report
|
||||
- How to show tags?
|
||||
- In main list?
|
||||
- Only in detail?
|
||||
- Show tags in main list as they were added to widget recently
|
||||
- They come from the api as an array of strings
|
||||
- Check the rights to the list before it gets the data
|
||||
- Sort and filter dialog
|
||||
|
||||
- Should list or any widgets fetch data automatically on display or should they have some way of requesting it to save bandwidth? (TTM CADILLAC PROBLEM?)
|
||||
- Perhaps with the custom widget repository where people can customize the UI they can decide what is visible immediately upon login so that handles this issue
|
||||
- Should the list be narrow to start and expand on demand?(TTM CADILLAC PROBLEM?)
|
||||
|
||||
- Login needs to scroll higher or logo smaller on sm so that the keyboard doesn't obscure the login lines
|
||||
- Need a test user that has access to every possible role so that I can see all the roles for testing purposes
|
||||
- About page has too big of margins on each side of display
|
||||
@@ -33,12 +35,23 @@ TODO CLIENT STUFF
|
||||
- numeric inputs need to be set as such so that the number keyboard appears
|
||||
- Make the copyright banner at bottom left aligned, right now it seems weird in small iPhone size when it breaks to two lines (make text smaller?)
|
||||
- Change server api page favicon to look like a SERVER version of the AyaNova logo, not the same one as the client uses [ fuck it, why? TTM!]
|
||||
- Disable google fonts for manual / docs generator:
|
||||
- first need to upgrade to latest mkdocs AND material theme for mkdocs
|
||||
- https://www.mkdocs.org/#installation
|
||||
- https://github.com/squidfunk/mkdocs-material
|
||||
- https://squidfunk.github.io/mkdocs-material/compliance/
|
||||
- Once docs no longer need google fonts can adjust the devops nginx config and remove the overrides for CORS and all that shit.
|
||||
- CRUD form for widget that supports all the aspects (NEED THIS BEFORE MUCH OTHER CODING HAPPENS)
|
||||
- Is this just not happening now?: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3494
|
||||
- Everything needs to work in this form right down to the reports so that once it's done I can move forward confidentally with testing, demo-ing and with cranking out the other forms
|
||||
- Don't want to solve any problems that should have been solved with this form later as I will inevitably be full on copy and pasting once I get it down and so it needs to be as solid as possible First
|
||||
- Every type of entry field fully localized properly including numeric, date, time, tags etc
|
||||
- A printable report
|
||||
- Even if there is no designer yet for the report and it has to use a manually created report format HTML doc
|
||||
- Error and validation properly implemented
|
||||
- Error reporting overall properly implemented
|
||||
- Dirty check and warning if navigate away.
|
||||
- Menu with common options
|
||||
- File attachments set and get
|
||||
- Duplicate
|
||||
- ETC (look it up)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -98,7 +111,8 @@ TODO CLIENT STUFF
|
||||
- Do not allow anything other than numeric display, i.e. no January or Saturday so we avoid localization issues
|
||||
|
||||
|
||||
|
||||
- WIKI PAGE
|
||||
- Doesn't require docs support as is now changed to a standard file attachment
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user