Installing Service Release 1

Service Release 1 includes improvements to every area of MetaEdit+: the program itself, the modeling languages and reports included, and the HTML help files. In a clean 3.0 SR1 installation, these are of course immediately ready for use. For upgrading a base 3.0 installation to 3.0 SR1, some care must be taken, especially if you have made your own modifications to the modeling languages in the database, or changed or added reports. If you have made no such changes, you can follow the basic instructions; otherwise, you should read the detailed instructions.

Basic Instructions: if you have changed no modeling languages or reports

When downloading the files that make up this Service Release, if your screen fills with rubbish you should select 'Save Link As...' or similar from the link's pop-up menu, rather than just clicking the link.

Program update

Download the image patch: me990920.pat
Please note that this image patch also updates those reports stored in the Graph metatype, i.e. in the image. If you have changed any of these reports, or made other reports that rely on them, you should see the list of report changes below.

File this patch into your image in the normal way, remembering that if you save the image with a different name, you should change your shortcut for starting MetaEdit+ to use the new image name.

Download the Word Template: MetaEdit+.dot (assuming you have Microsoft Word)
Simply place this file in the MetaEdit+ directory.

Database update

Download the zipped demo database: demo30r.zip (if you want it)
Download the zipped production ('db') database: db30r.zip

The new databases contain the following changes:

Removed many custom property dialogs (now automatically generated)
Redesigned remaining custom property dialogs so fields scale when the dialog is resized
Improved reports for documentation and code generation
Removed Parameter type from UML project, and replaced it with new Parameter type in mcc project

If you are taking one of the new databases into use 'as is', you face no problems. If you want to apply these updates to an existing database, you must take a little time and care over it. By applying the UML update

Install the new 'db' database

Unzip the new 'db' database into a new 'dbsr1' directory in your MetaEdit+ directory
Start MetaEdit+, but do not login yet
Press the little down arrow button in the Startup Launcher, then the Roots Browser button
In the Roots Browser pop-up menu, choose 'Add DB', and fill in 'dbsr1' for the name and the path to the new database, and press OK
If you are on a non-Windows platform, choose 'Edit manager.ab' and edit the areas' path type letters to be the appropriate ones for your platform (see the manual for details)
Choose 'Save' from the pop-up menu, and close the Roots Browser

Export the updated types to a patch file

Log in to the new dbsr1 database (user name and password both 'user')
Open all projects, and choose mcc as default
From the Main Launcher, select Metamodel | Type Manager
Select the methods you want to update (probably all of them, or else just Project Model) in the list on the left
Press the '->' button between the lists
Choose 'Save Selected Types' from the pop-up menu of the list on the right, and give an appropriate file name
Logout and exit

Backup your existing database
Import the updated types to your existing database

Start MetaEdit+, and login to your existing database, opening all projects
From the Main Launcher, select Repository | Options to open an Options Tool
On the Repository page, press File in Patches
Select the name of the patch file you saved the new types to, and choose 'file in' from the pop-up menu
When prompted for the project for new types, choose mcc
Commit

Documentation update

Download the zipped HTML manuals: htmlguidefor30d.zip
Empty the existing manuals directory, and unzip the htmlguidefor30d.zip into it.

Detailed instructions

If you have changed any existing generic reports in the Graph metatype, or reused any from there as subreports from your own reports, you should be aware that filing in patch me990920.pat will add, change and delete some reports in the Graph metatype, possibly affecting your own reports. Similarly, if you have added or changed reports in Project Model, and save the Project Model types from an SR1 database and apply them to your existing database, your changes will be overwritten. In either of the above cases, you should thus check the report changes in SR1 before applying it, and integrate your own changes with them.

To use the new documentation reports requires three things:

New and updated generic reports in Graph meta-type

Make the generated document use MetaEdit+.dot for its styles etc.
Stored in the image
Updated by filing in me990920.pat to the image

New and updated reports in Project Model type

Improve the layout of the report output
Stored in the db and demo MetaEdit+ dbs, in project mcc.
Updated by logging into the new db, making a type patch including at least Project Model, and filing it in to your existing db.

Word template MetaEdit+.dot

Contains AutoOpen macro which creates a single .DOC file from the .RTF file and .PCT files generated by the report
Just a Word template file
Simply place the file in the MetaEdit+ start-up directory

In addition, there are some reports in a base 3.0 image and database that are no longer needed by our documentation reports. These will be removed by steps 1 and 2 above.

Report changes in me990920.pat

me990920.pat adds and changes several reports. These are mostly connected with the documentation reports, but also include the Java code generation for attributes and operations.

New:: Export graph to Word; _RTF documentation cover page; Export graph to HTML; _imagemap_href
Updated:: _RTF table of contents; _Dictionary in RTF; _Relationships in RTF; _Links in RTF; _Object properties in RTF; _Dictionary in HTML; _Java attribute; _Java operation
Deleted:: Graph documentation in RTF; _RTF documentation header; _RTF documentation footer; _RTF document definitions; _Heading1 style for RTF reports; _Heading2 style for RTF reports; _Heading3 style for RTF reports; _Hyperlink style for RTF reports; Graph documentation in HTML