programatically exporting the code behind an .mlapp to an m file.

Appdesigner offers a way to export the underlying code out of the binary .mlapp to a .m file with a save as type dialog. This being the only way around storing in git for source control purposes. I want to be able to keep all these export for all the apps housed in a project in a seperate folder, to prevent clutter of the project. While I can maually hit the "export" menuitem , I then have to change the path and repeat indiviually.

Does anyone know if the method behind the menu item is exposed to the matalb command line so that a script could be used to semi automate?

chris

Answer 1

[Mario Malic]

Hey Chris,

If you set up your application as a project, and use MATLAB's Source Control to share your project to Git, you are able to inspect the differences within MATLAB, which probably is the correct way to do what you want to do.

Optional info below:

If you unzip the file, under 'matlab' folder, there's a file called 'document.xml' which contains the script you see in App Designer, however, you can only use it to see the changes, but you cannot reuse the file, as it is not yet known to us how to change data inside and have a working application.

[Steven Lord]

This documentation page includes instructions on how to configure your SCM to use tools provided by MathWorks to diff and merge our binary file formats.

[Christopher Ward]

Ahh I've just seen that as of R2020b appdesigner mlapps can be differenced and merged within Matlab without the need to export. This is great, problem resolved.

Answer 2

[Duijnhouwer]

You could add this to your MLAPP's startupFnc

writelines(evalc('type(mfilename(''fullpath'')+".mlapp")'),mfilename('fullpath')+".txt");

Each time you run the app, this will export the code as text for easy tracking with GIT.

[Xingwang Yong]

Nice!