I have a client who has expressly asked if the app could be built in modules (another developer said he’d do it this way). The idea being if there is a bug only part of the app needs playing with when updated. Is there any advantage gained, or is it even practical to execute in a webapp? Security issues?
Any thoughts appreciated. Cheers
I’m not sure what is being suggested here.
AppStudio already modularizes your code into Forms. In addition, you can use Code Modules to organize blocks of standalone or shared code. If you clearly define the purpose of each one, as well as the interfaces used to connect with other modules, you should achieve a good level of modularization.
Beyond that, there are frameworks such as React, which formally define modules as part of the framework. Since you’re not using React, it probably isn’t relevant to you.
(Here’s an artcl
Sorry, just saw this reply. I’m talking more in terms of finished project. Can parts of a program be separated. ie Can an “Invoicing” module be separated from an “Examination” module, with one front end program loading these other “programs/modules” if user chooses to access them. Potentially 5 separate projects in AS uploaded to 5 folders on my server. Updating the separate apps depending on needs.
Run a webapp in another webapp within an iframe or something? What I want to know is this an idea worth pursuing or just stupid?
You could be thinking of MVC - Model-view-controller methodology.
I do this in large projects. The form code handles the interaction on the screen. All interactions with the database are in separate modules (usually named with db*.js). The business logic routines are also in separate modules.
This makes it easier to share and swap out logic without having to mess with the input screens.
Thank you. That sounds right. That’s going to take a bit of change of thought to implement.
Are your db*.js files all loaded at startup or only loaded when needed?
They are all loaded at startup. JavaScript is actually very efficient at doing this.