Looking Toward 0.6.8 Soon

Early feedback has been full of small feature requests.  Some of these seem odd, like requests to make MMM into a general purpose resource editor or some sort of 24-bit color icon embedder.  Others are just off the wall, like asking that MMM support non-VB development tools (huh?).  Still others make a bit more sense, like requesting that MMM fully install as a development topol and add a "Package with MMM" shell verb for .VBP files.

Other programming tools already offer their own ways to generate isolated applications.  MMM is targeted at VB6 to help make up for Microsoft's failure to support the community.

Version 0.6.8 will probably be an even more minor update than 0.6.7 was.  The main difference will probably be delivering it as an MSI package for full installation, instead of as a self-extracting archive.  This should calm the noise about not knowing "where to put MMM" and "why doesn't MMM show in my Start Menu" and so on.

What I could really use is some feedback about the changes that went into 0.6.7 though.  In particular I'd like to know if the XML encoding changes have solved problems with components having Unicode characters in Descriptions and so on, and whether the new handling of interface versioning is helping those who don't manage component Binary Compatibility closely.

I just downloaded and ran your latest version, and was looking forward to trying it out, however when I read that all of the pieces of the project had to be in one folder that ruled out being a useful tool for me.

I love the idea and hope perhaps you can find a way to allow it to work with pieces of a project scattered in different folders.

In my senario, I have a folder for shared BAS modules that I use in several different programs, and to the same for Class modules if it is needed in other projects, and then my EXE files are kept in another folder. My vbp file is kept in a folder with the project name along with private source files (that are not being shared).

I am not positive, but I believe you can get all the paths you need, to find all of the parts in the project header... at least my modules are all pathed out and load up fine at startup.

I was also thinking that this would be an awesome addition to Visual Build Pro and would fit in perfect with creating builds. Here is their URL if you want to check it out; http://www.kinook.com/

I dont work for them, I just use the product, and this would be a very cool feature!

Anyway, if you can resolve the scattered project issue, I would be very keen on trying it out :)

Thanks,
Gary Bouchard
DDSI

Posted by Gary Bouchard on Wednesday, July 22, 2009 01:36 PM

MMM only needs to scan the .VBP file and locate the precompiled .EXE, it does not need to look at individual source module files. The *output* from MMM is in a single folder, which contains the .EXE and its dependencies and any supporting data files.

Thus you should not have any trouble using MMM on your projects. MMM's source tree itself has different modules in different folders.

Posted by BVOCS on Thursday, July 23, 2009 07:32 AM

Gary:

There won't be any MMM 0.6.8 as it turns out. The versioning scheme is changing, and the new version is called 0.7 now.

Why should you care? Version 0.7 has a change that should address the issue you raised here. I hope this helps!

Posted by BVOCS on Saturday, August 15, 2009 01:01 PM

Post a comment

  • Name:
  • E-Mail Address (optional):
  • URL (nofollow, optional):
  • Remember personal info
  • Comments (text only):