Smalltalk Studio Frequently Asked Questions

These are the questions most commonly asked about Smalltalk Studio (that we have an answer for)!

If you have questions, please contact us. Requests for support should be made by submitting a Technical Support Request form.

Horizontal Rule

 Contents

Horizontal Rule

Why did you develop Smalltalk Studio?

Simply put, to allow Smalltalk developers to work smarter and faster by making the Smalltalk development environment a better place!

The focus was on two main areas:

  1. Modernize and increase the functionality of the Smalltalk development environment
  2. Integrate software metrics into the development process.

Modernizing the development environment

For many years the Smalltalk development environment was way ahead of the tools available for others languages. Over the years, the development environments for other languages have improved while Smalltalk's browsers have remained much as they have always been. As a result, many languages now offer similar or better facilities, often presented in a more usable, less utilitarian manner.

We often find newcomers have as much trouble mastering the development environment as they do the Smalltalk language itself. The Smalltalk Studio environment is much easier to learn. It is modelled on the same design principles as the underlying operating system GUI, so if you know how to use the base system, you know how to use Smalltalk Studio. This allows newcomers to concentrate on learning the langauge, becoming productive more quickly.

Seasoned Smalltalkers learn to live with and work around many of the deficiencies inherent in the standard browsers. Smalltalk Studio removes these deficiencies, simplifies many tasks and adds a host of new functionality.

Both novice and seasoned Smalltalkers really do work smarter and faster with Smalltalk Studio.

Software Metrics

Software metrics measure the quality of your code in many different ways. Traditionally, metrics are measured after coding is "complete", during unit testing at best, during system testing at worst. The later the metrics are measured, the more expensive it is to fix problems.

There are more dependencies created the longer testing is delayed, and all of the dependents require retesting when problems are fixed. Problems are identified just as the schedules are getting really tight. What happens? Most often the easy, less important problems get fixed. The most critical ones are too expensive to fix and get left.

By fully integrating software metrics into the development cycle in a way that does not intrude on your normal working practises, Smalltalk Studio enables and encourages you to fix problems as they occur. Each time you update a method or declare a new class or variable, the relevant metrics are recalculated and displayed as part of the object's icon. Now you can see at a glance if there are problems and fix them immediately before there are any dependencies whatsoever. Instead of being onerous, metrics become a major tool to help you iteratively develop high quality code.

Horizontal Rule

Why do I need a third-party development environment when IBM Smalltalk has its own development environment already?

Smalltalk Studio provides far greater functionality than the standard development environment and is more intuitive. The bottom line is that it will help you produce better code more quickly.

See "Why did you develop Smalltalk Studio?".

Horizontal Rule

Does Smalltalk Studio replace the standard development environment?

No. The standard browsers are still available and accessed in the normal way. You can use Smalltalk Studio and the standard browsers concurrently if you wish.

Horizontal Rule

IBM Visual Age for Smalltalk already has a graphical interface, so why do I need Smalltalk Studio?

The graphical interface of IBM Visual Age for Smalltalk only handles the creation of applications from parts. New parts are written in Smalltalk. You can reap the rewards of using Smalltalk Studio to develop your new parts, just like any other Smalltalk programmer.

See "Why did you develop Smalltalk Studio?".

Horizontal Rule

What are the hardware requirements for Smalltalk Studio?

The hardware requirements for Smalltalk Studio are the same as for the corresponding IBM product; IBM VisualAge for Smalltalk or IBM VisualAge Smalltalk Enterprise.

Horizontal Rule

What are the software requirements for Smalltalk Studio?

There are currently editions of Smalltalk Studio for the Windows operating system family.

The operating system requirements are the same as the IBM VisualAge for Smalltalk / IBM VisualAge Smalltalk Enterprise requirements.

The table below lists the supported versions of IBM VisualAge for Smalltalk / IBM VisualAge Smalltalk Enterprise for the latest edition of Smalltalk Studio...

Smalltalk Studio Version 2.0
Supported Base Products
Windows
IBM VisualAge for Smalltalk for Windows, Version 4.x
IBM VisualAge Smalltalk Enterprise for Windows, Version 5.x

Horizontal Rule

Why can't I drop an object from a Smalltalk Studio folder on to the Desktop?

The underlying operating system and other applications do not understand Smalltalk objects!

IBM Visual Age for Smalltalk version 4.0 supports platform drag and drop, but for this to be useful to non-Smalltalk applications, the objects must be wrapped into a form the underlying operating system and other applications can deal with.

For Windows, OLE objects might be created.

Though nice to have, we see the provision of this level of functionality as the responsibility of the base Smalltalk product.

Horizontal Rule

 Go to Home page This page is © Copyright Synergy Systems Limited, 1998, 2001.
All rights reserved.