This viewer tool is a good idea.
Some suggestions:
1) named signals could be used as logging names automatically
2) some variables are created directly in MatlabWorkspace (better collect inside one struct or hide in the UserData of the SetupBlock)
3) Unfortunately, it does not work directly in 2012a (of course R2007b is mentioned above). (Simulink misses some 'Open
Fcn' to load the blockset on starting-up: An error occured while parsing "...\slblocks.m". Error Message: Reference to non-existent field 'OpenFcn'..)
The blocks itself works as proposed if the testmodel is created inside the folder 'gtk_ml_supp' (only a Warning of a depricated block parameter occurs).
Great because I've been looking for an example building and connecting simulink blocks.
But is this problem not solved since 2010a?
http://blogs.mathworks.com/seth/2011/12/05/initializing-buses-using-a-matlab-structure/
