350 lines
20 KiB
Plaintext
350 lines
20 KiB
Plaintext
|
|
=========================================================================================================
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 3
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
|
|
This stage is to consolidate the basics and set the final shell form.
|
|
A lot of it might be rundundent
|
|
|
|
|
|
todo: 8 Infrastructure cases outstanding all tagged as "INFRASTRUCTURE:"
|
|
|
|
todo: Joyce after testing issues:
|
|
On laptop, when in field that is a NUMBER (i.e. Count in Widget) have option to highlight and type in new number OR just use the UP/DOWN arrow on keyboard OR use the up/down arrow that is the field itself.
|
|
Whereas on android ONLY have option to type in new number
|
|
And number is limited in size to no more than 10 digits (says Value must be an integer in red under it if go over)
|
|
todo: Check if set to a number properly (I'm pretty sure it is but to be certain)
|
|
TODO: Check if this is a known issue on android mobile because I'm seeing it on both firefox and chrome on android
|
|
could be a vuetify bug
|
|
|
|
todo: login form on mobile is cut off due to the 100vh bug on chrome as per nav drawer logout issue
|
|
fix might be to put a 100% on something app level somewhere or maybe just the login form since it's the only one that has that issue
|
|
|
|
|
|
### RETEST ALL DEVICES WHEN GET TO HERE #####
|
|
TO TEST:
|
|
- above changes block
|
|
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 4 - REPORTING / DASHBOARD / KPI
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
|
|
Do reporting and dashboard here
|
|
Read over and maybe develop in parallel a bit here a bit there from client down to server as much of this code will overlap in theory
|
|
Reporting and dashboard are tied together in a sense because they both need similar data and likely will need similar controls etc
|
|
|
|
todo: DASHBOARD
|
|
- Joyce kpi / charts and graphs
|
|
- these cases:
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/2024
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1974
|
|
|
|
Won't have workorders, will need to test with widgets and users, maybe clients will be ported?
|
|
|
|
todo: REPORTS v8 MIGRATE / EXPORT (CUSTOMIZED NOT STOCK) FROM v7? Try to see if plugin can export any aspect of reports
|
|
code behind?
|
|
even if just exported as comments in js for the new format just to have the formula's etc
|
|
basic layout, maybe as HTML?
|
|
anything that would help, even just the name of it and it's existence and a TODO in the middle is better than nothing at all
|
|
Any info to assist report designer with V8.
|
|
Be nice to see field list with translation for equivalent new.
|
|
|
|
|
|
TODO: Reporting datasources
|
|
Needs to be able to handle getting data from different types of sources and be cool with it
|
|
e.g. Some datatables with selections are directly off a server list, not the regular datalist
|
|
others are datalist
|
|
yet others may just be an array at client with no tie to server at all
|
|
|
|
todo: REPORTING wiki Download, open as pdf, email?
|
|
- is this a reporting issue? I think it is, moving to reporting
|
|
|
|
todo: REPORTING wiki in datalist?
|
|
- will need for reports but can't show in a grid, maybe it's available for something but can't be seen or filtered?
|
|
- shows in grid as basically a bool like has wiki or not but doesn't show any actual wiki?
|
|
- this is only to feed report, no other purpose to it.
|
|
|
|
todo: Report editor for creating new report accessed from the report any **existing** reports preview form if have the rights.
|
|
- or maybe from the report selector dialog box if they have the rights, although would that fuck up navigation process?
|
|
- This seems better because, what if they can't preview a report for some reason, then they can never fix it or make a new one?
|
|
- NOT like v7 where accessed from the object edit form (this is to keep menu options down to a reasonable number)
|
|
- Every list sb reportable case https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3653
|
|
- Also search results and history? Can feed from UI level to report component?
|
|
- Reporting case with various things pertinent to look over BEFORE starting in on this:
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3451
|
|
- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1849
|
|
Instantly print? https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/818
|
|
Guy took the time to request it, so have a look think and see if there is a way to do this
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1734
|
|
- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/962
|
|
|
|
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
@@@@@@@@@@@@@ ROADMAP STAGE 5 - FINALIZE ALL NON BIZ OBJECT SPECIFIC FUNCTIONALITY
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
|
|
todo: Much of this stage below needs TRIAGING, do that first.
|
|
Any real (corebizobject) shit goes to stage 7
|
|
|
|
|
|
todo: MAPPING
|
|
getting a *lot* of request about this
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1816
|
|
maybe stage 7 or I guess could fake it for now, it's going to be known what will be needed
|
|
https://news.ycombinator.com/item?id=23722133
|
|
https://blog.mapbox.com/openstreetmap-a-global-map-for-worldwide-insight-4e041cbf1ec1
|
|
|
|
todo: can I support keycodes for saving in AyaNova and other shit that are the same as in v7 or as much as possible, i.e. ctrl-s to save (or whatever was defined)
|
|
What v7 used to support:
|
|
f1 - help, case (Keys.Alt | Keys.X) //Close form, alt-w new workorder, alt-m new pm workorder, alt-q new quote, alt-c new client, alt-u new unit, alt-p new part, ctrl-alt-g grid criteria for development,
|
|
IMPORTANT / DO THIS: insert date and time (localized) as text anywhere with a key combo
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1514
|
|
|
|
|
|
todo: back and forward buttons when running without browser controls in application mode?
|
|
- wait and see on this one, as it will be likely outside of any particular form so not something to be baked in early necessarily
|
|
|
|
todo: GUIDED TOUR
|
|
- This is an important feature and at least get a basic one in there for starters and initial release
|
|
- This is a replacement for the tutorials and videos in v7 a
|
|
- Need to add that auto-pilot thingy that allows for guided tours in HTML apps
|
|
- Specifically it should at least have an ONBOARDING walk through of how to move around, enter data, get help etc. Not feature specific but usage specfic.
|
|
- Later I'll add feature specfic tutorials like how to make a workorder etc
|
|
|
|
|
|
|
|
todo: clickable urls
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1738
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-----------------
|
|
|
|
TODO AFTER CLIENT block ABOVE:
|
|
TODO: ON UPDATE TO NEW version
|
|
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
|
|
maybe ideally it opens to a new document page "whats new in version x.xx"
|
|
this way no need to go beyond the local server or hit our site unnecessarily
|
|
|
|
|
|
|
|
|
|
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - INSTALLER, LICENSING, ROCKFISH SUPPORT FOR RAVEN
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
|
|
|
|
|
|
todo: WINDOWS INSTALLER
|
|
Runner harness wrapper thing?
|
|
even if windows only
|
|
it could modify config since it's outside the server
|
|
check for Postgres server extant and if not automatically start the standalone postgres instance
|
|
manage postgres start and stop and configuration changes, sit in tray, run AyaNova server from there?
|
|
|
|
easy way to select command line params without resorting to editing text files for end user
|
|
initially it's an installation option, but then need to edit after the fact
|
|
Quick check of installers available still and is it still kosher to keep using INNO setup or is something better, more supported by windows etc?
|
|
Wix if want MSI (some say that's desireable)
|
|
INNO is still relevant
|
|
I don't need hardly any requirements that can't just be copy or unzip deployed so maybe don't even need an installer for now?
|
|
(zip distribution is going to be problematic with Windows file protection shit)
|
|
https://docs.microsoft.com/en-us/dotnet/core/deploying/
|
|
https://docs.microsoft.com/en-us/dotnet/core/rid-catalog
|
|
|
|
|
|
Completely packaged and installable. REady for users to install as a test as I iterate stage 7 below
|
|
All the stuff needed for someone to run it as a test without the real objects yet.
|
|
Some kind of expiring license so they can't just keep using it as fucked as it may be some might do that
|
|
I want short targetted testing only, not someone downloading and trying it out a month later, that's useless for us
|
|
This needs to be focused on what I need to get from people about testing
|
|
|
|
|
|
todo: LINUX INSTALLER
|
|
Linux users don't mind doing the manual config thing as much, they're used to it and it could just be a shell file anyway
|
|
So mainly this would be a documentation steps to install type issue
|
|
|
|
|
|
todo: DOCUMENT DOCKER
|
|
Present dockerfile maybe for docker installation with FILES folder pre-ready to build / run
|
|
Whatever docker needs
|
|
Or maybe private registry with docker images on our servers somewhere
|
|
|
|
todo: rockfish, can't do purchase for raven or view it I think
|
|
Test a whole sales process from eval to purchase and make it work
|
|
todo: rockfish, upgrade to latest bootstrap, out of date Currently
|
|
todo: rockfish, trial license fetched On date not updating? (not showing in UI)
|
|
|
|
todo: Joyce rockfish notes:
|
|
Licensing:
|
|
noticed that the field "Fetched on" is NEVER updated.
|
|
is it much to be able to see the TIME as well as the DATE, when "Requested" and when "Processed"?
|
|
There are drop down selections NEW, APPROVED, REJECTED for the (already generated) listed keys. But can not actually save to a different Status. What is the purpose of the drop down options if can not select?
|
|
|
|
|
|
|
|
|
|
todo: Discourse bootstrapping install
|
|
look over, get ideas make case steal ideas profit FTW$
|
|
https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md
|
|
//here is their standalone config yml definition for DOCKER
|
|
https://github.com/discourse/discourse_docker/blob/master/samples/standalone.yml
|
|
|
|
|
|
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 7 - "REALITY"
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
All in on porting over all the real objects from v7
|
|
|
|
todo: First of all triage the features to port over in the sanest order so not stubbing too much stuff
|
|
Try to get scheduleable stuff early because schedule form will take some time
|
|
|
|
todo: Schedule form
|
|
- This one is big but requires the data to be there so as soon as implement enough things that are scheduleable then do this
|
|
todo: Notifications
|
|
Many are on hold until there are real objects to code against, now is the time to code them as the objects are added
|
|
|
|
todo: can beta test at this point
|
|
post installer, enlist trial users get feedback, don't get too down when they shit all over it as they will undoubtedly :)
|
|
|
|
todo: Document in user manual all form controls with instruction on how to use the various controls etc
|
|
- "Anatomy of a AyaNova Form"
|
|
|
|
WORKORDER UI
|
|
todo: Investigate Workorder structure and datagrid see case https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3768
|
|
Likely that workorder grids inside will not be full blown custom datagrid I wrote but just a vanilla v-data-table control since there is likely no need for the full customization shit
|
|
todo: workorder UI layout stuff (TTM!! Don't re-invent the wheel!)
|
|
There's been a lot of ideas about wo floating around and considered, but at the end of the day what I have works so maybe try to meld
|
|
into what I have the new concepts and see what comes out. Support a rich wo UI on big screens and scroll around UI on phone maybe.
|
|
some notes:
|
|
Workorder UI good ideas here: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3475
|
|
Basically (based on RI) it boils down to don't make the user go up to the workorder item level when they can go sideways directly to an alternate child of woitem
|
|
i.e. going from parts to labor shouldn't require going up a level
|
|
All workorder in one document and just really really tall? (people bitch about RI requiring too many navigation steps to get to shit)
|
|
Header and items in one document then bottom in seperate pages?
|
|
Is it going to be far easier to code this bitch if I have all the workorder data at hand or..?
|
|
How does WBI handle all this because it's kind of the poster child for RAVEN
|
|
Workorder is one of those things that may require different views for phone and tablet and laptop etc
|
|
Kind of like two views, tiny phone and anything larger
|
|
On a PC people will want and expect it to look as much like v7 workorder as possible, maybe that's still a valid layout
|
|
just tweaked to work better as a web app a bit but theoretically I could almost duplicate that layout with the tools I have
|
|
|
|
|
|
Consider UI in this as well, will need to decide at least what is visible when
|
|
Workorder UI good ideas here: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3475
|
|
How to add items, like new woitem?
|
|
send to server get back new object?
|
|
lots of biz rules and stuff need to happen, want to minimize load at client
|
|
but lots of data back and forth is not ideal
|
|
maybe request a woitem and get it back?
|
|
what exactly needs to be processed in the wo when items are added / removed?
|
|
math / totalling?
|
|
simple calcs sb client doable
|
|
this will drive what has to happen.
|
|
Need to go over all wo features and factor them into this decision properly
|
|
The whole idea of a completed section of a wo and stuff, is that dropped due to TTM or still viable?
|
|
maybe can pick out the best new features of that which can be integrated into existing design rather than re-inventing the wheel
|
|
Here is an overview: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3412
|
|
How best to be able to service LoanUnits on a workorder?
|
|
Just make them Units with extra properties exposed if type of loaner?
|
|
This seems simplest, but what will it effect?
|
|
Hard to make them serviceable if they are an alternate table of source for what's being repaired as that breaks a lot of other code or adds exceptions
|
|
Customer is then who exactly because it's fundamental to a lot of wo functionality?
|
|
from a biz perspective isn't it like you are your own customer when you service your own equipment that you loan out?
|
|
Does Serial field need to be numeric, could it be text instead?
|
|
prompted by case 3428 saying that it's hard to deal with constant conversion to text for UI etc
|
|
plus, I'm thinking it opens door to textual scheme like appending -A or whatever to a wo.
|
|
or, is that a display issue?
|
|
Calling something "serial" implies it's unique but it isn't, maybe I should call it "number" instead or "ID" or something?
|
|
INFO: did a test workorder with ALL fields filled out heavily and one woitem, exported from db entire graph based on detailed report so every line was every item repeated
|
|
still only 84kb and it's a lot bigger than any typical wo in v8 would be as it will be far more efficient without having to repeat lines flatly
|
|
so I think size of object is a non-issue really from a practical standpoint.
|
|
|
|
|
|
UI
|
|
|
|
idea: UI reflects tentativeness state of object:
|
|
The UI doesn't imply something is done by changing it fully until the save is completed.
|
|
This serves two purposes:
|
|
1) user knows at a glance what isn't saved yet and will know it's waiting for save clearly, hopefully leading them to save more often,
|
|
2) client doesn't need to track invisible shit behind the scenes, can more easily do patch updates right off UI source
|
|
|
|
e.g.:
|
|
if deleted a row in parts, that row doesn't disappear but rather shows crossed out, maybe grayed out but still there until save to indicate it's tentative status
|
|
if added a row, shows green or something or bold or asterisk, (can style with css based on state) until saved
|
|
problems:
|
|
how to handle regular fields that are changed (that's a lot of field data to track for changes)?
|
|
Maybe client keeps a virgin copy of the original wo for comparison
|
|
periodically does a compare and flags differences on updates?
|
|
(this would also help to serve as an Undo maybe?)
|
|
|
|
|
|
|
|
todo: Documentation
|
|
Need to think this through carefully
|
|
Need to get the critical bits in for onboarding and importing so people can get going
|
|
Most important stuff is anything non-obvious
|
|
Seems pointless to have one doc per form that just says "The name field is the name and must be unique"
|
|
maybe have that kind of stuff in the form basics and then have a doc per OBJECT instead with anything unique or interesting about the object
|
|
(and each object form has a link to formbasics so can link to the object form from UI and they get both)
|
|
Parts of it can be done post-release for sure
|
|
|
|
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 8 - EXTENSIONS (was plugins)
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
|
|
Plan the order of criticality for extensions
|
|
ACCOUNTING is obviously the first and foremost one and MUST be there for a lot of people to take up
|
|
MUST be done in a way to support other alternative accounting apps that are coming around now like freshbooks or whatever it's called that Joyce is using now
|
|
probably going to need a "trick" of some kind to interface with desktop accounting
|
|
i.e. a local windows app that uses the api and just copy over the qbi code
|
|
or a local server that has it's own web interface
|
|
or regular raven UI but the accounting section interfaces with a local server for local desktop qbi stuff and
|
|
the raven server interfaces with QBOnline for the QBOI stuff
|
|
|
|
based on sales, how many subscribed now
|
|
which ones are porting and which are not
|
|
Implement in order or priority
|
|
Fuck peachtree?
|
|
|
|
|
|
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 9 - RELEASE
|
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
|
|
Assuming has passed all testing
|
|
Plan pricing and sales strategy
|
|
What to do with licenses for v7 people
|
|
Another payment processor?
|
|
support bitcoin if possible as well
|
|
|
|
|
|
|
|
|
|
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 10 - ROCKFISH / HOSTING BACKEND SELF SERVER READINESS
|
|
DO server allocation, rockfish revamp to drive this part (or maybe it's an alternate app)
|
|
https://blog.digitalocean.com/its-all-about-the-bandwidth-why-many-network-intensive-services-select-digitalocean-as-their-cloud/?utm_medium=email&utm_source=do_newsletter&utm_campaign=04292020
|
|
https://www.youtube.com/watch?v=zZVoo5AbANI
|
|
|
|
@@@@@@@@@@@@@@@ ROADMAP STAGE 11 - RELEASE SELF SERVE / HOSTING
|
|
Fall of 2020 hopefully
|
|
links on website for sign up
|
|
marketing can begin in earnest
|
|
|
|
NOTE: HOSTING cases are all moved to priority 2 and most have "HOSTING" in the title tags
|
|
|
|
todo: Administration - Account
|
|
Down the road will need an Account page for seeing their account status in rental SAAS situation
|
|
Nothing to do here, it's an obvious one, just delete this later, it's to percolate in brain a bit
|
|
maybe under license
|