MT Studio is a very versatile product and can be used in three different ways:

In its simplest form, MT Studio can be used to write and serve static content, e.g. HTML pages, just like any other http server. While using MT Studio solely to develop static websites is rather a case of using a sledgehammer to crack a nut, this dimension of the product may come in useful when you have need for both static and dynamic pages.

MT Studio's easy-to-master tagging language makes it an excellent environment for developing web or intranet sites that require data connectivity. SQL calls are embedded in pages. Server-side variables can be set to maintain the flow of conversation between client and server.

The tags, SQL and server-side variables are resolved when a page is called and the database is read or updated. This type of development is ideal when a simple HTML client interface is all that is needed or, perhaps, possible.

When creating purely Static or Dynamic HTML, MTDesigner and MTClient are not required.

MT Studio really excels when there is a need for data intensive applications that require a sophisticated client-side graphical user interface (GUI). Effectively, any forms-based application that needs to access a server-side database is a candidate for development in MT Studio.

The wide selection of components available in MTDesigner, including trees, tables, modal windows, internal frames, panels and split panes, permits you to create a GUI to rival or surpass those found in mainstream client-server environments.

Because the underlying protocol is TCP/IP, you can run your applications over the Internet or through your corporate intranet. For users to utilise the forms you create, they will need to run MTClient. Although MTClient is available as a browser plug-in or a client-side application - which can be initiated through Java WebStart, if desired - the most likely usage will be as a Java applet. Because this applet is deployed automatically from the server-side, no special action is needed to enable your users to run your applications. They simply submit an appropriate URL to invoke your applications. They can then minimise (but not close) their browser and they will have your forms-based application sitting on their desktop.