Which part of it do you not understand? There are a number of different elements in that code and if you already understand some aspects it would be a waste of time someone explaining them in detail! So in relatively little detail:
- Properties blocks store class properties that are available to any function in the class, similar to variable in function scope, but referred to with the object scope when used (I assume you have no problem with these)
- Methods blocks contain the functions that you can call. In this case all may be called from external to the class, whether that is the intention or not.
- The first function is the constructor which takes a variable sized array of inputs and creates the actual object instance. It does no validation of the inputs, but the expected inputs can be worked out easily enough from the code which assigns them to the relevant properties. The body of the constructor appears to try to load data from a .mat file and if it fails it loads from a .tir file instead (which I assume is always valid since it has no error handling on that part).
- The second function is the loadFromTir called in the constructor when loading from .mat fails. The body of that uses regular expressions to extract the required information to store in the class properties using dynamic strings for the property names.
- The save function should theoertically save the tire name and directory to a mat file, but since inputname appears to be undefined I assume that function will crash.
The following syntax:
tire.(propname)
allows you to use dynamic strings to assign to properties, but it does come with the assumption that ' propname ' is something that evaluates to one of the properties defined in your properties blocks. It is a method I have used to good effect on a few occasions, but can easily become the source of difficult to track down bugs due to its obfuscation of the property names it is actually assigning to. Basically this will load in and assign all those properties you omitted as "not important for understanding the code itself".
The actual code in the load function is mostly just dynamic string manipulation with regular expressions and other string manipulation functions that trim off extra bits of the string to get the correct property names in the strings to then assign as mentioned above.
If you need more understanding of the exact nature of the regexp and string manipulations I will let someone else add that as it is something I battle with occasionally and forget quickly afterwards!! Your tags suggest it is the OOP aspect you are struggling with though.
