February 28, 2021
Hot Topics:

A Review of REALBasic

  • By Sonu Kapoor
  • Send Email »
  • More Articles »

Giving REALBasic a Trial Run

When working with a new development tool, one the first thing to do is to create a same very basic program. The program we generally create has a label, an entry box, and a button. In pulling up REALBasic, windows are presented all over the place. While we would have preferred to have these scattered windows docked to the main Windows, such a feature couldn't be found. After moving the windows to different areas (See Figure 4 below), we were ready to begin the creation of the simple application.

The dragging of controls from the toolbox to the untitled form was simple. Once over the form, guide lines helped me to position the control These guide lines seemed to work easier than the standard grid of dots that can be seen in other applications. The overall placement, sizing, and aligning of controls seemed to work smoothly. Repositioning and resizing all operated as you would expect in a WYSIWYG development tool.

As each control is selected, the standard GUI development action of setting properties can be done. For example, to change the size of the text, you can simply increased the TextSize value in the Properties window. To make the text bold, you would check a box in the properties Window. One item was a surprised. I expected to be able to get to the properties of the primary window being created by simply clicking on an area of the window where there were no controls. This, however, did nothing. Instead, you have to select the form from a different window in the IDE.

Figure 4 - The REALBasic IDE - Click here for larger image

Because adding the buttons was simple, we also dragged a Timer control onto the form along with another static text field. Using code, we tied the time to the text field. We set the static text field to initially display the number 0 as its text. We then added code to change this text field to count off seconds as the program runs. To add this code, simply double click on the timer control. This pulls up the Code Editor (See Figure 5).

RealBasic Screen Shot
Figure 1 - The REALBasic Code Editor

Using the Code Editor, you can enter your basic code. When you add code, you add it to a specific event. With REALBasic you are doing event-based programming, so don't expect to see a full listing of all your code. Rather, you can see code for any specified event.

In clicking on the Timer control, the code editor pulls up the Action event for the timer. As you can see in Figure 5, there are other events associated with each item on the form. Code can be added into any of these areas. For example, we added the following code to the button's Action event:

Text1.Text = Edit1.Text

This single line of code copies the text within the edit field over to the text that is displayed in the static text field. This command is similar to what you would see in other development tools as well. This one line of code along with the single line of code shown in Figure 2 are all the code in the application. Clicking the Debug menu's Run option causes my application to be compiled and executed. Figure 6 shows my executing application.

RealBasic Screen Shot
Figure 6 - The running test application.

Not bad for two lines of code. A few additional seconds of clicking and we added color to the text and included an icon on the application. This resulted in the application that is included here:

Download the Goofy program - 554 kb.

Who's Using REALBasic?

The simple program showed that basic applications are easy to create in REALBasic, but are people building real applications? A number of applications have been created using REALBasic. Many of these are currently being marketed. For some example applications, you can check out the following URL:



During the review, there were a few issues that were not totally clear. Although it is very easy to create dialog based (like notepad) applications with REALBasic, it doesn't seem like you can easily create a doc/view applications (like Microsoft Word). It was also curious to note that the toolbar controls are shown in the control window; however, they are only available for Mac applications—not for Windows.

Another nice feature is that when you are working with events, you see only one event at a time. In other development tools, you often see all of the implemented events, which can confuse developers. Additionally, bolding in the Windows helps you to identify which events have been coded and which have not. A comment from one developer regarding the ability to only see one event at a time; "People who are not 'hard core' programmers will probably like only seeing one event's code at a time. People who are experienced programmers will want to see the code. I like the fact that a tool like Visual Basic will now let you see all of the code."

For Windows developers there are better choices; however, if you are looking to target the Mac than you should go for REALBasic. As one developer stated, "I would use Visual Basic or Visual Basic .NET rather than REALBasic, unless I wanted to gain the ability to do cross-platform work with the Mac. If I wanted to develop on the Mac, then I'd definitely consider this one of my first choices for a tool".


REALBasic is really a nice tool to develop applications using the BASIC programming language. This product is very, very easy to use. Applications can be easily ported from or to the Mac. All you need do is compile your project on a Mac or Windows system.

The developers of REALBasic has to tried to hide a lot of code from you in order to keep development simple. For event driven programming, this is a relatively easy tool to use.

While experienced Visual Basic developers may not think this is the best tool in the world. If you are targeting the Macintosh platform, then you will find this a great tool to consider and to use. Developers new to event-driven programming may also find value in this tool!

About REALBasic

Retail Price

Supported OS

REALBasic 5.1
100$ Standard
399$ Professional

# # #

Page 2 of 2

This article was originally published on May 29, 2003

Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Thanks for your registration, follow us on our social networks to keep up-to-date