EP0760125B1 - System zur anpassung der erscheinung und des verhaltens graphischer benutzeroberflächen - Google Patents

System zur anpassung der erscheinung und des verhaltens graphischer benutzeroberflächen Download PDF

Info

Publication number
EP0760125B1
EP0760125B1 EP95920476A EP95920476A EP0760125B1 EP 0760125 B1 EP0760125 B1 EP 0760125B1 EP 95920476 A EP95920476 A EP 95920476A EP 95920476 A EP95920476 A EP 95920476A EP 0760125 B1 EP0760125 B1 EP 0760125B1
Authority
EP
European Patent Office
Prior art keywords
theme
appearance
pattern
interface
interface objects
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP95920476A
Other languages
English (en)
French (fr)
Other versions
EP0760125A1 (de
Inventor
Timothy J. Craycroft
Jeffrey R. Cobb
Robert G. Johnston, Jr.
Robert R. Ulrich
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Computer Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Computer Inc filed Critical Apple Computer Inc
Priority to EP01122896A priority Critical patent/EP1174792A3/de
Publication of EP0760125A1 publication Critical patent/EP0760125A1/de
Application granted granted Critical
Publication of EP0760125B1 publication Critical patent/EP0760125B1/de
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces

Definitions

  • the present invention relates generally to graphical user interfaces for computer systems. More particularly, the present invention relates to systems and methods for interfacing applications and operating systems which provide for flexible customization of graphical user interfaces.
  • GUI graphical user interface
  • GUI display is based on a visual metaphor which uses a monitor screen as a work surface called a "desktop” where documents are presented in relocatable regions termed “windows".
  • the user interacts with the computer by, for example, moving objects on the desktop, choosing commands from menus, and manipulating window controls, such as checkboxes and scroll bars.
  • An exemplary desktop screen is reproduced as Figure 1.
  • Windows are one example of desktop objects which can be virtually any size, shape, or color.
  • Some standard types of windows are commonly predefined for the interface including, for example, a document window and a dialog box.
  • a document window is illustrated in Figure 2A.
  • Each document window which conforms to this standard has a title bar with a title drawn in a system-defined font and color.
  • Active document windows can also have controls as illustrated in Figure 2A, for example, a close box, a zoom box, a size box, and scroll bars.
  • nonstandard window types can define their own nonstandard window types as desired, although each nonstandard window requires a relatively large block of memory. Further, even these nonstandard window types provide only limited flexibility and control over the appearance and behavior of desktop objects in that they are application-specific and do not present a consistent interface across all applications, i.e., if three different applications are running, each might present a different "look" on desktop. Once again, the user has no control over the appearance and/or behavior of these nonstandard window objects.
  • window format including the appearance, behavior and function of standard windows and window parts
  • these applications are written to take advantage of such knowledge.
  • Figure 3 suppose, for example that an application 10 desires to draw a rectangle in the color of the title bar (beige, in this example) in a window (not shown on the desktop).
  • the application assumes knowledge of the color of the title bar when using predefined standard window definitions 25 and, if this application uses window definitions created by the application itself, the application will have actual knowledge of colors defined by those windows. Accordingly, the application will simply send a command to the interface instructing that a beige rectangle be drawn in the window.
  • the window definition 25 includes all of the data necessary to define the window. Looking at the active window illustrated in Figure 1, data included in the window definition 25 for such an active window would include, for example, the size of the window, the relative location of the close box and zoom box in the upper lefthand and righthand corners, respectively, the number of parallel lines and their locations relative to the close box and the zoom box, and the upper boundary of the window and all of the other defining features of that particular window.
  • the application supplies the variable parameters such as the location of the window on the desktop interface and, perhaps, the colors and/or fonts to be used for the text and/or figures in the window.
  • the window definitions can include a large amount of data and, therefore, can require a large amount of memory for each definition.
  • Themes can be created which include sets of desktop objects that are designed in their visual appearance to project an overall impression to the area.
  • the user can switch between themes, even at runtime, to change this overall impression.
  • Windows can be characterized in a variety of ways.
  • a window can be characterized by the shape, size and color of the window as well as by the location, size, shape and color of each of its component parts, e.g., those parts identified in Figure 2A.
  • These attributes of a window and window parts are categorized herein as a window's appearance attributes.
  • the window and its parts also have associated therewith one or more functions which are invoked when a user provides an associated input, e.g., clicking on a close button or box causes the window to close. These are termed functional attributes.
  • a third category of attributes also exists for some windows and window parts. These windows and window parts exhibit a behavior when acted on by a user which is distinct from the underlying function of these objects, i.e., when a user clicks on a close button using a mouse, the button becomes shaded in such a way that it appears depressed prior to the window actually closing.
  • exemplary embodiments of the present invention provide users (the term users as applied throughout this document refers to both end users of applications, application developers and other individuals who use or invoke operating systems) with the capability to alter the appearance and behavior of object and object parts, but preferably not the underlying function thereof. It will be understood by those skilled in the art that the principles described herein are equally applicable to systems and methods in which the functional attributes can also be varied by users. However, standardization of system functionality provides certain advantages so that exemplary embodiments of the present invention separate functional manipulation from manipulation of the other attributes.
  • FIG. 4 An overview which summarizes how these types of customized user interfaces can be provided in a consistent and switchable manner begins with a discussion of Figure 4.
  • the application 38 interacts with the appearance management layer 40 through three paths: directly, through utilities 42 (e.g., Toolbox Managers), and through drawing procedures 46 which provide the fundamental instructions (e.g., defprocs) for drawing objects on the interface.
  • utilities 42 e.g., Toolbox Managers
  • drawing procedures 46 which provide the fundamental instructions (e.g., defprocs) for drawing objects on the interface.
  • drawing procedure refers to pieces of code which are responsible for drawing interface objects and which define the shape of those objects, e.g., window definitions.
  • Switchable pointers 44 and drawing procedures 46 provide the basic building blocks which allow the geometry of each interface object as well as the behavior of each object's controls to be manipulated in a consistent and replaceable fashion. By switching the pointers 44 to the drawing procedures 46, or by switching the data used by the procedures 46, the appearance and behavior of the interface can be readily changed.
  • a pattern table 48 is used to look up this information and serves to abstract the color and/or pattern of the object from its other attributes.
  • drawing primitives which allow "paint-by-number" interface drawing are sent by the client to the appearance management layer.
  • the application can simply command the appearance management layer 40 to draw an object using an index which identifies the pattern and/or color of that object, so that the visual geometry is abstracted from the colorspace and the application need not know which particular geometries and/or colors are currently being implemented.
  • the pattern table 48 acts as a pattern/color database and returns the relevant pattern information to the client. The client then instructs the graphic subsystem 56 to render the appropriate pattern.
  • the theme switching 50 and run time support 52 control interaction of the appearance management layer and the theme.
  • the terms “theme” and “themes” refer to coordinated designs of interface objects and object parts that create a distinct visual appearance on the display. These routines provide mechanisms for loading and unloading themes and obtaining theme attributes. Various routines are also provided to support animation and sounds and handling desktop patterns and screen saver modules in the interface as shown generally by block 54.
  • drawing procedures are designed for switching at run time to enable dynamic system appearance and behavior. While the procedure and mechanism for switching between themes is described in more detail below, this section focuses on exemplary ways in which these procedures are designed to provide a switchable routine environment.
  • the appearance management layer 40 is responsible for orchestrating various changes which allow switching of the user interface's appearance and behavior. Two exemplary ways in which the drawing procedures can be switched will now be described here.
  • all of the utilities which support switchable drawing procedures will be called to "disconnect" all of the drawing procedures for each of the interface objects supported by that particular utility. In essence, this amounts to sending a dispose message to the drawing procedure for each and every utility object element currently in existence. The utility then is called to swap pointers 44 to the drawing procedures. For example, if window drawing procedure A is being replaced by window drawing procedure B, the window drawing utility will be asked to replace all of its references to procedure A with references to procedure B. This process will occur for each drawing procedure that is switched out. Lastly, every drawing procedure for every utility interface element should be sent an initialize message and the display will be completely redrawn.
  • these drawing procedures can be data driven so as to allow each procedure to be able to support a wide variety of appearances and behaviors without modifying the code of the procedure itself.
  • themes can be switched without requiring that the drawing procedure code be switched.
  • Each theme provides its own data structures which are supplied to the parametric drawing procedure.
  • system-provided drawing procedures map directly from existing procedures to provide compatibility with existing systems.
  • each individual drawing procedure will correspond to a conventional procedure (e.g., WDEF0, WDEF1, CDEF0, CDEF1).
  • This mapping can be accomplished, for example, by the exemplary mapping procedure illustrated below in pseudocode form.
  • This exemplary procedure can handle loading both conventional drawing procedures as well as the new drawing procedures.
  • the first step is to determine the resource ID of the procedure being called. This will load either an old style procedure located in a resource chain or a stub resource from the system file.
  • Stub resources are modules which, when invoked, decode a conventional procedure's message and call the corresponding new drawing procedure based on the decoded message.
  • a utility creates a new interface object using a drawing procedure it will also load an appropriate stub resource and store its value in a procedure handle field of the object's data structure. Since the utilities can switch the drawing procedure that they call, the ability to dynamically change the set of drawing procedures which create the interface objects is now available.
  • the drawing procedures can be parametric in nature so that they need not be switched every time that a theme is changed. Instead, the data supplied to these procedures is changed with the theme.
  • a discussion of these exemplary embodiments begins with a description of the data used to drive these procedures.
  • the data structures which are used to drive the structural procedures according to this exemplary embodiment of the present invention can be categorized as interface geometry elements data and interface behavior elements data.
  • An object geometry is specified by a list of arbitrary geometry objects that are linked together with a simple rule based view system. Each of the geometry objects are arbitrary in size and shape and may repeat in either a horizontal or vertical direction. Drawing procedures such as window drawing procedures (e.g., WDEFs), and menu drawing procedures (e.g., MDEFs), can use these geometry resources to calculate and draw the structure region of an interface object, e.g., a window or a menu.
  • Opcodes Specify edges of glyphs in object by offsets.
  • Glyph List Points to data structure for each glyph.
  • Geometry Part List Combines glyphs with boundaries. Existence State Table All boundaries and geometry parts indicate when they exist in the object.
  • the resources that define this geometry model can be broken into four parts as seen in Table A, above.
  • Table A there are a list of operation codes which place horizontal and vertical boundaries that will be used to specify the edges of glyphs in the object.
  • Each boundary can be placed relative to a reference, which is either part of a parent shape (e.g., a rectangle that defines a window's, or other object's, workspace) or a previously defined boundary.
  • the offset can either be a constant or some other value recognized by the system, such as the height of a window's title.
  • a limit can be specified such that the new boundary will fall between the limit boundary and the reference boundary. Limit boundaries allow geometry elements to disappear when the parent shape becomes too small to support them.
  • a geometry resource can also contain a list of glyphs.
  • Each glyph can be derived from a pattern of pixels, a bitmapped image or an icon.
  • each glyph can also specify on which comer it is anchored to allow it to be drawn in the correct direction.
  • a window may be required to have a close box or button part but may also include many optional parts that are used to enhance the appearance of the window.
  • all boundaries and parts can specify in which states they exist. For example, a close box part and perhaps one or more of its boundaries might not exist in the inactive state of a window. This specification reduces the amount of computation and drawing that is done in any particular state.
  • Each interface element has a predefined set of states that may be used when traversing the geometry resources. Another use for this mechanism is to change the appearance of a part in a special state of the object. For example, to change the appearance of a window's bottom edge when the glyph is deactivated, two bottom edge parts can be defined that use different glyphs. One of these parts might exist only when the window is active, the other when the window is inactive.
  • FIG. 5 An exemplary table of glyphs appended as Figure 5 illustrate a set of glyphs which can be used to render a document window in an exemplary theme as shown in Figure 2B.
  • the horizontal and vertical boundaries are constructed so as to locate all of these glyphs around the content shape of the window to produce the desired look for this theme.
  • the second category of data structures used in the data driven structural procedure relate to interface objects' behaviors. Each behavior is associated with transitions between different states or values of controls in the interface and can be expressed by changes in visual or audio output that correspond to these transitions.
  • Data driven drawing procedures can use a common mechanism that implements state tables. These state tables contain bitmaps or glyphs for each state of the control represented thereby as well as information about transitions from one state to another. Each transition may contain one or more of, for example, an animation sequence, a sound or a routine to implement a custom transition, e.g., an algorithmic display or any other type of transitional effect.
  • state diagrams for each object and object part of the user interface, a template can be created that allows a theme designer to place customized glyphs for each state of the control and also to customize the transitions between states of the control as desired.
  • An exemplary state diagram is shown as Figure 6 which provides an example of the possible states and most common state transitions for a checkbox control of a window object.
  • this exemplary checkbox has nine possible states which can be displayed. These states include three highlighted states for each of the control's three values.
  • states Q1 In normal use, when a user clicks on an unchecked checkbox (state Q1), this action moves the control to its pressed state (state Q4). After the mouse is released, the control returns back to its original state (state Q1) and the application is notified of the button which has been pressed. The application then switches the value of the control to its new value, which might be checked (state Q2).
  • a matrix for these transitions can be provided. Note for example the exemplary matrix illustrated in Figure 7.
  • a theme designer can provide a visual and/or audio output such as an animation, sound, a custom transition procedure which can perform some type of algorithmic transition, e.g., a kaleidoscopic display or any combination thereof.
  • Custom drawing procedures can inherit from the system provided appearance using a form known as delegation or forwarding. Delegation involves passing control on to another object when inherited behavior is desired. To determine the particular object to which the drawing procedure should delegate in a dynamically changing interface, either the client can call in to the system or the system can track current implementations. According to exemplary embodiments, this burden can be placed on the system by providing an additional layer of redirection. As seen in Figure 8, the utility 61 calls the custom drawing procedure 63. The drawing procedure 63 inherits from the switcher 65 which delegates to the appropriate implementation 67 or 69. An example of this type of inheritance will now be described using menu drawing procedures.
  • a theme can provide a menu drawing procedure which controls drawing standard menus for that theme. While many applications have customized menu items, a theme may only change the appearance or behavior of a single item in the menu while letting the remaining menu items appear and behave as they do when the system default theme is in control.
  • the application can intercept the command to draw a menu item from the utility issuing the command. If the menu item to be drawn is an item whose appearance and/or behavior has been customized by the theme, then the theme's menu drawing procedure can be used to draw that item. Otherwise, the inherited code pointed to by the switcher object can be called to draw the item.
  • the theme's custom menu drawing procedure only overrides the system to draw that item, with any other items being drawn using the inherited code.
  • the themes used by the appearance management layer 40 should be able to operate on a variety of color data to draw the interface, e.g., a color pattern, a pattern defined on a pixel-by-pixel basis, bitmapped image or the like, etc.
  • the pattern tables provide a system and method for specifying this color data, so that the theme color set can be edited independently of the theme using resource-editing utilities.
  • the pattern tables provide this support by abstracting the notion of pen pattern and color, allowing an application or theme to draw interface pieces without being locked to a particular color set.
  • a mechanism including a pattern look-up table.
  • An index in a pattern look-up table references data for a color, a pattern defined on a pixel-by-pixel basis, bitmapped image or the other data, so that the client need not know anything about the datatype contained in the pattern look-up table entry.
  • the significance of this data independence is that a theme having solid-colored windows, for example, can be changed to instead draw the windows in a complex pattern, without changing the theme source code simply by editing the table entries.
  • pattern or “patterns”
  • it is intended to denote any type of graphic data that can be used in a pattern look-up table to draw in a graphics port. As such, this may be a solid color defined in terms of its red, green and blue (RGB) components, or a pattern defined on a pixel-by-pixel basis, e.g. a PixPat, or a new type of data.
  • RGB red, green and blue
  • a client 60 sends a command ThemeFillRect (kColorIndex) to the appearance management layer.
  • This command is one of a set of drawing primitives implemented by the appearance management layer 40.
  • it is a command to draw a rectangle that is filled with the pattern specified as kColorIndex.
  • the value of kColorIndex corresponds to a predetermined object or object part on the desktop. For example, index 3 might correspond to the window title color.
  • the kColorIndex parameter has a corresponding entry in the part index table. This entry maps into the theme pattern look-up table 62. As described previously, the entries in the theme pattern look-up table 62 can include any type of color or pattern data in any format. For the purposes of this example suppose that the entry in the part index table corresponding to the value of kColorIndex maps into a pattern called 'xpat' referring to a black and white criss-cross pattern. 'Xpat' has a corresponding entry in the pattern definition procedure table 64 where the procedure for drawing this black and white criss-cross pattern is located.
  • This table includes a procedure pointer which translates the commands defined by the 'xpat' record into commands which are recognized by the graphic subsystem 56 used by the system to draw the pattern onto the display. These commands are then sent to the graphic subsystem which displays the pattern at the appropriate point on the desktop interface.
  • the appearance management layer 40 does not command the graphic subsystem 56, but simply acts essentially as a pattern/color database.
  • a get theme pattern command is sent to the appearance management layer 40, instead of the drawing primitive in Figure 9.
  • the appearance management layer returns a pattern structure which can be rendered by the graphic subsystem in the currently implemented theme for the particular interface object or object part requested in the get theme pattern command, to the client which then sends its own command to the graphic subsystem to draw the appropriate pattern and/or color on the desktop interface.
  • This alternate exemplary embodiment also has the benefits described herein with respect to abstracting the pattern/color combination from the interface.
  • the color and/or pattern of desktop objects can be readily switched from one theme to another by changing the values in the part index table and/or the pattern look-up table 62.
  • This switching of patterns is totally transparent to the application.
  • new patterns can be added without any need to change the application itself.
  • the appearance management layer recognizes a set of drawing primitives which can be, for example, derived from those used by the system's graphic subsystem (for example, QuickDraw). These primitives can have the same calling sequence as their counterparts in the graphic subsystem, but use indices into the theme pattern table to specify the color and/or pattern details of the requested drawing command. Exemplary drawing primitives are illustrated below along with descriptions in italics.
  • the appearance management layer can also define a set of bevel, text and dialog grouping rectangle primitives which can be used by clients for drawing bevels and dialog group rectangles in a standard appearance.
  • the implementations of these routines can be overridden by the theme to generate special appearances. For this reason, the client should not draw bevels independent of the appearance management layer for user interface object parts, but should instead use the provided primitives. Exemplary primitives are shown and described below.
  • Pattern look-up tables are provided as part of the package which handles drawing requests, either with the aforedescribed drawing primitives or alone, which tables will now be described in somewhat more detail.
  • a pattern data structure holds the data necessary to draw a pattern. It can have, for example, the following structure:
  • the pattern data structure can be, for example, an eight-byte structure used to store pattern and/or color information. If the data required for the pattern is more than eight bytes long, it can be stored in a handle and the handle placed in the pattern data structure.
  • a pattern definition procedure, described below, is a component which is responsible for the loading and interpretation of a pattern data structure.
  • the pattern look-up table specifies the list of colors and patterns used by a theme.
  • a pattern look-up table contains a list of records, e.g., Pattern Spec record 'xpat' in Figure 9, each of which is typed and references a specialized procedure to load, unload and draw.
  • Pattern definition procedure a code module responsible for loading, unloading and interpreting a pattern look-up table entry's data, e.g., the pattern definition procedure 'xpat' of block 66 in Figure 9.
  • New pattern types may be defined by a theme for specific needs, such as algorithmic color and pattern generation, simply by adding new pattern definition procedures.
  • a pattern definition procedure can be defined, for example, as a code fragment module or a dynamically loaded library which exports a list of entrypoints as set forth below. The default behavior for unimplemented entrypoints is to return an error.
  • Pattern look-up tables may be created in memory by applications to allow them the benefits of a pattern look-up table within the application.
  • An exemplary application program interface (API) for creating pattern look-up tables is described below.
  • Themes can also define new pattern types to take advantage of special theme-specific behavior, such as algorithmically defined patterns.
  • the theme provides a resource defining the pattern type or registers a code fragment module or dynamically loaded library using, for example, the InstallPatternDefinition command described below.
  • the pattern definition procedure will be added to the internal type list of the system, and will be called directly to load, unload and draw patterns of the corresponding type.
  • This code can be stored as a code fragment module or dynamically loaded library, and remains loaded as long as there are pattern look-up table entries which reference its type. For this reason, pattern definitions can remain installed even after the theme which created the pattern is unloaded in case these definitions are used by other applications.
  • a pattern definition procedure When a pattern definition procedure is installed, it can be added to an internal pattern definition table. For speed, these pattern definition procedures can be referenced by index rather than type in the pattern look-up table.
  • the pattern definition table is scanned and the index of the definition for the pattern type is inserted into the record for the new pattern. As new types are added, they can be added at the end of the list.
  • pattern definition procedure An example of a pattern definition procedure is shown below, which procedure is used to get a pattern defined on a per pixel basis from the look-up table and command the graphic subsystem to draw same.
  • the appearance management layer also defines a range of common pattern indices that can be included in each theme's pattern look-up table so that these indices are available to all clients. These include the set of patterns used to generate bevels and groups, along with other useful patterns, for example, the current background of the menu bar. The current background of the menu bar index may be passed to one of the standard theme drawing routines to draw shapes in the menu bar color. Below, for illustration purposes, an exemplary set of such common pattern indices is defined.
  • a theme may define additional types which are used internally. These additional types can be indexed sequentially starting from whatever next highest index is available, e.g., 16384 in the example given above.
  • the command RGBColor specifies a red, blue or green color combination with which to draw an object or object part.
  • ColorPattern describes a two-color 8x8 pixel pattern with a fore and backcolor, each specified with an RGBColor.
  • An exemplary definition of a ColorPattern type is shown below:
  • a PixPat type specifies an arbitrary pattern defined on a per-pixel basis, wherein a designated area may be filled or drawn with the pattern contents by the graphics subsystem.
  • the PixPat (Pixel Pattern) data structure is defined by the graphics subsystem, and is used to contain this per-pixel pattern.
  • Themes provide a set of standard pattern look-up resources for use by the appearance management layer which are described below.
  • the pattern lookup table defines the set of colors and patterns used by the theme and is used to build the theme's pattern look-up table.
  • the part index table maps the set of standard theme pattern indices into the pattern look-up table.
  • exemplary embodiments of the present invention provide for pattern/color abstraction by returning information to the client rather than the appearance management layer commanding the graphic subsystem directly.
  • the client will ask the appearance management layer for a structure, e.g., a PixPat structure, corresponding to a specified index and will receive a handle that will allow the application to make the appropriate drawing call to the graphic subsystem 56.
  • a structure e.g., a PixPat structure
  • the appearance management layer returns a data structure to the client.
  • a pop-up, pull-down or drop-down menu 140 allows users to specify an overall appearance/behavior by selecting the theme to be installed.
  • Beneath the theme setting box 140 to the left is an options area 142 in which a user may select various options within each theme. For example, a user could specify a background color, a font and a highlight color.
  • a preview area 144 To the right of the options area 142, is a preview area 144 where exemplary interface elements of the theme currently selected in box 140 are shown so that a user can preview what the theme will look like before making a selection.
  • Exemplary interface elements can include, for example, a desktop pattern, a menu bar and menu, an active window, and a dialog box with radio buttons, a checkbox, push buttons, and selected text.
  • a user will be able to change the appearance of the desktop quickly and easily.
  • the appearance control panel can provide user selectibility over all of the objects which can be displayed on the user interface.
  • the appearance control panel could include a library of each type of interface object from which the user can select for inclusion in a user-defined theme. After selecting one of each the different types of interface objects, the user can be prompted for a theme name under which pointers to the appropriate drawing procedures and other information for realizing the selected objects can be stored.
  • an appearance object editor can be provided wherein a user can create his or her own interface objects using a library of parts provided by the object editor.
  • each of the glyphs illustrated in Figure 5 can have a multitude of variations from which a user can create his or her own document window (both active and inactive).
  • the new interface object can be stored in the library of interface objects from which user-defined themes can be created.
  • Theme attributes are a collection of theme properties that are both system-defined and theme-defined.
  • Each of the theme's properties can be queried and set by appearance management layer functions.
  • the following properties can be defined by the system:
  • a get theme property function can be called for example by: OSErr GetThemeProperty (OSType property, void *dataptr, Size dataSize) This function will return the requested property from the current theme. If the current theme does not include the requested property, typeNotFoundErr is returned.
  • Figure 12 illustrates interactions between, for example, a theme 70, the appearance management layer 40, and an application 38.
  • block 48 includes the pattern tables as discussed above, and block 54 contains the animation and sound utilities which supplement the runtime routines of block 52.
  • an icon is shown which diagrammatically illustrates an appearance control panel 69, e.g., the panel of Figure 10, which an end user can operate to switch themes.
  • a current theme's resource chain 72 is opened and managed by the theme switching 50 and runtime routines 52.
  • the resource chain 72 can include, for example, a theme attributes property list (e.g., behavior matrices as described above), theme preferences (e.g., a preferred background pattern, preferred system font, etc.), theme data resources (e.g., the pattern table which defines the set of patterns and colors used by the theme, pattern code procedures which allow definition of new pattern types, etc.) and override resources (e.g., icons for the theme which overrides system icons).
  • the theme resource chain can be maintained separately from the resources of the currently running application, and can be switched in and out in response to a demand by either an application or a user (appearance control panel).
  • the theme's resource chain 72 is setup whenever the appearance management layer 40 calls any of the theme's code.
  • the current theme is set by calling the appearance management layer's set theme function, for example, by the command: OSErr SetTheme (const FSSpec *themefile)
  • the set theme function uses an FSSpec parameter that identifies the theme file that should be loaded and activated by the appearance management layer. In normal operation, this function loads the requested theme file, switches to the new theme and then releases the old theme. The old theme is released after the new theme is completely loaded so that if the new theme could not be activated, the system can revert back to the original theme such that the user does not become stranded without an interface.
  • a new theme info record is created.
  • This data structure contains all of the global information that the appearance management layer uses to keep track of the state of the current theme and contains its own resource chain information, e.g., procedure pointer tables for the switcher, the theme property list, the theme pattern tables, etc.
  • the appearance management layer creates a new resource chain at block 102.
  • the new theme's resource file is then opened at 104 after which the theme's runtime code is loaded, at 106, and its open function is called.
  • the new theme can test the operating conditions of the system to determine if the load should continue or be aborted. If the load aborts, the theme may present an alert to the user as to why the theme could not be loaded. If the theme has its own preferences file, it can be opened by the theme at this time.
  • the theme's property list is loaded at block 108, for example, by calling a get resource function. This allows the property list to come from any preferences file that may have been opened in the previous step. If a property list is found, it is stored in the theme info record. Subsequently, at block 110, the theme's pattern look-up table is loaded. First, all pattern definition procedure resources are loaded. Then the standard pattern look-up table and part index table resources are loaded. The pattern look-up table is then built from the contents of these resources. A pointer table to be used by the switcher resources is then built as shown by block 112. This table is stored in the theme info record. Lastly, the new theme's initialize function is called at block 114. The new theme can allocate memory or load extra resources that it requires while being active.
  • Figure 14 illustrates steps that can be executed to switch from an old theme to a new theme.
  • a transition effect can be presented as block 116.
  • the screen may fade to black, a dialog can be presented, or the themes could gradually blend from one to the other, e.g., "morphing".
  • the old theme's resource chain is switched in as described by block 118. All of the drawing procedures are called with a deallocate message.
  • These messages 120 are sent to the appearance management layer's switcher definition procedures, which are currently routing messages to the old theme's implementations of the definition procedures. This allows any of the theme's definition functions to deallocate any global data that they may have been allocated.
  • the appearance management layer sets the new theme info record as the current theme's information record at 122. Once the new theme info record is set, all of the external calls into the appearance management layer will affect the new theme.
  • the new theme's resource chain is switched in at block 124. All of the drawing procedures are called with an initialize message. These messages are sent to the appearance management layer's switcher resources, which are currently routing messages to the new theme's implementations of the drawing procedures. This allows any of the theme's definition functions to allocate any global data that they may need.
  • the steps executed to release the old theme file are shown in Figure 15.
  • the old theme's deallocate function is called at 130.
  • the theme is responsible for disposing of any allocations that it may have made when it received its initialize message.
  • the old pointer table used by the switcher definition procedures is disposed of per block 132.
  • the old theme's pattern look-up table and property list are disposed of as denoted by blocks 134 and 136, respectively.
  • the files in the old theme's resource chain can then be closed and the resource chain disposed of prior to disposing of the old theme's theme info record (blocks 138 and 140).
  • the switch is aborted and the set theme function attempts to reverse all of the steps that have already successfully completed so that the system continues to generate an interface using the old theme.
  • the error that caused the switch to abort can be returned by this function.
  • an FSSpec parameter to the system file or NIL can be passed in the themefile parameter.
  • a get theme function can be called, for example by the command: OSErr GetTheme (FSSpec *currentThemeSpec)
  • An FSSpec parameter value referencing the currently active theme file will be returned in the currentThemeSpec parameter. If the current theme is the default system theme, an FSSpec referencing the system file will be returned. If an error occurs while attempting to locate the FSSpec of the current theme, an appropriate error code will be returned and the currentThemeSpec parameter will remain unchanged.
  • the current theme's resource file is not present in the currently running application's resource chain. This can be done to prevent resource identification conflicts between applications, the operating system and the current theme.
  • the appearance management layer maintains a separate resource chain that contains the current theme file and any other files that the current theme may have opened (such as a preferences file).
  • the appearance management layer executes code in the theme, the theme's resource chain is setup by the appearance management layer, which allows for normal GetResource calls to be used to get theme resources. If an application wishes to gain access to the current theme's resources, several functions can be provided.
  • a get theme resource function can be called, for example: Handle GetThemeResource (OSType restype, UIntl6 id) GetThemeResource has the same function as the GetResource function, except that this command gets the resource from the current theme's resource chain.
  • the low-level appearance management layer function GetThemeTopMapHandle may be used to get the top of the current theme's resource chain.
  • OSErr GetThemeTopMapHandle (Handle *themeMap)
  • the GetThemeTopMapHandle function returns the top map handle that contains the current theme file and any other opened theme files (such as a preferences file) and all of the system resource maps. Caution should be exercised when using the GetThemeTopMapHandle function to avoid leaving the theme's resource chain switched in when executing utility functions or after returning to other parts of an application's code. When the theme's resource chain is switched in, the application's resource chain is unavailable. Note also that when the theme changes, this map handle and associated resources will no longer be valid, so this value should not be cached.
  • a theme can implement three theme definition functions that the appearance management layer calls when a theme is being loaded or disposed of.
  • the theme's function can be called.
  • pascal OSErr ThemeFilePreflight void *themedata
  • the theme's test function is called before any resources are loaded by the appearance management layer. In this way, the theme has an opportunity to test the conditions of the operating system (such as memory or graphics capability). If the test function returns an error, the appearance management layer will close the theme file and not attempt to continue loading. If the test function returns no error, the appearance management layer continues to load the theme, as described above.
  • the themedata parameter returned by the exemplary test function shown above is used by the theme to allocate and store any global data that the theme wishes to keep for itself.
  • the themedata parameter points to NIL.
  • the test function (or any of the other theme definition functions) may change the value pointed to by themedata. This themedata value is persistent as long as the theme remains loaded.
  • the theme's initialize function When the appearance management layer is finished loading all of the theme's resources and loading each of the theme's standard definition procedures, the theme's initialize function is called, for example: pascal OSErr ThemeFileInitialize (void *themedata)
  • the theme's initialize function can be used to do any special processing after the appearance management layer has completely loaded the theme. It may allocate data structures, load additional resources, open preferences files, setup its theme property list, etc.
  • the themedata parameter points to a global storage location useful for storing a pointer to the themes global data. If the theme's initialize function returns an error, the appearance management layer will abort the switch to the theme. The appearance management layer will dispose of any allocations it has already made and close the theme file.
  • the theme's dispose function is called, for example: pascal OSErr ThemeFileDispose (void *themedata)
  • the dispose function should dispose of any allocations that were made with either the test or initialize functions.
  • the theme file then has an opportunity to store any resources in its preferences file and/or set its theme properties. After the theme returns from this function, the appearance management layer will deallocate all of the appearance management layer's storage for the theme and close the theme's file.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Claims (17)

  1. Graphische Benutzeroberfläche umfassend:
    einen ersten Satz an Oberflächenobjekten, deren individuelle Aussehen mit einem ersten gemeinsamen Thema verbunden sind;
    einen zweiten Satz an Oberflächenobjekten, von denen jeder in der Funktion eines verbundenen Oberflächenobjekts im ersten Satz entspricht, deren individuelle Aussehen aber mit einem zweiten üblichen Thema verbunden sind, das sich vom ersten Thema unterscheidet;
    Mittel (50) für ein selektives Wechseln zwischen dem ersten Thema und dem zweiten Thema, wobei die graphische Benutzeroberfläche unter Verwendung von einem aus dem ersten Satz und dem zweiten Satz Oberflächenobjekte anzeigt;
    dadurch gekennzeichnet, dass das Mittel zum selektiven Wechsel der Themen ferner umfasst:
    Mittel zum Ändern der Zeiger (44) aus einem ersten Satz an Zeichenverfahren (46, 63), die dem ersten Thema entsprechen, zu einem zweiten Satz an Zeichenverfahren (46, 63), die einem zweiten Thema entsprechen.
  2. Graphische Benutzeroberfläche gemäß Anspruch 1, wobei die individuellen Aussehen der Oberflächenobjekte durch Aussehenseigenschaften von Objektteilen bestimmt werden, die die Oberflächenobjekte umfassen.
  3. Graphische Benutzeroberfläche gemäß Anspruch 2, wobei die Aussehenseigenschaften Größe, Form, Farbe und Lage einschließen.
  4. Graphische Benutzeroberfläche gemäß Anspruch 2, wobei die Objektteile einschließen: Zoom-Boxen, Schließfelder, Gleiter, Kontrollkästchen, Abschrägungen, Trennzeichen, Gruppierungsfelder, Aufdeckungsdreiecke, Knöpfe und Bildlaufleisten.
  5. Graphische Benutzeroberfläche gemäß Anspruch 2, wobei zumindest einer der Objektteile, der eine der Oberflächenobjekte im ersten Satz umfasst, ein erstes Verhalten zeigt, das sich von einer Funktion unterscheidet, die zumindest einem der Objektteile zuzuschreiben ist.
  6. Graphische Benutzeroberfläche gemäß Anspruch 5, wobei zumindest einer der Objektteile ein Schließfeld ist, das erste Verhalten ist es, schattiert zu werden, und die Funktion das Schließen eines Fensterobjekts ist.
  7. Graphische Benutzeroberfläche gemäß Anspruch 5, wobei ein Objektteil im zweiten Satz von Oberflächenobjekten, der dem zumindest einen Objektteil entspricht und dessen Betätigung durch den Benutzer die Funktion ergibt, ein zweites Verhalten zeigt, das sich vom ersten Verhalten unterscheidet.
  8. Graphische Benutzeroberfläche gemäß Anspruch 1, die ferner einen Effektgenerator umfasst, der einen vorübergehenden Effekt erzeugt, wenn das erste Thema auf das zweite Thema umgeschalten wird.
  9. Graphische Benutzeroberfläche gemäß Anspruch 1, wobei das Mittel zur selektiven Änderung der Themen umfasst:
    eine Schalttafel, die es einem Benutzer ermöglicht, zwischen den Themen selektiv zu wechseln.
  10. Verfahren zur Bildung einer graphischen Oberfläche zwischen einem Benutzer und einem Computersystem, die Schritte umfassend:
    Anzeigen von Oberflächenobjekten unter Verwendung eines Aussehens für jedes, das mit einem ersten Thema verbunden ist;
    Ändern eines gewählten Themas vom ersten Thema zu einem zweiten Thema;
    Anzeigen der Oberflächenobjekte nach dem Änderungsschritt unter Verwendung eines Aussehens für jedes, das mit dem zweiten Thema verbunden ist; und
    dadurch gekennzeichnet, dass der Schritt der Änderung eines gewählten Themas ferner den Schritt umfasst:
    Ändern der Zeiger (44) aus einem ersten Satz an Zeichenverfahren (46, 63), die dem ersten Thema entsprechen, zu einem zweiten Satz an Zeichenverfahren (46, 63), die dem zweiten Thema entsprechen.
  11. Verfahren gemäß Anspruch 10, ferner die Schritte umfassend:
    Bestimmen des ersten Themas durch Wahl der Aussehenseigenschaften für Objektteile der Oberflächenobjekte, die einen ersten gemeinsamen Eindruck vermitteln; und
    Bestimmen des zweiten Themas durch Wahl von Aussehenseigenschaften für Objektteile des Oberflächenobjekts, die einen zweiten gemeinsamen Eindruck vermitteln.
  12. Verfahren gemäß Anspruch 11, ferner den Schritt umfassend: Bereitstellung der Objektteile zumindest eines von:
    einer Zoom-Box, einem Schließfeld, einem Gleiter,
    einem Kontrollkästchen, einer Abschrägung, einem Trennzeichen, einem Gruppierungsfeld, einem Aufdeckungsdreieck und einer Bildlaufleiste als Objektteile.
  13. Verfahren gemäß Anspruch 11, ferner umfassend die Schritte:
    Zeigen eines ersten Verhaltens und Erzeugen einer entstandenen Funktion, wenn ein Objektteil, das eines der Oberflächenobjekte ist, betätigt wird, während das der Oberflächenobjekte angezeigt wird, unter Verwendung des Aussehens, das mit dem ersten Thema verbunden ist; und
    Zeigen eines zweiten Verhaltens und Erzeugen der entstandenen Funktion, wenn der Objektteil des einen der Oberflächenobjekte betätigt wird, während das eine der Oberflächenobjekte angezeigt wird, unter der Verwendung des Aussehens, das mit dem zweiten Thema verbunden ist.
  14. Verfahren gemäß Anspruch 13, wobei der Schritt:
    Zeigen eines ersten Verhaltens und Erzeugen einer entstandenen Funktion den Schritt umfasst: Schattieren eines Schließfeldes und Schließen eines Fensterobjekts.
  15. Verfahren gemäß Anspruch 14, wobei der Schritt Zeigen eines zweiten Verhaltens und Erzeugen der entstandenen Funktion den Schritt umfasst: Zeichnen von Linien, die vom Schließfeld ausgehen und Schließen des Fensterobjekts.
  16. Verfahren gemäß Anspruch 10, wobei der Schritt der Änderung eines gewählten Themas ferner die Schritte umfasst:
    Anzeigen einer Schalttafel für die Eingabe der Themenwahlen.
  17. Verfahren gemäß Anspruch 10, ferner umfassend den Schritt:
    Erzeugen (116) eines vorübergehenden Effekts vor der Anzeige der Oberflächenobjekte unter Verwendung eines Aussehens, das mit dem zweiten Thema verbunden ist.
EP95920476A 1994-05-16 1995-05-16 System zur anpassung der erscheinung und des verhaltens graphischer benutzeroberflächen Expired - Lifetime EP0760125B1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP01122896A EP1174792A3 (de) 1994-05-16 1995-05-16 Eine graphische Benutzerschnittstelle und Verfahren

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US24332794A 1994-05-16 1994-05-16
US243327 1994-05-16
PCT/US1995/006175 WO1995031775A1 (en) 1994-05-16 1995-05-16 A system and method for customizing appearance and behavior of graphical user interfaces

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP01122896A Division EP1174792A3 (de) 1994-05-16 1995-05-16 Eine graphische Benutzerschnittstelle und Verfahren

Publications (2)

Publication Number Publication Date
EP0760125A1 EP0760125A1 (de) 1997-03-05
EP0760125B1 true EP0760125B1 (de) 2002-04-03

Family

ID=22918310

Family Applications (2)

Application Number Title Priority Date Filing Date
EP95920476A Expired - Lifetime EP0760125B1 (de) 1994-05-16 1995-05-16 System zur anpassung der erscheinung und des verhaltens graphischer benutzeroberflächen
EP01122896A Withdrawn EP1174792A3 (de) 1994-05-16 1995-05-16 Eine graphische Benutzerschnittstelle und Verfahren

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP01122896A Withdrawn EP1174792A3 (de) 1994-05-16 1995-05-16 Eine graphische Benutzerschnittstelle und Verfahren

Country Status (6)

Country Link
US (2) US5959624A (de)
EP (2) EP0760125B1 (de)
JP (1) JPH10500512A (de)
AU (1) AU2591995A (de)
DE (1) DE69526218T2 (de)
WO (1) WO1995031775A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102193784A (zh) * 2010-03-09 2011-09-21 新奥特（北京）视频技术有限公司 一种用户自定义界面的方法及装置

Families Citing this family (147)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9286294B2 (en) 1992-12-09 2016-03-15 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator content suggestion engine
US7168084B1 (en) 1992-12-09 2007-01-23 Sedna Patent Services, Llc Method and apparatus for targeting virtual objects
US6307574B1 (en) * 1995-05-08 2001-10-23 Apple Computer, Inc. Graphical user interface with hierarchical structure for customizable menus and control objects
US6014137A (en) 1996-02-27 2000-01-11 Multimedia Adventures Electronic kiosk authoring system
US20040019610A1 (en) * 1996-02-27 2004-01-29 Burns Kevin S. Portal information delivery system for personal computers and SOHO computer systems
US6300949B1 (en) * 1996-09-10 2001-10-09 Minolta Co., Ltd. Information processor
US5995102A (en) * 1997-06-25 1999-11-30 Comet Systems, Inc. Server system and method for modifying a cursor image
US6188399B1 (en) * 1998-05-08 2001-02-13 Apple Computer, Inc. Multiple theme engine graphical user interface architecture
US6754905B2 (en) 1998-07-23 2004-06-22 Diva Systems Corporation Data structure and methods for providing an interactive program guide
US9924234B2 (en) 1998-07-23 2018-03-20 Comcast Ip Holdings I, Llc Data structure and methods for providing an interactive program
KR100655248B1 (ko) 1998-07-23 2006-12-08 세드나 페이턴트 서비시즈, 엘엘씨 대화형 사용자 인터페이스
US6389591B1 (en) * 1998-09-03 2002-05-14 Microsoft Corporation Method and apparatus for determining preferred controls for an upgradable operating system
US6262726B1 (en) * 1998-10-09 2001-07-17 Dell U.S.A., L.P. Factory installing desktop components for an active desktop
WO2000028518A2 (en) * 1998-11-09 2000-05-18 Broadcom Corporation Graphics display system
GB9824482D0 (en) * 1998-11-09 1999-01-06 Nokia Mobile Phones Ltd Portable controller
AU1668200A (en) * 1998-12-09 2000-06-26 Business Management Software Limited Employee self service customization system and method
US6577350B1 (en) * 1998-12-21 2003-06-10 Sony Corporation Method and apparatus for displaying an electronic program guide
US6904610B1 (en) 1999-04-15 2005-06-07 Sedna Patent Services, Llc Server-centric customized interactive program guide in an interactive television environment
US7096487B1 (en) 1999-10-27 2006-08-22 Sedna Patent Services, Llc Apparatus and method for combining realtime and non-realtime encoded content
US6754271B1 (en) 1999-04-15 2004-06-22 Diva Systems Corporation Temporal slice persistence method and apparatus for delivery of interactive program guide
US7356569B1 (en) * 1999-04-26 2008-04-08 Mainstream Scientific, Llc Apparatus and method for tracing the distribution of diversely sourced internet content
US7089530B1 (en) 1999-05-17 2006-08-08 Invensys Systems, Inc. Process control configuration system with connection validation and configuration
WO2000070417A1 (en) 1999-05-17 2000-11-23 The Foxboro Company Process control configuration system with parameterized objects
US6633315B1 (en) * 1999-05-20 2003-10-14 Microsoft Corporation Context-based dynamic user interface elements
US6788980B1 (en) 1999-06-11 2004-09-07 Invensys Systems, Inc. Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network
ATE359669T1 (de) 1999-10-27 2007-05-15 Sedna Patent Services Llc Vielfache videoströme unter verwendung von slice- basierter kodierung
WO2001033845A1 (en) * 1999-11-01 2001-05-10 Diva Systems Corporation Service provider side interactive program guide encoder
US6606103B1 (en) * 1999-11-30 2003-08-12 Uhc Llc Infinite resolution scheme for graphical user interface object
US6920607B1 (en) * 1999-12-15 2005-07-19 Microsoft Corp. Methods and systems for dynamically creating user interfaces
USD757052S1 (en) 2000-01-04 2016-05-24 Apple Inc. Computer display screen with graphical user interface
JP3942335B2 (ja) * 2000-02-28 2007-07-11 東芝テック株式会社 ウインドウのデザイン変更方法およびシステム
US6636246B1 (en) * 2000-03-17 2003-10-21 Vizible.Com Inc. Three dimensional spatial user interface
JP2001283243A (ja) 2000-03-31 2001-10-12 Mitsubishi Electric Corp ３次元グラフィックス描画データを記録した記録媒体およびその描画方法
US7137066B2 (en) * 2000-04-06 2006-11-14 Microsoft Corporation Binary cache file format for themeing the visual appearance of a computer system
US20010048448A1 (en) * 2000-04-06 2001-12-06 Raiz Gregory L. Focus state themeing
US6762767B2 (en) * 2000-04-06 2004-07-13 Microsoft Corporation Theme aware management using fusion
EP1143334A3 (de) * 2000-04-06 2005-03-30 Microsoft Corporation "Themen"-berücksichtigende graphische Benutzerschnittstelle
US6753885B2 (en) * 2000-04-06 2004-06-22 Microsoft Corporation System and theme file format for creating visual styles
US6873337B1 (en) * 2000-04-06 2005-03-29 Microsoft Corporation Application programming interface for changing the visual style
US20050091576A1 (en) * 2003-10-24 2005-04-28 Microsoft Corporation Programming interface for a computer platform
US6886135B2 (en) * 2000-04-07 2005-04-26 Microsoft Corp. Extensible schema for defining the visual appearance of computer system components
US7761798B1 (en) * 2000-04-18 2010-07-20 Apple Inc. System and method for controlling the screen display appearance for a data processing system
US7941756B1 (en) * 2000-05-22 2011-05-10 Realnetworks, Inc. System and method for creating and displaying classes of graphical display objects
US7426695B1 (en) * 2000-06-15 2008-09-16 Hewlett-Packard Development Company, L.P. Method and apparatus for coordinating display elements with the structure of a computer system
US6677962B1 (en) * 2000-06-26 2004-01-13 Microsoft Corporation Methods and systems for manipulating user interface controls
US8006192B1 (en) * 2000-10-04 2011-08-23 Apple Inc. Layered graphical user interface
US8271333B1 (en) * 2000-11-02 2012-09-18 Yahoo! Inc. Content-related wallpaper
US20020065877A1 (en) * 2000-11-30 2002-05-30 John Kowtko Methods and systems for creating and sharing customized web sites and portals
US20020089540A1 (en) * 2001-01-08 2002-07-11 Freddie Geier Media editing and creating interface
US6791581B2 (en) * 2001-01-31 2004-09-14 Microsoft Corporation Methods and systems for synchronizing skin properties
US7073130B2 (en) 2001-01-31 2006-07-04 Microsoft Corporation Methods and systems for creating skins
CA2385401C (en) * 2001-05-07 2012-09-25 Vizible.Com Inc. Method of representing information on a three-dimensional user interface
US7793326B2 (en) 2001-08-03 2010-09-07 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator
US7908628B2 (en) 2001-08-03 2011-03-15 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator content coding and formatting
US20030071860A1 (en) * 2001-08-29 2003-04-17 Goddard Edward Wayne System and method for managing graphical components
US20030084109A1 (en) * 2001-10-30 2003-05-01 Balluff Daniel A. Efficient message notification system and method for communication devices
US7102643B2 (en) * 2001-11-09 2006-09-05 Vibe Solutions Group, Inc. Method and apparatus for controlling the visual presentation of data
US7086006B2 (en) * 2001-11-09 2006-08-01 Corel Corporation Component user interface management
US7289132B1 (en) 2003-12-19 2007-10-30 Apple Inc. Method and apparatus for image acquisition, organization, manipulation, and publication
US7107545B2 (en) * 2002-02-04 2006-09-12 Draeger Medical Systems, Inc. System and method for providing a graphical user interface display with a conspicuous image element
US7017117B2 (en) * 2002-02-14 2006-03-21 Symantec Corporation Attenuating and amplifying user interface themes
US20030197716A1 (en) * 2002-04-23 2003-10-23 Krueger Richard C. Layered image compositing system for user interfaces
JP4368098B2 (ja) * 2002-08-30 2009-11-18 富士通株式会社 携帯端末及びアプリケーションプログラム
JP3755499B2 (ja) * 2002-09-06 2006-03-15 ソニー株式会社 Ｇｕｉアプリケーション開発支援装置、ｇｕｉ表示装置、および方法、並びにコンピュータ・プログラム
US20040220943A1 (en) * 2003-04-30 2004-11-04 Motorola, Inc. Data structure and method facilitating a custom user interface
US7644367B2 (en) * 2003-05-16 2010-01-05 Microsoft Corporation User interface automation framework classes and interfaces
US8127252B2 (en) * 2003-11-07 2012-02-28 Microsoft Corporation Method and system for presenting user interface (UI) information
KR100526345B1 (ko) * 2003-06-12 2005-11-08 엘지전자 주식회사 클로즈드 캡션의 옵션 운용방법
US7533367B2 (en) * 2003-06-27 2009-05-12 Microsoft Corporation Behavior architecture for component designers
US6892357B2 (en) * 2003-07-14 2005-05-10 Sap Aktiengesellschaft Logistics management method and system
US8166101B2 (en) 2003-08-21 2012-04-24 Microsoft Corporation Systems and methods for the implementation of a synchronization schemas for units of information manageable by a hardware/software interface system
US8238696B2 (en) 2003-08-21 2012-08-07 Microsoft Corporation Systems and methods for the implementation of a digital images schema for organizing units of information manageable by a hardware/software interface system
US7730073B2 (en) * 2003-10-23 2010-06-01 Microsoft Corporation System and a method for presenting related items to a user
US20050091181A1 (en) * 2003-10-23 2005-04-28 Mckee Timothy P. System and method for the presentation of items stored on a computer
US7908562B2 (en) * 2003-10-23 2011-03-15 Microsoft Corporation System and a method for presenting items to a user with a contextual presentation
US7721254B2 (en) * 2003-10-24 2010-05-18 Microsoft Corporation Programming interface for a computer platform
US7613600B2 (en) * 2003-12-24 2009-11-03 Sap Ag Unified personalization
JP4630672B2 (ja) * 2004-01-23 2011-02-09 キヤノン株式会社 アクセス制御装置及びアクセス制御方法及びアクセス制御プログラム
US7873916B1 (en) * 2004-06-22 2011-01-18 Apple Inc. Color labeling in a graphical user interface
US9213714B1 (en) 2004-06-22 2015-12-15 Apple Inc. Indicating hierarchy in a computer system with a graphical user interface
US7490295B2 (en) 2004-06-25 2009-02-10 Apple Inc. Layer for accessing user interface elements
US9471332B2 (en) * 2004-10-19 2016-10-18 International Business Machines Corporation Selecting graphical component types at runtime
KR100703690B1 (ko) * 2004-11-19 2007-04-05 삼성전자주식회사 스킨 이미지를 사용하여 아이콘을 그룹별로 관리하는사용자 인터페이스 및 방법
US20060150104A1 (en) * 2004-12-31 2006-07-06 Luigi Lira Display of user selected digital artworks as embellishments of a graphical user interface
US8024658B1 (en) 2005-01-09 2011-09-20 Apple Inc. Application for designing photo albums
KR100631755B1 (ko) * 2005-01-25 2006-10-11 삼성전자주식회사 자바 응용 프로그램의 룩을 실시간으로 전환하는 장치 및방법
US7917860B2 (en) * 2005-03-03 2011-03-29 Microsoft Corporation Simple styling
US7549087B2 (en) * 2005-03-29 2009-06-16 Microsoft Corporation User interface panel for hung applications
US7613957B2 (en) * 2005-04-06 2009-11-03 Microsoft Corporation Visual indication for hung applications
US8490015B2 (en) * 2005-04-15 2013-07-16 Microsoft Corporation Task dialog and programming interface for same
EP1727040A1 (de) * 2005-05-27 2006-11-29 Tektronix International Sales GmbH Verfahren, graphische Benutzeroberfläche und Computerprogrammprodukt zum Bereitstellen von Graphiken, die sich voneinander unterscheiden für die Änderung von einem oder mehreren Parametern
US7752556B2 (en) 2005-10-27 2010-07-06 Apple Inc. Workflow widgets
US20070113189A1 (en) * 2005-11-15 2007-05-17 Microsoft Corporation Specifying per theme styles for custom graphical elements
US20070124686A1 (en) * 2005-11-16 2007-05-31 Microsoft Corporation Locating graphical elements for an object
US7707514B2 (en) * 2005-11-18 2010-04-27 Apple Inc. Management of user interface elements in a display environment
US7418668B2 (en) * 2005-11-30 2008-08-26 Microsoft Corporation Glass appearance window frame colorization
US8700469B2 (en) 2006-03-06 2014-04-15 Apple Inc. System and method for delivering advertising with enhanced effectiveness
US7646392B2 (en) 2006-05-03 2010-01-12 Research In Motion Limited Dynamic theme color palette generation
US20070271520A1 (en) * 2006-05-19 2007-11-22 Sun Microsystems, Inc. Method for transforming a graphical user interface
US7962120B2 (en) * 2006-05-22 2011-06-14 Alcatel-Lucent Usa Inc. Allocation of internet protocol (IP) multimedia subsystem (IMS) charges
US7861310B2 (en) * 2006-07-14 2010-12-28 Sap Ag Runtime modification of client user controls
US20080046822A1 (en) * 2006-08-15 2008-02-21 Frank Meyer Apparatus and method for interactive user software interface design
US20080055315A1 (en) * 2006-09-05 2008-03-06 Dale Ducharme Method and System to Establish and Animate a Coordinate System for Content on a Display
US20080079750A1 (en) * 2006-09-29 2008-04-03 Vidya Setlur Perceptually adaptive graphical user interface
US7536645B2 (en) * 2006-10-23 2009-05-19 Research In Motion, Ltd System and method for customizing layer based themes
US20080134077A1 (en) * 2006-12-05 2008-06-05 Sap Ag Chameleon graphic user interface
US8285732B2 (en) * 2006-12-18 2012-10-09 Sap Ag Method and system for providing themes for software applications
US7539796B2 (en) 2007-03-30 2009-05-26 Motorola, Inc. Configuration management of an electronic device wherein a new configuration of the electronic device is selected based on attributes of an application
US20080244470A1 (en) * 2007-03-30 2008-10-02 Motorola, Inc. Theme records defining desired device characteristics and method of sharing
US20080297521A1 (en) * 2007-05-31 2008-12-04 Liang-Yu Chi System and method for providing skins for a web page
US8954871B2 (en) 2007-07-18 2015-02-10 Apple Inc. User-centric widgets and dashboards
KR101320919B1 (ko) * 2008-01-29 2013-10-21 삼성전자주식회사 분할 화면을 통한 ｇｕｉ 제공방법 및 이를 적용한멀티미디어 기기
RU2495476C2 (ru) * 2008-06-20 2013-10-10 Инвенсис Системз, Инк. Системы и способы для иммерсивного взаимодействия с действительными и/или имитируемыми техническими средствами для управления технологическим процессом, контроля состояния окружающей среды и производственного контроля
US20090319928A1 (en) * 2008-06-20 2009-12-24 Microsoft Corporation Generating previews for themes that personalize an operating environment
US9760234B2 (en) * 2008-10-14 2017-09-12 International Business Machines Corporation Desktop icon management and grouping using desktop containers
US20100185965A1 (en) * 2009-01-21 2010-07-22 Frederick Collin Davidson Artistic file manager
US8127060B2 (en) 2009-05-29 2012-02-28 Invensys Systems, Inc Methods and apparatus for control configuration with control objects that are fieldbus protocol-aware
US8122434B2 (en) * 2009-05-29 2012-02-21 Invensys Sytems, Inc. Methods and apparatus for control configuration control objects associated with a track attribute for selecting configuration information
US8463964B2 (en) 2009-05-29 2013-06-11 Invensys Systems, Inc. Methods and apparatus for control configuration with enhanced change-tracking
US20110153435A1 (en) * 2009-09-17 2011-06-23 Lexos Media Inc. System and method of cursor-based content delivery
US8972878B2 (en) * 2009-09-21 2015-03-03 Avaya Inc. Screen icon manipulation by context and frequency of Use
US20110199388A1 (en) * 2010-02-17 2011-08-18 Samsung Electronics Co., Ltd. Method and apparatus for configuring graphical effect in a mobile terminal
US8331855B2 (en) 2010-07-12 2012-12-11 Invensys Systems, Inc. Methods and apparatus for process control with improved communication links
US9095002B2 (en) 2010-07-12 2015-07-28 Invensys Systems, Inc. Methods and apparatus for process control with improved communication links
US20120117497A1 (en) * 2010-11-08 2012-05-10 Nokia Corporation Method and apparatus for applying changes to a user interface
US9361132B2 (en) * 2011-02-08 2016-06-07 Qualcomm Incorporated System and method for providing application-based user interface features on a computing device
US9154813B2 (en) 2011-06-09 2015-10-06 Comcast Cable Communications, Llc Multiple video content in a composite video stream
US20130207994A1 (en) * 2012-02-13 2013-08-15 Vilen Rodeski System and method for generating and applying a color theme to a user interface
US20130321445A1 (en) * 2012-06-01 2013-12-05 Harald Buerner Colorizing user interfaces
EP2793115A1 (de) * 2013-04-18 2014-10-22 Océ-Technologies B.V. Verfahren zur Animation von Änderungen in einer Liste
JP6070423B2 (ja) * 2013-06-03 2017-02-01 株式会社リコー 情報処理装置、情報処理方法、及びプログラム
FR3010812A1 (fr) * 2013-09-13 2015-03-20 Eads Europ Aeronautic Defence Procede de conception assistee par ordinateur comportant une etape de modelisation
JP6053717B2 (ja) 2014-05-07 2016-12-27 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ マークアップ言語で記述されたページのカラーシームを抽出する方法、上記カラーシームを抽出するための電子装置、及び、その電子装置用プログラム
US10073604B2 (en) * 2014-05-15 2018-09-11 Oracle International Corporation UI-driven model extensibility in multi-tier applications
CN106575230A (zh) 2014-09-02 2017-04-19 苹果公司 用于可变触觉输出的语义框架
US20160110054A1 (en) * 2014-10-21 2016-04-21 Cyanogen Inc. System and method for customizing a theme for modifying a look and feel of a graphical user interface
US10152804B2 (en) 2015-02-13 2018-12-11 Smugmug, Inc. System and method for dynamic color scheme application
CN106371811A (zh) * 2015-07-21 2017-02-01 中兴通讯股份有限公司 一种java窗口控件的识别方法及装置
DK179489B1 (en) 2016-06-12 2019-01-04 Apple Inc. Devices, methods and graphical user interfaces for providing haptic feedback
DK179823B1 (en) 2016-06-12 2019-07-12 Apple Inc. DEVICES, METHODS, AND GRAPHICAL USER INTERFACES FOR PROVIDING HAPTIC FEEDBACK
DK179278B1 (en) 2016-09-06 2018-03-26 Apple Inc Devices, methods and graphical user interfaces for haptic mixing
DK201670720A1 (en) 2016-09-06 2018-03-26 Apple Inc Devices, Methods, and Graphical User Interfaces for Generating Tactile Outputs
DK201770372A1 (en) 2017-05-16 2019-01-08 Apple Inc. TACTILE FEEDBACK FOR LOCKED DEVICE USER INTERFACES
US11372624B2 (en) 2018-08-10 2022-06-28 Google Llc System for creating graphical content
US11321857B2 (en) 2018-09-28 2022-05-03 Apple Inc. Displaying and editing images with depth information
USD945481S1 (en) * 2020-06-18 2022-03-08 Apple Inc. Display screen or portion thereof with graphical user interface
US11507729B1 (en) * 2021-05-13 2022-11-22 Salesforce, Inc. Scoped containers using CSS custom properties and color pairs

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5394521A (en) * 1991-12-09 1995-02-28 Xerox Corporation User interface with multiple workspaces for sharing display system objects
US4866638A (en) * 1988-03-04 1989-09-12 Eastman Kodak Company Process for producing human-computer interface prototypes
US5121478A (en) * 1988-09-08 1992-06-09 Xerox Corporation Window system with independently replaceable window functionality
JPH0778782B2 (ja) * 1989-07-19 1995-08-23 インターナショナル・ビジネス・マシーンズ・コーポレーシヨン 対話型コンピュータ・システムならびにその使用環境適合化装置および方法
US5287514A (en) * 1990-01-08 1994-02-15 Microsoft Corporation Method and system for customizing a user interface in a computer system
US5220675A (en) * 1990-01-08 1993-06-15 Microsoft Corporation Method and system for customizing a user interface in an integrated environment
US5388202A (en) * 1990-02-02 1995-02-07 Viacom International Inc. Method and apparatus for generating window borders having pictorial frame elements
US5101364A (en) * 1990-02-09 1992-03-31 Massachusetts Institute Of Technology Method and facility for dynamic video composition and viewing
US5327529A (en) * 1990-09-24 1994-07-05 Geoworks Process of designing user's interfaces for application programs
JPH04281514A (ja) * 1991-03-11 1992-10-07 Matsushita Electric Ind Co Ltd 入力装置
US5341466A (en) * 1991-05-09 1994-08-23 New York University Fractal computer user centerface with zooming capability
US5371844A (en) * 1992-03-20 1994-12-06 International Business Machines Corporation Palette manager in a graphical user interface computer system
US5408603A (en) * 1992-03-31 1995-04-18 Dow Benelux N.V. Global process control information system and method
JP2525546B2 (ja) * 1992-09-08 1996-08-21 インターナショナル・ビジネス・マシーンズ・コーポレイション グラフィックリソ―ス・エディタ
JP2522898B2 (ja) * 1992-09-08 1996-08-07 インターナショナル・ビジネス・マシーンズ・コーポレイション 動的カストマイズ方法及びグラフィックリソ―ス・エディタ
US5438659A (en) * 1992-10-08 1995-08-01 Hewlett-Packard Company Object-action user interface management system
US5345550A (en) * 1992-12-23 1994-09-06 International Business Machines Corporation User-modifiable popup menus for object oriented behavior
US5452406A (en) * 1993-05-14 1995-09-19 Microsoft Corporation Method and system for scalable borders that provide an appearance of depth
US5615320A (en) * 1994-04-25 1997-03-25 Canon Information Systems, Inc. Computer-aided color selection and colorizing system using objective-based coloring criteria
US5880729A (en) * 1994-05-16 1999-03-09 Apple Computer, Inc. Graphical user interfaces having animated control elements
US5675520A (en) * 1995-03-30 1997-10-07 Microsoft Corporation Method for extending a common user interface
US5917487A (en) * 1996-05-10 1999-06-29 Apple Computer, Inc. Data-driven method and system for drawing user interface objects
US5905492A (en) * 1996-12-06 1999-05-18 Microsoft Corporation Dynamically updating themes for an operating system shell

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102193784A (zh) * 2010-03-09 2011-09-21 新奥特（北京）视频技术有限公司 一种用户自定义界面的方法及装置
CN102193784B (zh) * 2010-03-09 2016-01-20 新奥特（北京）视频技术有限公司 一种用户自定义界面的方法及装置

Also Published As

Publication number Publication date
EP1174792A2 (de) 2002-01-23
US6104391A (en) 2000-08-15
AU2591995A (en) 1995-12-05
DE69526218T2 (de) 2002-12-12
DE69526218D1 (de) 2002-05-08
EP1174792A3 (de) 2007-07-25
JPH10500512A (ja) 1998-01-13
US5959624A (en) 1999-09-28
WO1995031775A1 (en) 1995-11-23
EP0760125A1 (de) 1997-03-05

Similar Documents

Publication Publication Date Title
EP0760125B1 (de) System zur anpassung der erscheinung und des verhaltens graphischer benutzeroberflächen
EP0760122B1 (de) Umschaltung zwischen darstellungs-/verhaltensthemen in graphischen benutzeroberflächen
US5963206A (en) Pattern and color abstraction in a graphical user interface
US8531480B2 (en) Data-driven layout engine
US6710782B2 (en) Data driven layout engine
US6188399B1 (en) Multiple theme engine graphical user interface architecture
US7694229B2 (en) System and theme file format for creating visual styles
US6100885A (en) Supporting modification of properties via a computer system's user interface
US5977971A (en) Tree view control
US6664981B2 (en) Graphical user interface with hierarchical structure for customizable menus and control objects
US6456296B1 (en) Color scheme for zooming graphical user interface
US5790132A (en) Image rendering system with extensible mechanism for providing visual user feedback when an image graphic is selected
JPH0666049B2 (ja) 属性データ管理方法
Colebourne et al. MOG user interface builder: a mechanism for integrating application and user interface
Gansner et al. The eXene widgets manual
Lam Tix Programming Guide
EP0760121B1 (de) Aspekt- und formelemente einer verbesserten graphischen benutzerschnittstelle
Hudson et al. SubArctic UI Toolkit user’s manual st. Paul release (beta version 0.8 e)
Sannella Analyzing Interactive Graphics Systems
urgen Herczeg et al. Programming and Reference Manual
Training Adobe®

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 19961118

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE GB

17Q First examination report despatched

Effective date: 19991125

GRAG Despatch of communication of intention to grant

Free format text: ORIGINAL CODE: EPIDOS AGRA

GRAG Despatch of communication of intention to grant

Free format text: ORIGINAL CODE: EPIDOS AGRA

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

REG Reference to a national code

Ref country code: GB

Ref legal event code: IF02

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE GB

REF Corresponds to:

Ref document number: 69526218

Country of ref document: DE

Date of ref document: 20020508

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20030106

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 69526218

Country of ref document: DE

Representative=s name: BARDEHLE PAGENBERG PARTNERSCHAFT MBB PATENTANW, DE

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20140514

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20140515

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 69526218

Country of ref document: DE

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20150515

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20150515