This commit is contained in:
@@ -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,55 +370,52 @@
|
|||||||
|
|
||||||
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
|
||||||
|
Save / load from server (or locally only? as formSettings.saved)??
|
||||||
|
saved with device or saved with account is the heart of it
|
||||||
|
wo display section:
|
||||||
|
DISPLAY
|
||||||
|
Color: wostatus/woitemstatus/woitempriority/none
|
||||||
|
Weekdays: weekdays to display, copy from pm exclude days thingy
|
||||||
|
More info: checkbox beside each item below that can be shown in wo
|
||||||
|
|
||||||
persist, imminentize
|
todo: Needs a refresh button somewhere to refresh for new appts.
|
||||||
Save / load from server (or locally only? as formSettings.saved)??
|
todo: ### find all trans keys and make sure they are fetched in initform ###
|
||||||
saved with device or saved with account is the heart of it
|
|
||||||
wo display section:
|
TESTING:
|
||||||
DISPLAY
|
Test here locally and check for layout issues while doing it on all devices
|
||||||
Color: wostatus/woitemstatus/woitempriority/none
|
drag/extend in all views working?
|
||||||
Weekdays: weekdays to display, copy from pm exclude days thingy
|
mobile device testing
|
||||||
More info: checkbox beside each item below that can be shown in wo
|
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
|
||||||
|
the more I can move out of it the easier to do more scheds in other places
|
||||||
|
|
||||||
|
DOCS:
|
||||||
|
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
|
||||||
|
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
|
||||||
|
|
||||||
Needs a refresh button at top
|
Move on to the shared service schedule with categories being people and all that entails
|
||||||
|
|
||||||
|
|
||||||
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 ###
|
|
||||||
|
|
||||||
TESTING:
|
|
||||||
drag/extend in all views working?
|
|
||||||
touch mode still can do all ops
|
|
||||||
ultimately test on devices
|
|
||||||
|
|
||||||
|
|
||||||
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
|
|
||||||
|
|
||||||
DOCS:
|
|
||||||
how to use the schedule
|
|
||||||
|
|
||||||
reporting - make it happen
|
|
||||||
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
|
|
||||||
|
|
||||||
Move on to the shared service schedule with categories being people and all that entails
|
|
||||||
|
|
||||||
*/
|
*/
|
||||||
|
|
||||||
// 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;
|
||||||
|
|||||||
Reference in New Issue
Block a user