Building New And Modifying
As the coding begins for the MOOVPAD Pro Desktop, I thought I'd share the approach and some of the progress with the structure and work so far. We've already seen that this MOOVPAD app will need it's own webAPI. It will also need it's own class library for the bulk of the processing code, and this will be similar in structure to the library used for the MOOVPAD general user apps (desktop, mobile and web).
For now, the larger image above shows the integration of both the class libraries. There will also be opportunities to take some controls developed for the general user version and implement them, with modifications, into the MOOVPAD Pro Desktop. Scheduling, for example, can perhaps reuse some of the same controls without too many changes.
But there's no denying that I'll be needing to put a lot more work into this version. So it's lucky it's not due for release until the end 🙂
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.