This commit is contained in:
@@ -44,7 +44,7 @@ EDGE desktop
|
||||
=-=-=-=-=- OLD STUFF =-=-=-=-
|
||||
- does it update automatically
|
||||
- No localization bugs
|
||||
- Login as different locale users and confirm no ?? showing
|
||||
- Login as different translation users and confirm no ?? showing
|
||||
- Menu
|
||||
- surfaces properly given size changes
|
||||
- enabled works
|
||||
|
||||
@@ -45,18 +45,19 @@ CURRENT TODOs
|
||||
@@@@@@@@@@@ ROADMAP STAGE 1 and 2:
|
||||
|
||||
|
||||
todo: locale is a confusing term, can it be surfaced with something a little more on the nose?
|
||||
todo: translation is a confusing term, can it be surfaced with something a little more on the nose?
|
||||
- "Translation"
|
||||
|
||||
|
||||
todo: move the now properly "locale" settings for the browser OUT of translation.js into somewhere more appropriate and fixup calling code appropriately
|
||||
|
||||
|
||||
todo: move locale setting for user to useroptions object
|
||||
todo: move translation setting for user to useroptions object
|
||||
- then put on form and document
|
||||
- also, any other things in User that should be in UserOptions? (like user configurable stuff)
|
||||
|
||||
todo: User settings && password change documentation
|
||||
- do it now?
|
||||
- needs section explaining about how locale is displayed so can link to it from other places
|
||||
- needs section explaining about how translation is displayed so can link to it from other places
|
||||
- is that it's own page? (maybe because each subject should be short and focused and look clean with lots of whitespace, clear large text)
|
||||
- If I do it in parallel it will be done when I'm done
|
||||
- If I wait I won't waste time with changes needing to be udpated
|
||||
@@ -128,8 +129,8 @@ todo: ANY TIME - SIDE v7 STUFF DataDump plugin needs an explanation of what it i
|
||||
=================== FINALIZATION OF EDIT FORM BEFORE "STAMPING" OUT MORE ===========================================
|
||||
todo: VET translations
|
||||
- There are still a large number of non translated lt's in the non english stock languages (i.e. "More...")
|
||||
- Make it easy to dump the local storage locale text for vetting the translations
|
||||
- Login as each language, exercise the entire UI and then dump all the locale text that was fetched from the server and look for non english words
|
||||
- Make it easy to dump the local storage translation text for vetting the translations
|
||||
- Login as each language, exercise the entire UI and then dump all the translation text that was fetched from the server and look for non english words
|
||||
|
||||
|
||||
todo: REPORT LIST
|
||||
@@ -173,7 +174,7 @@ todo: AUTOMATIC TEST *** SUPER IMPORTANT *****
|
||||
- Ideally it will test every input component and validate the entire record round trips properly, maybe it needs to also try different states like creating new, editing etc
|
||||
- Also function as a "smoke" test that will heavily exercise the server and client repeatedly for as long as I let it run which will reveal issues before releases
|
||||
|
||||
todo: Locale page with locale settings
|
||||
todo: translation page with translation settings
|
||||
|
||||
todo: Trial route ui support in client (ON HOLD NEEDS BACKEND WORK)
|
||||
- Went to do this but found it's a bit of a maze and has some hacked temp code in the license fetch route etc for development purposes
|
||||
@@ -264,7 +265,7 @@ todo: INVESTIGATE - Dark mode / theming (dark with a half moon icon)
|
||||
- Also see how to allow theming maybe or colour choices? Nah, dark mode is the most useful; I should decide the colours and stick with them it's part of our image
|
||||
|
||||
|
||||
#locale stuff
|
||||
#translation stuff
|
||||
|
||||
todo: LOCALIZATION form
|
||||
- Dedicated area for localization adjustments
|
||||
@@ -273,11 +274,11 @@ todo: LOCALIZATION form
|
||||
|
||||
|
||||
todo: //todo: timezone doesn't match, offer to fix it in initialize.js there needs to be a prompt and autofix
|
||||
todo: code the user options with the currency symbol etc on the server and then update client to fetch them. Use static values instad in locale.
|
||||
Locale should fetch those settings the first time it sees they are not present so that they are refreshed upon use and are not stored in localstorage
|
||||
todo: code the user options with the currency symbol etc on the server and then update client to fetch them. Use static values instad in translation.
|
||||
translation should fetch those settings the first time it sees they are not present so that they are refreshed upon use and are not stored in localstorage
|
||||
(or should they be? anyway, can work that out later)
|
||||
todo: Local user settings page / UI where can
|
||||
- set locale choices and values
|
||||
- set translation choices and values
|
||||
- Reset to default form settings
|
||||
- Other shit I can't think of right now but there will be a lot
|
||||
|
||||
@@ -331,7 +332,7 @@ MAYBE: AUTO-LOGOUT EXPIRED SESSION?
|
||||
- first off, is this really an issue?
|
||||
- No, actually it's kind of useful for keeping on working when a server needs a restart or something
|
||||
- Only real issue is cached data mismatch so perhaps when detected it should toss cached data forcing a reload
|
||||
- Or is this really an issue either? things cached are form customization and locale text which in the normal course of things won't change much
|
||||
- Or is this really an issue either? things cached are form customization and translation text which in the normal course of things won't change much
|
||||
|
||||
- Right now a user can simply close the browser in the middle of a session, re-open it any amount of time later and it will just keep working, however it might have outdatd cached data from the server
|
||||
- What about a time limit after which a session needs to login again just to protect the users from themselves?
|
||||
@@ -367,11 +368,11 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
|
||||
- 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
|
||||
- TEST SMALL and LARGE device layout regularly, don't get too far ahead of the testing
|
||||
- Every type of entry field fully localized properly including numeric, date, time, tags etc
|
||||
- Client: initialize after login sets locale formats for everything.
|
||||
- Client: initialize after login sets translation formats for everything.
|
||||
- Best to do this useroptions stuff after a form is in place that I can play with at the client and experiment to see what is possible
|
||||
- How much flexibility do we have to set things like numeric / currency input / display format?
|
||||
- First it gets useroptions to know what to override or not, then sets defaults based on browser or override settings in central client area for all display/parsing etc
|
||||
- All numeric and date displays and input in locale format
|
||||
- All numeric and date displays and input in translation format
|
||||
- numeric inputs need to be set as such so that the number keyboard appears
|
||||
- And all specialty inputs of course
|
||||
- Custom fields implemented!
|
||||
@@ -416,7 +417,7 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
|
||||
- Override browser with these numeric format settings instead (see below)
|
||||
- Digit grouping symbol i.e. the , in 1,000,000
|
||||
- decimalValid symbol i.e. the . in 1.00
|
||||
- Currency symbol string (may be more than one character in some locales i.e. "Eur")
|
||||
- Currency symbol string (may be more than one character in some translations i.e. "Eur")
|
||||
- negative display format one of these: -1.1, (1.1), 1.1-
|
||||
- Use browser Datetime format
|
||||
- Override browser datetime with these settings instead (see below)
|
||||
@@ -456,13 +457,13 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
|
||||
TESTING TODO
|
||||
Localized input and parsing and validation
|
||||
- Going to need to handle localized numeric entry formats
|
||||
- Deal with this once form is in good shape and worth testing with different locales
|
||||
- Deal with this once form is in good shape and worth testing with different translations
|
||||
-----------------
|
||||
|
||||
TODO AFTER CLIENT block ABOVE:
|
||||
ON UPDATE: have an url that opens automatically or a notification and link to one after a new version has been detected just like visual studio does in order to show what is new in this version
|
||||
|
||||
ABOUT form - add the user settings such as timezone offset, locale formatting patterns etc, will be useful for troubleshooting
|
||||
ABOUT form - add the user settings such as timezone offset, translation formatting patterns etc, will be useful for troubleshooting
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user