This commit is contained in:
2021-09-21 23:55:21 +00:00
parent 41b1f2d2ec
commit b4ed978244

View File

@@ -21,7 +21,7 @@
{{ $refs.calendar.title }}</v-btn {{ $refs.calendar.title }}</v-btn
> >
</v-toolbar-title> </v-toolbar-title>
<!-- <v-spacer></v-spacer> --> <v-spacer v-if="!$vuetify.breakpoint.xs"></v-spacer>
<v-btn <v-btn
class="mr-3" class="mr-3"
fab fab
@@ -370,14 +370,9 @@
TODO NEXT: TODO NEXT:
Display and open Reviews
Review object changes:
Due date sb changed to "ReviewDate" meaning this is when the review should happen
if completed date is set then editable is false for schedule adn it should should a checkmark symbol indicating it's been done
review icon, appt color - no inherent so do grayish neutral and test on both dark and light modes
Settings form Settings form
Settings should be for the FORM, not the user so that a user can have different settings in personal schedule vs svc-schedule etc
persist, imminentize persist, imminentize
Save / load from server (or locally only? as formSettings.saved)?? Save / load from server (or locally only? as formSettings.saved)??
saved with device or saved with account is the heart of it saved with device or saved with account is the heart of it
@@ -387,18 +382,17 @@ TODO NEXT:
Weekdays: weekdays to display, copy from pm exclude days thingy Weekdays: weekdays to display, copy from pm exclude days thingy
More info: checkbox beside each item below that can be shown in wo More info: checkbox beside each item below that can be shown in wo
Needs a refresh button at top todo: Needs a refresh button somewhere to refresh for new appts.
todo: red current time line is cool, see if can implement (also follows google calendar ui)
todo: ### find all trans keys and make sure they are fetched in initform ### todo: ### find all trans keys and make sure they are fetched in initform ###
TESTING: TESTING:
Test here locally and check for layout issues while doing it on all devices
drag/extend in all views working? drag/extend in all views working?
touch mode still can do all ops mobile device testing
ultimately test on devices phones
ipad
shitty tablet
NOTE: no need for drag drop extend on non mouse device, but do want it to be able to create at least near the touch point
Move common functionality out of home-schedule to be re-used in svc-schedule and also potentially other scheds like customer view of workorders or visual calendar view of work for a single customer for techs etc Move common functionality out of home-schedule to be re-used in svc-schedule and also potentially other scheds like customer view of workorders or visual calendar view of work for a single customer for techs etc
the more I can move out of it the easier to do more scheds in other places the more I can move out of it the easier to do more scheds in other places
@@ -406,6 +400,11 @@ TODO NEXT:
DOCS: DOCS:
how to use the schedule how to use the schedule
Investigate: can AyaNova be a calendar source for Google calendar and others (like provide ical)
so they can view, move around but create would be outside that but provided for when refresh.
This way a user could just use their built in calendar app rather than fighting with our implementation
reporting - make it happen reporting - make it happen
could just default to regular reporting list, doesn't absolutely need to be a calendar at least at first could just default to regular reporting list, doesn't absolutely need to be a calendar at least at first
as long as it has all appointments consolidated in single list as long as it has all appointments consolidated in single list
@@ -417,8 +416,6 @@ TODO NEXT:
// const FORM_CUSTOM_TEMPLATE_KEY = "home-schedule"; // const FORM_CUSTOM_TEMPLATE_KEY = "home-schedule";
const FORM_KEY = "home-schedule"; const FORM_KEY = "home-schedule";
const CLICK_DETECT_TIMEOUT = 100; const CLICK_DETECT_TIMEOUT = 100;
let mouseX = 0;
let mouseY = 0;
export default { export default {
async created() { async created() {
let vm = this; let vm = this;