UI Interop Intermediate Objects
First, a quick note regarding the ongoing security incident: the screenshot to the left shows the most recent data from the host. As this site is currently hosted by a third-party, and has been from the beginning, I haven't really needed to do too much in terms of security as their team handles any major concerns. However I've been using these incidents as opportunities to learn and improve future plans.
The large screenshot above from MOOVPAD's GitHub shows the roadmap updated for the work being done over the past few days on the calendar control and the relevant UI Interop objects. Important template approaches are being setup in these objects. Perhaps the most important of these are the relevant "coordinates" for UI and UI Interop objects. Not just positional points on the UI, but also things like date co-ordinates, making the process of linking any date-dependent operations easier and more efficient.
Ideally, I would simply share the code for these objects to make things a bit clearer. But since the work encompasses MOOVPAD Web App features and processes not yet disclosed, I can't upload code screenshots yet. What I can say is that for both app/API security reasons, as well as operational efficiency improvements, I'll also be building intermediate carrier objects to bring data back from the API calls, which are then disposed.
Even I see how confusing that is rn 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.