hi @stu01509 ,
Looking better, for the deliverables:
- item 1 makes sense
- item 2 would separate out the jquery and focus more on “Remove legacy javascript components and packages” since jquery-ui may be gone already, but never fear, there is a spot left in the OpenEMR codebase where there are still legacy js packages are being used; check out Modules->Manage Modules to see what I mean.
- item 3 makes sense
- item 4 makes sense
- item 5 is where would add something like Develop pathway for migrating away from Jquery (this is because would be way overly ambitious to do this to entire codebase, however, deriving a solution and then incorporating it into a small portion of the codebase would be feasible)
I would incorporate migrating/removal of inline styling (part of item 3 likely). I’d rec trying that in a couple scripts also to get an idea of what that will entail for the entire codebase.
Since this is basically a code walk through, the timeline makes sense where focusing on one script first (to design the process), then followed by a set of scripts (to further optimize the process), then followed by rolling it out on the codebase.
Will be happy to look at the next revision (prob would do after have a better idea of what the extent of removing inline styling will be; ie. try to do a couple).