Stuart’s MATLAB Videos

Watch and Learn

Release 2012B is live 6

Posted by Doug Hull,

Every six month we release a new version of MATLAB. This 2012B Release is kind of a big deal. There is a major change in the desktop that should increase the discoverability of features in MATLAB. Scott and I used to joke that the best release of MATLAB would be one where people simply found all the features we already had. This might just be that release! So take a look at the video and launch description page.

What do you think of this new release and how long have you been using MATLAB for reference.

6 CommentsOldest to Newest

Paulo Rigg replied on : 1 of 6
I was looking forward to distributing my custom GUIs using the new Package App feature. However, after trying it out, I realize that this is not the solution I am looking for. First, the current version of this feature does not allow me to change the icon of the app. As I have almost a dozen GUIs that I currently manage/update, I find this to be very annoying. It certainly prevents (or at least discourages one from adding one of my apps to the Quick Access Toolbar. This is not a show stopper for me in using this feature, but I do hope it is addressed in a future release. Second, and more importantly, this feature does not work with pcode'ed files and therefore once the app is installed on another user's machine, they can simply go to the Apps directory and have full access to my source code. I find this to be unacceptable. First,I believe it is important that an author have the option of keeping their work proprietary and second I want to be able to control the release of updates and do not want other users to fix bugs or add features on their own. This one is a show stopper and would have to be addressed in a future release before I would consider using this feature to deploy my apps.
doug replied on : 2 of 6
Paulo, Both of these suggestions are already known to development. Thank you for 'voting' them higher. We do watch these and try to move where the users, like you, want. Doug
Paulo Rigg replied on : 3 of 6
Doug, Thank you for letting me know this. I really do think this will be the ultimate way for me to distribute my programs to other users. It will make updates so much easier.
Scott Hirsch replied on : 4 of 6
Paulo - Apps can use pfiles, with some limitations: * The main file must be .m, not .p * Any files which are called only from .p files need to be added manually. I think both of these restrictions are in place because any automated dependency analysis of pfiles would violate the inherent obfuscation of these files. If I could apply the dependency analysis from the app packaging dialog to your pfile, I could get some additional insight into your code. For what it's worth, I've found ways to create apps which use pcode: * Create a thin wrapper launching function which is not pcoded. If this does nothing more than launch the app, the code visibility is not giving away any useful information. * Manually include all of the necessary files in the app packaging dialog I hope this helps. Good luck using this new feature, and please let us know if you identify additional capabilities you need.
Paulo Rigg replied on : 5 of 6
Scott, Thank you so much for your response. This is great news as I always write a wrapper for my programs that only contain the data structure and initialization of the parameters used throughout the program before launching the main gui from a .p file. Adding the .p files manually is a small price to pay to retain version control and I can always run the analysis on my original folder containing the .m files to make sure I do not miss including any .p files. I will give it a try.