MetaEdit+ 5.1 Workbench Evaluation Linux

Before installing MetaEdit+

Description:

MetaEdit+ is a modeling tool for any and every modeling language - including your own! It includes prebuilt support for UML, BSP etc., code generation (C++, Java, Delphi, Corba, Smalltalk, SQL etc.) and documentation generation (HTML, RTF etc.).

Customize for your own powerful code and documentation generation, integrated with your existing development environment.

URL: http://www.metacase.com/
Contact Information: info@metacase.com

License Terms:

This product is licensed for evaluation use only. All other use, copying or distribution is forbidden. See LICENSE for more details. 

Upgrade Path to Full Version:

Contact MetaCase for details.

Installation Requirements:

  • kernel 2.4 or newer
  • libraries (always 32-bit, even on 64-bit Linux)
    libc.so.6 (glibc 2.2 or newer)
    libz.so.1
    libX11.so.6 (X Windows X11R6)
    libXft.so.2 (Xft)
    libcairo.so.2 (Cairo graphics library - optional but recommended)
    NB installing the packages for Xft and Cairo should be enough: it installs the others by dependencies.
  • web browser and PDF reader (for manuals)
  • bash (for manual and executing external commands)

Installing MetaEdit+

Installation Per System:

Make sure the Xft and Cairo libraries are installed - this also gets the other necessary 32-bit libraries, if you are on a 64-bit Linux. (If your Linux doesn't use apt-get, adjust accordingly - if it is 32-bit you may well have the libraries anyway, but if it is 64-bit see below.)

sudo apt-get install libxft2:i386 libcairo2:i386

Create a directory for MetaEdit+ Evaluation 5.1 binaries (for example, /usr/local/mep51eval) and untar the downloaded file into this directory (the sample below assumes that the downloaded file is in the user's home directory's Downloads directory). Installing binaries requires system administrator privileges, so you have to log in as root or use sudo commands as in our example:

cd /usr/local
sudo mkdir mep51eval
cd mep51eval
sudo tar -xzvf ~/Downloads/MetaEdit+EVAL-5.1*.tar.gz

Installation Per User:

Add the MetaEdit+ binary directory to your path by adding the command below to a startup script such as ~/.bashrc

export PATH=$PATH:/usr/local/mep51eval

Start a new shell to make the new path active. Move to your home directory and create a new directory to host your repositories and other user-specific files (here called 'metaedit'):

bash
cd ~
mkdir metaedit

Change to the newly created directory and execute the MetaEdit+ setup script:

cd metaedit
mesetup

The setup will create the following:

  • demo directory with a copy of the default repository
  • reports directory for generator output
  • metaedit.ini file with options
  • patches soft link to the patches directory in the MetaEdit+ binary directory

If you need to add additional repositories, simply copy them into this directory and they will be available next time you start MetaEdit+.


After installing MetaEdit+

Usage Instructions:

To start MetaEdit+, change to your MetaEdit+ working directory under your home directory and execute the MetaEdit+ start-up script:

cd ~/metaedit
metaedit

You can also create a desktop icon or menu item to start MetaEdit+. Make sure that it changes to your repository directory before starting MetaEdit+, e.g. by using the following as the command to run:

bash -c "cd ~/metaedit; /usr/local/mep51eval/metaedit"

When MetaEdit+ has started, open Help | Contents and go to the Evaluation Tutorial, which includes information about logging in.

Uninstallation Instructions:

To uninstall MetaEdit+, simply delete the its binary directory and the 'metaedit' directory in your home directory. Remember that your work is stored in the database directories: copy them before uninstalling if you want to save them.


Note for System Administrators:

If you do not have Firefox or another supported browser installed in the path expected by MetaEdit+, you will want to edit the metahelp script file. This is called by MetaEdit+ with an HTML file name (possibly with a # bookmark reference appended), to open its online help files.

MetaEdit+ propagates a set of files and directories for each user, locating them in a directory in the user's home directory. The default setup includes a demo repository, a directory for the generator output and a few support data files like artbase.roo and metaedit.ini. If more files need to be distributed to users during the user specific setup, follow these guidelines:

  1. A repository can be added for initial user setup by creating a .tar.gz archive of it and placing this archive into the 'dbs' directory within the MetaEdit+ binary directory (e.g. /usr/local/mep51eval/dbs). The setup will, by default, uncompress and extract all .tar.gz archives found from this location into user's 'metaedit' directory.
  2. Other files can be placed in the 'user_data' directory in the MetaEdit+ binary directory (e.g. /usr/local/mep51eval/user_data). These will be copied to the user's metaedit directory during the setup.

Known Problems

If starting MetaEdit+ on 64-bit Linux gives no output, or an error:
    bash: <visual>: No such file or directory
install 32-bit libraries from your package manager or command line:
   Ubuntu 12.04     sudo apt-get install ia32-libs
   Ubuntu 13.10     sudo apt-get install libxft2:i386 libcairo2:i386
   openSUSE 12.2  sudo zypper install libX11-6-32bit libXft2-32bit libCairo2-32bit
for other distros and more info, please see this forum post:
http://www.metacase.com/forums/forum_posts.asp?TID=649

When printing, you will be asked for the name of the printer to send the printed PostScript file to. The file will be printed with:
    lpr -P<printername> <PSfilename>
so the printer name you give should be for a PostScript printer, or the CUPS PostScript-capable queue for a non-PostScript printer.

Unicode characters are supported on the X clipboard/selection when pasting into MetaEdit+. When copying from MetaEdit+, ISO-8859-1 characters are supported, and other characters are written to the X clipboard by escaping them in the standard X format for unsupported characters. These escaped characters look like \u2aff, and cannot be pasted directly, but can be easily transformed into the real characters: e.g. paste in 3rd field and press Convert here:
http://unicode.online-toolz.com/tools/text-unicode-entities-convertor.php