Browse Prior Art Database

Optimizing Notebook Size to Reflect Dynamically Added Notebook Pages in a Distributed Environment

IP.com Disclosure Number: IPCOM000114342D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 2 page(s) / 89K

Publishing Venue

IBM

Related People

Cuthbertson, WL: AUTHOR [+3]

Abstract

Disclosed is a technique that enables the product to calculate at runtime the proper size for the notebook to reflect the sizes of any dialogs added at runtime by other applications.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Optimizing Notebook Size to Reflect Dynamically Added Notebook Pages
in a Distributed Environment

      Disclosed is a technique that enables the product to calculate
at runtime the proper size for the notebook to reflect the sizes of
any dialogs added at runtime by other applications.

      The notebook control, part of the OS/2* Presentation Manager*
(PM) control set, is a powerful metaphor that many applications use.
It presents multiple dialog windows as pages in a notebook; the user
tabs or pages forward and backward through the notebook in order to
interact with the dialogs.

      The initial sizing of a window containing a notebook is of
concern from a usability standpoint.  Though pages in a notebook are
scrollable if the dialog on the page is larger than the page itself,
most users prefer that the notebook be sized large enough that
scrolling is not required.

      For products that operate in a distributed environment and that
allow other applications to add pages to its notebooks, the proper
sizing of the notebook is unknown when the notebook is initially
created.  Because the size of the dialogs that can be added by other
applications is totally dependent on the dialogs themselves, and
because they can be added to the notebook (depending on aspects of
the current runtime environment), the product has to be able to
adjust the original notebook size to reflect the size of the added
pages when they are added.

      The optimal size for a notebook is one that displays the
largest pages without requiring scrolling, but is not any larger than
is absolutely necessary to display these pages.  This size may be
based on two different pages, since one page may be the tallest,
while another is the widest.

      After all other applications have had the chance to add their
unique pages to the notebook, the notebook size needs to be
recalculated.  The first step is to query the sizes of all of the
dialogs that make up the pages of the notebook.  This can be
ascertained from the dialogs themselves.

      The sizes of each of the dialogs is compared, and the tallest
height and widest width of any of the dialogs is noted.  This
combination of height and width is the size that the area in the
notebook where the page is displayed should be sized.

      The current size of the page area can be obtained from the
notebook itself.  The WinQueryWindowRect API returns the size of the
entire notebook cont...