This commit is contained in:
@@ -1,6 +1,3 @@
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - BETA "MAKE IT HAPPEN" All in on porting over all the real objects from v7
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
“Accept the things to which fate binds you, and love the people with whom fate brings you together,but do so with all your heart.”
|
||||
― Marcus Aurelius, Meditations
|
||||
"Make it happen"
|
||||
@@ -10,18 +7,14 @@
|
||||
|
||||
|
||||
|
||||
2021-12-10 STATS
|
||||
198,588 lines of code in all projects (code only not comments)
|
||||
Languages: Vue, C#, SQL, Javascript, JSON, markdown, XML, YAML, HTML, Batch, CSS
|
||||
Platforms: Windows, Linux, iOS
|
||||
FIRST BACK END SOURCE CODE COMMIT JUNE 28 2018 (3 years 6 months ago to jan 4th 2022)
|
||||
FIRST CLIENT SOURCE CODE COMMIT JAN 3rd 2019
|
||||
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - BETA "MAKE IT HAPPEN" All in on porting over all the real objects from v7
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
|
||||
# OUTSTANDING MAJOR AREAS TO BETA
|
||||
|
||||
# OUTSTANDING #B4BETA
|
||||
|
||||
|
||||
|
||||
@@ -29,15 +22,24 @@ FIRST CLIENT SOURCE CODE COMMIT JAN 3rd 2019
|
||||
|
||||
todo: test with licensed key to ensure evaluate is gone and everything works logging in as each user to regular home page
|
||||
|
||||
- License agreement change from beta to regular
|
||||
- Docs completed filling in, many empty pages still
|
||||
critical path items:
|
||||
- docs completed
|
||||
- QBI
|
||||
- QBOI (or server to login and path for them to do it on their server however that works so we can exit that biz)
|
||||
- import inventory and parts for future new sales will be critical
|
||||
ultimately being able to import directly from other apps export formats or online api keys would be ideal
|
||||
- License agreement change from beta to regular
|
||||
- Docs completed filling in, many empty pages still
|
||||
- business stuff like rockfish, licensing new site, new forums (update docs links when new forum), direct purchase
|
||||
|
||||
- New website for v8?
|
||||
- New forums for v8?
|
||||
|
||||
TODO: //MIGRATE_OUTSTANDING comment tag
|
||||
search for this comment tag as it will contain items that could not be done until other items were migrated first
|
||||
The tag will contain the description for each
|
||||
|
||||
|
||||
- Beta testing completed
|
||||
this is going to be huge becuase users will find a million bugs and issues with how things work and it will be a big clusterfuck for a while so plan for time and patience
|
||||
this is going to be huge because users will find a million bugs and issues with how things work and it will be a big clusterfuck for a while so plan for time and patience
|
||||
- Here switch from BETA to RC designation, let it soak for a bit before full release
|
||||
- onboarding process for v7 users guide to migration and also including licensing and etc which requires figuring out pricing and shit
|
||||
trial / seeder system
|
||||
@@ -50,21 +52,13 @@ trial / seeder system
|
||||
or something along those lines, ideas fuzzy at the moment
|
||||
maybe it's what is there plus additional Task based ones
|
||||
maybe the UI drives it because we have specific ideas for that
|
||||
dashboard widgets
|
||||
Not the highest priority for BETA but there shoudl be at least a couple so that feature can be tested also it shoudl at least replicate v7 stuff
|
||||
Just enough an no more, this could be endless, come up with a top 5 or something and limit it to that
|
||||
(this is also a very juicy v.next feature thing too)
|
||||
Note that it *must* at minimum recreate the v7 dashboard stuff (but nicer and graphical)
|
||||
personal upcoming events like maybe an "next 5 open work orders I'm scheduled on"
|
||||
or a widget that is upcoming work orders that are a specific status (maybe, just speculating here)
|
||||
Late night high email to myself about dashboard widgets:
|
||||
Dashboard segregate by levels of detail. Adobe people want overview quick some more detailed like Google maps timeline insights can't drill out to year no big overview.
|
||||
In app lists are ultimate detail need coarser grained widgets option just big picture stuff.
|
||||
|
||||
- Plugin / addon replacements implemented and fully tested
|
||||
qbi - 4alarm can't migrate until this is done
|
||||
qboi
|
||||
(if pt, well after release if ever)
|
||||
??? others??
|
||||
|
||||
- Regression tests completed and ready to use *before* release so we can add issues to it as they come up and test reliably
|
||||
- Rockfish licensing finished up
|
||||
lots to do there but enough for trial and sales for now in existing is enough
|
||||
@@ -89,13 +83,18 @@ dashboard widgets
|
||||
also accepting crypto?? (then fuck shareit in that case we don't need a middle man)
|
||||
Export restrictions??
|
||||
Since it's all open source now, are there still export restrictions??
|
||||
canad ones maybe that apply to us?
|
||||
canada ones maybe that apply to us?
|
||||
Legacy area for v7 on release and new area for raven
|
||||
forum for support squared away
|
||||
|
||||
|
||||
|
||||
|
||||
todo: ARCHIVE ALL DEPENDENCIES
|
||||
Get all code for all 3rd party libs used for front and back of AyaNova 8
|
||||
Need to store that in an archive somewhere just in case
|
||||
Needs to be done with each release so can go back to that if necessary
|
||||
Going to be big, maybe archived to all storage drives locally and burned to a dvd?
|
||||
If check into the repo it will be an issue probably but you never know
|
||||
|
||||
|
||||
|
||||
@@ -194,6 +193,8 @@ todo:3 todo: check out this SPA memory leak detector, it *does* have a login abi
|
||||
|
||||
|
||||
todo: 1 should a superuser really have a dashboard?
|
||||
todo: 2 adm-import lists a lot of objects that are work order item children etc, I think people mainly want invenotry (which isn't there), customers, ho maybe, whatever is the biggest lists
|
||||
so remove unimportable types, implement most desired import types
|
||||
|
||||
todo: 2 or 3 category team view color based on user color?
|
||||
check category schedule control docs or implement in my slot override
|
||||
@@ -201,13 +202,10 @@ todo: 2 or 3 category team view color based on user color?
|
||||
todo: 2 create workorder, quote, pm from customer record??
|
||||
was that a v7 feature? make it so? v.next?
|
||||
|
||||
todo:2 need to track fetched keys vs used keys so can tell if fetched a key that I don't need or stopped using due to code change
|
||||
|
||||
todo:3 profiler page has columns: Request Start Response Start Dom Complete which are all empty, somethjing new added that needs to be disabled maybe??
|
||||
|
||||
|
||||
todo:2 profiler page has columns: Request Start Response Start Dom Complete which are all empty, somethjing new added that needs to be disabled maybe??
|
||||
|
||||
todo: 2 adm-import lists a lot of objects that are work order item children etc, I think people mainly want invenotry (which isn't there), customers, ho maybe, whatever is the biggest lists
|
||||
so remove unimportable types, implement most desired import types
|
||||
............................
|
||||
|
||||
|
||||
@@ -400,6 +398,8 @@ console.log(parseFloat(localeParseFloat("1,100.9", "nl"))); // Dutch locale: rev
|
||||
|_____/|______|_| \_\ \/ |______|_| \_\
|
||||
|
||||
|
||||
todo: 2 Should the database integrity check run as a regular job?
|
||||
because a person could fuck up the db while the server is running and the server wouldn't notice until it tried to access a fucked up table
|
||||
|
||||
todo: 2 trial eval server on digital ocean, need way to generate unique login creds and data for people who are trialing based on request to try it on
|
||||
a d.o. server online. Basically ease it from our end to make it simple and maybe automatic as possible but also have it work with trial login accounts, so maybe a way to
|
||||
@@ -492,8 +492,6 @@ todo:2 errors are inconsistent some use "error" some use "code" to mean the same
|
||||
some things are producing {message:"blah",target:"blah",error:"blah"}
|
||||
controller apierror
|
||||
and validation errors are : {message:"blah", target:"blah", code:"blah"}
|
||||
todo: 2 Should the database integrity check run as a regular job?
|
||||
because a person could fuck up the db while the server is running and the server wouldn't notice until it tried to access a fucked up table
|
||||
|
||||
|
||||
|
||||
@@ -528,24 +526,9 @@ todo:2 Changes to allow in place updates of server without erasing data:
|
||||
Stock locales can just be completely replaced at any time, custom ones need a fixup,
|
||||
Custom locales should include where they came from (which language) so can more easily add new keys
|
||||
Schema updates in place not require full delete
|
||||
todo:2 figure out method to determine all translation keys actually used and remove unused ones entirely as they will show in the Translation ui and don't want to confuse people
|
||||
Note: can do a search in Code editor at client for ay.t( and it will show all the translation keys fetched in code for the most part other than grid columns
|
||||
can click in results and copy all to text which could then be processed to find all unique values??
|
||||
Or, just exercise the whole app and all lists and then can pull from the local cache in the browser!!!
|
||||
|
||||
|
||||
|
||||
todo:3 NOTIFICATION after the fact (PROBABLY JUST DOCUMENT THIS IS HOW IT WORKS)
|
||||
what happens when a user subscribes to a notification after an object was created
|
||||
for example if a unit has a contract and they subscribe to contract expiring they won't get notified about units unless they are edited and saved
|
||||
*after* the user subscribed
|
||||
What did v7 do?
|
||||
How to handle this??
|
||||
Ideally it would work with existing objects and not require them all to be edited or is that an issue, can it be good enough that it works going forward?
|
||||
Most subscriptions won't matter as they are direct immediate and one off but the timed and aged ones are definitely an issue.
|
||||
It might have to run through those and subscribe in the user, maybe a static op on a *Biz object that you call and say "subscribe this user to all subs" and it iterates
|
||||
the biz objects one by one and sets as appropriate??
|
||||
|
||||
todo:2 GetWorkorderSerial/name from leaf nodes
|
||||
traverse up the tree and fetch the serial number
|
||||
once coded fixup in purchaseorderbiz::getasync MIGRATE_OUTSTANDING bit
|
||||
@@ -559,14 +542,6 @@ todo:2 tag search in picklist, does it support more than one tag? I forget
|
||||
todo:2 unit meter reading event?
|
||||
|
||||
|
||||
TODO:2 //MIGRATE_OUTSTANDING comment tag
|
||||
search for this comment tag as it will contain items that could not be done until other items were migrated first
|
||||
The tag will contain the description for each
|
||||
|
||||
todo:2 many biz objects are not using new PUT methodology
|
||||
Might be because new methodology assumes complete PUT object as a entire replacement not a partial update
|
||||
some of these objects (User) do partial updates so....
|
||||
might be that they don't need it but for consistency should check into it
|
||||
|
||||
|
||||
|
||||
@@ -684,28 +659,14 @@ todo: PRICING
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 9 - RELEASE
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
|
||||
todo: ARCHIVE ALL DEPENDENCIES
|
||||
Get all code for all 3rd party libs used for front and back of AyaNova 8
|
||||
Need to store that in an archive somewhere just in case
|
||||
Needs to be done with each release so can go back to that if necessary
|
||||
Going to be big, maybe archived to all storage drives locally and burned to a dvd?
|
||||
If check into the repo it will be an issue probably but you never know
|
||||
|
||||
|
||||
TODO: CSP Policy that should be enabled at server?
|
||||
I had to add per this: https://docs.telerik.com/kendo-ui/troubleshoot/content-security-policy#content-security-policy
|
||||
to my csp because I kept getting errors in client end debug console mentioning csp issues
|
||||
this seemed to come after I updated the client build process to do a legacy and modern build but I'm not 100% sure about that
|
||||
|
||||
TODO: Docker HUB
|
||||
if we can put AyaNova on Docker hub then many hosting providers have 1 click methods to instantiate it so that's a viable easy onroad for potential customers
|
||||
e.g. digital ocean "app platform" https://www.digitalocean.com/products/app-platform/
|
||||
also here separately https://marketplace.digitalocean.com/
|
||||
|
||||
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
|
||||
|
||||
|
||||
DONATE
|
||||
@@ -714,10 +675,7 @@ Send a tip / buy a coffee link to the graphic designer who made the rabbit logo
|
||||
coffee button top right
|
||||
if I use it in release I should at least send them the small amount they get tipped
|
||||
|
||||
Send a tip / donate to the favicon generator guy
|
||||
https://realfavicongenerator.net/
|
||||
I broke it at one point by bringing down the site while it was checking ... oops.
|
||||
Used it several times and should donate
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -733,7 +691,7 @@ https://www.youtube.com/watch?v=zZVoo5AbANI
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 11 - RELEASE SELF SERVE / HOSTING
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
Fall of 2021 hopefully
|
||||
|
||||
links on website for sign up
|
||||
marketing can begin in earnest
|
||||
|
||||
@@ -769,6 +727,21 @@ It's all done in Photoshop. Just take screenshots, then transform, rotate, disto
|
||||
reply
|
||||
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 12 - v.next release
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
|
||||
going to need ongoing maint can't let it get weedy like before:
|
||||
|
||||
- New vuetify and vue versions start work early on porting to that
|
||||
- get on radar for .net v.next and see what's what and coming
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
tradingviewpw
|
||||
upupandaway1
|
||||
|
||||
@@ -785,6 +758,18 @@ redbone come and get your love
|
||||
|
||||
|
||||
|
||||
2021-12-10 STATS
|
||||
198,588 lines of code in all projects (code only not comments)
|
||||
Languages: Vue, C#, SQL, Javascript, JSON, markdown, XML, YAML, HTML, Batch, CSS
|
||||
Platforms: Windows, Linux, iOS
|
||||
FIRST BACK END SOURCE CODE COMMIT JUNE 28 2018 (3 years 6 months ago to jan 4th 2022)
|
||||
FIRST CLIENT SOURCE CODE COMMIT JAN 3rd 2019
|
||||
|
||||
2022-03-11 stats 208,875 TOTAL LOC
|
||||
Just counting code lines and only in front and back end not migrate or any testing, installers etc
|
||||
server: Total : 666 files, 96641 codes, 21272 comments, 22982 blanks, all 140895 lines
|
||||
client: Total : 295 files, 112234 codes, 6586 comments, 5547 blanks, all 124367 lines
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user