From 23502e1b358583e78e3b0bc11bcda77ab3fd2e59 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 11 Feb 2022 17:56:34 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 49 +++++++------------------ ayanova/src/components/time-control.vue | 1 + 2 files changed, 14 insertions(+), 36 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index e2152afa..f742e0c4 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -150,35 +150,6 @@ Coded by importance -todo: 1 the form Validation errors are probably not documented in the form docs but should be just to explain basically what to look for and an example - -TODO: 1 BETA DOCS: - - *** IMPORTANT *** before beta go through *every* doc page one at a time and read through them for outdated stuff and wording that should not be public - - - administration setup which should be mostly done but go over it and find missing bits that a beta tester will need - - MIGRATION docs, there *must* be a migration page and it needs to tie into the installation docs perhaps - - evaluation docs where it explains about trial license and requesting and generating data etc, just the basic process and why to do it that way - - See Global Settings form for format for all feature pages - MOST IMPORTANT is the basic stuff about how to use forms and controls and stuff before getting into actual feature pages - this is because beta testers and users will probably already know about each object so the first thing is to get them going with basic usability docs if prioritizing - - Has pertinent cases - - ROLES need a completely full documentation or some way to view what is accessible for what maybe in code in the UI??? - - Every form's docs should have a ##Roles section that outlines which roles get access to that form - - There is no clear ROLES guide and we need one for sure. I like the idea of dynamically generated in the UI so we can change it and it's always accurate and - useful for us to ref as well, should have done it long time ago. - - Forms and controls - Every form help page should, at the top have a link to Standard form controls or How to use forms so user can move from any topic to how to use the basic controls etc - I guess in a section outlining the fields and menu options on the form there should be links to "Common menu options" and "Common controls" and common controls should have a link to how to use forms - common controls means Wiki, active, attachments, tags, names and their uniqueness etc - - Somewhere document that a login is good for 5 days from moment of login before needing to login again - WORKORDER docs page is just a placeholder, needs to be written for BETA or people will not be able to figure out basics - do the workorder and the links that go off of it like basic forms shit etc - CLEANUP, go through each docs page look for swear words, inside info, stuff that shouldn't be there and replace with UNDER CONSTRUCTION instead - - --1 Somewhere document that a login is good for 5 days from moment of login before needing to login again - 2 consolidate pages, in many cases I have too many pages that are too short, when it could be consolidated as the mkdocs has a nice toc to the right making it easy to find stuff and saving opening new pages a lot ot move around @@ -230,16 +201,17 @@ TODO: 1 BETA DOCS: \_____|______|_____|______|_| \_| |_| - --1 todo: why should user be able to open a part inventory transaction record in the first place? It opens to the history form, isn't that weird, theres nothing to see that isn't -in the grid is there?? - -- 1 todo: window.$gz.locale.diffHoursFromUTC8601String is often calculated a total of 1.99 due to some rounding even though the two times look identical - must be seconds or something, needs a round up in those cases, that's weird. To recreate try a start time of 11:21 and end time of 1:21pm which should be two hours but is 1.99 hours - sometimes it just works, I'm guessing it's a milliseconds issue or something, round first maybe to remove ms then calc? - 1 todo: time control in native browser format isn't showing a title at all, check date as well. Date and time is ok - 1 todo: about FORM - does it show user has native date time input use browser override? + + + + + + + + - 2 todo: CURRENCY / DECIMAL control, not too happy with them, considering rolling my own maybe here are some ideas: To get current use the latest version which is completely different and seems ok, here is a dude who implemented it with vuetify so would need to copy this @@ -276,6 +248,11 @@ console.log(parseFloat(localeParseFloat("1,100.9", "nl"))); // Dutch locale: rev +-2 todo: why should user be able to open a part inventory transaction record in the first place? It opens to the history form, isn't that weird, theres nothing to see that isn't +in the grid is there?? +- 2 todo: window.$gz.locale.diffHoursFromUTC8601String is often calculated a total of 1.99 due to some rounding even though the two times look identical + must be seconds or something, needs a round up in those cases, that's weird. To recreate try a start time of 11:21 and end time of 1:21pm which should be two hours but is 1.99 hours + sometimes it just works, I'm guessing it's a milliseconds issue or something, round first maybe to remove ms then calc? - 2 todo: when hide a section in wo like all tasks in customize should hide the add task woitem context menu item too - 2: the home notify subscription table shows object types but without the square brackets around them and should for consistency diff --git a/ayanova/src/components/time-control.vue b/ayanova/src/components/time-control.vue index 568167c3..4e8251d4 100644 --- a/ayanova/src/components/time-control.vue +++ b/ayanova/src/components/time-control.vue @@ -45,6 +45,7 @@ :value="timeValue" :readonly="readonly" :disabled="disabled" + :label="label" type="time" :data-cy="`${dataCy}:time`" @change="updateTimeValue"