Windows Chicago Build 58
Every time I look it seems like someone has found an older build of Windows 95. This is Chicago build 58 which has recently turned up and is earlier and even more primitive than build 73.
I have said it before but I will say it again, Chicago is unique as it was really the only time in Windows history that Microsoft seems to have put significant effort and design research in to the Windows user interface. With the exception of Chicago (and perhaps any pre-1.01 version that might exist) I am really not interested in Windows alpha / betas.
For the most part build 58 looks like build 73. These screen shots mainly show the difference between the two. Please see the build 73 screen shots for more detailed information.
What is not obvious from just looking at the screen shots is that this version of Windows is almost entirely 16 bit including the Cabinet Explorer desktop. There were many new 16-bit APIs added, as a result these 16 bit applications will not run on Windows 3.1.
The tracker program that appears minimized above is launched from the startup group and stores the users beta ID info.
The system tray buttons are mostly the same as the ones in build 73.
Also each file folder in this version has a "parent folder" icon that will open the parent folder when double clicked.
Removing these options made it slightly more difficult to open a parent folder although this can be still done with the tool bar (by default off in Windows 95) as well as with the backspace key.
"Chicago" is the code name used by Microsoft for early development version of what eventually became Windows 95. Build 73 was created in November 1993 as a "preliminary release" before beta testing began. Beta testing is a development stage where completed components are tested by designated users at special testing sites.
The Chicago Boot screen.
IF it starts up. Being such an early pre-beta release a lot of stuff doesn't work or isn't completed and it can be very temperamental.
Some of the terminology in this version of Windows is different.
The Windows Explorer is the "Chicago Cabinet Explorer"
The icons on the desktop are:
The Briefcase - An early Plus pack component
optionally included with this Chicago Build.
The first button has window and desktop functions. There is no "programs" item on this menu, and the "Task List" option launches the Task Manager.
The bottom of this menu displays a list of all windows that are currently open. This is the same as the task list that appears in the tray (taskbar). This is redundant but is probably meant for use when the tray is being displayed as a folder (see below).
Also notice the maximize, minimize, and close window controls work the same way as Windows 3.1. In addition, minimized programs do not minimize to the tray, but instead display as boxed icons just above the tray.
The familiar "Task List" on the tray had only just recently been implemented. Earlier versions of chicago only had the "Tray as folder" and looked like the above screen shot. In these versions, all task switching was done through the Task Manager which performed the functions of the modern Task Bar. This explains why the functionality of the Win 9x Task Manager was greatly enhanced from Windows 3.1 yet in Windows 95 it is rarely even used.
The way you create links (shortcuts) is different. To create a shortcut you right click on a file and click "Link" then right click on the place you want to create the shortcut and select "link here".
The New Folder option does not seem to work and other new items can not be created from this menu.
Interestingly the right click menus on the desktop include a "Task List" option that starts the task manager.
The Chicago Cabinet Explorer is the "big thing" in windows chicago and later versions of windows. It finally enables users to manage files similar to the way the Macintosh and Lisa were doing it back in 1983.
There are several names used inconsistently for "Explorer" in this version of Chicago. In some places it is "Chicago Cabinet Explorer", "Cabinet Explorer", "Chicago Explorer", just "Explorer", or "Windows Explorer". There seems to be no relation to the compressed "Cabinet" archive files used by Windows 95 and later. In fact this version of Chicago is not compressed in to installation files. Since it is probably not clear to some people it also has nothing at all to with "Internet Explorer", which is not present at all in Chicago or the original Windows 95.
In this version of Chicago there is no Explorer.exe, it is instead a file called Cab32.exe. The documentation references a 16-bit Cabinet.exe that preceded the 32 bit version.
The Desktop Properties does not yet include the tab for the color appearances. Also note the diamond radio buttons.
The TCP/IP support seems to be incomplete as it does not have DHCP or working DNS support and winsock seems to be broken or incomplete. It is enough to access remote file shares though.
Instead of "WordPad" chicago has "WritePad" which appears to be an early version of WordPad.
Microsoft Windows "Chicago" beta-1
Microsoft's Chicago Beta-1 operating system from around May 1994.
The Desktop: Neat, Clean, and Logical
After you boot into Chicago, you are presented with the new Chicago desktop (see Figure below). Itís neat and clean with only a few graphical objects on the screen. Itís like moving into a new office before you have the chance to really get it messy.
Figure 5. The Chicago Desktop
The simplicity of the desktop appeals to all usersí sense of cleanliness but also serves to focus the novice user on the essentials:
The Chicago Taskbar: Home Base
More than any other feature, the Taskbar exemplifies the order of magnitude improvement in ease of use and learnability of the Chicago UI. It is the anchor of the UI. Its mission is to make 95% of what a typical user wants to do with the operating system easily accessible at all times. An indicator of a great design is that it turns out to be much more than it was originally intended. The Taskbar started out specifically as a novice user program launcher and task switcher. However, its simplicity and power have turned out to be favorites of experienced windows users, and it has many more capabilities.
Figure 6. The Chicago Taskbar
The two key features of the Taskbar are the Start Button and Push-button task switching.
The Start Button: Up and Running in Seconds
Usability tests on Windows 3.1 show that it takes a brand new Windows user an average of nine minutes to open "Write". With Chicago, opening Wordpad takes a new user an average of three minutes. If only the users that launched Wordpad via the Start Button (rather than by other means) are counted the average time to launch drops below one minute! The main reason for this dramatic 3x-9x speed improvement is the Start Button. Without ever having to know about double clicking, complex hierarchies, or program manger groups, a beginning Chicago user can quickly launch a program and get to work.
Figure 7. The Chicago Start Button
However, the Start button is much more than a
super-efficient program launcher.
Task Switching Made Simple From the Taskbar
Novices need powerful features presented to them in a very simple and compelling way, otherwise these features will not be used. Research on active Windows users shows that only 27% of general Windows users frequently use more than one application at a time and only 20% frequently use ALT+TAB task switching. These powerful features of Windows 3.1 are simply not discoverable.
The objective of the Taskbar is to make switching among multiple applications as simple as changing channels on a television set. Every new window that is opened automatically gets a button on the Taskbar. To change tasks, all the user must do is go to the Taskbar and select the desired channel. No more minimized program icons, no more disappearing windows. No matter where the user is, he or she can see all of his or her active tasks simply by looking at the Taskbar, the Windows TV guide.
Task Buttons re-size automatically depending on the number of active tasks. Should the buttons get too small to be useful the user can custom configure the Taskbar. In fact, there are a host of Windows Taskbar configuration options that allow the user to configure it to fit his or her needs including:
Also, noteworthy is the animation when a task is minimized into the Taskbar or maximized from the Taskbar. It helps new users understand "where" a program goes when it is minimized.
An Easier Model for File Management and Browsing
File management and browsing in Windows 3.1 was not
intuitive. Fewer than 55% of general Windows users regularly use the File
Manager. For novice users the File Manger is especially confusing and
New Windows and Large Icons Work for those new to Windows
Designing a discoverable and comfortable model for browsing and file management for the novice user has been a priority for the UI design team because of the observed difficulties with Windows 3.1. Several significantly different designs have been tested and thrown out. In the course of this testing the design team made a few basic discoveries about file management and browsing:
The "My Computer" default browsing model is the result of
all of this design, testing, and learning. A folder or drive can be opened by
double clicking or selecting it and choosing File Open. The default browsing
model brings up a new window in large icon view. To many advanced users this
behavior seems cumbersome. Why not open in list view? Why create a new window,
it just clutters up my screen? Why not open to a dual pane view? Itís much
more efficient for me. Why not turn the Toolbar on by default? All of these
models and more were tested thoroughly and discarded (as the default
configuration) because they caused confusion and stress among novices. Novices
respond best when presented only with essential information and when they can
easily "get back" to where they just were.
Chicago has a very powerful dual-pane browsing application for Experienced users called the Explorer, which is likely how you, as an experienced user, will prefer to browse. The Explorer will be covered in "Power" below. Additionally, the File Manager can be run for backwards compatibility.
New Capabilities in the Default Browsing Model
New capabilities of the default browsing model should not be overlooked in this discussion of simplicity. Folders can be created within folders. Files and folders respond very logically to being dragged and dropped. Files and folders can be cut, copied, and pasted just like text and objects within applications. Views can be customized by the user and each window "remembers" how the user last configured it, so that the next time it opens it is in the userís favorite view. The best way to discover the capabilities of the default browsing model is to play with it yourself, or better yet, find a novice user and watch him use it.
Name Files in English with Long Filenames
By far, the number one most requested feature since Microsoft has been in the operating system business is long filenames. The usability win by eliminating the need to conform to the 8.3 naming convention is obvious and large. To ensure backwards compatibility with the universe of existing MS-DOS and Win16 applications, extensions have not been eliminated, just hidden from view by default.
Additionally, files can be renamed in place in Chicago by selecting the file, clicking on the filename, and typing a new name. The hidden file extension is not affected by renaming the file. Files can also be renamed from within the new Chicago common dialogs (including File Open and Save).
Network Neighborhood and Networking Accessibility
This section will discuss how the Chicago client makes browsing networks possible and easy, independent of the network provider (such as, Windows NT Advanced Server, Netware, or Chicago itself). For more details about Chicagoís networking capabilities, see the section called "Chicago Networking and Systems Management."
The Network Neighborhood icon, shown in the figure below, sits on the desktop and logically separates for the user the place to go to browse resources not on "My Computer". The user can easily browse the network via the Network Neighborhood just as if he or she were browsing his or her hard disk.
Figure 10. Network Neighborhood desktop icon in Chicago
New Help Engine: Accessible and Useful Online Information
Online help has been completely re-tooled in Chicago. It underwent extensive usability testing in the labs and the result is a significantly easier to use and learn help system. Additionally, customizing and developing Windows help files by ISVs and corporate customers has been made dramatically easier. A brief description of the major features of new Chicago Help follows.
Figure 11. Help Shortcut button
OLE 2 introduced document-centricity with in-place editing of objects. The application window changes and the document stays the same. This makes the software begin to work the way people work, rather than vice-versa.
Figure 12. New Word document template
The Chicago UI picks up on the concept of document-centricity in several subtle, but powerful ways including:
Wizards: Your Guide to Powerful Capabilities
Started in Microsoftís Applications Group, Wizards are a
proven tool that make it easy for all classes of user to take advantage of
powerful but complex functionality. A series of questions are posed to the user
in a friendly and straight-forward way.
Figure 13. New Device Installation Wizard Walks User Through Installing a Printer
Chicago uses Wizards throughout the system, including:
Experienced users glean many of the same benefits from the Start Button and the Chicago Taskbar as do beginners-quickly launch a new program, quickly task switch, etc. However, experienced users need more. They need a powerful way to browse and manage file hierarchies be they local or somewhere else. They need to be able to customize the UI to suit their needs and tastes. They need to be able to take shortcuts to get tasks done more quickly and efficiently. They need to be able to do more. The new Chicago UI enables the experienced user to do more, as you will see in the coming pages and during youíre own explorations.
The Explorer: Power Browsing and File Management
Figure 14. The Chicago Explorer
One Chicago developer describes the Chicago Explorer as the "File Manger on steroids". It is powerful, flexible, efficient and extensible. It also solves many fundamental problems with the Windows 3.1 File Manager, like having to have a new window for every drive. For many Chicago power users the Explorer will be the primary interface. The best way to understand the Explorer is to experience it firsthand, however, here is an overview of its major features:
Shortcuts are an abstract but extremely powerful tool for increasing efficiency and are especially useful in a networked environment. A user can create a shortcut to any object (such as file, program, network folder, Control Panel tool, disk drive, and so on) in the Chicago UI and place it anywhere else in the UI or in an application. When this shortcut is opened the object that the shortcut is "pointing" to is opened. For example, a shortcut to "My network folder" could be created and dropped on my desktop. When the shortcut is opened, it actually opens my network folder which is out on some network server somewhere. Shortcuts are represented just like regular icons, except that in the lower left corner there is a small "jump" arrow, as shown in Figure 15.
Figure 15. Chicago Shortcut Icon
A shortcut can be deleted without affecting the object to which it points. A shortcut can be created by selecting an object and choosing Create Shortcut from the File menu or from the right mouse click context menu. If shortcuts are created on an object that was created since Chicago was installed, then Chicago keeps track of renames. This means you can create a shortcut to \\Server\Share\Public Folder and put it on your desktop. Then if you or anyone else renames the network folder, the shortcut will still work regardless of the fact that the name of the folder it points to has changed. You can also rename shortcuts themselves.
Uses for shortcuts are virtually limitless, but some common powerful uses for shortcuts include:
Property sheets are an all-pervasive feature in Chicago. All objects in the UI carry context sensitive properties that can be accessed and customized by selecting File Properties or by right-clicking. Good, consistent, easily accessible properties sheets have been a favorite of power user testers to date. Properties will be illustrated through a series of "Try This" tips.
Try This-Rename Your Hard Drive in Disk Properties
Figure 16. Chicago drive properties
Right-clicking, like properties, is another all pervasive, context-sensitive feature of Chicago. (Right-clicking refers to clicking the secondary mouse button because most right-handed people set their mouse options to use the left button as primary and the right as secondary.) Usability tests have shown that in general, right-clicking is not a feature that novices discover or remember, therefore, the vast majority of functions performed on the right-click can also be performed by selecting the corresponding menu commands. However, right-clicking as a short cut for the most common actions to perform on an object has proven to be another very popular power user feature. The power of right-clicking is best illustrated through a series of "Try This" tips.
Control Panel: The Consolidated Control Center
The objective of the Control Panel special folder in Chicago is to consolidate into one location, all command, control, and configuration functions. A problem with Windows 3.1 was that these functions were difficult to find, use, and remember (such as, Windows Setup to change video resolution). The UI team has striven to create distinct and memorable visuals for all important functions and offer previews where appropriate. Individual Control Panel tool functionality will be covered in the section to which it pertains (such as, "Network" in the "Chicago networking and Systems Management" section of this guide).
Figure 18. Explorer larger icon view of the Control Panel
There is one Control Panel tool, however, that pertains to customization of the UI itself, "Display". Display gives the user total control over the configuration of the Chicago UI allowing for personalization. Its four tabs are:
Figure 19. Chicago Display Properties
Find Files or Folders: Easily Location
Figure 20. Chicago's Find Files or Folders
Figure 21. Search in Windows 3.1
A powerful new Find utility is built into Chicago. It goes far beyond the minimal functionality of the File Mangerís Search utility in Windows 3.1. Features include:
Printers Folder: Consolidated Printer Control
The Chicago Printers Folder offers one stop shopping for printer management and configuration. It replaces the troublesome Print Manger and Printers Control Panel Tool from Windows 3.1.
Figure 22. Chicago Printers Folder
Figure 23. Printer Configuration from Windows 3.1
Font Settings: More Powerful Font Management and Preview
Figure 24. Chicago Fonts Settings
Figure 30. Properties for a File, Showing New File Attributes
Figure 32. Virtual Memory Settings in Chicago are Simplified Over Windows 3.1
Figure 33. Hierarchy of Registry as Displayed by the Registry Editor
Figure 34. Local Reboot Dialog Box in
Figure 37. Property Sheet for
Configuring an MS-DOSĖBased Application
Figure 39. With TrueType Font Support,
Users Can Scale an MS-DOS Window
Figure 42. Select Device Dialog Box
for Supported Display Adapters
Figure 43. Properties for Display Dialog Box
Figure 44. Screen Saver Settings for Energy Saving Monitor Features
Figure 45. Properties for Mouse Dialog Box
Figure 71. Sample Modem Property Sheet
Figure 72. Dial Assistant Property Sheet for Configuring Location Information
The Info Center
As described earlier, the Chicago shell features a single namespace that represents all of the data accessible locally and on the network. Through the new user interface, new users are protected from the complexities of a large hierarchy of information by Chicago's simple folder metaphor. Advanced users can choose to make full use of this powerful namespace by using the Explorer tool to see the entire hierarchy at once. The Chicago namespace is initially divided into three fundamental "places":
Messaging and information services "plug in" to the Info
Center. It provides a common interface in Windows where users access all of the
services they use. Users can choose to view the Info Center resources as
regular folders (the default), or they may "explore" the Info Center. The
figure below shows the Info Center opened with the Explorer, in this case open
to the user's Inbox folder.
Figure 79. Chicago Desktop Showing Info Center
Within the Info Center, the user can:
Info Center Components
Chicagoís Info Center system is the part of the Windows operating system that allows Windows to handle all these different types of information. It consists of a number of components:
A Chicago user can install a combination of drivers so that their Info Center can be used for multiple email or workgroup systems at the same time. To make it easy to use different information services, Chicago allows users to set up profiles. A userís profile specifies which messaging and information services the user will have access to, along with preference information and settings. In the example below, the user has set up a profile that contains both CompuServe Mail as well as Microsoft Mail. This user will be able to send and receive on both systems simultaneously-while sharing a common inbox and address book. Profiles are stored in the Chicago Registry on a per-user basis.
Figure 81. Configuring a Profile with Multiple Services
A Quick Tour
To best understand the role the Info Center would play in a userís day-to-day access to electronic mail and online services, a sample scenario is presented as follows.
To read their email in Chicago, a user would first log onto Windows. With many of the MAPI drivers under no separate logon is required for the mail system-it has been unified with the "system" logon. For simple access to the userís common tasks, Chicago has a Start button. One of the items on the Start button is "View Inbox."
This immediately takes the user to the inbox (see Figure 79 above) where he or she can read any new mail received. Users can compose new messages or choose to reply to existing ones. There is also a "Compose New Message" item on the Start Menu. The Info Center includes an OLE 2.0-compatible rich text message editor that lets the user get the point across in an effective way using a combination of fonts, font styles, and font attributes.
Figure 82. Rich Text Message Editor
Note that this same message editor can be used with any of the back-end messaging systems that have MAPI drivers available. If the underlying messaging system doesnít support rich text, the message can be sent as plain text to maintain compatibility. Or, if the destination reader also uses the Info Center Viewer the rich text information can be automatically encapsulated and sent as a binary file.
The user can address this message to any user on any of the email systems to which he or she is connected. Additionally, the message may be sent as a Fax by choosing a recipient from their address book who has a Fax address, or simply entering [FAX:phone#] on the TO: line.
Messages received in the inbox can be saved for future reference, if the user so chooses. The user simply drags the messages into any of the other folders in the mailbox (message stores)-or the user can drag the message to any folder on their local or network hard drives. In the latter case, the message becomes a .MSG file-but maintains all of the messaging-specific fields such as Sender, Recipient, and so on.
Sets of folders in the Info Center are also called
Information Stores. Users can also drag items from the file system into
information store folders. Information Stores go beyond the basic MS-DOS file
system in many ways. They can be physically stored in local files, or represent
a database on a network server. One of the differences between the file system
and an information store is the set of fields -- called object properties --
that are stored along with each item. Object properties include not only
messaging-related properties like Sender, Recipients, Date Received, Subject,
and so on-but also custom properties including:
The data in a Personal Information Store is kept in a single file, making it easy for companies to distribute rich documents and messages in a standard format. Every Chicago user then has a built-in tool (Info Center Viewer) that can browse, search, and organize the information in rich ways. Personal Information Stores can be encrypted and password-protected for security. Besides the Personal Information Store, the MAPI architecture makes it possible to plug in many different types of servers and databases as information stores.
The Info Center - Summary
The Info Center architecture then, provides Chicago with a single toolset and user interface for accessing, exchanging, and organizing information-regardless of data type, including E-mail, faxes, documents, and others. Through MAPI, it provides an extremely open platform-making the Windows desktop the "place to live" regardless of the back-end services in use.
International Language Solution: Multilingual Content Support
Chicago resolves many problems related to international language issues by integrating multilingual content support in the core of the operating system. Chicago also offers national language support to software developers as a series of APIs that are part of the Win32 API set.
What is Multilingual Content?
Multilingual content support is the ability to display and edit text of various languages and scripts in a single document. Multilingual content support is a core feature in the Chicago product and will be supported in the next major release of Windows NT (code named "Cairo").
Multilingual content support in an application has two major benefits. The first is that users who need to deal with content in multiple languages and scripts and exchange these documents with users on other language systems can do so. This is an important feature within the European Union, for example, where Greek- and Latin-based languages must coexist in documents. The second benefit is that an application which supports multilingual content will support the native content of any market into which it is sold. A multilingual application is a great application for the world.
Switching Between Languages and Keyboards the Easy Way
Chicago allows the user to add support for multiple keyboard layouts to match different international conventions. In Control Panel, the Keyboard icon provides the ability to configure the system to support the preferred keyboard layouts as shown in Figure 92.
Figure 92. Keyboard Properties Dialog Showing International Layout Support
Under Windows 3.1, to change the keyboard layout a user would go to Control Panel each time he or she wanted to change to a different keyboard format. Chicago makes this even easier. Figure 93 shows a sample legacy word processing document that illustrates the ability to integrate text using the Arial font in different languages within the same document. The language identifier in the status area of the Taskbar allows the user to easily switch the system language between the available language options. A Chicago application that uses NLS APIs would incorporate the ability to switch the preferred language directly on the toolbar of the application.
Figure 93. Chicago Makes it Easy to Switch Between Different Languages to Create Multilingual Documents
Multilingual Extensions to the ChooseFont Dialog Box
The ChooseFont common dialog is now enhanced to include a list box showing the character set scripts supported by a particular font. This allows for proper representation of fonts for a given language.
Figure 94 shows an early representation of the new ChooseFont common dialog box, illustrating the integration of font script selection options. The scripts list shows the script names for each of the character sets covered by the font selected in the Font control. The preview window displays a font sample that is dependent on the script selected, as well as the other font attributes. The sample preview string is specific to the character set chosen by the user, showing what each of the different scripts look like.
Figure 94. Chicago Displays the Available Font Selections for a Given Font Script Chosen by the User
Internationally-aware applications can support multilingual font selection by using the ChooseFont common dialog box (thus allowing users to select fonts) and by recognizing the extensions to the ChooseFont data structures in Chicago. Even WindowsĖbased applications-which, though not originally designed for Chicago, still support formatted text, but not multilingual messages-may gain some basic level of support for multilingual content. If an application uses the ChooseFont common dialog box, it benefits from the enhancements, allowing users to select from the full range of character sets and fonts configured in the system. As long as the application saves the complete logical font data structure representation for fonts, an existing WindowsĖbased application can get by without being aware that the font change a user has made includes a possible change of character set. (Applications do generally save this data, at least when saving text in their native format. Fewer save this when writing to interchange formats such as RTF.)
Multilingual Support for Exchanging Information Via the ClipBoard
A good multilingual-aware application should can exchange multilingual content with other aware applications and can exchange appropriate flat text to others, within the limitations of the ASCII text formats. Chicago provides special support in the data exchange APIs to pass language information along with the rich text data.
OLE 2.0 Functionality
Users are getting and using more applications per PC than ever before. In 1992, InfoCorp reported the average number of applications purchased per desktop running the Windows operating system increased to more than 7 programs, up from an average of 3.4 programs for customers using the MS-DOS* operating system in 1986. People are not just acquiring more applications, they are using them together. Research shows that users cite the ability to move and share information among applications as the most important reason for using windows applications.
Users who learn one Windows application find it easy to learn a second or third. So, as users access several applications in the course of creating a compound document, theyíll feel comfortable with those applications.
The Solution for Application Integration
Object Linking and Embedding (OLE) 2.0 is a mechanism that allows applications to interoperate more effectively, thereby allowing users to work more productively. Users of OLE 2.0 applications create and manage compound documents. These are documents which seamlessly incorporate data, or objects, of different formats. Sound clips, spreadsheets, text, bitmaps are some examples of objects commonly found in compound documents. Each object is created and maintained by its server application. But through the use of OLE 2.0, the services of the different server applications are integrated. Users feel as if a single application, with all the functionality of each of the server applications, is being used. Users of OLE 2.0 enabled applications donít need to be concerned with managing and switching between the various server applications; they focus solely on the compound document and the task being performed OLE 2.0-based features.
Features of OLE 2.0
With OLE 2.0, Microsoft Chicago increases the degree of
application integration available to any applications which take advantage of
the services. This gives users tangible benefits, allowing them to share data
and functionality across applications, and to combine them as they please.
Because OLE 2.0 is based on an open industry-standard, users can extend their
applications with additional third-party products, further expanding their
choice and flexibility.
Drag-and-drop is a new and more intuitive way to move data between applications. The most widely used way to transfer data between applications has been to use the Clipboard. But this involves multiple steps; namely using the Copy operation, moving to the destination application, and using the Paste command. A more effective way to move information-drag-and-drop-already exists within applications and, with OLE 2.0, it now works between applications, too. The user simply selects an object in one application, drags it to its destination in another application and drops it into place. Objects also can be dragged over the desktop to system resource icons such as printers and mailboxes, making it faster and easier to send, print, or share files.
Visual editing makes revising a compound document faster, easier, and more intuitive. For example, a Microsoft Excel worksheet thatís contained within a Word document (see Figure 96 below), can be double-clicked by the user. The user then is able to interact with the Microsoft Excel worksheet right there, without switching to a different application or window.
The menus and toolbars necessary to interact with the Microsoft Excel spreadsheet temporarily replace the existing menus and controls of Word. Microsoft Excel, the application that is needed to edit or modify the spreadsheet, partially "takes over" the Word document window (see Figure 97 below). When the user wants to work on the word processing portion of the document, the focus returns to Word, and the original Word menus and controls are restored.
The advantage of visual editing is even greater for example, when users create compound Word documents including large numbers of objects created by different applications, such as Microsoft Excel worksheets and charts, PowerPoint graphics, sound and video clips, and so on. Instead of switching back and forth among different windows to update the objects, the user is presented with a single document window in Word, providing a single location for editing and other interactions with the data. Visual editing offers users a more "document-centric" approach, putting the primary focus on the creation and manipulation of information rather than on the operation of the environment and its applications.
Windows User Interface Style Guideline 4.0
As in previous version of Windows, one of the reasons why
applications are easy to learn is the fact that they look and act alike. With
Chicago, Microsoft has taken great steps to improve the basic common controls
that all applications can share. These controls have evolved based on user
feedback and extensive usability testing here at Microsoft. Applications that
use these controls provide the users with commonality and improved features-such
as being able to create new folders in the Save As dialog box-without having to
switch to the Explorer or File Manager.
Figure 98. Save As Common Dialog
In the new Printer Properties dialog you can see examples
of some of the new controls with make access to features even easier for users.
At the top of the dialog you can see tabs for "Paper," "Device Options,"
Graphics," and, in the case of the printer shown in Figure 99, "Postscript."
Clicking any tab presents the user with properties for that particular area.
Another new control available to all applications is the Spin Control next to
the number of Copies.
Figure 99. Sample Tabbed Dialog Box Property Sheet
The new Open Dialog allows the user to see long filenames, and navigate the entire PC, and connected network to look for files to open.
Figure 100. Open Common Dialog
The new Open dialog also uses Tree Lists to allow the user to navigate through the hierarchy of the hard disks attached to the computer and through the network to which the computer is connected.
Figure 101. Open Common Dialog Provides Easy Access to Network Resources
Figure 102 shows another new control that makes viewing
and accessing hierarchical information even easier. This is a tree list control
found in the property sheet for the Device Manager in the System section of
Control Panel. As users expand and collapse the tree, they can see information
relevant to their topic of choice.
Applications no longer have to include their own custom
slider controls. Figure 103 shows the new common slider control included in
Figure 103. Sample Slider Control
There are many new common controls, tool bar, status bar, column heading, tabs, slider, progress indicator, rich text control, list view, tree view... and much more. Great Chicago applications will use these new controls to make the users access consistent across applications and make the entire system much easier to use.
Long Filename Support
As you have seen by now, there is a much improved new shell for Chicago. But the shell itself is only part of what is really here for users. Now an application that takes advantage of this new shell support can offer their users long filenames and direct file viewing. Long filename support means that documents no longer have to be limited to eight characters for names. They now can have up to 255 characters. Instead of "23ISM_JB.doc", you can name a file "Status report July 23 regarding the ISM project for my boss Jim Bernstein"-a title that really tells you what the document is about. Applications that support the Viewer capabilities in Chicago provide users with a quick and easy way to view their documents directly from the shell without launching the application.
Figure 104. Chicago Applications Support Long Filenames
Copyright © 2002