A Document In Tabs
Introducing the tabbed document interface
Issue: 9.3 (March/April 2011)
Author: JC Cruz
Article Description: No description available.
Article Length (in bytes): 22,124
Starting Page Number: 44
RBD Number: 9309
9309project.zip Updated: Wednesday, March 2, 2011 at 1:46 PM
Related Web Link(s):
place download URL here
Known Limitations: None
Excerpt of article text...
We return again to face the challenge of designing a document-oriented application. This time, we take a look at the tabbed document interface, made popular by Safari and now a standard fixture of many web browsers. We will study three REALbasic classes with which to create said interface. Later, we will build a basic text editor that makes use of a tabbed interface.
A Pile of Documents
Now some users need to work with multiple data sets at the same time. Often, these sets are of the same type, and thus can be treated in the same way. On the other hand, each set stands as a separate entity. Changes and actions made by a user on one set do not affect the other sets.
Software products that provide this service are said to have a document-oriented design (Figure 1). Each data set is a document, often loaded from an external file. The set that gets the user's immediate attention is the active document. Those that do not are considered inactive. A product feature may affect only the active document, or it may affect all visible documents.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.