US6820111B1 - Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history - Google Patents

Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history Download PDF

Info

Publication number
US6820111B1
US6820111B1 US09/456,975 US45697599A US6820111B1 US 6820111 B1 US6820111 B1 US 6820111B1 US 45697599 A US45697599 A US 45697599A US 6820111 B1 US6820111 B1 US 6820111B1
Authority
US
United States
Prior art keywords
user
page
user interface
links
history
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
US09/456,975
Inventor
Darryl E. Rubin
Andrew C. Baird
John L. Beezer
Jonathan C. Cluts
Susan D. Woolf
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.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Corp
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 Microsoft Corp filed Critical Microsoft Corp
Priority to US09/456,975 priority Critical patent/US6820111B1/en
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: RUBIN, DARRYL E., BAIRD, ANDREW C., BEEZER, JOHN L., CLUTS, JONATHAN C., WOOLF, SUSAN D.
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BAIRD, ANDREW C., BEEZER, JOHN L., CLUTS, JONATHAN C., WOOLF, SUSAN D., RUBIN, DARRYL E.
Priority to US10/875,174 priority patent/US7496830B2/en
Application granted granted Critical
Publication of US6820111B1 publication Critical patent/US6820111B1/en
Assigned to MICROSOFT TECHNOLOGY LICENSING, LLC reassignment MICROSOFT TECHNOLOGY LICENSING, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT CORPORATION
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction 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
    • G06F3/0483Interaction with page-structured environments, e.g. book metaphor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/955Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9562Bookmark management

Definitions

  • This invention relates generally to computer user interface architectures. More particularly, the invention provides a user interface architecture in which both user content and user interface are composed of document pages with links.
  • Prior art UIs for desktop computers typically require a keyboard and mouse in order for a user to interact with them, and most pen-enabled palmtop computers have cumbersome means of interaction. Therefore, there is a need for more “natural” styles of interacting with a computer by using a minimum number common gestures such as touch, hold, erase, draw or write.
  • Prior art UI desktop metaphors applied to small form factor devices are typically cluttered and difficult to use.
  • applications that provide rich functionality are sometimes constrained by the limited ability of a user to navigate menus and dialogs of prior art UIs. For instance, for such applications, the menus and tool bars may get too big, and the help system may get too cumbersome to navigate or search. Accordingly, in addition to the need for a simpler more unified experience for the user of an application, there is also a need to facilitate the uncluttered presentation of user interfaces for applications providing very rich functionality.
  • Prior art UIs typically offer limited capabilities for customizing the UI. Accordingly, there is a need for a UI architecture that provides greater flexibility to users, content developers, and third-party software developers by providing broader capabilities for easily customizing the UI. For example, different groups of users may be of different levels of computer skill and have need of different sets of features, and the UI can be customized to better suit their needs.
  • Prior art device-to-device and device-to-PC synchronization schemes typically are not seamless and require a great deal of configuration and attention from the user. Accordingly, there is a need to provide automatic and transparent synchronization between a user's computers, such as a handheld computer and a desktop computer.
  • the invention includes a user interface architecture in which user content and user interface are composed of documents with links.
  • a link can relate a spot or region in a document with a spot or region in another document, so that touching the link causes the display to navigate to that other document.
  • a link can also relate a spot or region in a document and an active runable object such that when a user activates that link or touches that spot in the document, the associated object is run. Parameters for the execution of the object may be supplied by properties associated with the link. Links, therefore, can act as commands. Links may be to any kind of command code.
  • a link may manifest in various ways based on the link's properties. Links can look like not only clickable spots, but also fill-in fields and other kinds of well-known and later-developed user interface elements. Alternatively, links can manifest in the containing document a frame displaying the contents of part, or all, of the linked-to document. When links are displayed, in addition to basing the display format of the link on the link's display properties, the link display format may depend upon the characteristics of the linked-to document.
  • the path a user takes to reach a document typically affects the behavior and presentation of the document.
  • State-like information for displaying a linked-to document page is stored separately from the linked-from and linked-to documents as part of the link's properties.
  • Users access, interact with, and navigate among both user content documents and user interface documents in a unified way, namely, by activating links. Further, both user content document pages and user interface document pages are displayed in a single viewing frame. This unified approach simplifies the user's interaction with both user content and user interface documents by reducing the number of concepts a user must learn in order to access, interact with, and modify both user content documents and the user interface.
  • a non-linear navigation history is maintained such that a user can navigate along a first path, back up using a previous link an appropriate number of times, navigate along a second path, back up along the second path using the previous link an appropriate number of times, and re-navigate along the first path again using a next link.
  • Every document page to which a user navigates is saved in the user's navigation history.
  • Users can query their navigation histories and view their navigation history in various ways, such as: by time, by appearance, by site, document, section, page, and the like.
  • User can also view their navigation history as nodes with side tracking branches, as a linear list, or as a combination of most recently viewed pages and last few task categories.
  • navigation from user content pages through user interface pages that results in a command being executed is automatically removed from the user's view of the navigational history in order to keep the navigational history view uncluttered.
  • a flexible selection model is supported allowing users to select the object of a command either before or after the command itself is selected.
  • This flexible selection model allows UIs built according to the principles of this invention to scale to small display areas.
  • UIs built according to the principles of this invention also scale well to applications having voluminous and/or complicated user interfaces by facilitating an organized and uncluttered view of the user interface command hierarchy and/or user interface help information for such applications.
  • the documents-with-links UI according to the principles of this invention is organized to make frequently used commands a single navigation step away, or through customizations, no steps away.
  • a self-explanatory document, the Guide Book is provided.
  • the Guide Book is a readable manual that users can go through in a logical order, a page at a time, like any conventional user manual. Each command mention, however, is an active command instance that can be invoked in place.
  • FIG. 1 is a schematic diagram of a conventional general-purpose digital computing environment that can be used to implement various aspects of the invention.
  • FIG. 2 shows a conventional tablet and stylus-based computer that can be used to implement various aspects of the invention.
  • FIG. 3 is a flowchart showing simplified steps at a high level of abstraction for implementing a UI architecture according to the principles of this invention upon start up.
  • FIG. 4 is a flow chart showing simplified steps for implementing the “display state” step of the flow chart in FIG. 3 .
  • FIG. 5 depicts an example Start Page displayed on a personal viewer according to a preferred embodiment of the invention.
  • FIG. 6 depicts an example book cover page and table of contents displayed on a personal viewer according to a preferred embodiment of the invention.
  • FIG. 7 depicts example Guide Book pages displayed on a personal viewer according to a preferred embodiment of the invention.
  • FIG. 8 depicts example Quick Help pages, one of which is bookmarked, displayed on a personal viewer according to a preferred embodiment of the invention.
  • FIG. 9 depicts an example of a pinned user content page displayed on a personal viewer according to a preferred embodiment of the invention.
  • FIG. 11 depicts an example End Page displayed on a personal viewer according to a preferred embodiment of the invention.
  • the UI architecture of this invention also referred to herein as a “documents-with-links UI,” supports creation of UI's that have essentially zero clutter, and few concepts to master. In this way, it is a major departure from prior art UI's using a desktop metaphor.
  • the user of a documents-with-links UI according to this invention focuses primarily on content and not on UI appurtenances. Starting with just knowledge of how to page through a document and to follow links, a user can learn how to do any other UI operation.
  • the documents-with-links UI works without drop-down menus, toolbars, windows, or other cluttering UI elements (although some of these elements may optionally be made available where they are desired).
  • UI UI
  • content UI
  • smart next/previous logic and intelligent management of the navigation chain solve technical problems caused by treating “UI” and content as the same thing in a unified navigational context.
  • the documents-with-links UI is conceptually simpler for the user than a model that has separate UI and content webs.
  • the one-space model is also more powerful and customizable, as described in more detail below.
  • UI shortcuts and direct manipulations may exist as a configurable layer on top of the documents-with-links UI, so more experienced users can do the most common operations in context, without navigating to UI pages.
  • the user gets the best of terse command access plus the richness of the full browser and answer system for exploring the command set.
  • the documents-with-links UI uses a web architecture, with UI shortcuts layered on top.
  • a na ⁇ ve user will typically start by using the documents-with-links UI without the shortcuts—that is, by using the Guide Book to access UI functions.
  • An advanced user will typically be able to perform all common operations via the shortcuts and without resorting to the documents-with-links UI Guide Book as often.
  • the documents-with-links UI is scalable across a wide range of device and display types from desktop computers to laptops to hand-held devices. Accordingly, the documents-with-links UI is intended to be implemented on any type of computing platform.
  • the documents-with-links UI exploits a large screen by being able to show content in a book-like way—two full side-by-side pages, as depicted, for instance, in FIG. 8 .
  • UI being content, takes advantage of the large format of pages and the ability to turn/navigate pages (versus the smaller size of menus/dialog boxes in prior art UIs and their limited or nonexistent provisions for navigation).
  • the UI scales to small screens because of the flexible selection model that allows command selection regions to be initiated either before or after the desired command is chosen. This means, for example, that on a small screen a user can call up a page of command choices that completely obscure the original document due to screen size limitations, choose the command, then return to the user document and then select the region for the command to operate on.
  • a user wanted to reformat some text, but had not selected the text to be reformatted yet. The user could press a link that indicates that it will reformat text.
  • the UI of this invention will display an indicator on the screen prompting the user to select the text to be reformatted.
  • the user can finish the reformatting operation by clicking on another link, such as a link that indicates that the selected text will be reformatted.
  • another link such as a link that indicates that the selected text will be reformatted.
  • the user could select the region first and then go find and invoke the command. Being able to select the object upon which a command will operate after selecting the command is unlike the selection model of prior art UIs where object selection must precede command selection.
  • the selection model of the documents-with-links UI is discussed in more detail below.
  • Users can use the full power of the UI to manipulate the UI itself. For example, users can search, annotate, customize and edit UI pages the same as any content (subject to permissions). Users can select from multiple views for the page being viewed.
  • the model naturally accommodates dynamic content, including downloaded content, that mixes content and UI on the same page or as part of a network of related pages.
  • a link can be an association between two different spots in a collection of document pages.
  • the spots could be two spots on the same page.
  • the spots could be a spot on one page and a spot on another page.
  • Links can have properties that indicate certain things about the link beyond simply the fact that it relates two different places. What a link relates need not necessarily always be displayable pages.
  • a link can relate a spot in a document and an active runable object such that when a user activates that link or touches that spot in the document, the associated object is run. Links, therefore, can act as commands. Links may be to any kind of command code. Scripts are one example. Binary code objects are another example. As a result, pages that have links replace the drop-down menus and dialog boxes of prior art UIs.
  • a link may manifest in various ways based on the link's properties. Links can look like not only clickable spots, but also fill-in fields and other kinds of well-known and later-developed user interface elements. A document page could have these other kinds of active elements that are really a form of link. Accordingly, activating links goes beyond merely clicking on colored underlined text and can include filling in fields, pressing radio buttons, and the like. Again, pages with links replace prior art dialog boxes having buttons and the like. The links may look like buttons, but the links are simply links.
  • links have properties that govern their appearance and behavior. For example, a link's properties may dictate that it appear as a blue underscored text string as in prior art browsers, or as a 3D button, as a graphic icon, as a thumbnail image of the content being linked to, or even as an embedded frame that is open on the content being linked to.
  • a user can modify how a link manifests by modifying the link's properties.
  • the ability to control a link's appearance and behavioral properties makes possible rich authoring and customization of both content and the user interface.
  • Actions in a UI occur by clicking on commands that exist on pages.
  • a command looks like a link, and in fact it is a link.
  • a command is a link whose source anchor is the command hotspot, whose destination anchor is the script or code that implements the command, and whose properties are the command parameters.
  • Some commands may run with canned parameters while others may present users with a form for entering the parameters (for example, the Properties command).
  • a command is a link, it has all the functionality of links.
  • commands can visualize in multiple ways, such as an underlined blue label, a button, an icon, or a graphic image. They can be copied from one place to another, moved, and deleted. Their properties can be manipulated, such as to change their appearance or to preset some or all of their parameters.
  • Commands can also be created the same way that any kind of link is created, via a Link command, which establishes a link between a source and destination that the user specifies; in the case of creating a command link, the destination is an executable object such as a command script or binary. Everything users can do to a link, or to objects in general (since a link is an object), users can do to commands.
  • the documents-with-links UI is organized to make frequently used commands a single navigation step away, or through customizations, no steps away. Less commonly used commands may take more steps to get to.
  • the documents-with-links UI includes a self-explanatory document, the Guide Book. This is literally a readable manual that users can go through in a logical order, a page at a time, like any current user manual. The difference is that each command mention is an active command instance that can be invoked in place.
  • a variety of Quick Help pages and indices make it easy to get quick access to sets of commands that are commonly used together, that are logically related, or that are typically used as part of a given scenario. Such Quick Help pages could be assembled dynamically based upon the context of the document or documents being viewed by the user.
  • the documents-with-links UI would not be ideal, because users want the most common commands to be zero hops away. Users also want context sensitivity to command presentation, like that provided by conventional context menus.
  • the documents-with-links UI therefore accommodates things like toolbars, context menus, and other UI shortcuts that the user can customize.
  • shortcuts are implemented as documents with links.
  • the UI shortcuts can be conceptualized as being layered on top of the base documents-with-links UI, yet shortcuts are actually constructed out of the same components that comprise the documents-with-links UI: documents with links.
  • shortcuts will be discussed below, with reference to a preferred embodiment of this UI architecture implemented on a personal viewer, as the shortcuts would appear to a user, because, eventually, shortcuts are what most users would use in their day-to-day activities with the documents-with-links UI.
  • a record is created of where the user navigated to and at what date and time this occurred. It is thus possible to query this set of records to derive many views of a user's navigational history, including, for instance, a network view, also referred to as a history map view. Ways in which a user's navigational history may be viewed are discussed in more detail below in the Viewing History section.
  • the history map view is a generalization of the linear history provided by prior art browsers.
  • the history map view makes it easy for a user to revisit a place the user visited previously, with important cues about the context in terms of other places the user was visiting at the time.
  • the Next command works with the branching history too.
  • a user can explore a chain of links, back up, explore a different chain, back up, and Next the user's way down the original chain to get back to where the user was. This is much easier than having to manually re-follow the original chain of links, which would be impossible if the user has forgotten the chain of links they had previously followed.
  • the documents-with-links UI doesn't forget all the twists and turns of where the user has been just because the user backs up and proceeds in a different direction.
  • the documents-with-links UI stores not only where the user has been, but also the path(s) the user took to get there. The user can use the history map and/or the Next/Previous commands to get back there again.
  • the Next function works in this network-style navigational context by using heuristics to pick which path forward the user most likely intends.
  • the most basic rule is to pick the forward path along which the user backed to the current node.
  • Other rules provide additional intelligence to account for a user's known navigational patterns, such as whether the user got to the current node by navigating back by individual pages or by groupings of pages (such as by site), or by linking from a parent to a child.
  • the Next function could include options to present a user with a list of forward choices, textually and/or as a map in which the user could zoom into desired areas. In this way, the user can control which branch to take, if the user is not satisfied with the documents-with-links UI's selection.
  • the documents-with-links UI can include knowledge of collections of pages making up sections and chapters, of collections of sections and chapters making up a document, of collections of documents making up web sites, and so on. The same is true for the layers of command finding and invocation.
  • Such knowledge of semantic clustering helps guide decisions about popping contexts and for presenting the user with reasonable choices about points to jump to along the Next/Previous chain.
  • a problem with treating content and UI as part of the same navigation space is that the user's navigation chain gets cluttered with UI-related pages.
  • the documents-with-links UI solves that through intelligent management of the navigation context, and by making that context a true network, not just a linear chain.
  • a new branch in the navigation chain is started. So, if a user's context is currently B in the existing chain of document pages A-B-C, and the user navigates to D, then the new context is D. D might be a UI page the user navigated to from document B. When the user clicks a command on page D, the command executes and removes D from the navigation context. Thus, after finding and executing the command, the user's navigation context is restored to document page B.
  • the documents-with-links UI knows what to act on, and what to remove from the navigation context as follows. Commands operate on the current selection, and, in general, remove the navigation nodes that lie on the branch leading from the current selection to the command. Further, additional heuristics may be used for unusual cases.
  • the current selection is the most recently selected area. All commands that are configured to operate on selections will operate on that most recently selected area. Having executed, they will trim the navigation context at the branch point that leads from the current selection to the command itself.
  • the benefit is that users are free to link into the web of UI pages, exploring them as necessary to find the desired command, and then to invoke it. The act of doing so will end up trimming all the UI navigation from the context, leaving the user back where the user was before navigating to UI pages. Note that depending on the length and content of the navigational path between the command and recent selection, the UI may show the user the target and prompt the user to confirm before proceeding.
  • the effect of the algorithm for trimming the navigational context is typically to isolate and remove the branch whose purpose was to find the command that was just executed. Trimming the navigational context of navigation to UI pages does not always occur, however. For example, an Apply command for property setting could leave the property form active and not trim the navigation context. Of course, different commands may choose to operate on the navigation context in different ways. Nevertheless, a couple standard ways will typically cover most of the cases.
  • the documents-with-links UI does not require users to make a selection before invoking a command. Users are free to select first and then click a command, or click the command first and then make a selection. If an appropriate selection does not exist when a command is invoked, the user is prompted to make a selection at that time.
  • the selection mechanism and command verbs are designed to give users a lot of latitude about the order in which they do things when carrying out commands. Besides fitting better to users' personal habits, this makes it harder for users to do something “wrong,” such as inadvertently applying formatting to text other than the text the user wants to reformat.
  • the documents-with-links UI may display the same page of a document differently depending upon which link navigated a user to the page.
  • the user wants to fill in the TO: field of an e-mail message.
  • the user wants to open the address book and make possibly several choices.
  • forms could have special-purpose chooser controls where this provides a good shortcut for the most common choices.
  • the chooser UI should also make it possible to leverage the full power of the navigation, browsing, viewing, and search UI that is available in list-oriented documents like file folders and the address book. Making a choice from such a list should be a matter of just navigating to that list as a user would in any other context and making the choice.
  • the documents-with-links UI provides a link to the address book that is associated with the input field.
  • the documents-with-links UI makes the link from an input field to its choice document, the address book in this example, be a command with navigation behavior, as opposed to being an ordinary link.
  • This command navigates the user to the document the user needs to choose from and captures anything the user selects.
  • the user can simply navigate back to the send form where the TO: field is.
  • the user could close the address book or use an OK command, either of which would return the user automatically. There is nothing to save, because all choice state is captured as the user proceeds. If there is a change in plan, the user could simply cancel the current selection, or clear the TO: field when the user returns.
  • the user may click the TO: field link again, and the user is taken back to the address book, with all the current choices still highlighted.
  • the current choices are highlighted because the command that takes the user to the address book picks up the TO: state and paints the required selection regions.
  • the command which presents the document to choose from can also cause checkboxes to appear next to each entry in the document. Rather than manually selecting items in the document, the user can check or uncheck the checkboxes. This causes the associated entry to be selected or unselected, respectively.
  • the user is accessing a standard document, the address book, and the normal multiple selection idiom to make and change the user's TO: field fill-in choices.
  • the user has the full power of the normal UI for navigating, viewing, and searching, the address book and can navigate to other documents containing addresses where the user can make other choices.
  • the selection state is associated with the path the user took to reach the address book, the user will see the TO: items highlighted in the address book only if the user links to the address book (or successor nodes) via the TO: field in question.
  • the existence of an active To: field does not interfere with other uses of the address book or with other active To: fields.
  • the documents-with-links UI is essentially modeless. For example, a user could be involved in filling out a form for carrying out a UI operation such as creating a formatting style for a table. In the middle of doing this the user could navigate away from this UI form and get engaged in some other UI operation, such as filling out another form for a different purpose, and then, at any time, navigate back to the original, incomplete form. There is no restriction on the number of such incomplete operations that can be in progress simultaneously. Nor is there any limitation on switching away from such incomplete operations. This is unlike the prior art, where complex operations, typically performed via dialogs, must generally be complete or cancelled before the user switches to another activity. Unlike prior UI's, the user of a documents-with-links UI is typically not restricted from interrupting one operation to initiate another, or several others, nor would such an interruption cause the user to lose work already performed in partially completing the first operation.
  • Another architectural topic central to the documents-with-links UI is the model for creating and saving information. Any time a user creates something new, the user is creating a new document and linking it into a context. For an object inserted into an existing document, such as an embedded annotation, the user is linking it into the document that is to contain it, with link properties implicitly set to make the object visualize in place (OLE-style embedding). Physically, the object is stored as a child within the parent document's container.
  • the object is instead added to the current navigation context, as if the user had done a Next to it from wherever the user was when the user issued the New command. Physically, the object may be stored in the user's sea of “free space” in a hidden system folder, not part of any folder the user is aware of, unless and until the user chooses to file it somewhere.
  • the user does not need to put documents into a filing hierarchy or save them. This is because the documents-with-links UI stores all navigational history. Accordingly, users can find the documents they create by viewing or searching their history map.
  • a user could file a document into a folder as an optional step, using a Save As command or by manually creating a link in the folder that leads to the document (the Save As command could be simply a shortcut for creating such a link). Also, the user could use Save/Save As to update or create versions of a document in the filing hierarchy as desired.
  • FIG. 1 is a schematic diagram of a conventional general-purpose digital computing environment that can be used to implement various aspects of the invention.
  • Computer 100 includes a processing unit 110 , a system memory 120 , and a system bus 130 that couples various system components including the system memory to the processing unit 110 .
  • the system bus 130 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
  • the system memory includes read only memory (ROM) 140 and random access memory (RAM) 150 .
  • a basic input/output system 160 (BIOS), containing the basic routines that help to transfer information between elements within the computer 100 , such as during start-up, is stored in ROM 140 .
  • Computer 100 also includes a hard disk drive 170 for reading from and writing to a hard disk (not shown), a magnetic disk drive 180 for reading from or writing to a removable magnetic disk 190 , and an optical disk drive 191 for reading from or writing to a removable optical disk 192 such as a CD ROM or other optical media.
  • the hard disk drive 170 , magnetic disk drive 180 , and optical disk drive 191 are connected to the system bus 130 by a hard disk drive interface 192 , a magnetic disk drive interface 193 , and an optical disk drive interface 194 , respectively.
  • the drives and their associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the personal computer 100 . It will be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs), and the like, may also be used in the example operating environment.
  • RAMs random access memories
  • ROMs read only memories
  • a number of program modules can be stored on the hard disk, magnetic disk 190 , optical disk 192 , ROM 140 or RAM 150 , including an operating system 195 , one or more application programs 196 , other program modules 197 , and program data 198 .
  • a user can enter commands and information into the computer 100 through input devices such as a keyboard 101 and pointing device 102 .
  • Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, or the like.
  • These and other input devices are often connected to the processing unit 110 through a serial port interface 106 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB).
  • a monitor 107 or other type of display device is also connected to the system bus 130 via an interface, such as a video adapter 108 .
  • personal computers typically include other peripheral output devices (not shown), such as speakers and printers.
  • the computer 100 can operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 109 .
  • Remote computer 109 can be a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to computer 100 , although only a memory storage device 111 has been illustrated in FIG. 1 .
  • the logical connections depicted in FIG. 1 include a local area network (LAN) 112 and a wide area network (WAN) 113 .
  • LAN local area network
  • WAN wide area network
  • Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
  • the computer 100 is connected to the local network 112 through a network interface or adapter 114 .
  • the personal computer 100 When used in a WAN networking environment, the personal computer 100 typically includes a modem 115 or other means for establishing a communications over the wide area network 113 , such as the Internet.
  • the modem 115 which may be internal or external, is connected to the system bus 130 via the serial port interface 106 .
  • program modules depicted relative to the personal computer 100 may be stored in the remote memory storage device.
  • network connections shown are example and other means of establishing a communications link between the computers can be used.
  • the existence of any of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like is presumed, and the system can be operated in a client-server configuration to permit a user to retrieve web pages from a web-based server.
  • Any of various conventional web browsers can be used to display and manipulate data on web pages.
  • FIG. 2 shows a tablet and stylus computer that can be used in accordance with various aspects of the present invention. Any or all of the features, subsystems, and functions in the system of FIG. 1 can be included in the computer of FIG. 2 .
  • Computer 201 includes a large display surface 202 (e.g., a flat panel display) on which a plurality of windows 203 is displayed. Using stylus 204 , a user can select, highlight, and write on the display area. Computer 201 interprets marks made using stylus 204 in order to manipulate data, enter text, and execute conventional computer application tasks such as spreadsheets, word processing programs, and the like.
  • One commercially available tablet and stylus computer incorporating many of these features is the Stylistic 2300 computer sold by Fujitsu Personal Systems, Inc., of Santa Clara, Calif.
  • a stylus could be equipped with buttons or other features to augment its selection capabilities.
  • a stylus could be implemented as a “pencil” or “pen” in which one end constitutes a writing portion and the other end constitutes an “eraser” end which, when moved across the display, indicates that portions of the display are to be erased.
  • Other types of input devices such as a mouse, trackball, or the like could be used.
  • a user's own finger could be used to select or indicate portions of the displayed image on a touch-sensitive or proximity-sensitive display. Consequently, the term “user input device” is intended to have a broad definition and encompasses many variations on well-known input devices.
  • FIG. 3 is a flowchart showing simplified steps at a high level of abstraction for implementing a UI architecture according to the principles of this invention upon start up. Processing begins at start block 300 .
  • the system checks to see whether there is a prior existing state. If there is a prior existing state, then that state is used as the current state. If there is no prior existing state, then in step 304 the system retrieves a previously stored default prior state and assigns the value of that default state, which could be, for instance, a default start page, to the current state.
  • the current state is stored as a document that contains links.
  • step 308 the system waits for input from a user.
  • the system determines the nature of the user input in step 310 . Gestures for performing UI actions are discussed below. The nature of the user input could include a combination of the input device, such as a pen, and the gesture performed by the user.
  • the system determines the region of the user input in step 312 , and, based upon the region of the user input, determines an object associated with the region in step 314 .
  • the system determines an action to be performed based upon both the nature of the user input and the object associated with the region of the input in step 316 .
  • the system then performs the action in step 318 .
  • the system then loops back to step 308 to wait for more user input.
  • FIG. 4 is a flow chart showing simplified steps for implementing the “display state” step, step 306 , in FIG. 3 .
  • processing begins at block 400 .
  • the system retrieves a link from the previously saved display state, which may include a list of active or visible links.
  • the retrieved link's display properties are examined in step 404 .
  • a frame is then displayed based on the link's properties.
  • a check is performed to see whether, based upon the link's properties, linked-to content or other information about the linked-to document is to be displayed in the link's display frame.
  • step 410 If such content or information is to be displayed, then the link's target is examined, as depicted in step 410 . Otherwise, there is typically no need to examine the link's target. Then, in step 412 , the link (with or without content or information or both from the linked-to document) is displayed in the display frame. Steps 402 - 412 are repeated until the check for more links in the current display state fails in step 414 . Display state processing then ends in step 416 .
  • PV refers to a personal viewer upon which various aspects of preferred embodiments of a documents-with-links UI according to the principles of this invention are implemented.
  • an example Start Page is displayed on a PV UI 500 that includes the following elements:
  • the display surface 502 This is touch sensitive for both fingertip and pen operations.
  • the touch zones at the four corners 504 , 506 , 508 , and 510 are used to initiate navigation operations such as turning pages and traversing the user's navigational history chain. Labels may be applied to these areas to cue completely näive users how to turn pages the first time they interact with a PV UI.
  • the display margins Documents that present on a PV UI typically show as print-like pages, including margins.
  • the margin space is available for jotting notes and displaying UI-generated features like bookmark tabs and UI shortcuts.
  • a default margin arrangement could be
  • Top margin 512 bookmark tabs. Bookmarks or other objects placed here are associated with the containing document.
  • Bottom margin 514 document and command shortcuts and toolbar tabs. Document shortcuts or other objects placed here are associated with the display surface.
  • Left margin of leftmost display 516 clippings tabs Clippings or other objects placed here are associated with the containing page.
  • Right margin of rightmost display 518 clipping tabs. Clippings or other objects placed here are associated with the containing page.
  • Inner margin to right of spine 600 (see FIG. 6) (dual display PV UI): no default use. Inner margin to left of spine 602 : no default use.
  • Inner margin to left of spine 602 no default use.
  • the margins may be referred to as the bookmark, document, clip, and command margins, respectively.
  • the edge zones could contain command shortcuts and other kinds of links.
  • Command and shortcuts and toolbar tabs could prefer the lower edge zone, and links representing the thumbnail view of documents could prefer the left and upper edge zones.
  • clipping tabs could by default use the left margin of the left page for clippings on the left page and the right margin of the right page for clippings on the right page.
  • the inner margins could remain unused, except if the user puts annotations or other links there.
  • the difference between the margins-only embodiment and the edge-zones embodiment is that, in the margins-only embodiment, the user sees no surrounding frame, and a tap action in the margins has the defaults specified in the list above.
  • the user sees a surrounding frame that is wide enough to provide an edge zone, and taps in the corresponding edge zones have the effects specified in the list above.
  • the default action for taps in each of the document's margins is to insert an embedded annotation (i.e., a user note).
  • the user would insert annotations into a margin not by tapping there but by explicitly invoking a command, such as an Insert Note command available on the margin's popup menu.
  • the display content This is the area inside the page margins where content is displayed.
  • Content may include links that the user can navigate by touching them, as well as user-created highlighting, jottings, and embedded notes and recordings.
  • the note form This is a document template that is used to implement several important PV UI features, including bookmarks, notes, and clippings.
  • the note form is just a blank document that has predefined fields like an entry field for a title, and option boxes to control the note's presentation and behavior (e.g., its color, type, source back link, and anchor spec).
  • the note form can also have a Send button.
  • the built-in documents The PV has a few built-in documents, as listed below. There is nothing “special” about being a built-in document; these are just documents that a PV UI happens to contain by default. The list can be customized as desired. Possible standard built-ins are:
  • Sign-in Page This document provides the form for signing in if and when a PV is set in a secure mode.
  • Start Page An example Start Page is depicted in FIG. 5 . This is the central starting point for the PV UI. From here a user can link to any content, including UI, accessible to the user, for instance, documents on the PV itself as well as in the user's desktop workspace and the Internet.
  • the Start Page may take the form of a personal newsletter.
  • My Documents 520 This is a folder listing of all the documents a user has read, authored, subscribed to, or purchased. It is essentially a catalog of a user's personal library. It supports various views to let a user get an overview of what content the user has and to find the content that the user is looking for. My Documents may have links to other PV content like the Address Book and Guide Book, for instance.
  • FIG. 7 Example pages of an Guide Book are shown in FIG. 7 .
  • the UI is embedded in the Guide Book as links that perform UI functions according to the principles of this invention.
  • the Guide Book includes the Quick Help page of frequently used UI commands.
  • FIG. 8 depicts an example Quick Help page.
  • Map book A book of maps, including the current site map, history map, topic (browsing) map, net neighborhood, physical vicinity (nearby machines), and local machine.
  • Annotations Folder This is a folder of the notes, clippings, bookmarks, jottings, and highlights a user has entered into the user's various documents. A user will typically be able to see each of these forms of annotations in the context of the original document to which they relate. These items are stored as external annotations in the Annotations Folder. A user does not usually view this folder, but instead views one of the following persistent views derived from the Annotations Folder.
  • Clippings Folder A persistent view of the Annotations Folder, showing only clippings.
  • the default view categorizes by document, with more recently read documents ahead of less recently read documents.
  • Notebook This is a blank document where a user can write notes that are not associated with a particular document.
  • the notebook is provided by default because most users would like to have a notebook to write in.
  • the mailbox, calendar, and address book will synchronize with a user's desktop or network-based counterparts.
  • a PV UI can include a single-display and/or a dual-display. Some dual-display UI actions will cause only the rightmost display image to be replaced. When this happens, the original image may or may not be shifted to the left display when this happens.
  • a rule that can be used is that when the UI action was invoked from a link or menu action initiated on the right display, the image is shifted to the left display and the new page opens on the right. If the action was initiated on the left display, the new page simply opens on the right and no shift occurs. The result is that the new page opens on the right and the page from which it was initiated appears on the left.
  • the current display image is simply replaced by the new page.
  • a user can use the Previous and Next functions to flip between the original and new pages.
  • a PV can be held horizontally or vertically. Further, dual-display PV's can treat the two displays as separate pages, or as halves of the same (large) page.
  • the PV can adapt its assignment of case touch zones and display areas to present a consistent geometry to the user regardless of its orientation and display mode. That is, the PV re-maps its definition of things like “upper left corner” and “right margin” to be consistent with its current orientation.
  • PV UI actions will be described as occurring via touch operations using a fingertip or pen.
  • Users can use a fingertip or the pen, also referred to as a stylus, interchangeably.
  • the pen could have three tips: an erasing tip at one end, a highlighting tip at the other, and, by twisting the pen barrel to extend a small shaft, a writing tip.
  • the fingertip may be recognized as a highlighting tip, with a gesture allowing it to erase.
  • the basic touch idioms are:
  • Tap touch and release after a brief time. The action taken depends on where a user tapped. It does not depend on what tip the user is using. The tap would typically last a certain minimum (configurable) time, so that an accidental or glancing touch will be ignored.
  • Hold touch and hold contact
  • the action taken depends on what the user held; usually it opens an object or its context menu. The action does not depend on what tip is being used.
  • the hold time can be a preference parameter.
  • Swipe A swipe is any continuous motion of a tip in contact with the display surface. Swiping will write or erase ink or highlighting, depending on which tip is being used. Swipes are also used to make and extend current selections.
  • Tap-swipe A tap immediately followed by a swipe starting at the same spot.
  • Erase (a jiggling swipe). When done with the fingertip, this is treated as a swipe with the erasing tip. (The motion is the same as erasing with a real pencil eraser). With the pen, a user can just swipe with the erasing tip.
  • a user can automatically extend the range of a highlight, current selection, or erasure by holding the pen or fingertip after swiping a part of the range; that is, swipe part of the range, then hold for auto-complete to take over.
  • the range auto-extends to end of word, sentence or line, paragraph, page, section or chapter, and document, in that order, the longer a user holds.
  • the UI provides feedback on the extent of the selection.
  • the selection auto-extends by cells to the end of a row or column, and then by rows or columns, depending on whether the swipe was across or down.
  • Arbitrary rectangular blocks can be highlighted, selected, or erased by swiping a box shape around the desired area. Selecting the page number of a page selects the whole page.
  • Swipe is hold left or right button and move mouse. Swiping with left button down selects, with right down highlights. There is no need for tap-swipe.
  • Jotting is done via the keyboard (i.e., the user gets text instead of ink)
  • the mouse supports a few other idioms as follows. These and other idioms can be customized.
  • the PV UI renders textual hyperlinks using a visual emphasis similar to the way a prior art browser does. Tapping a link will navigate the user to the linked-to place. The user can use the Previous and Next operations to move along the link chain.
  • the PV UI Start Page can exist as the most previous document page in the chain.
  • a user can also hold a link. Doing this will perform a link-specific action.
  • the default behavior for hyperlinks is to present preview information about where the link will take the user; i.e., document name and document position information and/or a thumbnail view of the linked-to document.
  • Continuing to hold the link could cause the preview information to expand into a navigational map of the link context emanating from the link the user is holding.
  • Popup menu choices could also be presented allowing the user to manipulate the link, such as to change its properties.
  • Another way to navigate is via browser-like Next and Previous commands, performed (in the default assignment) by tapping the PV's lower right and left corners 508 and 510 , respectively. Specifically, these functions navigate a user along the chain of visitations caused by link operations.
  • Page-turning operations are not part of the next/previous chain. For example, if a user opens a book, reads the first ten pages and then does “previous”, the user will return to wherever the user was before the book was opened. The user will not go back to the previous page of the current document (for that, the user can use the previous page operation 504 ).
  • the distinct page-level and navigation-level functions exist because the page forward/back functions 504 and 506 take the place of the traditional scrollbar for scanning within a single document.
  • PV UI users are not limited to the links that are authored into content; they can create their own.
  • the PV UI implements a rich linking model in which links can have source and destination anchor ranges as well as their own properties. Despite the richness of available features, users can create links as easily as they can copy text, and all with a fingertip; the pen is not required.
  • How a link is displayed is controlled by its properties. Conventions and heuristics may be used to assign values to these properties at the time the link is created.
  • a simple example is that when the user taps inside the content of a document, a note is created. This entails creating a note document and then creating a link leading from the spot that was tapped to the new note document. In this case the link properties are set to visualize the link as a note icon.
  • the link is made to visualize as a hotspot over the originally selected text, with the selected text changed (for example) to a blue underlined font.
  • link 700 in FIG. 7 depicts how examining a link's target allows the PV UI to display information about the destination of a link.
  • the destination of link 700 is Earth to the Moon, while the destination of link 102 is the Start Page.
  • a PV UI link property sheet like user content and other UI pages, is implemented as a document. It has several pages. The, first page is the subset of properties that users would most commonly change, presented in a way that less expert users can understand. Subsequent pages provide the full set of advanced properties and options. Typically, only the most expert user (a content author) would ever modify these.
  • the first page may contain just the property comments (a notes field), information about where the link leads to, and a chooser that lets a user choose from a few options on how the hotspot should appear (e.g., emphasized text, button, icon, or thumbnail).
  • the subsequent pages give full access to properties including the source and destination anchor specifications, the visual extent and appearance of the hotspot, and the link behavior options.
  • Each page of the link property sheet is bookmarked so a user can jump directly to it if desired.
  • link property pages encompasses a lot of information, including general properties, source and destination anchors, hotspot characteristics, and link behavior:
  • Link type information describes the semantic nature of the link and how it relates the things being linked. Typically, only authoring and viewing software would ever access the type properties, as they pertain to the organization of the material containing the links.
  • Type indicates whether the link expresses a parent, child, or peer relationship, and whether the destination represents:
  • a document component a figure, table, footnote, or other cross-reference.
  • Source anchor Specifies whether the link is anchored to a character, word, paragraph, image, part of an image, table row, cell, or column, or an arbitrary range of document positions. This parameter is automatically set according to the source selection the user makes when creating the link; this property provides a way to change the anchor.
  • Hotspot Specifies the physical extent and appearance of the hotspot. By default the extent matches that of the anchor, but it can be made bigger or smaller and of arbitrary shape; noncontiguous hotspots are also possible.
  • the default appearance is blue underlined text, but the foreground and background colors and text attributes can be changed.
  • Other appearance options include manifesting the link as an icon, button, thumbnail of the link target, or as an in-place (active) rendering of the link target. Hotspots can also be invisible, which is appropriate for links over GIF images, for instance.
  • Another hotspot option specifies how the link is previewed: any or all of: the name of the target, a thumbnail of it, and/or specific balloon text.
  • Destination anchor Specifies the target of the link and its range.
  • the basic link creation UI results in destination anchors that are a single document position (a “point”) rather than a range.
  • Destination ranges that are not points are a very advanced feature mainly used in implementing certain viewing and collaboration features. For example, if the destination anchor is a range, the viewing software can automatically synthesize appropriate link preview information based on the content of the range.
  • Run Causes the destination content to be executed, with specified run parameters.
  • the target is typically a command or script.
  • other behavior properties could indicate latency periods for updating the display of the linked-to content relative to a change in the linked-to content by, for instance, specifying a link as hot (display updated often), warm (display updated less often than hot), or cold (display not updated). Further behavior properties could set the pre-fetch, refresh, and caching parameters for hot and warm links.
  • the user may completely customize the PV UI (unless authored-in content controls prevent editing). Because there is no distinction between the interface and the content, the kinds of normal editing commands the user might use to alter content can be used to customize the interface.
  • links are not restricted to existing only in the content area of the display. They can exist anywhere. A user could, for example, place a link over a bookmark; the link would take precedence for tap operations, meaning that the bookmark would act as a document-associated shortcut to some other document; whereas a bookmark is normally a link within the current document.
  • the PV UI display may be divided into regions in which different content may be displayed. Unlike prior art UIs, each region may be individually navigated without changing focus or “window” state. Each region may include concurrently active links that may be activated without changing focus. This aspect of the current invention is referred to as page pinning. Page pinning provides access to and interaction with multiple sources of content concurrently, while reducing the complexity associated with both the design and use of the interface.
  • each window runs a separate application that has state information associated with it.
  • state information for a word processor might be that it is currently in insert mode, or replace mode and what the current font is.
  • the user often has to keep in mind which application is running in which window and what the state of that application is to avoid unexpected results.
  • Any display region may include active links.
  • the user can touch anywhere on the screen and will get an appropriate action based on what the user touches. For instance, if a user has a page pinned as depicted in FIG. 9, and both pages being displayed contain links the user can simply touch a link in either page and the link will be activated.
  • page pinning resembles a multi-windowing user interface.
  • dialog boxes may be included in a documents-with-links UI according to the principles of this invention.
  • multi-windowing UIs contain more than one UI.
  • Each window in a multi-windowing UI gets its own UI, with its own state information, such as history information, and its own UI features, such as menu or tool bars.
  • pinned pages like all other content (the UI included), share a single UI having only one set of state information and having a unified navigational history.
  • the unified navigational history is discussed in more detail below.
  • the navigation context is essentially a record of every place a user has ever navigated to and when the user navigated there.
  • the navigation context can be thought of as a map or history of the user's navigation.
  • a visible frame, such as a pinned page is just a view port into a single shared history.
  • the only state associated with a displayed page-pinning frame is an indication of the document page that is currently being displayed.
  • the PV UI contains methods for paging within a document (previous/next) and for traversing chronology (history through back/forward). Attaching properties to links enables a rich model for navigation. For example, holding on a link offers additional information about where that link will lead. Link preview information could be displayed in thumbnail form and further holding could result in a graphical map of the links attached to that prospective destination. Back and forward buttons, by default, display thumbnail views of the pages that tapping that button will lead to.
  • History (which could include all the pages the user has viewed) may be viewed in a number of ways: by time, by appearance, by site, document, section, page, and the like. Since a user's navigation history is saved, the users' sequence may be viewed: as nodes with side tracking branches, as a linear list, or as a combination of most recently viewed pages and last few task categories. For example, a query could perform a multilevel categorization by document id resulting in a hierarchy that represents all the forward navigation paths a user has taken from any given document. By restricting (filtering) this categorization to a particular time frame, the navigation network as it existed at a particular point in time can be shown. Of course, other kinds of views are also possible.
  • the history can be categorized by higher level groupings like web sites or user tasks, with the results presented in alphabetical rather than time order, thus letting users return to a previous location according to the kind of information or activity, as opposed to the time during which, the location was last visited.
  • additional property information may be stored on each navigation record. Accordingly, maintaining the navigation context as a database of navigation records allows support for a rich variety of queries and views.
  • UI is built out of content
  • features used to search text, change viewing options on lists and tables, annotate, and the like all work for UI as well as for user content.
  • the contents of any view such as a view of a filing or command hierarchy, become searchable, sortable, and annotatable.
  • PV UI unlike prior art browsers, maintains a non-linear navigation history. For example, if a user navigates through a set of links then goes “back” several steps, and then navigates through a different set of links, the user is still able to go “back” and then retrace the original path of links they navigated. With prior art browser's this is not possible—recollection of the first set of documents that were “backed” over is lost.
  • the PV UI maintains a nonlinear navigation context that records every place a user has ever navigated to, when in time the user was there, and where the user went to from there.
  • This allows a user to navigate from general content pages into user interface pages, perform interface functionality, and then return to the user's documents without losing what the user's navigational context was before navigating to the user interface pages.
  • this invention automatically removes navigation from the beginning of navigation into UI pages that lead up to performance of some UI functionality so the user's navigational history does not get cluttered with navigation within UI pages.
  • Saving the user's navigation history may also help a user retrace navigational steps that the user would not otherwise be able to remember. For instance, suppose a user does not remember where they were when they viewed some content they liked. If the user remembers where they had been before they viewed that content, then the user can navigate to this prior place and query navigational history for everywhere they had navigated to from that particular location.
  • the PV UI allows a user to interact with content and the UI to make either or both more memorable, via bookmarks, clippings, highlights, overlaid and embedded ink and audio notes.
  • Bookmarks are described further in commonly assigned and currently pending U.S. patent application Ser. No. 09/456,127, entitled Bookmarking and Placemarking a Displayed Document in a Computer System, filed contemporaneously herewith, which is incorporated herein by reference.
  • Example bookmarks 800 and 802 are depicted in FIG. 8 .
  • Ink annotations are described further in commonly assigned and currently pending: U.S. patent application Ser. No. 09/455,805, entitled System and Method for Annotating an Electronic Document Independently Of Its Content, filed contemporaneously herewith, which is incorporated herein by reference.
  • These annotations may be performed with not only different input methods, but adapted to the most convenient or natural one, such as a finger for highlighting, a stylus for writing or doodling, and speech for lengthier commentary.
  • annotations exist apart from the content (as files with links to the content); therefore annotations can be displayed not only layered on the content in appropriate positions within the content, such as, for instance, note 1000 in FIG. 10, but in other locations and visualizations. That is, each of these annotations is available to the user not only in situ, in the content where it was created, but cross-referenced in automatically-created indices which can be manipulated much as described in the Viewing History section above: by time, by appearance, by site, document, section, page, etc. Likewise, annotations could be shared, selectively shared, or kept private with the kind of functionality described in the Collaboration section below.
  • the PV UI can include heuristics, which allow it to offer up most-likely-to-use links to additional material.
  • One case of these is the context menu that appears when the user holds the Next button; in addition to the most recent documents the user has visited subsequent to the current one, the Next menu includes heuristically determined choices of other places the user may wish to visit (for example, documents on a topic related to the current one).
  • Another case is a feature called_an End Page, such as, for instance, End Page 1100 depicted in FIG. 11 .
  • Such an End Page is essentially a summary page at the end of a document or book that offers the user related topics such as “additional works by this author/on this topic/written in the same time period/commented on by these critics” etc.
  • directories such as email, where each message is technically a document, the end page offers threads based on that message/other messages by same author/other text on the same topic, and the like.
  • heuristics could also be used depending on the context. For example, when offering up a set of command choices to a user, the heuristics could be based on analysis of the user's current document context, recently used commands, and commands the user has used most frequently in this and similar contexts in the past. Such heuristics are described further, in the context of navigating to a particular portion of the Guide Book, in commonly assigned and currently pending U.S. patent application Ser. No. 09/456,952, entitled Method and Apparatus for Providing Help and Settings Control to Users of an Electronic Book, filed contemporaneously herewith, which is incorporated herein by reference.
  • the PV VI could also provide commands (actually links) embedded in the page that are related to the kind of material on the page.
  • commands actually links
  • “reply” “reply all,” and “forward” are links so frequently used as to warrant their inclusion directly on the page.
  • the top level of the PV UI provides the user with a Personal Newsletter or Start Page, which is the launch point for many activities.
  • An example Start Page is depicted in FIG. 5 .
  • Highlights might include urgent mail messages, projects, PIM items, documents, news, which could be divided into system-offered default components, such as Messages, Notes, Clippings, and the like.
  • Favorite links that the user wants to keep readily available could also be included. What appears on the Start Page can be both user-configured as well as configured from profile information the PV UI has learned by observing a user's browsing and e-mail reading patterns and the like.
  • Advanced users can perform the same kinds of operations on the interface itself as those performed on content. If the default components on their Start Page are not to their liking, they can delete or alter even system-offered components such as Mail Messages. Or, for instance, if the automatic page number used by the bookmark header is insufficient for recognition, they can alter its text, color or any other property.
  • the PV UI supports the creation of audio clips that can be used for annotation of any displayed document.
  • the clips are based on a timeline model in which audio (or video) recording is a data stream parallel to and synchronized with the material in a document. If the user has changed pages while recording, then the clip when played back will also change the page when the appropriate place in the audio clip is reached.
  • the interface supports both document and page-specific audio noted as well as global recording.
  • the interface is presented with cassette-like controls, including index forward/back and editing.
  • Each clip is stored as an individual document and can be sorted and filtered to present the clips in multiple ways (all audio on a given page, all audio for a given book, audio notes in the order they were recorded, and the like).
  • the audio clip recorder supports intelligent VOX for hands-off note taking.
  • a further feature is the ability to embed audio notes at specific points in the content of a document in a manner similar to creating footnotes. These audio notes can be created and played back by a single tap on the screen at the point where the audio note was (or is to be) inserted. The presence of embedded audio notes is signified by a small icon in the content that is laid out in a manner similar to a footnote symbol.
  • FIG. 8 shows two pages of an example Guide Book.
  • the page on the right, page 9 of 10 includes descriptions of commands, such as the “PIN THIS PAGE” command 800 .
  • the Guide Book describes what the command does. For instance, for “PIN THIS PAGE” the description states that “Tapping on this command will “freeze” a secondary copy of the current page and display it as a floating page over the book.”
  • FIG. 9 shows an example of a pinned page.
  • the text “PIN THIS PAGE” is a link that, when activated, will execute the “PIN THIS PAGE” command on either the most recently selected page or on a page to be selected after activating the “PIN THIS PAGE” command link.
  • the PV UI is constructed as a set of document pages just like a user document or a web site is constructed as set of document pages.
  • This invention puts all of the user's content pages and user interface pages into a single grouping of information that the user can access.
  • This invention leverages well-known browser-like navigational capabilities to allow a user to navigate back and forth between various pages and to put links to pages in favored lists and the like. All of this is leveraged to provide the means by which a user navigates to user interface pages.
  • the PV UI can provide context-specific dynamically synthesized views of links to give the user direct access to relevant UI help pages.
  • the user can search for user interface functionality in the same way the user can search other document pages.
  • pop-up menus and other devices such as permanent links placed on the screen that give the user direct access to UI help information can also be provided.
  • the Guide Book is simply content
  • operations that may be performed on other types of content, such as the Start Page, the UI, and content in general may also be performed on the Guide Book.
  • the way a user gets help for performing a function and the way the user performs the function are the same.
  • the user simply activates a link.

Abstract

A user interface architecture wherein user content and user interface are composed of documents with links. Links have properties that indicate how links should be displayed. Link display may depend upon characteristics of the linked-to frame. Commands are implemented as links that link to command code. The display format of a document page depends upon the path a user navigated in order to get to the displayed page. User content documents and user interface documents are both displayed in a single viewing frame. A non-linear navigation history is maintained such that a user can navigate along a first path, back up using a previous link, navigate along a second path, back up along the second path using the previous link, and re-navigate along the first path again using a next link. Every document page to which a user navigates is saved in the user's navigation history. Users can query their navigation histories and view their navigation histories in various ways. A flexible selection model is supported allowing users to select the object of a command either before or after the command itself is selected. A Guide Book includes command descriptions and active instances of the described commands, implemented as links. Users can access, annotate, and customize the user interface in the same manner in which users access, annotate, and modify user content documents.

Description

TECHNICAL FIELD
This invention relates generally to computer user interface architectures. More particularly, the invention provides a user interface architecture in which both user content and user interface are composed of document pages with links.
BACKGROUND OF THE INVENTION
Many personal computer users find the desktop metaphor of prior art computer user interfaces (“UIs”) confusing and difficult to learn. Accordingly, there is a need for a system that simplifies the user's interaction with the computer by using fewer kinds of user interface controls in a more general way.
Further, the ways in which users interact with information about prior UIs is different than the way the user interacts with content, such as documents, presentations, and the like. For example, in prior art UIs, content and UI information are displayed entirely differently. Content is typically displayed in a particular region or frame of the display. User interface information is never displayed there. Instead, user interface information is displayed in dialog boxes, drop down menus, and tool bars. User content never shows up in dialog boxes, drop down menus, and tool bars. Similarly, users find user content documents and UI help information differently. Accordingly, there is a need for a UI architecture in which the concepts and actions the user must learn are the same for interacting with both content and the UI. Such a unification makes computer software easier and more efficient to use.
Prior art UIs for desktop computers typically require a keyboard and mouse in order for a user to interact with them, and most pen-enabled palmtop computers have cumbersome means of interaction. Therefore, there is a need for more “natural” styles of interacting with a computer by using a minimum number common gestures such as touch, hold, erase, draw or write.
Prior art UI desktop metaphors applied to small form factor devices are typically cluttered and difficult to use. In addition, applications that provide rich functionality are sometimes constrained by the limited ability of a user to navigate menus and dialogs of prior art UIs. For instance, for such applications, the menus and tool bars may get too big, and the help system may get too cumbersome to navigate or search. Accordingly, in addition to the need for a simpler more unified experience for the user of an application, there is also a need to facilitate the uncluttered presentation of user interfaces for applications providing very rich functionality.
Usability data for prior art UIs show that users of multi-windowed systems don't always know which actions will produce results in which window. Therefore, there is a need to reduce the complexity and confusion sometimes caused by multi-windowed user interfaces.
Prior art UIs typically offer limited capabilities for customizing the UI. Accordingly, there is a need for a UI architecture that provides greater flexibility to users, content developers, and third-party software developers by providing broader capabilities for easily customizing the UI. For example, different groups of users may be of different levels of computer skill and have need of different sets of features, and the UI can be customized to better suit their needs.
Users of prior art UIs sometimes become extremely frustrated when their work is lost because their work was not properly saved. Accordingly, there is a need to provide a save-less model, so that users do not need to explicitly save their work.
Users of prior art UIs typically do not have a convenient and seamless way to record notes verbally and to associate notes with particular parts of a document. Accordingly, there is a need to provide rich support for audio note taking with the ability to correlate and synchronize audio and textual material and to review and retrieve audio notes.
Prior art device-to-device and device-to-PC synchronization schemes typically are not seamless and require a great deal of configuration and attention from the user. Accordingly, there is a need to provide automatic and transparent synchronization between a user's computers, such as a handheld computer and a desktop computer.
In prior art UIs, methods for getting help are currently separate from the content and often require completely different interactions than interacting with content. Accordingly, there is a need to make the process of getting help about a function the same as the process for carrying out the function.
Prior art UIs typically have a “single-user model” at the heart of their interface metaphors, which makes sharing content and annotations with other users difficult and non-intuitive. Accordingly, there is a need to make sharing and collaborating on documents easier and more automatic.
SUMMARY OF THE INVENTION
According to various preferred embodiments, the invention includes a user interface architecture in which user content and user interface are composed of documents with links. A link can relate a spot or region in a document with a spot or region in another document, so that touching the link causes the display to navigate to that other document. A link can also relate a spot or region in a document and an active runable object such that when a user activates that link or touches that spot in the document, the associated object is run. Parameters for the execution of the object may be supplied by properties associated with the link. Links, therefore, can act as commands. Links may be to any kind of command code.
A link may manifest in various ways based on the link's properties. Links can look like not only clickable spots, but also fill-in fields and other kinds of well-known and later-developed user interface elements. Alternatively, links can manifest in the containing document a frame displaying the contents of part, or all, of the linked-to document. When links are displayed, in addition to basing the display format of the link on the link's display properties, the link display format may depend upon the characteristics of the linked-to document.
The path a user takes to reach a document typically affects the behavior and presentation of the document. State-like information for displaying a linked-to document page is stored separately from the linked-from and linked-to documents as part of the link's properties. Users access, interact with, and navigate among both user content documents and user interface documents in a unified way, namely, by activating links. Further, both user content document pages and user interface document pages are displayed in a single viewing frame. This unified approach simplifies the user's interaction with both user content and user interface documents by reducing the number of concepts a user must learn in order to access, interact with, and modify both user content documents and the user interface.
A non-linear navigation history is maintained such that a user can navigate along a first path, back up using a previous link an appropriate number of times, navigate along a second path, back up along the second path using the previous link an appropriate number of times, and re-navigate along the first path again using a next link. Every document page to which a user navigates is saved in the user's navigation history. Users can query their navigation histories and view their navigation history in various ways, such as: by time, by appearance, by site, document, section, page, and the like. User can also view their navigation history as nodes with side tracking branches, as a linear list, or as a combination of most recently viewed pages and last few task categories. According to a preferred embodiment, navigation from user content pages through user interface pages that results in a command being executed is automatically removed from the user's view of the navigational history in order to keep the navigational history view uncluttered.
A flexible selection model is supported allowing users to select the object of a command either before or after the command itself is selected. This flexible selection model allows UIs built according to the principles of this invention to scale to small display areas. UIs built according to the principles of this invention also scale well to applications having voluminous and/or complicated user interfaces by facilitating an organized and uncluttered view of the user interface command hierarchy and/or user interface help information for such applications.
Users get at commands by navigating to a page where the desired command is found. In a preferred embodiment, the documents-with-links UI according to the principles of this invention is organized to make frequently used commands a single navigation step away, or through customizations, no steps away. A self-explanatory document, the Guide Book is provided. The Guide Book is a readable manual that users can go through in a logical order, a page at a time, like any conventional user manual. Each command mention, however, is an active command instance that can be invoked in place.
Other features and advantages of the invention will become apparent through the following description, the figures, and the appended claims.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic diagram of a conventional general-purpose digital computing environment that can be used to implement various aspects of the invention.
FIG. 2 shows a conventional tablet and stylus-based computer that can be used to implement various aspects of the invention.
FIG. 3 is a flowchart showing simplified steps at a high level of abstraction for implementing a UI architecture according to the principles of this invention upon start up.
FIG. 4 is a flow chart showing simplified steps for implementing the “display state” step of the flow chart in FIG. 3.
FIG. 5 depicts an example Start Page displayed on a personal viewer according to a preferred embodiment of the invention.
FIG. 6 depicts an example book cover page and table of contents displayed on a personal viewer according to a preferred embodiment of the invention.
FIG. 7 depicts example Guide Book pages displayed on a personal viewer according to a preferred embodiment of the invention.
FIG. 8 depicts example Quick Help pages, one of which is bookmarked, displayed on a personal viewer according to a preferred embodiment of the invention.
FIG. 9 depicts an example of a pinned user content page displayed on a personal viewer according to a preferred embodiment of the invention.
FIG. 10 depicts an example of inked annotation displayed on a personal viewer according to a preferred embodiment of the invention.
FIG. 11 depicts an example End Page displayed on a personal viewer according to a preferred embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION Table of Contents for the Detailed Description Section
Introduction . . .
Clutter-Free And Simple . . .
Content And UI Are Unified . . .
Shortcuts . . .
Scalability To Various Display Sizes And Types . . .
General Concepts Underlying The Documents-With-Links UI Architecture . . .
No Distinction Between Content Documents And UI Documents . . .
Links As Commands And Link Properties . . .
Guide Book . . .
Rich Navigation And Maintaining The User's Navigational History . . .
Flexible Selection Model . . .
Page Display Depends Upon The Link Used To Navigate To The Page . . .
Modeless UI . . .
Creating And Saving Information . . .
Example Hardware Platforms For Implementing Aspects Of The Invention . . .
Example Steps For Implementing Aspects Of The Invention . . .
Preferred Embodiments Of The UI Architecture For a Personal Viewer . . .
Personal Viewer UI Elements . . .
Personal Viewer Display Modes . . .
Gestures For Performing PV UI Actions . . .
Navigating . . .
Hyperlinking . . .
Next And Previous Commands . . .
Scrolling Is Possible . . .
Users Can Create Links . . .
Links . . .
Displaying Links . . .
Link Property Sheet . . .
Customizable UI . . .
Users Can Place Links In UI . . .
Page Pinning . . .
Navigating Documents/Link Properties . . .
Viewing History . . .
Applies To UI . . .
Non-Linear Navigation History . . .
Annotations . . .
Making Annotations . . .
Storing Annotations . . .
Interface Shortcuts And Smarts . . .
Most-Likely-To-Use-Links And Other Heuristics . . .
Frequently Used Links . . .
Start Page . . .
User Can Modify Start Page . . .
Audio Recording And Annotation . . .
Guide Book . . .
Obtain Help And Perform Functions In The Same Way . . .
Concluding Remarks . . .
Introduction
Clutter-free and Simple
The UI architecture of this invention, also referred to herein as a “documents-with-links UI,” supports creation of UI's that have essentially zero clutter, and few concepts to master. In this way, it is a major departure from prior art UI's using a desktop metaphor. The user of a documents-with-links UI according to this invention focuses primarily on content and not on UI appurtenances. Starting with just knowledge of how to page through a document and to follow links, a user can learn how to do any other UI operation. Significantly, the documents-with-links UI works without drop-down menus, toolbars, windows, or other cluttering UI elements (although some of these elements may optionally be made available where they are desired).
Content and UI are Unified
In the UI architecture of this invention there is essentially no distinction between UI pages and content pages. “UI” and “content” are the same thing, and exist in the same navigation space. As described in more detail below, smart next/previous logic and intelligent management of the navigation chain solve technical problems caused by treating “UI” and content as the same thing in a unified navigational context.
Because there is no seam between UI and content, no notion of “dual” spaces, the documents-with-links UI is conceptually simpler for the user than a model that has separate UI and content webs. The one-space model is also more powerful and customizable, as described in more detail below.
Shortcuts
Numerous UI shortcuts and direct manipulations may exist as a configurable layer on top of the documents-with-links UI, so more experienced users can do the most common operations in context, without navigating to UI pages. The user gets the best of terse command access plus the richness of the full browser and answer system for exploring the command set.
The documents-with-links UI uses a web architecture, with UI shortcuts layered on top. A naïve user will typically start by using the documents-with-links UI without the shortcuts—that is, by using the Guide Book to access UI functions. An advanced user will typically be able to perform all common operations via the shortcuts and without resorting to the documents-with-links UI Guide Book as often.
Scalability to Various Display Sizes and Types
Various preferred embodiments of the documents-with-links UI will be explained below in the context of a portable “personal viewer” platform. Nevertheless, the documents-with-links UI is scalable across a wide range of device and display types from desktop computers to laptops to hand-held devices. Accordingly, the documents-with-links UI is intended to be implemented on any type of computing platform. The documents-with-links UI exploits a large screen by being able to show content in a book-like way—two full side-by-side pages, as depicted, for instance, in FIG. 8. UI, being content, takes advantage of the large format of pages and the ability to turn/navigate pages (versus the smaller size of menus/dialog boxes in prior art UIs and their limited or nonexistent provisions for navigation).
At the other end of the spectrum, the UI scales to small screens because of the flexible selection model that allows command selection regions to be initiated either before or after the desired command is chosen. This means, for example, that on a small screen a user can call up a page of command choices that completely obscure the original document due to screen size limitations, choose the command, then return to the user document and then select the region for the command to operate on. Suppose a user wanted to reformat some text, but had not selected the text to be reformatted yet. The user could press a link that indicates that it will reformat text. The UI of this invention will display an indicator on the screen prompting the user to select the text to be reformatted. After selecting the text, the user can finish the reformatting operation by clicking on another link, such as a link that indicates that the selected text will be reformatted. Alternatively, the user could select the region first and then go find and invoke the command. Being able to select the object upon which a command will operate after selecting the command is unlike the selection model of prior art UIs where object selection must precede command selection. The selection model of the documents-with-links UI is discussed in more detail below.
General Concepts Underlying the Documents-with-links UI Architecture
No Distinction Between Content Documents and UI Documents
The basic principle of the documents-with-links UI is that everything the user sees and interacts with is a document. This applies equally to both content and UI. These documents could be implemented in HTML, XML, and the like. There is essentially no difference between content and UI documents. In fact the same document can mix content and UI. Even though some UI elements like context menus and toolbars may be presented in ways that do not look document-like, they are in fact implemented as documents and can be manipulated as such.
The uniform treatment of content and “UI” pages is important for several reasons:
Users only need to deal with one set of navigation controls and conventions, and only one navigation space. Users never need to think about whether they are in content space or UI space.
Users can use the full power of the UI to manipulate the UI itself. For example, users can search, annotate, customize and edit UI pages the same as any content (subject to permissions). Users can select from multiple views for the page being viewed.
The model naturally accommodates dynamic content, including downloaded content, that mixes content and UI on the same page or as part of a network of related pages.
Links as Commands and Link Properties
A link can be an association between two different spots in a collection of document pages. The spots could be two spots on the same page. The spots could be a spot on one page and a spot on another page. Links can have properties that indicate certain things about the link beyond simply the fact that it relates two different places. What a link relates need not necessarily always be displayable pages. A link can relate a spot in a document and an active runable object such that when a user activates that link or touches that spot in the document, the associated object is run. Links, therefore, can act as commands. Links may be to any kind of command code. Scripts are one example. Binary code objects are another example. As a result, pages that have links replace the drop-down menus and dialog boxes of prior art UIs.
A link may manifest in various ways based on the link's properties. Links can look like not only clickable spots, but also fill-in fields and other kinds of well-known and later-developed user interface elements. A document page could have these other kinds of active elements that are really a form of link. Accordingly, activating links goes beyond merely clicking on colored underlined text and can include filling in fields, pressing radio buttons, and the like. Again, pages with links replace prior art dialog boxes having buttons and the like. The links may look like buttons, but the links are simply links.
Even the desktop metaphor of files and folders is expressed as lists of links on a page. Additionally, links have properties that govern their appearance and behavior. For example, a link's properties may dictate that it appear as a blue underscored text string as in prior art browsers, or as a 3D button, as a graphic icon, as a thumbnail image of the content being linked to, or even as an embedded frame that is open on the content being linked to.
As described in more detail below, a user can modify how a link manifests by modifying the link's properties. The ability to control a link's appearance and behavioral properties makes possible rich authoring and customization of both content and the user interface.
Actions in a UI according to the principles of this invention occur by clicking on commands that exist on pages. To the user, a command looks like a link, and in fact it is a link. Specifically, a command is a link whose source anchor is the command hotspot, whose destination anchor is the script or code that implements the command, and whose properties are the command parameters. Some commands may run with canned parameters while others may present users with a form for entering the parameters (for example, the Properties command).
Because a command is a link, it has all the functionality of links. For example, commands can visualize in multiple ways, such as an underlined blue label, a button, an icon, or a graphic image. They can be copied from one place to another, moved, and deleted. Their properties can be manipulated, such as to change their appearance or to preset some or all of their parameters. Commands can also be created the same way that any kind of link is created, via a Link command, which establishes a link between a source and destination that the user specifies; in the case of creating a command link, the destination is an executable object such as a command script or binary. Everything users can do to a link, or to objects in general (since a link is an object), users can do to commands.
Guide Book
Users get at commands by navigating to a page where the desired command is found. The documents-with-links UI is organized to make frequently used commands a single navigation step away, or through customizations, no steps away. Less commonly used commands may take more steps to get to.
The documents-with-links UI includes a self-explanatory document, the Guide Book. This is literally a readable manual that users can go through in a logical order, a page at a time, like any current user manual. The difference is that each command mention is an active command instance that can be invoked in place. A variety of Quick Help pages and indices make it easy to get quick access to sets of commands that are commonly used together, that are logically related, or that are typically used as part of a given scenario. Such Quick Help pages could be assembled dynamically based upon the context of the document or documents being viewed by the user.
Users can also use search to find commands. This could call into play an intelligent user assistant or other conventional help mechanisms when appropriate.
Even if all commands were only one navigational hop away, however, the documents-with-links UI would not be ideal, because users want the most common commands to be zero hops away. Users also want context sensitivity to command presentation, like that provided by conventional context menus. The documents-with-links UI therefore accommodates things like toolbars, context menus, and other UI shortcuts that the user can customize. Like everything else in the documents-with-links UI, shortcuts are implemented as documents with links. The UI shortcuts can be conceptualized as being layered on top of the base documents-with-links UI, yet shortcuts are actually constructed out of the same components that comprise the documents-with-links UI: documents with links.
As a user looks up commands from the Guide Book, the user will learn short cuts so that the more a user interacts with the UI, the less often the user will typically need to navigate to the Guide Book. Therefore, shortcuts will be discussed below, with reference to a preferred embodiment of this UI architecture implemented on a personal viewer, as the shortcuts would appear to a user, because, eventually, shortcuts are what most users would use in their day-to-day activities with the documents-with-links UI.
Rich Navigation and Maintaining the User's Navigational History
When a user performs a navigation action, a record is created of where the user navigated to and at what date and time this occurred. It is thus possible to query this set of records to derive many views of a user's navigational history, including, for instance, a network view, also referred to as a history map view. Ways in which a user's navigational history may be viewed are discussed in more detail below in the Viewing History section.
The history map view is a generalization of the linear history provided by prior art browsers. The history map view makes it easy for a user to revisit a place the user visited previously, with important cues about the context in terms of other places the user was visiting at the time. The Next command works with the branching history too. A user can explore a chain of links, back up, explore a different chain, back up, and Next the user's way down the original chain to get back to where the user was. This is much easier than having to manually re-follow the original chain of links, which would be impossible if the user has forgotten the chain of links they had previously followed.
This is an important extension of the prior art browsing metaphor. Unlike prior art browser UIs with their linear navigation chain, the documents-with-links UI doesn't forget all the twists and turns of where the user has been just because the user backs up and proceeds in a different direction. The documents-with-links UI stores not only where the user has been, but also the path(s) the user took to get there. The user can use the history map and/or the Next/Previous commands to get back there again.
The Next function works in this network-style navigational context by using heuristics to pick which path forward the user most likely intends. The most basic rule is to pick the forward path along which the user backed to the current node. Other rules provide additional intelligence to account for a user's known navigational patterns, such as whether the user got to the current node by navigating back by individual pages or by groupings of pages (such as by site), or by linking from a parent to a child. The Next function could include options to present a user with a list of forward choices, textually and/or as a map in which the user could zoom into desired areas. In this way, the user can control which branch to take, if the user is not satisfied with the documents-with-links UI's selection.
Part of what makes the navigation and context trimming heuristics possible is built-in knowledge of logical levels of information grouping. For example, the documents-with-links UI can include knowledge of collections of pages making up sections and chapters, of collections of sections and chapters making up a document, of collections of documents making up web sites, and so on. The same is true for the layers of command finding and invocation. Such knowledge of semantic clustering helps guide decisions about popping contexts and for presenting the user with reasonable choices about points to jump to along the Next/Previous chain.
A problem with treating content and UI as part of the same navigation space is that the user's navigation chain gets cluttered with UI-related pages. The documents-with-links UI solves that through intelligent management of the navigation context, and by making that context a true network, not just a linear chain.
Specifically, when a user navigates from one place to another, a new branch in the navigation chain is started. So, if a user's context is currently B in the existing chain of document pages A-B-C, and the user navigates to D, then the new context is D. D might be a UI page the user navigated to from document B. When the user clicks a command on page D, the command executes and removes D from the navigation context. Thus, after finding and executing the command, the user's navigation context is restored to document page B.
To find a needed command the user might have to navigate along a chain from D to several other pages in the Guide Book, resulting in a chain of several steps branching off from B. When the user finally picks a command, the documents-with-links UI knows what to act on, and what to remove from the navigation context as follows. Commands operate on the current selection, and, in general, remove the navigation nodes that lie on the branch leading from the current selection to the command. Further, additional heuristics may be used for unusual cases.
Current selections in the documents-with-links UI are similar to current selections in prior art desktop UIs, but there are differences because the documents-with-links UI deals with a network of active documents that are different than a desktop of active windows. The two schemes are similar in that every document can have a single, possibly disjoint, selected area. The schemes differ in that the documents-with-links UI can't use the idea of the current focus to decide what selection a command should operate on. In prior art desktop UIs, the document the user wants to operate on typically has the current focus, and all UI elements implicitly reference this focus. In the documents-with-links UI world, the user may have navigated several hops away from the document the user wants to operate on, as the user looked for the desired command, so, in the documents-with-links UI, focus doesn't disambiguate anything.
Therefore, in accordance with a preferred embodiment, instead of the current selection being the one whose document has the focus, the current selection is the most recently selected area. All commands that are configured to operate on selections will operate on that most recently selected area. Having executed, they will trim the navigation context at the branch point that leads from the current selection to the command itself.
The benefit is that users are free to link into the web of UI pages, exploring them as necessary to find the desired command, and then to invoke it. The act of doing so will end up trimming all the UI navigation from the context, leaving the user back where the user was before navigating to UI pages. Note that depending on the length and content of the navigational path between the command and recent selection, the UI may show the user the target and prompt the user to confirm before proceeding.
Note that if no selection exists when a command is executed, then the next selection the user establishes will be considered to be the most recent selection for purposes of determining the command target. In this case, after the user makes the selection, command buttons will be presented in context with the selection by which the user can confirm or cancel execution of the previously selected command. Of course, other suitable methods of determining what selection to operate on are also possible. For instance, one such method is to allow only a single selection to be extant at a time. That is, any time a new selection is initiated, any prior selection is cancelled (un-selected). Another method is to choose what selection to operate on by doing a backwards scan in time order through the navigation context until an active selection is found. In most cases envisioned by the inventors, this latter solution produces the same result as the first one discussed; i.e., the most recent selection will be found.
The effect of the algorithm for trimming the navigational context is typically to isolate and remove the branch whose purpose was to find the command that was just executed. Trimming the navigational context of navigation to UI pages does not always occur, however. For example, an Apply command for property setting could leave the property form active and not trim the navigation context. Of course, different commands may choose to operate on the navigation context in different ways. Nevertheless, a couple standard ways will typically cover most of the cases.
Flexible Selection Model
The documents-with-links UI does not require users to make a selection before invoking a command. Users are free to select first and then click a command, or click the command first and then make a selection. If an appropriate selection does not exist when a command is invoked, the user is prompted to make a selection at that time. The selection mechanism and command verbs are designed to give users a lot of latitude about the order in which they do things when carrying out commands. Besides fitting better to users' personal habits, this makes it harder for users to do something “wrong,” such as inadvertently applying formatting to text other than the text the user wants to reformat.
Page Display Depends Upon the Link Used to Navigate to the Page
The documents-with-links UI may display the same page of a document differently depending upon which link navigated a user to the page. Suppose the user wants to fill in the TO: field of an e-mail message. In this situation, the user wants to open the address book and make possibly several choices. To accomplish this within the document/navigation metaphor, forms could have special-purpose chooser controls where this provides a good shortcut for the most common choices. But the chooser UI should also make it possible to leverage the full power of the navigation, browsing, viewing, and search UI that is available in list-oriented documents like file folders and the address book. Making a choice from such a list should be a matter of just navigating to that list as a user would in any other context and making the choice.
For the address book example, the documents-with-links UI provides a link to the address book that is associated with the input field. The documents-with-links UI makes the link from an input field to its choice document, the address book in this example, be a command with navigation behavior, as opposed to being an ordinary link. This command navigates the user to the document the user needs to choose from and captures anything the user selects. After selecting the addresses the user wants, the user can simply navigate back to the send form where the TO: field is. Alternatively, the user could close the address book or use an OK command, either of which would return the user automatically. There is nothing to save, because all choice state is captured as the user proceeds. If there is a change in plan, the user could simply cancel the current selection, or clear the TO: field when the user returns.
If the user later wants to change the TO: field choices, the user may click the TO: field link again, and the user is taken back to the address book, with all the current choices still highlighted. The current choices are highlighted because the command that takes the user to the address book picks up the TO: state and paints the required selection regions.
To facilitate making selections in scenarios like this address book example, an additional facility is provided. The command which presents the document to choose from can also cause checkboxes to appear next to each entry in the document. Rather than manually selecting items in the document, the user can check or uncheck the checkboxes. This causes the associated entry to be selected or unselected, respectively.
In this address book example, the user is accessing a standard document, the address book, and the normal multiple selection idiom to make and change the user's TO: field fill-in choices. The user has the full power of the normal UI for navigating, viewing, and searching, the address book and can navigate to other documents containing addresses where the user can make other choices. Note that because the selection state is associated with the path the user took to reach the address book, the user will see the TO: items highlighted in the address book only if the user links to the address book (or successor nodes) via the TO: field in question. Thus, the existence of an active To: field does not interfere with other uses of the address book or with other active To: fields.
This is a significant principle of the documents-with-links UI: the path a user takes to reach a document typically affects the behavior and presentation of the document. This is a way to achieve state-like behavior without requiring special modes or UI mechanisms like dialogs. The implementation of chooser fields is one of the more important uses of this concept.
Modeless UI
Unlike prior art UI's, the documents-with-links UI is essentially modeless. For example, a user could be involved in filling out a form for carrying out a UI operation such as creating a formatting style for a table. In the middle of doing this the user could navigate away from this UI form and get engaged in some other UI operation, such as filling out another form for a different purpose, and then, at any time, navigate back to the original, incomplete form. There is no restriction on the number of such incomplete operations that can be in progress simultaneously. Nor is there any limitation on switching away from such incomplete operations. This is unlike the prior art, where complex operations, typically performed via dialogs, must generally be complete or cancelled before the user switches to another activity. Unlike prior UI's, the user of a documents-with-links UI is typically not restricted from interrupting one operation to initiate another, or several others, nor would such an interruption cause the user to lose work already performed in partially completing the first operation.
Creating and Saving Information
Another architectural topic central to the documents-with-links UI is the model for creating and saving information. Any time a user creates something new, the user is creating a new document and linking it into a context. For an object inserted into an existing document, such as an embedded annotation, the user is linking it into the document that is to contain it, with link properties implicitly set to make the object visualize in place (OLE-style embedding). Physically, the object is stored as a child within the parent document's container.
For new, standalone objects, like a new word processing document, the object is instead added to the current navigation context, as if the user had done a Next to it from wherever the user was when the user issued the New command. Physically, the object may be stored in the user's sea of “free space” in a hidden system folder, not part of any folder the user is aware of, unless and until the user chooses to file it somewhere.
The user does not need to put documents into a filing hierarchy or save them. This is because the documents-with-links UI stores all navigational history. Accordingly, users can find the documents they create by viewing or searching their history map. A user could file a document into a folder as an optional step, using a Save As command or by manually creating a link in the folder that leads to the document (the Save As command could be simply a shortcut for creating such a link). Also, the user could use Save/Save As to update or create versions of a document in the filing hierarchy as desired.
Example Hardware Platforms for Implementing Aspects of the Invention
FIG. 1 is a schematic diagram of a conventional general-purpose digital computing environment that can be used to implement various aspects of the invention. Computer 100 includes a processing unit 110, a system memory 120, and a system bus 130 that couples various system components including the system memory to the processing unit 110. The system bus 130 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory includes read only memory (ROM) 140 and random access memory (RAM) 150.
A basic input/output system 160 (BIOS), containing the basic routines that help to transfer information between elements within the computer 100, such as during start-up, is stored in ROM 140. Computer 100 also includes a hard disk drive 170 for reading from and writing to a hard disk (not shown), a magnetic disk drive 180 for reading from or writing to a removable magnetic disk 190, and an optical disk drive 191 for reading from or writing to a removable optical disk 192 such as a CD ROM or other optical media. The hard disk drive 170, magnetic disk drive 180, and optical disk drive 191 are connected to the system bus 130 by a hard disk drive interface 192, a magnetic disk drive interface 193, and an optical disk drive interface 194, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the personal computer 100. It will be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs), and the like, may also be used in the example operating environment.
A number of program modules can be stored on the hard disk, magnetic disk 190, optical disk 192, ROM 140 or RAM 150, including an operating system 195, one or more application programs 196, other program modules 197, and program data 198. A user can enter commands and information into the computer 100 through input devices such as a keyboard 101 and pointing device 102. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 110 through a serial port interface 106 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). A monitor 107 or other type of display device is also connected to the system bus 130 via an interface, such as a video adapter 108. In addition to the monitor, personal computers typically include other peripheral output devices (not shown), such as speakers and printers.
The computer 100 can operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 109. Remote computer 109 can be a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to computer 100, although only a memory storage device 111 has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include a local area network (LAN) 112 and a wide area network (WAN) 113. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet. When used in a LAN networking environment, the computer 100 is connected to the local network 112 through a network interface or adapter 114. When used in a WAN networking environment, the personal computer 100 typically includes a modem 115 or other means for establishing a communications over the wide area network 113, such as the Internet. The modem 115, which may be internal or external, is connected to the system bus 130 via the serial port interface 106. In a networked environment, program modules depicted relative to the personal computer 100, or portions thereof, may be stored in the remote memory storage device.
It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used. The existence of any of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like is presumed, and the system can be operated in a client-server configuration to permit a user to retrieve web pages from a web-based server. Any of various conventional web browsers can be used to display and manipulate data on web pages.
FIG. 2 shows a tablet and stylus computer that can be used in accordance with various aspects of the present invention. Any or all of the features, subsystems, and functions in the system of FIG. 1 can be included in the computer of FIG. 2. Computer 201 includes a large display surface 202 (e.g., a flat panel display) on which a plurality of windows 203 is displayed. Using stylus 204, a user can select, highlight, and write on the display area. Computer 201 interprets marks made using stylus 204 in order to manipulate data, enter text, and execute conventional computer application tasks such as spreadsheets, word processing programs, and the like. One commercially available tablet and stylus computer incorporating many of these features is the Stylistic 2300 computer sold by Fujitsu Personal Systems, Inc., of Santa Clara, Calif.
A stylus could be equipped with buttons or other features to augment its selection capabilities. In one embodiment, a stylus could be implemented as a “pencil” or “pen” in which one end constitutes a writing portion and the other end constitutes an “eraser” end which, when moved across the display, indicates that portions of the display are to be erased. Other types of input devices such as a mouse, trackball, or the like could be used. Additionally, a user's own finger could be used to select or indicate portions of the displayed image on a touch-sensitive or proximity-sensitive display. Consequently, the term “user input device” is intended to have a broad definition and encompasses many variations on well-known input devices.
Example Steps for Implementing Aspects of the Invention
FIG. 3 is a flowchart showing simplified steps at a high level of abstraction for implementing a UI architecture according to the principles of this invention upon start up. Processing begins at start block 300. In step 302, the system checks to see whether there is a prior existing state. If there is a prior existing state, then that state is used as the current state. If there is no prior existing state, then in step 304 the system retrieves a previously stored default prior state and assigns the value of that default state, which could be, for instance, a default start page, to the current state. In a preferred embodiment, like other content and UI, the current state is stored as a document that contains links.
In step 308, the system waits for input from a user. Upon user input, the system determines the nature of the user input in step 310. Gestures for performing UI actions are discussed below. The nature of the user input could include a combination of the input device, such as a pen, and the gesture performed by the user. The system then determines the region of the user input in step 312, and, based upon the region of the user input, determines an object associated with the region in step 314. The system then determines an action to be performed based upon both the nature of the user input and the object associated with the region of the input in step 316. The system then performs the action in step 318. The system then loops back to step 308 to wait for more user input.
FIG. 4 is a flow chart showing simplified steps for implementing the “display state” step, step 306, in FIG. 3. Referring to FIG. 4, processing begins at block 400. In step 402, the system retrieves a link from the previously saved display state, which may include a list of active or visible links. The retrieved link's display properties are examined in step 404. In step 406, a frame is then displayed based on the link's properties. In step 408, a check is performed to see whether, based upon the link's properties, linked-to content or other information about the linked-to document is to be displayed in the link's display frame. If such content or information is to be displayed, then the link's target is examined, as depicted in step 410. Otherwise, there is typically no need to examine the link's target. Then, in step 412, the link (with or without content or information or both from the linked-to document) is displayed in the display frame. Steps 402-412 are repeated until the check for more links in the current display state fails in step 414. Display state processing then ends in step 416.
Preferred Embodiments of the UI Architecture for a Personal Viewer
Various preferred embodiments of the documents-with-links UI of this invention are described herein as implemented on a personal viewer (hereinafter the term “PV” refers to a personal viewer upon which various aspects of preferred embodiments of a documents-with-links UI according to the principles of this invention are implemented).
Personal Viewer UI Elements
Referring now to FIG. 5, an example Start Page is displayed on a PV UI 500 that includes the following elements:
The display surface 502. This is touch sensitive for both fingertip and pen operations. The touch zones at the four corners 504, 506, 508, and 510 are used to initiate navigation operations such as turning pages and traversing the user's navigational history chain. Labels may be applied to these areas to cue completely näive users how to turn pages the first time they interact with a PV UI.
The display margins. Documents that present on a PV UI typically show as print-like pages, including margins. The margin space is available for jotting notes and displaying UI-generated features like bookmark tabs and UI shortcuts. A default margin arrangement could be
Top margin 512: bookmark tabs. Bookmarks or other objects placed here are associated with the containing document.
Bottom margin 514: document and command shortcuts and toolbar tabs. Document shortcuts or other objects placed here are associated with the display surface.
Left margin of leftmost display 516: clippings tabs Clippings or other objects placed here are associated with the containing page.
Right margin of rightmost display 518: clipping tabs. Clippings or other objects placed here are associated with the containing page.
Inner margin to right of spine 600 (see FIG. 6) (dual display PV UI): no default use. Inner margin to left of spine 602: no default use.
Inner margin to left of spine 602: no default use.
In the above list, examples of other objects that may be present in any of the margins are user annotations.
A user can reassign which functions are associated with which margin. Accordingly, the margins may be referred to as the bookmark, document, clip, and command margins, respectively. Of course, other suitable default margin arrangements could also be used. For instance, there could be a zone around the entire document that is outside the document called the edge zone or zones. The edge zones could contain command shortcuts and other kinds of links. Command and shortcuts and toolbar tabs could prefer the lower edge zone, and links representing the thumbnail view of documents could prefer the left and upper edge zones. Because a page margin would not be needed for carrying command links, clipping tabs could by default use the left margin of the left page for clippings on the left page and the right margin of the right page for clippings on the right page. The inner margins could remain unused, except if the user puts annotations or other links there.
The difference between the margins-only embodiment and the edge-zones embodiment is that, in the margins-only embodiment, the user sees no surrounding frame, and a tap action in the margins has the defaults specified in the list above. In the edge zones embodiment, the user sees a surrounding frame that is wide enough to provide an edge zone, and taps in the corresponding edge zones have the effects specified in the list above. In this latter embodiment, the default action for taps in each of the document's margins is to insert an embedded annotation (i.e., a user note). In the margins-only embodiment, the user would insert annotations into a margin not by tapping there but by explicitly invoking a command, such as an Insert Note command available on the margin's popup menu.
The display content. This is the area inside the page margins where content is displayed. Content may include links that the user can navigate by touching them, as well as user-created highlighting, jottings, and embedded notes and recordings.
The note form. This is a document template that is used to implement several important PV UI features, including bookmarks, notes, and clippings. The note form is just a blank document that has predefined fields like an entry field for a title, and option boxes to control the note's presentation and behavior (e.g., its color, type, source back link, and anchor spec). The note form can also have a Send button.
The built-in documents. The PV has a few built-in documents, as listed below. There is nothing “special” about being a built-in document; these are just documents that a PV UI happens to contain by default. The list can be customized as desired. Possible standard built-ins are:
Sign-in Page. This document provides the form for signing in if and when a PV is set in a secure mode.
Start Page. An example Start Page is depicted in FIG. 5. This is the central starting point for the PV UI. From here a user can link to any content, including UI, accessible to the user, for instance, documents on the PV itself as well as in the user's desktop workspace and the Internet. The Start Page may take the form of a personal newsletter.
My Documents 520. This is a folder listing of all the documents a user has read, authored, subscribed to, or purchased. It is essentially a catalog of a user's personal library. It supports various views to let a user get an overview of what content the user has and to find the content that the user is looking for. My Documents may have links to other PV content like the Address Book and Guide Book, for instance.
Guide Book. This is both the PV's help document and the PV's user interface. Example pages of an Guide Book are shown in FIG. 7. The UI is embedded in the Guide Book as links that perform UI functions according to the principles of this invention. The Guide Book includes the Quick Help page of frequently used UI commands. FIG. 8 depicts an example Quick Help page.
Map book. A book of maps, including the current site map, history map, topic (browsing) map, net neighborhood, physical vicinity (nearby machines), and local machine.
Annotations Folder. This is a folder of the notes, clippings, bookmarks, jottings, and highlights a user has entered into the user's various documents. A user will typically be able to see each of these forms of annotations in the context of the original document to which they relate. These items are stored as external annotations in the Annotations Folder. A user does not usually view this folder, but instead views one of the following persistent views derived from the Annotations Folder.
Clippings Folder. A persistent view of the Annotations Folder, showing only clippings. The default view categorizes by document, with more recently read documents ahead of less recently read documents.
Bookmarks Folder. Same as the Clippings Folder, but showing only bookmarks.
The Notes Folder. Same as the Clippings Folder, but showing only notes.
Notebook. This is a blank document where a user can write notes that are not associated with a particular document. The notebook is provided by default because most users would like to have a notebook to write in.
The mailbox, calendar, and address book. In a preferred embodiment, these will synchronize with a user's desktop or network-based counterparts.
Personal Viewer Display Modes
A PV UI can include a single-display and/or a dual-display. Some dual-display UI actions will cause only the rightmost display image to be replaced. When this happens, the original image may or may not be shifted to the left display when this happens. A rule that can be used is that when the UI action was invoked from a link or menu action initiated on the right display, the image is shifted to the left display and the new page opens on the right. If the action was initiated on the left display, the new page simply opens on the right and no shift occurs. The result is that the new page opens on the right and the page from which it was initiated appears on the left.
For a single-display PV, the current display image is simply replaced by the new page. A user can use the Previous and Next functions to flip between the original and new pages.
A PV can be held horizontally or vertically. Further, dual-display PV's can treat the two displays as separate pages, or as halves of the same (large) page. The PV can adapt its assignment of case touch zones and display areas to present a consistent geometry to the user regardless of its orientation and display mode. That is, the PV re-maps its definition of things like “upper left corner” and “right margin” to be consistent with its current orientation.
Gestures for Performing PV UI Actions
While other suitable input equipment could also be used, PV UI actions will be described as occurring via touch operations using a fingertip or pen. Users can use a fingertip or the pen, also referred to as a stylus, interchangeably. The pen could have three tips: an erasing tip at one end, a highlighting tip at the other, and, by twisting the pen barrel to extend a small shaft, a writing tip. The fingertip may be recognized as a highlighting tip, with a gesture allowing it to erase.
The basic touch idioms are:
Tap (touch and release after a brief time). The action taken depends on where a user tapped. It does not depend on what tip the user is using. The tap would typically last a certain minimum (configurable) time, so that an accidental or glancing touch will be ignored.
Hold (touch and hold contact). The action taken depends on what the user held; usually it opens an object or its context menu. The action does not depend on what tip is being used. The hold time can be a preference parameter.
Swipe. A swipe is any continuous motion of a tip in contact with the display surface. Swiping will write or erase ink or highlighting, depending on which tip is being used. Swipes are also used to make and extend current selections.
Tap-swipe. A tap immediately followed by a swipe starting at the same spot.
This causes the pen or fingertip to start a current selection region. Either the writing or highlighting tip can be used. Swiping starting at the current edit cursor location (i.e., the tap is optional when starting on top of the edit cursor) can also draw a selection.
Erase (a jiggling swipe). When done with the fingertip, this is treated as a swipe with the erasing tip. (The motion is the same as erasing with a real pencil eraser). With the pen, a user can just swipe with the erasing tip.
A user can automatically extend the range of a highlight, current selection, or erasure by holding the pen or fingertip after swiping a part of the range; that is, swipe part of the range, then hold for auto-complete to take over. The range auto-extends to end of word, sentence or line, paragraph, page, section or chapter, and document, in that order, the longer a user holds. The UI provides feedback on the extent of the selection. In tables, the selection auto-extends by cells to the end of a row or column, and then by rows or columns, depending on whether the swipe was across or down. Arbitrary rectangular blocks can be highlighted, selected, or erased by swiping a box shape around the desired area. Selecting the page number of a page selects the whole page.
Typically, whatever a user can do with a pen, the user can do with a fingertip, except write ink. While other mapping are of course possible, an example set of keyboard/mouse idioms for the pen idioms and pen tips is:
Tap is left-click
Hold is hold left button
Swipe is hold left or right button and move mouse. Swiping with left button down selects, with right down highlights. There is no need for tap-swipe.
Erase is hold both buttons and move mouse
Jotting is done via the keyboard (i.e., the user gets text instead of ink)
The mouse supports a few other idioms as follows. These and other idioms can be customized.
Right click brings up a context menu, the same one that a hold operation at this location would.
Mouse wheel does page forward and back operations.
Clicking the mouse wheel/third button links to the Quick Help page.
Navigating
Hyperlinking
One way to navigate is by hyperlinking. The PV UI renders textual hyperlinks using a visual emphasis similar to the way a prior art browser does. Tapping a link will navigate the user to the linked-to place. The user can use the Previous and Next operations to move along the link chain. The PV UI Start Page can exist as the most previous document page in the chain.
A user can also hold a link. Doing this will perform a link-specific action. The default behavior for hyperlinks is to present preview information about where the link will take the user; i.e., document name and document position information and/or a thumbnail view of the linked-to document. Continuing to hold the link could cause the preview information to expand into a navigational map of the link context emanating from the link the user is holding. Popup menu choices could also be presented allowing the user to manipulate the link, such as to change its properties.
When the user releases a held link no navigation occurs. The user can tap the link to make it navigate. If holding the link opened a navigation map, the map will persist for a short time after the user lets go. This gives the user a chance to tap a spot on the map to go there, or to hold a spot in order to preview and then to expand the map context around that point.
Next and Previous Commands
Another way to navigate is via browser-like Next and Previous commands, performed (in the default assignment) by tapping the PV's lower right and left corners 508 and 510, respectively. Specifically, these functions navigate a user along the chain of visitations caused by link operations.
Page-turning operations are not part of the next/previous chain. For example, if a user opens a book, reads the first ten pages and then does “previous”, the user will return to wherever the user was before the book was opened. The user will not go back to the previous page of the current document (for that, the user can use the previous page operation 504). The distinct page-level and navigation-level functions exist because the page forward/back functions 504 and 506 take the place of the traditional scrollbar for scanning within a single document.
Scrolling is Possible
Even though the PV UI is page oriented, there are times when a scroll-oriented presentation is the only reasonable display choice. The PV UI supports this by displaying traditional scroll bars when stream-oriented presentation is required. The user may touch the scroll bars to perform the scrolling actions. This looks and works much like conventional scroll bars.
Users can Create Links
PV UI users are not limited to the links that are authored into content; they can create their own. The PV UI implements a rich linking model in which links can have source and destination anchor ranges as well as their own properties. Despite the richness of available features, users can create links as easily as they can copy text, and all with a fingertip; the pen is not required.
Links
Displaying Links
How a link is displayed is controlled by its properties. Conventions and heuristics may be used to assign values to these properties at the time the link is created. A simple example is that when the user taps inside the content of a document, a note is created. This entails creating a note document and then creating a link leading from the spot that was tapped to the new note document. In this case the link properties are set to visualize the link as a note icon. As another example if the user highlights some text in a user document and then chooses the “Make link command”, followed by the steps to complete that command, the link is made to visualize as a hotspot over the originally selected text, with the selected text changed (for example) to a blue underlined font. Unless a user changes a link's display properties, once these property-setting decisions are made, the link will typically continue to be displayed in the same way. Depending upon a link's properties, when the link is displayed, content of the linked-to document, or other information about the linked-to document, may be displayed in a frame in the linked-from document. For instance, two example previous links, previous link 700 in FIG. 7 and previous link 1102 in FIG. 11, depict how examining a link's target allows the PV UI to display information about the destination of a link. For instance, the destination of link 700 is Earth to the Moon, while the destination of link 102 is the Start Page.
Link Property Sheet
A PV UI link property sheet, like user content and other UI pages, is implemented as a document. It has several pages. The, first page is the subset of properties that users would most commonly change, presented in a way that less expert users can understand. Subsequent pages provide the full set of advanced properties and options. Typically, only the most expert user (a content author) would ever modify these.
For example, the first page may contain just the property comments (a notes field), information about where the link leads to, and a chooser that lets a user choose from a few options on how the hotspot should appear (e.g., emphasized text, button, icon, or thumbnail).
The subsequent pages give full access to properties including the source and destination anchor specifications, the visual extent and appearance of the hotspot, and the link behavior options. Each page of the link property sheet is bookmarked so a user can jump directly to it if desired.
Together, the set of link property pages encompasses a lot of information, including general properties, source and destination anchors, hotspot characteristics, and link behavior:
General properties. These include the type and file system properties of the link. Link type information describes the semantic nature of the link and how it relates the things being linked. Typically, only authoring and viewing software would ever access the type properties, as they pertain to the organization of the material containing the links. Type indicates whether the link expresses a parent, child, or peer relationship, and whether the destination represents:
A document component: a figure, table, footnote, or other cross-reference.
The next or previous “page” (in the web sense) of the current document/topic.
The next or previous document/topic in an authored web of documents/topics.
Something not part of the current document/topic: a comment or hyperlink.
Source anchor. Specifies whether the link is anchored to a character, word, paragraph, image, part of an image, table row, cell, or column, or an arbitrary range of document positions. This parameter is automatically set according to the source selection the user makes when creating the link; this property provides a way to change the anchor.
Hotspot. Specifies the physical extent and appearance of the hotspot. By default the extent matches that of the anchor, but it can be made bigger or smaller and of arbitrary shape; noncontiguous hotspots are also possible. For hotspots on text, the default appearance is blue underlined text, but the foreground and background colors and text attributes can be changed. Other appearance options include manifesting the link as an icon, button, thumbnail of the link target, or as an in-place (active) rendering of the link target. Hotspots can also be invisible, which is appropriate for links over GIF images, for instance. Another hotspot option specifies how the link is previewed: any or all of: the name of the target, a thumbnail of it, and/or specific balloon text.
Destination anchor. Specifies the target of the link and its range. The basic link creation UI results in destination anchors that are a single document position (a “point”) rather than a range. Destination ranges that are not points are a very advanced feature mainly used in implementing certain viewing and collaboration features. For example, if the destination anchor is a range, the viewing software can automatically synthesize appropriate link preview information based on the content of the range.
Behavior. Specifies the action to take on-tap and hold operations. Choices include
Navigate. Goes to the link destination.
Preview. Pops up navigational preview information as explained above.
Run. Causes the destination content to be executed, with specified run parameters. The target is typically a command or script.
Additionally, for links set to appear as thumbnails or in-place renderings, other behavior properties could indicate latency periods for updating the display of the linked-to content relative to a change in the linked-to content by, for instance, specifying a link as hot (display updated often), warm (display updated less often than hot), or cold (display not updated). Further behavior properties could set the pre-fetch, refresh, and caching parameters for hot and warm links.
Customizable UI
The user may completely customize the PV UI (unless authored-in content controls prevent editing). Because there is no distinction between the interface and the content, the kinds of normal editing commands the user might use to alter content can be used to customize the interface.
Users can Place Links in UI
For instance, links are not restricted to existing only in the content area of the display. They can exist anywhere. A user could, for example, place a link over a bookmark; the link would take precedence for tap operations, meaning that the bookmark would act as a document-associated shortcut to some other document; whereas a bookmark is normally a link within the current document.
Page Pinning
The PV UI display may be divided into regions in which different content may be displayed. Unlike prior art UIs, each region may be individually navigated without changing focus or “window” state. Each region may include concurrently active links that may be activated without changing focus. This aspect of the current invention is referred to as page pinning. Page pinning provides access to and interaction with multiple sources of content concurrently, while reducing the complexity associated with both the design and use of the interface.
In prior art user interfaces, each window runs a separate application that has state information associated with it. For instance the state information for a word processor might be that it is currently in insert mode, or replace mode and what the current font is. The user often has to keep in mind which application is running in which window and what the state of that application is to avoid unexpected results.
In the PV UI, unlike prior art user interfaces, there is no notion of a selected one of multiple windows having the current “focus.” Any display region may include active links. The user can touch anywhere on the screen and will get an appropriate action based on what the user touches. For instance, if a user has a page pinned as depicted in FIG. 9, and both pages being displayed contain links the user can simply touch a link in either page and the link will be activated.
Superficially, page pinning resembles a multi-windowing user interface. The same may be said for dialog boxes that may be included in a documents-with-links UI according to the principles of this invention. Nevertheless, unlike this invention, multi-windowing UIs contain more than one UI. Each window in a multi-windowing UI gets its own UI, with its own state information, such as history information, and its own UI features, such as menu or tool bars. According to the principles of this invention, pinned pages, like all other content (the UI included), share a single UI having only one set of state information and having a unified navigational history. There are no separate UI controls, such as menu bars or tool bars, for the separate concurrently displayed pages. The unified navigational history is discussed in more detail below.
When the user has pinned a page and is viewing two pages side-by-side, the user essentially has two different view ports into a single navigation context. A set of documents exists in a navigation context. The navigation context is essentially a record of every place a user has ever navigated to and when the user navigated there. The navigation context can be thought of as a map or history of the user's navigation. A visible frame, such as a pinned page is just a view port into a single shared history. The only state associated with a displayed page-pinning frame is an indication of the document page that is currently being displayed.
Page pinning is described further in commonly assigned U.S. patent application Ser. No. 09/556,865, entitled Method and Apparatus for Displaying Multiple Contexts In Electronic Documents, filed contemporaneously herewith, which is incorporated herein by reference.
Navigating Documents/Link Properties
The PV UI contains methods for paging within a document (previous/next) and for traversing chronology (history through back/forward). Attaching properties to links enables a rich model for navigation. For example, holding on a link offers additional information about where that link will lead. Link preview information could be displayed in thumbnail form and further holding could result in a graphical map of the links attached to that prospective destination. Back and forward buttons, by default, display thumbnail views of the pages that tapping that button will lead to.
Viewing History
History (which could include all the pages the user has viewed) may be viewed in a number of ways: by time, by appearance, by site, document, section, page, and the like. Since a user's navigation history is saved, the users' sequence may be viewed: as nodes with side tracking branches, as a linear list, or as a combination of most recently viewed pages and last few task categories. For example, a query could perform a multilevel categorization by document id resulting in a hierarchy that represents all the forward navigation paths a user has taken from any given document. By restricting (filtering) this categorization to a particular time frame, the navigation network as it existed at a particular point in time can be shown. Of course, other kinds of views are also possible. For example, the history can be categorized by higher level groupings like web sites or user tasks, with the results presented in alphabetical rather than time order, thus letting users return to a previous location according to the kind of information or activity, as opposed to the time during which, the location was last visited. To make certain views such as the network view more efficient to recreate, additional property information may be stored on each navigation record. Accordingly, maintaining the navigation context as a database of navigation records allows support for a rich variety of queries and views.
Applies to UI
Because the UI is built out of content, features used to search text, change viewing options on lists and tables, annotate, and the like all work for UI as well as for user content. As an example, the contents of any view, such as a view of a filing or command hierarchy, become searchable, sortable, and annotatable.
Non-linear Navigation History
A key difference between the navigation mechanism of the PV UI and prior art browsers is that the PV UI, unlike prior art browsers, maintains a non-linear navigation history. For example, if a user navigates through a set of links then goes “back” several steps, and then navigates through a different set of links, the user is still able to go “back” and then retrace the original path of links they navigated. With prior art browser's this is not possible—recollection of the first set of documents that were “backed” over is lost.
Further, the PV UI maintains a nonlinear navigation context that records every place a user has ever navigated to, when in time the user was there, and where the user went to from there. This, in turn, allows a user to navigate from general content pages into user interface pages, perform interface functionality, and then return to the user's documents without losing what the user's navigational context was before navigating to the user interface pages. As described in more detail above in the Rich Navigation And Maintaining The User's Navigational History section, this invention automatically removes navigation from the beginning of navigation into UI pages that lead up to performance of some UI functionality so the user's navigational history does not get cluttered with navigation within UI pages. Saving the user's navigation history may also help a user retrace navigational steps that the user would not otherwise be able to remember. For instance, suppose a user does not remember where they were when they viewed some content they liked. If the user remembers where they had been before they viewed that content, then the user can navigate to this prior place and query navigational history for everywhere they had navigated to from that particular location.
This is very unlike prior art multi-windowing UIs in which each application has its own navigation history that can not be integrated with the history of other applications a user is concurrently running. For example, suppose a user runs a word processor and a browser concurrently on a desktop computer. The user can switch between them in a way well known in the art. The word processor and the web browser will both have their own state information. In other words, the word processor and the web browser will each be separately nested in their own experience of history or navigation. As a result, if the user switches from the word processor to the browser, visits a few web sites and wants to return to the word processor, the user will not be able to get back to the word processor by hitting the browser's “back” button. The browser and the word processor essentially exist in separate contexts, with each context having its own state information and unique history.
Annotations
The PV UI allows a user to interact with content and the UI to make either or both more memorable, via bookmarks, clippings, highlights, overlaid and embedded ink and audio notes. Bookmarks are described further in commonly assigned and currently pending U.S. patent application Ser. No. 09/456,127, entitled Bookmarking and Placemarking a Displayed Document in a Computer System, filed contemporaneously herewith, which is incorporated herein by reference. Example bookmarks 800 and 802 are depicted in FIG. 8. Ink annotations are described further in commonly assigned and currently pending: U.S. patent application Ser. No. 09/455,805, entitled System and Method for Annotating an Electronic Document Independently Of Its Content, filed contemporaneously herewith, which is incorporated herein by reference. These annotations may be performed with not only different input methods, but adapted to the most convenient or natural one, such as a finger for highlighting, a stylus for writing or doodling, and speech for lengthier commentary.
Storing Annotations
The annotations exist apart from the content (as files with links to the content); therefore annotations can be displayed not only layered on the content in appropriate positions within the content, such as, for instance, note 1000 in FIG. 10, but in other locations and visualizations. That is, each of these annotations is available to the user not only in situ, in the content where it was created, but cross-referenced in automatically-created indices which can be manipulated much as described in the Viewing History section above: by time, by appearance, by site, document, section, page, etc. Likewise, annotations could be shared, selectively shared, or kept private with the kind of functionality described in the Collaboration section below.
Interface Shortcuts and Smarts
Most-likely-to-use-links and Other Heuristics
The PV UI can include heuristics, which allow it to offer up most-likely-to-use links to additional material. One case of these is the context menu that appears when the user holds the Next button; in addition to the most recent documents the user has visited subsequent to the current one, the Next menu includes heuristically determined choices of other places the user may wish to visit (for example, documents on a topic related to the current one). Another case is a feature called_an End Page, such as, for instance, End Page 1100 depicted in FIG. 11. Such an End Page is essentially a summary page at the end of a document or book that offers the user related topics such as “additional works by this author/on this topic/written in the same time period/commented on by these critics” etc. In the case of directories such as email, where each message is technically a document, the end page offers threads based on that message/other messages by same author/other text on the same topic, and the like.
Of course, other heuristics could also be used depending on the context. For example, when offering up a set of command choices to a user, the heuristics could be based on analysis of the user's current document context, recently used commands, and commands the user has used most frequently in this and similar contexts in the past. Such heuristics are described further, in the context of navigating to a particular portion of the Guide Book, in commonly assigned and currently pending U.S. patent application Ser. No. 09/456,952, entitled Method and Apparatus for Providing Help and Settings Control to Users of an Electronic Book, filed contemporaneously herewith, which is incorporated herein by reference.
Frequently Used Links
The PV VI could also provide commands (actually links) embedded in the page that are related to the kind of material on the page. In a mail message for example, “reply” “reply all,” and “forward” are links so frequently used as to warrant their inclusion directly on the page. There may be other commands or links used so often that they are dynamically bubbled up, or in the case of linear reading, used so infrequently that none appear. The second level of visibility—“hold on the page for more information”—offers a more extensive list. If none of these satisfy the user's need, the user can summon the Guide Book.
Start Page
The top level of the PV UI provides the user with a Personal Newsletter or Start Page, which is the launch point for many activities. An example Start Page is depicted in FIG. 5. Highlights might include urgent mail messages, projects, PIM items, documents, news, which could be divided into system-offered default components, such as Messages, Notes, Clippings, and the like. Favorite links that the user wants to keep readily available could also be included. What appears on the Start Page can be both user-configured as well as configured from profile information the PV UI has learned by observing a user's browsing and e-mail reading patterns and the like.
User can Modify Start Page
Advanced users can perform the same kinds of operations on the interface itself as those performed on content. If the default components on their Start Page are not to their liking, they can delete or alter even system-offered components such as Mail Messages. Or, for instance, if the automatic page number used by the bookmark header is insufficient for recognition, they can alter its text, color or any other property.
Audio Recording and Annotation
The PV UI supports the creation of audio clips that can be used for annotation of any displayed document. The clips are based on a timeline model in which audio (or video) recording is a data stream parallel to and synchronized with the material in a document. If the user has changed pages while recording, then the clip when played back will also change the page when the appropriate place in the audio clip is reached. The interface supports both document and page-specific audio noted as well as global recording. The interface is presented with cassette-like controls, including index forward/back and editing. Each clip is stored as an individual document and can be sorted and filtered to present the clips in multiple ways (all audio on a given page, all audio for a given book, audio notes in the order they were recorded, and the like). Additionally, the audio clip recorder supports intelligent VOX for hands-off note taking. A further feature is the ability to embed audio notes at specific points in the content of a document in a manner similar to creating footnotes. These audio notes can be created and played back by a single tap on the screen at the point where the audio note was (or is to be) inserted. The presence of embedded audio notes is signified by a small icon in the content that is laid out in a manner similar to a footnote symbol.
Guide Book
Because the commands in the PV UI are simply links on a document page, there is no difference between documentation, help, wizards and the other ways the PV UI helps a user perform an action. Asking for help by clicking on a help link summons an appropriate help page composed on the fly from the content of the Guide Book. The principles that underlie this composition are contextual: that is, if the user is currently in the “list” or “books” of Mail Messages, the help system infers that requests for assistance are about how to perform work with Mail Messages.
For instance, FIG. 8 shows two pages of an example Guide Book. The page on the right, page 9 of 10 includes descriptions of commands, such as the “PIN THIS PAGE” command 800. The Guide Book describes what the command does. For instance, for “PIN THIS PAGE” the description states that “Tapping on this command will “freeze” a secondary copy of the current page and display it as a floating page over the book.” FIG. 9 shows an example of a pinned page. In addition to describing this command, the text “PIN THIS PAGE” is a link that, when activated, will execute the “PIN THIS PAGE” command on either the most recently selected page or on a page to be selected after activating the “PIN THIS PAGE” command link.
Obtain Help and Perform Functions in the Same Way
Unlike prior art UIs, the PV UI is constructed as a set of document pages just like a user document or a web site is constructed as set of document pages. This invention puts all of the user's content pages and user interface pages into a single grouping of information that the user can access. This invention then leverages well-known browser-like navigational capabilities to allow a user to navigate back and forth between various pages and to put links to pages in favored lists and the like. All of this is leveraged to provide the means by which a user navigates to user interface pages.
The PV UI can provide context-specific dynamically synthesized views of links to give the user direct access to relevant UI help pages. The user can search for user interface functionality in the same way the user can search other document pages. Of course, pop-up menus and other devices such as permanent links placed on the screen that give the user direct access to UI help information can also be provided.
Because the Guide Book is simply content, operations that may be performed on other types of content, such as the Start Page, the UI, and content in general may also be performed on the Guide Book. Unlike prior art user interfaces, the way a user gets help for performing a function and the way the user performs the function are the same. To perform a function and to get help for a function, the user simply activates a link.
Concluding Remarks
The foregoing has described a user interface architecture based on documents-with-links that facilitates creation of user interfaces that allow users to read, annotate, collaborate and perform other tasks typical of knowledge work, as well as alter the interface to best suit their work patterns. It will be appreciated that many modifications and variations of the invention are possible, and the specific examples and descriptions herein do not limit the scope of the invention.

Claims (17)

We claim:
1. A computer user interface comprising:
a plurality of user interface pages having links within a single document;
a plurality of user content pages having links within the single document;
a unified navigational context for allowing a user to interface with both the user interface pages and the user content pages within the single document by activating the links of the user interface pages and the links of the user content pages, the unified navigational context automatically storing a navigational history of each user interface page and each user content page to which a user navigates; and
a history view map for depicting the stored navigational history non-linearly,
wherein the stored navigational history includes a first navigational path of at least one user interface page and at least one user content page and a second navigational path of at least one user interface page or at least one user content page, the second navigational path being different from the first navigational path,
wherein the history view man automatically excludes a portion of the stored navigation history from a user content page through at least one user interface page that leads to execution of a user interface command.
2. The computer user interface of claim 1 wherein the stored navigational history includes information about when the user navigated to each user interface page and each user content page.
3. A computer-readable medium having computer-executable instructions for generating the computer user interface of claim 2.
4. The computer user interface of claim 1 wherein for each user interface page and each user content page to which the user navigated, the stored navigational history includes information about where the user navigated.
5. A computer-readable medium having computer-executable instructions for generating the computer user interface of claim 4.
6. The computer user interface of claim 1 wherein the history view map depicts the stored navigational history as all forward navigation paths the user has taken from at least one user interface page or user content page.
7. The computer user interface of claim 6 wherein the history view map depicts the forward navigation paths restricted to a particular time frame.
8. A computer-readable medium having computer-executable instructions for generating the computer user interface of claim 7.
9. A computer-readable medium having computer-executable instructions for generating the computer user interface of claim 6.
10. The computer user interface of claim 1 wherein the second navigational path includes at least one user interface page and at least one user content page.
11. A computer-readable medium having computer-executable instructions for generating the computer user interface of claim 1.
12. A method for storing a navigational history comprising steps of:
generating a computer user interface comprising a plurality of user interface pages having links within a single document and a plurality of user content pages having links within the single document;
generating a unified navigational context for allowing a user to interface with both the user interface pages and the user content pages within the single document;
receiving input signals representative of activation of the links of the user interface pages and the links of the user content pages;
automatically storing a navigational history of each user interface page and each user content page to which a user navigates in the unified navigational context;
generating a history view map for depicting the stored navigational history non-linearly; and
automatically excluding a portion of the stored navigation history from a user content page through at least one user interface page that leads to execution of a user interface command,
wherein the stored navigational history includes a first navigational path of at least one user interface page and at least one user content page and a second navigational path of at least one user interface page or at least one user content page, the second navigational path being different from the first navigational path.
13. The method of claim 12 wherein the stored navigational history includes information about when the user navigated to each user interface page and each user content page.
14. The method of claim 12 wherein for each user interface page and each user content page to which the user navigated, the stored navigational history includes information about where the user navigated.
15. The method of claim 12 wherein the history view map depicts the stored navigational history as all forward navigation paths the user has taken from at least one user interface page or user content page.
16. The method of claim 15 wherein the history view map depicts the forward navigation paths restricted to a particular time frame.
17. The method of claim 12 wherein the second navigational path includes at least one user interface page and at least one user content page.
US09/456,975 1999-12-07 1999-12-07 Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history Expired - Lifetime US6820111B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US09/456,975 US6820111B1 (en) 1999-12-07 1999-12-07 Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history
US10/875,174 US7496830B2 (en) 1999-12-07 2004-06-25 Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US09/456,975 US6820111B1 (en) 1999-12-07 1999-12-07 Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US10/875,174 Continuation US7496830B2 (en) 1999-12-07 2004-06-25 Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history

Publications (1)

Publication Number Publication Date
US6820111B1 true US6820111B1 (en) 2004-11-16

Family

ID=33418076

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/456,975 Expired - Lifetime US6820111B1 (en) 1999-12-07 1999-12-07 Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history
US10/875,174 Expired - Fee Related US7496830B2 (en) 1999-12-07 2004-06-25 Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history

Family Applications After (1)

Application Number Title Priority Date Filing Date
US10/875,174 Expired - Fee Related US7496830B2 (en) 1999-12-07 2004-06-25 Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history

Country Status (1)

Country Link
US (2) US6820111B1 (en)

Cited By (105)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020107861A1 (en) * 2000-12-07 2002-08-08 Kerry Clendinning System and method for collecting, associating, normalizing and presenting product and vendor information on a distributed network
US20020194280A1 (en) * 2001-06-15 2002-12-19 International Business Machines Corporation Electronic mail system for generating a mail message to multiple recipients with multiple attention levels
US20030018665A1 (en) * 2001-07-11 2003-01-23 International Business Machines Corporation Method and system for dynamic web page breadcrumbing using javascript
US20030088827A1 (en) * 2000-06-08 2003-05-08 Stg Interactive Multimedia data publishing system
US20030135506A1 (en) * 2002-01-16 2003-07-17 Hausheer Kurt J. Method for collating experiences of an interactive internet session
US20030225858A1 (en) * 2002-05-30 2003-12-04 International Business Machines Corporation Method and apparatus for traversing Web pages in a network data processing system
US20030231220A1 (en) * 2002-06-14 2003-12-18 Fujitsu Limited Novel data processing method and system
US20040001104A1 (en) * 2002-06-28 2004-01-01 Microsoft Corporation Resource browser sessions search
US20040027391A1 (en) * 2002-08-06 2004-02-12 Tu Robert F. Z. Web site navigation under a hierarchical menu structure
US20040098249A1 (en) * 2002-11-18 2004-05-20 Yaliang Wang Method and system to utilize web resources for language vocabulary learning
US20040133845A1 (en) * 2003-01-06 2004-07-08 Scott Forstall User interface for accessing presentations
US20040139143A1 (en) * 2002-12-31 2004-07-15 Canakapalli Sri K. Multi-dimensional navigation for a web browser
US20040205464A1 (en) * 2002-01-31 2004-10-14 International Business Machines Corporation Structure and method for linking within a website
US20050025390A1 (en) * 2003-05-12 2005-02-03 Osamu Tsujii Information processing apparatus and method
US20050080872A1 (en) * 2003-10-08 2005-04-14 Davis Brockton S. Learned upload time estimate module
US20050102381A1 (en) * 2003-11-10 2005-05-12 Jiang Zhaowei C. Upload security scheme
US20050114798A1 (en) * 2003-11-10 2005-05-26 Jiang Zhaowei C. 'Back' button in mobile applications
US20050226530A1 (en) * 2004-04-08 2005-10-13 Hajime Murayama Image processing program, image processing method, image processing apparatus and storage medium
US20050259120A1 (en) * 2000-05-04 2005-11-24 Stephen Mansfield Method for adding a user-selectable function to a hyperlink
US20060085733A1 (en) * 2004-10-19 2006-04-20 International Business Machines Corporation Document display device, method, and program product
US7062475B1 (en) * 2000-05-30 2006-06-13 Alberti Anemometer Llc Personalized multi-service computer environment
US20060195526A1 (en) * 2003-07-04 2006-08-31 Thomas Lederer Device and method for user-based processing of electronic message comprising file attachments
US20060224406A1 (en) * 2005-03-30 2006-10-05 Jean-Michel Leon Methods and systems to browse data items
US20060236260A1 (en) * 2004-12-09 2006-10-19 Microsoft Corporation Journal display having three dimensional appearance
US20070006100A1 (en) * 2005-06-29 2007-01-04 Virpi Roto Mobile communication terminal
US20070038952A1 (en) * 2005-06-29 2007-02-15 Erika Reponen Mobile communication terminal
US20070061755A1 (en) * 2005-09-09 2007-03-15 Microsoft Corporation Reading mode for electronic documents
US20070143688A1 (en) * 2005-12-20 2007-06-21 Cheng Jian H System and method for mark and navigation to facilitate content view
US20070174300A1 (en) * 2006-01-12 2007-07-26 Samsung Electronics Co., Ltd. Method and apparatus for storing and restoring state information of remote user interface
US20070186177A1 (en) * 2006-02-03 2007-08-09 Yahoo! Inc. Content navigation interfaces and associated methods
US20070186173A1 (en) * 2006-02-03 2007-08-09 Yahoo! Inc. Instant messenger alerts and organization systems
US20070233377A1 (en) * 2006-04-04 2007-10-04 Brian Salay Content display and navigation interface
US20070294277A1 (en) * 2006-06-16 2007-12-20 Jos Manuel Accapadi Methodology for directory categorization for categorized files
US20070294202A1 (en) * 2006-06-16 2007-12-20 Jos Manuel Accapadi Methodology for file identification and retrieval in directories for categorized files
US20080046218A1 (en) * 2006-08-16 2008-02-21 Microsoft Corporation Visual summarization of activity data of a computing session
US20080098294A1 (en) * 2006-10-23 2008-04-24 Mediq Learning, L.L.C. Collaborative annotation of electronic content
US20080147671A1 (en) * 2006-12-18 2008-06-19 Lampdesk Corporation System for Running Web Applications Offline and Providing Access to Native Services
US20080163127A1 (en) * 2006-12-29 2008-07-03 Microsoft Corporation Enhanced user navigation in a media environment
US20080244451A1 (en) * 2007-03-30 2008-10-02 Katharina Goering Adaptive dynamic navigational control for navigating within an application
US20080282199A1 (en) * 2007-05-11 2008-11-13 Demand Media, Inc. Cross taxonomy navigation from a bread crumb in a graphical user interface
US20080295021A1 (en) * 2007-05-21 2008-11-27 Laurent An Minh Nguyen Zone-Associated Objects
US20090089368A1 (en) * 2007-09-28 2009-04-02 International Business Machines Corporation Automating user's operations
US20090178008A1 (en) * 2008-01-06 2009-07-09 Scott Herz Portable Multifunction Device with Interface Reconfiguration Mode
US20090204900A1 (en) * 2008-02-13 2009-08-13 International Business Machines Corporation Method And System For Navigation Of Web Sites And Applications
US7602379B2 (en) * 2001-06-19 2009-10-13 Hewlett-Packard Development Company, L.P. Digital annotator
US20090260060A1 (en) * 2008-04-14 2009-10-15 Lookwithus.Com, Inc. Rich media collaboration system
US20090264158A1 (en) * 2004-09-21 2009-10-22 Research In Motion Limited User Interface and Method for Persistent Viewing of a User Selected Folder on a Mobile Device
US20090327973A1 (en) * 2008-04-29 2009-12-31 International Business Machines Corporation Preserving a complete history of a set of application actions when non-linear interactions are permitted
US20100070856A1 (en) * 2008-09-12 2010-03-18 International Business Machines Corporation Method for Graphical Visualization of Multiple Traversed Breadcrumb Trails
US20100095201A1 (en) * 1999-08-10 2010-04-15 Sharp Kabushiki Kaisha Electronic book contents recording medium with electronic book contents recorded thereon, electronic book transmission apparatus and electronic book display apparatus
US20100100852A1 (en) * 2007-02-13 2010-04-22 Buchanan Michael G Nestable system and method for accessing, organizing, and interacting with visual representations of data
US7797724B2 (en) 2004-08-31 2010-09-14 Citrix Systems, Inc. Methods and apparatus for secure online access on a client device
US20100251162A1 (en) * 2006-10-03 2010-09-30 Verizon Data Services Inc. Interactive search graphical user interface systems and methods
US20100257456A1 (en) * 2009-04-07 2010-10-07 Clearside, Inc. Presentation access tracking system
US20100306663A1 (en) * 2009-05-27 2010-12-02 International Business Machines Corporation Sequential Clicked Link Display Mechanism
US7853899B1 (en) 2002-12-30 2010-12-14 Sap Aktiengesellschaft Configuring and extending a user interface
US7908284B1 (en) 2006-10-04 2011-03-15 Google Inc. Content reference page
US20110066609A1 (en) * 2009-09-14 2011-03-17 International Business Machines Corporation Crawling Browser-Accessible Applications
US20110091844A1 (en) * 2009-10-20 2011-04-21 Best Roger J Virtual book
US7979785B1 (en) 2006-10-04 2011-07-12 Google Inc. Recognizing table of contents in an image sequence
US8005946B2 (en) 2007-09-10 2011-08-23 Microsoft Corporation Managing navigation history for intra-page state transitions
US8069226B2 (en) 2004-09-30 2011-11-29 Citrix Systems, Inc. System and method for data synchronization over a network using a presentation level protocol
US20120131071A1 (en) * 2010-11-18 2012-05-24 Samsung Electronics Co. Ltd. Apparatus and method for providing e-note function in mobile terminal
US8190676B2 (en) 2004-09-29 2012-05-29 Citrix Systems, Inc. System and method for event detection and re-direction over a network using a presentation level protocol
US20120159373A1 (en) * 2010-12-15 2012-06-21 Verizon Patent And Licensing, Inc. System for and method of generating dog ear bookmarks on a touch screen device
US20120210237A1 (en) * 2011-02-16 2012-08-16 Computer Associates Think, Inc. Recording A Trail Of Webpages
US8316320B2 (en) * 2006-10-03 2012-11-20 Verizon Patent And Licensing Inc. Expandable history tab in interactive graphical user interface systems and methods
US20130024804A1 (en) * 2011-07-20 2013-01-24 International Business Machines Corporation Navigation History Tracking In a Content Viewing Environment
US8434017B2 (en) 2011-03-21 2013-04-30 Business Objects Software Limited Computer user interface having selectable historical and default values
US20130311557A1 (en) * 2012-05-18 2013-11-21 Dropbox, Inc. Systems and methods for displaying file and folder information to a user
US8627197B2 (en) 1999-12-07 2014-01-07 Microsoft Corporation System and method for annotating an electronic document independently of its content
US20140164892A1 (en) * 2012-12-11 2014-06-12 Microsoft Corporation Consuming content incrementally
US8782551B1 (en) * 2006-10-04 2014-07-15 Google Inc. Adjusting margins in book page images
US8881217B2 (en) 2006-09-06 2014-11-04 Verizon Patent And Licensing Inc. Systems and methods for accessing media content
US20150178403A1 (en) * 2013-12-20 2015-06-25 Google Inc. History of Reading Positions in eBooks
US9069743B2 (en) 2011-10-13 2015-06-30 Microsoft Technology Licensing, Llc Application of comments in multiple application functionality content
US20150221037A1 (en) * 2014-02-05 2015-08-06 Wipro Limited System and method for allocting investment fund for an application
US9176933B2 (en) 2011-10-13 2015-11-03 Microsoft Technology Licensing, Llc Application of multiple content items and functionality to an electronic content item
US9183314B2 (en) * 2012-04-16 2015-11-10 International Business Machines Corporation Providing browsing history on client for dynamic webpage
US9223475B1 (en) 2010-06-30 2015-12-29 Amazon Technologies, Inc. Bookmark navigation user interface
US20160070446A1 (en) * 2014-09-04 2016-03-10 Home Box Office, Inc. Data-driven navigation and navigation routing
US20160085878A1 (en) * 2014-09-24 2016-03-24 Lg Electronics Inc. Mobile terminal and method for controlling the same
US20160154575A1 (en) * 2014-12-02 2016-06-02 Yingyu Xie Gesture-Based Visualization of Data Grid on Mobile Device
US9367227B1 (en) * 2010-06-30 2016-06-14 Amazon Technologies, Inc. Chapter navigation user interface
US9367232B2 (en) 2007-01-07 2016-06-14 Apple Inc. Portable multifunction device, method, and graphical user interface supporting user navigations of graphical objects on a touch screen display
US20160216858A1 (en) * 2015-01-22 2016-07-28 Manzurul Khan Method and program product for an interactive e-book
US9772751B2 (en) 2007-06-29 2017-09-26 Apple Inc. Using gestures to slide between user interfaces
US9933913B2 (en) 2005-12-30 2018-04-03 Apple Inc. Portable electronic device with interface reconfiguration mode
US10084730B2 (en) 2014-10-21 2018-09-25 Unify Gmbh & Co. Kg Apparatus and method for quickly sending messages
US10134093B1 (en) * 2015-12-28 2018-11-20 iControl Systems USA, LLC System, method, and computer program for dynamically reconciling a distributor invoice with a retailer receiving invoice for products sold under multiple UPCs and in multiple quantity units
US20190095406A1 (en) * 2005-08-03 2019-03-28 Oath Inc. Enhanced favorites service for web browsers and web applications
US10250735B2 (en) 2013-10-30 2019-04-02 Apple Inc. Displaying relevant user interface objects
US10275506B1 (en) * 2013-12-20 2019-04-30 Amazon Technologies, Inc. Coordinating data across services
US10313505B2 (en) 2006-09-06 2019-06-04 Apple Inc. Portable multifunction device, method, and graphical user interface for configuring and displaying widgets
US10620780B2 (en) 2007-09-04 2020-04-14 Apple Inc. Editing interface
US10739974B2 (en) 2016-06-11 2020-08-11 Apple Inc. Configuring context-specific user interfaces
US10788953B2 (en) 2010-04-07 2020-09-29 Apple Inc. Device, method, and graphical user interface for managing folders
WO2020237015A1 (en) 2019-05-22 2020-11-26 Sion Power Corporation Electrically coupled electrodes, and associated articles and methods
US11126321B2 (en) 2007-09-04 2021-09-21 Apple Inc. Application menu user interface
US11188978B2 (en) 2002-12-31 2021-11-30 Ebay Inc. Method and system to generate a listing in a network-based commerce system
US11263679B2 (en) 2009-10-23 2022-03-01 Ebay Inc. Product identification using multiple services
US11281368B2 (en) 2010-04-07 2022-03-22 Apple Inc. Device, method, and graphical user interface for managing folders with multiple pages
US11307763B2 (en) 2008-11-19 2022-04-19 Apple Inc. Portable touch screen device, method, and graphical user interface for using emoji characters
US11675476B2 (en) 2019-05-05 2023-06-13 Apple Inc. User interfaces for widgets
US11816325B2 (en) 2016-06-12 2023-11-14 Apple Inc. Application shortcuts for carplay

Families Citing this family (167)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6735253B1 (en) * 1997-05-16 2004-05-11 The Trustees Of Columbia University In The City Of New York Methods and architecture for indexing and editing compressed video over the world wide web
US7143434B1 (en) * 1998-11-06 2006-11-28 Seungyup Paek Video description system and method
DE10115895C1 (en) * 2001-03-30 2002-12-19 Siemens Ag Method for generating a representation for the retrieval of an information page that has already been called up
US7246118B2 (en) * 2001-07-06 2007-07-17 International Business Machines Corporation Method and system for automated collaboration using electronic book highlights and notations
US7165105B2 (en) * 2001-07-16 2007-01-16 Netgenesis Corporation System and method for logical view analysis and visualization of user behavior in a distributed computer network
US7093201B2 (en) * 2001-09-06 2006-08-15 Danger, Inc. Loop menu navigation apparatus and method
WO2003051031A2 (en) * 2001-12-06 2003-06-19 The Trustees Of Columbia University In The City Of New York Method and apparatus for planarization of a material by growing and removing a sacrificial film
US7310636B2 (en) * 2002-01-15 2007-12-18 International Business Machines Corporation Shortcut enabled, context aware information management
JP2005525011A (en) * 2002-04-26 2005-08-18 ザ トラスティーズ オブ コロンビア ユニヴァーシティ イン ザ シティ オブ ニューヨーク Method and system for optimal video transcoding based on utility function description
US7421438B2 (en) 2004-04-29 2008-09-02 Microsoft Corporation Metadata editing control
US7240292B2 (en) 2003-04-17 2007-07-03 Microsoft Corporation Virtual address bar user interface control
US7627552B2 (en) 2003-03-27 2009-12-01 Microsoft Corporation System and method for filtering and organizing items based on common elements
US7769794B2 (en) 2003-03-24 2010-08-03 Microsoft Corporation User interface for a file system shell
US7712034B2 (en) 2003-03-24 2010-05-04 Microsoft Corporation System and method for shell browser
US7823077B2 (en) 2003-03-24 2010-10-26 Microsoft Corporation System and method for user modification of metadata in a shell browser
US7650575B2 (en) 2003-03-27 2010-01-19 Microsoft Corporation Rich drag drop user interface
US7925682B2 (en) 2003-03-27 2011-04-12 Microsoft Corporation System and method utilizing virtual folders
US8024335B2 (en) 2004-05-03 2011-09-20 Microsoft Corporation System and method for dynamically generating a selectable search extension
US7694236B2 (en) 2004-04-23 2010-04-06 Microsoft Corporation Stack icons representing multiple objects
US7657846B2 (en) 2004-04-23 2010-02-02 Microsoft Corporation System and method for displaying stack icons
US8707209B2 (en) 2004-04-29 2014-04-22 Microsoft Corporation Save preview representation of files being created
US20060048068A1 (en) * 2004-08-31 2006-03-02 Michael Danninger Method and system to facilitate access to a user interface element on a user interface
US8880597B1 (en) * 2004-09-07 2014-11-04 Evernote Corporation Electronic note management system and user-interface
US8385589B2 (en) 2008-05-15 2013-02-26 Berna Erol Web-based content detection in images, extraction and recognition
US8825682B2 (en) 2006-07-31 2014-09-02 Ricoh Co., Ltd. Architecture for mixed media reality retrieval of locations and registration of images
US9373029B2 (en) 2007-07-11 2016-06-21 Ricoh Co., Ltd. Invisible junction feature recognition for document security or annotation
US8369655B2 (en) 2006-07-31 2013-02-05 Ricoh Co., Ltd. Mixed media reality recognition using multiple specialized indexes
US9384619B2 (en) 2006-07-31 2016-07-05 Ricoh Co., Ltd. Searching media content for objects specified using identifiers
US8510283B2 (en) 2006-07-31 2013-08-13 Ricoh Co., Ltd. Automatic adaption of an image recognition system to image capture devices
US7970171B2 (en) 2007-01-18 2011-06-28 Ricoh Co., Ltd. Synthetic image and video generation from ground truth data
US8184155B2 (en) 2007-07-11 2012-05-22 Ricoh Co. Ltd. Recognition and tracking using invisible junctions
US8838591B2 (en) 2005-08-23 2014-09-16 Ricoh Co., Ltd. Embedding hot spots in electronic documents
US9530050B1 (en) 2007-07-11 2016-12-27 Ricoh Co., Ltd. Document annotation sharing
US8156115B1 (en) 2007-07-11 2012-04-10 Ricoh Co. Ltd. Document-based networking with mixed media reality
US8521737B2 (en) 2004-10-01 2013-08-27 Ricoh Co., Ltd. Method and system for multi-tier image matching in a mixed media environment
US8949287B2 (en) 2005-08-23 2015-02-03 Ricoh Co., Ltd. Embedding hot spots in imaged documents
US8856108B2 (en) 2006-07-31 2014-10-07 Ricoh Co., Ltd. Combining results of image retrieval processes
US8335789B2 (en) 2004-10-01 2012-12-18 Ricoh Co., Ltd. Method and system for document fingerprint matching in a mixed media environment
US9405751B2 (en) 2005-08-23 2016-08-02 Ricoh Co., Ltd. Database for mixed media document system
US8600989B2 (en) 2004-10-01 2013-12-03 Ricoh Co., Ltd. Method and system for image matching in a mixed media environment
US8276088B2 (en) 2007-07-11 2012-09-25 Ricoh Co., Ltd. User interface for three-dimensional navigation
US8176054B2 (en) 2007-07-12 2012-05-08 Ricoh Co. Ltd Retrieving electronic documents by converting them to synthetic text
US7702673B2 (en) 2004-10-01 2010-04-20 Ricoh Co., Ltd. System and methods for creation and use of a mixed media environment
US8144921B2 (en) 2007-07-11 2012-03-27 Ricoh Co., Ltd. Information retrieval using invisible junctions and geometric constraints
US8156427B2 (en) 2005-08-23 2012-04-10 Ricoh Co. Ltd. User interface for mixed media reality
US9171202B2 (en) 2005-08-23 2015-10-27 Ricoh Co., Ltd. Data organization and access for mixed media document system
US8156116B2 (en) 2006-07-31 2012-04-10 Ricoh Co., Ltd Dynamic presentation of targeted information in a mixed media reality recognition system
US8195659B2 (en) * 2005-08-23 2012-06-05 Ricoh Co. Ltd. Integration and use of mixed media documents
US8332401B2 (en) 2004-10-01 2012-12-11 Ricoh Co., Ltd Method and system for position-based image matching in a mixed media environment
US8868555B2 (en) 2006-07-31 2014-10-21 Ricoh Co., Ltd. Computation of a recongnizability score (quality predictor) for image retrieval
WO2006096612A2 (en) * 2005-03-04 2006-09-14 The Trustees Of Columbia University In The City Of New York System and method for motion estimation and mode decision for low-complexity h.264 decoder
US8195646B2 (en) 2005-04-22 2012-06-05 Microsoft Corporation Systems, methods, and user interfaces for storing, searching, navigating, and retrieving electronic information
JP3865141B2 (en) * 2005-06-15 2007-01-10 任天堂株式会社 Information processing program and information processing apparatus
US7665028B2 (en) 2005-07-13 2010-02-16 Microsoft Corporation Rich drag drop user interface
US8225231B2 (en) 2005-08-30 2012-07-17 Microsoft Corporation Aggregation of PC settings
US9020966B2 (en) 2006-07-31 2015-04-28 Ricoh Co., Ltd. Client device for interacting with a mixed media reality recognition system
US8676810B2 (en) 2006-07-31 2014-03-18 Ricoh Co., Ltd. Multiple index mixed media reality recognition using unequal priority indexes
US9063952B2 (en) 2006-07-31 2015-06-23 Ricoh Co., Ltd. Mixed media reality recognition with image tracking
US8489987B2 (en) 2006-07-31 2013-07-16 Ricoh Co., Ltd. Monitoring and analyzing creation and usage of visual content using image and hotspot interaction
US8201076B2 (en) 2006-07-31 2012-06-12 Ricoh Co., Ltd. Capturing symbolic information from documents upon printing
US9176984B2 (en) 2006-07-31 2015-11-03 Ricoh Co., Ltd Mixed media reality retrieval of differentially-weighted links
US20080148188A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Persistent preview window
US20080148164A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Toolbox minimizer/maximizer
US20080147708A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Preview window with rss feed
US20080270932A1 (en) * 2006-12-15 2008-10-30 Iac Search & Media, Inc. Toolbox editing
US20080147653A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Search suggestions
US20080147606A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Category-based searching
US8601387B2 (en) * 2006-12-15 2013-12-03 Iac Search & Media, Inc. Persistent interface
US20080147709A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Search results from selected sources
US20080148192A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Toolbox pagination
US7579541B2 (en) * 2006-12-28 2009-08-25 Texas Instruments Incorporated Automatic page sequencing and other feedback action based on analysis of audio performance data
US8103971B2 (en) * 2006-12-29 2012-01-24 Sap Ag System and method for notifying actions
US8433995B1 (en) * 2007-04-24 2013-04-30 Google Inc. Managing bookmarks for web pages
US8094137B2 (en) 2007-07-23 2012-01-10 Smart Technologies Ulc System and method of detecting contact on a display
US20090100321A1 (en) * 2007-10-12 2009-04-16 Microsoft Corporation Universal contextual actions menu across windows applications
WO2009052308A1 (en) * 2007-10-17 2009-04-23 Roseman Neil S Nlp-based content recommender
KR101489693B1 (en) * 2007-10-18 2015-02-05 삼성전자주식회사 Method and apparatus for providing customized contents
US9298477B2 (en) * 2007-11-27 2016-03-29 Autodesk, Inc. Wizard navigation list
US20090199133A1 (en) * 2008-02-05 2009-08-06 Microsoft Corporation Generating a destination list utilizing usage data
US9612847B2 (en) * 2008-02-05 2017-04-04 Microsoft Technology Licensing, Llc Destination list associated with an application launcher
US20090249179A1 (en) * 2008-03-28 2009-10-01 Shieh Johnny M Method to display multiple cached webpages related to a bookmark
WO2009126785A2 (en) * 2008-04-10 2009-10-15 The Trustees Of Columbia University In The City Of New York Systems and methods for image archaeology
WO2009155281A1 (en) * 2008-06-17 2009-12-23 The Trustees Of Columbia University In The City Of New York System and method for dynamically and interactively searching media data
US9030418B2 (en) * 2008-06-24 2015-05-12 Lg Electronics Inc. Mobile terminal capable of sensing proximity touch
US20100083109A1 (en) * 2008-09-29 2010-04-01 Smart Technologies Ulc Method for handling interactions with multiple users of an interactive input system, and interactive input system executing the method
US8810522B2 (en) * 2008-09-29 2014-08-19 Smart Technologies Ulc Method for selecting and manipulating a graphical object in an interactive input system, and interactive input system executing the method
US20100079409A1 (en) * 2008-09-29 2010-04-01 Smart Technologies Ulc Touch panel for an interactive input system, and interactive input system incorporating the touch panel
US20100087169A1 (en) * 2008-10-02 2010-04-08 Microsoft Corporation Threading together messages with multiple common participants
US20100087173A1 (en) * 2008-10-02 2010-04-08 Microsoft Corporation Inter-threading Indications of Different Types of Communication
US20100105441A1 (en) * 2008-10-23 2010-04-29 Chad Aron Voss Display Size of Representations of Content
US8086275B2 (en) 2008-10-23 2011-12-27 Microsoft Corporation Alternative inputs of a mobile communications device
US8385952B2 (en) * 2008-10-23 2013-02-26 Microsoft Corporation Mobile communications device user interface
US20100105424A1 (en) * 2008-10-23 2010-04-29 Smuga Michael A Mobile Communications Device User Interface
US8411046B2 (en) * 2008-10-23 2013-04-02 Microsoft Corporation Column organization of content
US9710240B2 (en) * 2008-11-15 2017-07-18 Adobe Systems Incorporated Method and apparatus for filtering object-related features
US8671069B2 (en) 2008-12-22 2014-03-11 The Trustees Of Columbia University, In The City Of New York Rapid image annotation via brain state decoding and visual pattern mining
US20100169756A1 (en) * 2008-12-29 2010-07-01 Yahoo! Inc. Automated bookmarking
US8355698B2 (en) * 2009-03-30 2013-01-15 Microsoft Corporation Unlock screen
US8238876B2 (en) 2009-03-30 2012-08-07 Microsoft Corporation Notifications
US8175653B2 (en) 2009-03-30 2012-05-08 Microsoft Corporation Chromeless user interface
US8269736B2 (en) * 2009-05-22 2012-09-18 Microsoft Corporation Drop target gestures
US8836648B2 (en) 2009-05-27 2014-09-16 Microsoft Corporation Touch pull-in gesture
US8385660B2 (en) 2009-06-24 2013-02-26 Ricoh Co., Ltd. Mixed media reality indexing and retrieval for repeated content
WO2011003171A1 (en) * 2009-07-08 2011-01-13 Smart Technologies Ulc Three-dimensional widget manipulation on a multi-touch panel
MX2012002504A (en) * 2009-09-01 2012-08-03 Smart Technologies Ulc Interactive input system with improved signal-to-noise ratio (snr) and image capture method.
JP5327017B2 (en) 2009-11-24 2013-10-30 ソニー株式会社 Remote operation device, remote operation system, information processing method and program using remote operation device
US8502789B2 (en) 2010-01-11 2013-08-06 Smart Technologies Ulc Method for handling user input in an interactive input system, and interactive input system executing the method
US8260664B2 (en) * 2010-02-05 2012-09-04 Microsoft Corporation Semantic advertising selection from lateral concepts and topics
US8983989B2 (en) * 2010-02-05 2015-03-17 Microsoft Technology Licensing, Llc Contextual queries
US8903794B2 (en) 2010-02-05 2014-12-02 Microsoft Corporation Generating and presenting lateral concepts
US8150859B2 (en) * 2010-02-05 2012-04-03 Microsoft Corporation Semantic table of contents for search results
US8421766B2 (en) * 2010-02-12 2013-04-16 Acer Incorporated Visualized information conveying system
US20110231395A1 (en) * 2010-03-19 2011-09-22 Microsoft Corporation Presenting answers
US20120159383A1 (en) 2010-12-20 2012-06-21 Microsoft Corporation Customization of an immersive environment
US20120159395A1 (en) 2010-12-20 2012-06-21 Microsoft Corporation Application-launching interface for multiple modes
US8612874B2 (en) 2010-12-23 2013-12-17 Microsoft Corporation Presenting an application change through a tile
US8689123B2 (en) 2010-12-23 2014-04-01 Microsoft Corporation Application reporting in an application-selectable user interface
US9423951B2 (en) 2010-12-31 2016-08-23 Microsoft Technology Licensing, Llc Content-based snap point
US9383917B2 (en) 2011-03-28 2016-07-05 Microsoft Technology Licensing, Llc Predictive tiling
US8789014B2 (en) 2011-05-13 2014-07-22 Microsoft Corporation Managing a working set in an integrated development environment
US9495782B2 (en) * 2011-05-24 2016-11-15 Novell, Inc. Integrated media browse and insertion
US9104440B2 (en) 2011-05-27 2015-08-11 Microsoft Technology Licensing, Llc Multi-application environment
US9104307B2 (en) 2011-05-27 2015-08-11 Microsoft Technology Licensing, Llc Multi-application environment
US20120304132A1 (en) 2011-05-27 2012-11-29 Chaitanya Dev Sareen Switching back to a previously-interacted-with application
US9158445B2 (en) 2011-05-27 2015-10-13 Microsoft Technology Licensing, Llc Managing an immersive interface in a multi-application immersive environment
US9658766B2 (en) 2011-05-27 2017-05-23 Microsoft Technology Licensing, Llc Edge gesture
US8893033B2 (en) 2011-05-27 2014-11-18 Microsoft Corporation Application notifications
US10162604B2 (en) 2011-06-16 2018-12-25 Microsoft Technology Licensing, Llc Navigation history visualization in integrated development environment
US9026948B2 (en) 2011-06-29 2015-05-05 Microsoft Technology Licensing, Llc Multi-faceted relationship hubs
US20130007602A1 (en) 2011-06-29 2013-01-03 Apple Inc. Fixed layout electronic publications
US9058331B2 (en) 2011-07-27 2015-06-16 Ricoh Co., Ltd. Generating a conversation in a social network based on visual search results
CN102902697A (en) 2011-07-29 2013-01-30 国际商业机器公司 Method and system for generating structured document guide view
US8687023B2 (en) 2011-08-02 2014-04-01 Microsoft Corporation Cross-slide gesture to select and rearrange
US20130057587A1 (en) 2011-09-01 2013-03-07 Microsoft Corporation Arranging tiles
US9557909B2 (en) 2011-09-09 2017-01-31 Microsoft Technology Licensing, Llc Semantic zoom linguistic helpers
US10353566B2 (en) 2011-09-09 2019-07-16 Microsoft Technology Licensing, Llc Semantic zoom animations
US8922575B2 (en) 2011-09-09 2014-12-30 Microsoft Corporation Tile cache
US9244802B2 (en) 2011-09-10 2016-01-26 Microsoft Technology Licensing, Llc Resource user interface
US9146670B2 (en) 2011-09-10 2015-09-29 Microsoft Technology Licensing, Llc Progressively indicating new content in an application-selectable user interface
US8933952B2 (en) 2011-09-10 2015-01-13 Microsoft Corporation Pre-rendering new content for an application-selectable user interface
US20130067338A1 (en) * 2011-09-14 2013-03-14 Microsoft Corporation Dynamic navigation region based on site usage
USD706789S1 (en) * 2011-11-21 2014-06-10 Google Inc. Portion of a display panel with a topic icon
USD689507S1 (en) * 2011-11-21 2013-09-10 Google Inc. Portion of a display panel with a user interface component
US9037958B2 (en) 2011-11-22 2015-05-19 International Business Machines Corporation Dynamic creation of user interface hot spots
US9223472B2 (en) 2011-12-22 2015-12-29 Microsoft Technology Licensing, Llc Closing applications
US9128605B2 (en) 2012-02-16 2015-09-08 Microsoft Technology Licensing, Llc Thumbnail-image selection of applications
USD732550S1 (en) * 2012-12-14 2015-06-23 Symantec Corporation Display device with graphical user interface
US9729403B1 (en) * 2013-03-15 2017-08-08 EMC IP Holding Company LLC Proficiency-based GUI adaptation
US9450952B2 (en) 2013-05-29 2016-09-20 Microsoft Technology Licensing, Llc Live tiles without application-code execution
JP6495907B2 (en) 2013-08-15 2019-04-03 ノキア テクノロジーズ オサケユイチア Apparatus and method for facilitating browser navigation.
GB2518298A (en) 2013-09-13 2015-03-18 Box Inc High-availability architecture for a cloud-based concurrent-access collaboration platform
US8892679B1 (en) 2013-09-13 2014-11-18 Box, Inc. Mobile device, methods and user interfaces thereof in a mobile device platform featuring multifunctional access and engagement in a collaborative environment provided by a cloud-based platform
US9704137B2 (en) * 2013-09-13 2017-07-11 Box, Inc. Simultaneous editing/accessing of content by collaborator invitation through a web-based or mobile application to a cloud-based collaboration platform
US10028028B2 (en) 2013-09-30 2018-07-17 Sonos, Inc. Accessing last-browsed information in a media playback system
US20150106741A1 (en) 2013-10-15 2015-04-16 Microsoft Corporation Managing conversations
US10866931B2 (en) 2013-10-22 2020-12-15 Box, Inc. Desktop application for accessing a cloud collaboration platform
EP3126969A4 (en) 2014-04-04 2017-04-12 Microsoft Technology Licensing, LLC Expandable application representation
CN105359055A (en) 2014-04-10 2016-02-24 微软技术许可有限责任公司 Slider cover for computing device
CN105378582B (en) 2014-04-10 2019-07-23 微软技术许可有限责任公司 Calculate the foldable cap of equipment
US10678412B2 (en) 2014-07-31 2020-06-09 Microsoft Technology Licensing, Llc Dynamic joint dividers for application windows
US10592080B2 (en) 2014-07-31 2020-03-17 Microsoft Technology Licensing, Llc Assisted presentation of application windows
US10254942B2 (en) 2014-07-31 2019-04-09 Microsoft Technology Licensing, Llc Adaptive sizing and positioning of application windows
US10642365B2 (en) 2014-09-09 2020-05-05 Microsoft Technology Licensing, Llc Parametric inertia and APIs
CN105573574A (en) * 2014-10-09 2016-05-11 阿里巴巴集团控股有限公司 Application interface navigation method and apparatus
WO2016065568A1 (en) 2014-10-30 2016-05-06 Microsoft Technology Licensing, Llc Multi-configuration input device
US11003627B2 (en) 2016-04-21 2021-05-11 Microsoft Technology Licensing, Llc Prioritizing thumbnail previews based on message content
US11449351B2 (en) * 2018-04-06 2022-09-20 Microsoft Technology Licensing, Llc History aware interfaces

Citations (109)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1987001481A1 (en) 1985-08-30 1987-03-12 Norbert Joseph Stein Electronic book device
US5146552A (en) 1990-02-28 1992-09-08 International Business Machines Corporation Method for associating annotation with electronically published material
US5239466A (en) 1990-10-04 1993-08-24 Motorola, Inc. System for selectively routing and merging independent annotations to a document at remote locations
USRE34476E (en) 1990-05-14 1993-12-14 Norwood Donald D Hybrid information management system for handwriting and text
US5434929A (en) 1994-07-12 1995-07-18 Apple Computer, Inc. Method and apparatus for setting character style preferences in a pen-based computer system
US5434965A (en) 1992-12-23 1995-07-18 Taligent, Inc. Balloon help system
US5471568A (en) 1993-06-30 1995-11-28 Taligent, Inc. Object-oriented apparatus and method for scan line conversion of graphic edges
WO1996020908A1 (en) 1994-12-29 1996-07-11 Institut Francais Du Petrole Paraxylene separation process comprising at least two high temperature crystallization stages
US5559942A (en) 1993-05-10 1996-09-24 Apple Computer, Inc. Method and apparatus for providing a note for an application program
US5572643A (en) 1995-10-19 1996-11-05 Judson; David H. Web browser with dynamic display of information objects during linking
US5625833A (en) 1988-05-27 1997-04-29 Wang Laboratories, Inc. Document annotation & manipulation in a data processing system
US5632022A (en) * 1991-11-13 1997-05-20 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Encyclopedia of software components
WO1997022109A1 (en) 1995-12-14 1997-06-19 Motorola Inc. Electronic book and method of annotation therefor
US5666113A (en) 1991-07-31 1997-09-09 Microtouch Systems, Inc. System for using a touchpad input device for cursor control and keyboard emulation
US5682439A (en) 1995-08-07 1997-10-28 Apple Computer, Inc. Boxed input correction system and method for pen based computer systems
US5687331A (en) 1995-08-03 1997-11-11 Microsoft Corporation Method and system for displaying an animated focus item
US5717860A (en) * 1995-09-20 1998-02-10 Infonautics Corporation Method and apparatus for tracking the navigation path of a user on the world wide web
US5717879A (en) 1995-11-03 1998-02-10 Xerox Corporation System for the capture and replay of temporal data representing collaborative activities
WO1998006054A1 (en) 1996-08-05 1998-02-12 Motorola Inc. Book-like interface for browsing on-line documents and methods therefor
US5719595A (en) 1995-05-09 1998-02-17 Apple Computer, Inc. Method and apparauts for generating a text image on a display with anti-aliasing effect
WO1998009446A2 (en) 1996-08-26 1998-03-05 Seng Beng Ho A browsing system and method for computer information
US5727129A (en) * 1996-06-04 1998-03-10 International Business Machines Corporation Network system for profiling and actively facilitating user activities
US5729687A (en) 1993-12-20 1998-03-17 Intel Corporation System for sending differences between joining meeting information and public meeting information between participants in computer conference upon comparing annotations of joining and public meeting information
US5737599A (en) 1995-09-25 1998-04-07 Rowe; Edward R. Method and apparatus for downloading multi-page electronic documents with hint information
US5745116A (en) 1996-09-09 1998-04-28 Motorola, Inc. Intuitive gesture-based graphical user interface
US5760773A (en) 1995-01-06 1998-06-02 Microsoft Corporation Methods and apparatus for interacting with data objects using action handles
US5790818A (en) 1993-12-30 1998-08-04 Intel Corporation Remote highlighting of objects in a conferencing system by logically anding a highlight bitmap and a foreground bitmap
US5802516A (en) 1993-11-03 1998-09-01 Apple Computer, Inc. Method of controlling an electronic book for a computer system
US5801687A (en) * 1994-09-30 1998-09-01 Apple Computer, Inc. Authoring tool comprising nested state machines for use in a computer system
US5819301A (en) 1995-09-25 1998-10-06 Adobe Systems Incorporated Method and apparatus for reading multi-page electronic documents
US5821925A (en) 1996-01-26 1998-10-13 Silicon Graphics, Inc. Collaborative work environment supporting three-dimensional objects and multiple remote participants
US5832263A (en) 1996-03-15 1998-11-03 Digidox, Inc. System and method for in-place modification of information recorded in read-only storage using modifiable non-volatile storage associated with an agent
US5835092A (en) * 1996-04-09 1998-11-10 Silicon Graphics, Inc. Mechanism for non-linear browsing of diverse information sources
US5838914A (en) 1993-03-19 1998-11-17 Ncr Corporation Collaboration system for allowing computer to draw annotation images on the output of selected program and replicating the annotation images on displays of other computers
US5845262A (en) 1995-07-10 1998-12-01 Hitachi, Ltd. Electronic press information dispatching system
US5854630A (en) * 1996-07-01 1998-12-29 Sun Microsystems, Inc. Prospective view for web backtrack
US5877757A (en) 1997-05-23 1999-03-02 International Business Machines Corporation Method and system for providing user help information in network applications
EP0902379A2 (en) 1997-09-15 1999-03-17 Xerox Corporation A method and system for organizing documents based upon annotations in context
US5893126A (en) 1994-09-30 1999-04-06 Intel Corporation Method and apparatus for annotating a computer document incorporating sound
US5893132A (en) * 1995-12-14 1999-04-06 Motorola, Inc. Method and system for encoding a book for reading using an electronic book
US5918236A (en) * 1996-06-28 1999-06-29 Oracle Corporation Point of view gists and generic gists in a document browsing system
US5920694A (en) 1993-03-19 1999-07-06 Ncr Corporation Annotation of computer video displays
US5931912A (en) * 1996-08-09 1999-08-03 International Business Machines Corporation Traversal path-based approach to understanding user-oriented hypertext object usage
US5933140A (en) 1997-06-30 1999-08-03 Sun Microsystems, Inc. Child window containing context-based help and a miniaturized web page
US5937416A (en) 1997-03-25 1999-08-10 Bennethum Computer Systems Method for preserving data in an electronic document
US5940080A (en) 1996-09-12 1999-08-17 Macromedia, Inc. Method and apparatus for displaying anti-aliased text
US5950214A (en) 1993-11-19 1999-09-07 Aurigin Systems, Inc. System, method, and computer program product for accessing a note database having subnote information for the purpose of manipulating subnotes linked to portions of documents
US5948040A (en) 1994-06-24 1999-09-07 Delorme Publishing Co. Travel reservation information and planning system
US5956034A (en) 1996-08-13 1999-09-21 Softbook Press, Inc. Method and apparatus for viewing electronic reading materials
WO1999049383A1 (en) 1998-03-20 1999-09-30 Nuvomedia, Inc. Electronic book system
US5978818A (en) 1997-04-29 1999-11-02 Oracle Corporation Automated hypertext outline generation for documents
US5983248A (en) 1991-07-19 1999-11-09 Inso Providence Corporation Data processing system and method for generating a representation for and random access rendering of electronic documents
US5986665A (en) 1996-09-06 1999-11-16 Quantel Limited Electronic graphic system
US6011537A (en) 1997-01-27 2000-01-04 Slotznick; Benjamin System for delivering and simultaneously displaying primary and secondary information, and for displaying only the secondary information during interstitial space
US6012055A (en) 1996-04-09 2000-01-04 Silicon Graphics, Inc. Mechanism for integrated information search and retrieval from diverse sources using multiple navigation methods
US6018742A (en) 1998-07-07 2000-01-25 Perigis Corporation Constructing a bifurcated database of context-dependent and context-independent data items
US6018344A (en) * 1995-11-30 2000-01-25 Matsushita Electric Industrial Co., Ltd. History display apparatus
US6018334A (en) * 1997-02-20 2000-01-25 Eckerberg; Mark Computer pointing device
US6018342A (en) * 1995-07-03 2000-01-25 Sun Microsystems, Inc. Automatically generated content-based history mechanism
US6035330A (en) * 1996-03-29 2000-03-07 British Telecommunications World wide web navigational mapping system and method
US6034689A (en) * 1996-06-03 2000-03-07 Webtv Networks, Inc. Web browser allowing navigation between hypertext objects using remote control
US6037934A (en) 1997-11-21 2000-03-14 International Business Machines Corporation Named bookmark sets
US6038598A (en) 1998-02-23 2000-03-14 Intel Corporation Method of providing one of a plurality of web pages mapped to a single uniform resource locator (URL) based on evaluation of a condition
US6049812A (en) * 1996-11-18 2000-04-11 International Business Machines Corp. Browser and plural active URL manager for network computers
US6052514A (en) 1992-10-01 2000-04-18 Quark, Inc. Distributed publication system with simultaneous separate access to publication data and publication status information
US6054990A (en) 1996-07-05 2000-04-25 Tran; Bao Q. Computer system with handwriting annotation
US6072490A (en) * 1997-08-15 2000-06-06 International Business Machines Corporation Multi-node user interface component and method thereof for use in accessing a plurality of linked records
US6081829A (en) 1996-01-31 2000-06-27 Silicon Graphics, Inc. General purpose web annotations without modifying browser
US6091930A (en) 1997-03-04 2000-07-18 Case Western Reserve University Customizable interactive textbook
US6094197A (en) 1993-12-21 2000-07-25 Xerox Corporation Graphical keyboard
US6122649A (en) 1996-05-30 2000-09-19 Microsoft Corporation Method and system for user defined and linked properties
US6157381A (en) * 1997-11-18 2000-12-05 International Business Machines Corporation Computer system, user interface component and method utilizing non-linear scroll bar
US6163778A (en) 1998-02-06 2000-12-19 Sun Microsystems, Inc. Probabilistic web link viability marker and web page ratings
US6181344B1 (en) 1998-03-20 2001-01-30 Nuvomedia, Inc. Drag-and-release method for configuring user-definable function key of hand-held computing device
US6195694B1 (en) * 1997-03-13 2001-02-27 International Business Machines Corporation Server for reconfiguring control of a subset of devices on one or more kiosks
US6195679B1 (en) * 1998-01-06 2001-02-27 Netscape Communications Corporation Browsing session recording playback and editing system for generating user defined paths and allowing users to mark the priority of items in the paths
US6199082B1 (en) * 1995-07-17 2001-03-06 Microsoft Corporation Method for delivering separate design and content in a multimedia publishing system
US6205455B1 (en) 1995-04-27 2001-03-20 Michael Umen & Co. , Inc. Drug document production system
US6230171B1 (en) 1998-08-29 2001-05-08 International Business Machines Corporation Markup system for shared HTML documents
US6243091B1 (en) * 1997-11-21 2001-06-05 International Business Machines Corporation Global history view
US6266772B1 (en) 1997-07-22 2001-07-24 Fujitsu Limited Authentication system for electronic data objects to be opened to public, and storage medium
US6271840B1 (en) 1998-09-24 2001-08-07 James Lee Finseth Graphical search engine visual index
US6279005B1 (en) 1997-03-04 2001-08-21 Paul Zellweger Method and apparatus for generating paths in an open hierarchical data structure
US6289362B1 (en) 1998-09-01 2001-09-11 Aidministrator Nederland B.V. System and method for generating, transferring and using an annotated universal address
US6301590B1 (en) 1997-08-11 2001-10-09 Viador Method and apparatus for formatting and displaying data from the internet
US6321244B1 (en) * 1997-12-04 2001-11-20 Siemens Corporate Research, Inc. Style specifications for systematically creating card-based hypermedia manuals
US6331867B1 (en) 1998-03-20 2001-12-18 Nuvomedia, Inc. Electronic book with automated look-up of terms of within reference titles
US6356287B1 (en) 1998-03-20 2002-03-12 Nuvomedia, Inc. Citation selection and routing feature for hand-held content display device
US6370497B1 (en) 1998-06-29 2002-04-09 International Business Machines Corp. Natural language transformations for propagating hypertext label changes
US6369811B1 (en) 1998-09-09 2002-04-09 Ricoh Company Limited Automatic adaptive document help for paper documents
US6377983B1 (en) 1998-08-31 2002-04-23 International Business Machines Corporation Method and system for converting expertise based on document usage
US6389434B1 (en) 1993-11-19 2002-05-14 Aurigin Systems, Inc. System, method, and computer program product for creating subnotes linked to portions of data objects after entering an annotation mode
US6393422B1 (en) 1998-11-13 2002-05-21 International Business Machines Corporation Navigation method for dynamically generated HTML pages
US6397264B1 (en) * 1999-11-01 2002-05-28 Rstar Corporation Multi-browser client architecture for managing multiple applications having a history list
US6405221B1 (en) 1995-10-20 2002-06-11 Sun Microsystems, Inc. Method and apparatus for creating the appearance of multiple embedded pages of information in a single web browser display
US6421065B1 (en) 1998-02-09 2002-07-16 Microsoft Corporation Access of online information featuring automatic hide/show function
US20020099552A1 (en) 2001-01-25 2002-07-25 Darryl Rubin Annotating electronic information with audio clips
US20020097261A1 (en) * 1999-11-15 2002-07-25 Gottfurcht Elliot A. Apparatus and method for simple wide-area network navigation
US6446110B1 (en) 1999-04-05 2002-09-03 International Business Machines Corporation Method and apparatus for representing host datastream screen image information using markup languages
US6457013B1 (en) 1997-07-15 2002-09-24 Microsoft Corporation Data formating property modifiers
US6460058B2 (en) * 1996-12-06 2002-10-01 Microsoft Corporation Object-oriented framework for hyperlink navigation
US6486895B1 (en) * 1995-09-08 2002-11-26 Xerox Corporation Display system for displaying lists of linked documents
US6490603B1 (en) 1998-03-31 2002-12-03 Datapage Ireland Limited Method and system for producing documents in a structured format
US6535294B1 (en) 1998-06-23 2003-03-18 Discount Labels, Inc. System and method for preparing customized printed products over a communications network
US6539370B1 (en) 1998-11-13 2003-03-25 International Business Machines Corporation Dynamically generated HTML formatted reports
US6549220B1 (en) * 1999-06-10 2003-04-15 International Business Machines Corporation Method, system, and program for providing pages of information with navigation and content areas
US6560621B2 (en) 1997-12-29 2003-05-06 Intel Corporation World wide web formatting for program output through print function
US6585776B1 (en) 1997-09-08 2003-07-01 International Business Machines Corporation Computer system and method of displaying hypertext documents with internal hypertext link definitions
US6697997B1 (en) 1998-08-12 2004-02-24 Nippon Telegraph And Telephone Corporation Recording medium with a signed hypertext recorded thereon signed hypertext generating method and apparatus and signed hypertext verifying method and apparatus

Family Cites Families (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5337438A (en) * 1992-05-04 1994-08-16 The Babcock & Wilcox Company Method and apparatus for constant progression of a cleaning jet across heated surfaces
US5237648A (en) 1990-06-08 1993-08-17 Apple Computer, Inc. Apparatus and method for editing a video recording by selecting and displaying video clips
JPH07104765B2 (en) 1990-08-24 1995-11-13 ゼロックス コーポレイション Electronic documentation as a user interface to computer-resident software systems
US5347295A (en) 1990-10-31 1994-09-13 Go Corporation Control of a computer through a position-sensed stylus
US5239468A (en) * 1990-12-07 1993-08-24 United Technologies Corporation Automated helicopter maintenance monitoring
DE69434007T2 (en) 1993-07-16 2005-09-15 Sony Corp. image editing system
US5390138A (en) 1993-09-13 1995-02-14 Taligent, Inc. Object-oriented audio system
JP2521035B2 (en) 1993-12-03 1996-07-31 インターナショナル・ビジネス・マシーンズ・コーポレイション Placing annotations on the display
US5822720A (en) 1994-02-16 1998-10-13 Sentius Corporation System amd method for linking streams of multimedia data for reference material for display
US5630125A (en) 1994-05-23 1997-05-13 Zellweger; Paul Method and apparatus for information management using an open hierarchical data structure
US5621871A (en) 1994-08-31 1997-04-15 Jaremko; Mark Automated system and method for annotation using callouts
US5826025A (en) 1995-09-08 1998-10-20 Sun Microsystems, Inc. System for annotation overlay proxy configured to retrieve associated overlays associated with a document request from annotation directory created from list of overlay groups
US5786814A (en) 1995-11-03 1998-07-28 Xerox Corporation Computer controlled display system activities using correlated graphical and timeline interfaces for controlling replay of temporal data representing collaborative activities
US5838313A (en) 1995-11-20 1998-11-17 Siemens Corporate Research, Inc. Multimedia-based reporting system with recording and playback of dynamic annotation
US5761485A (en) 1995-12-01 1998-06-02 Munyan; Daniel E. Personal electronic book system
US5761683A (en) 1996-02-13 1998-06-02 Microtouch Systems, Inc. Techniques for changing the behavior of a link in a hypertext document
US5801685A (en) 1996-04-08 1998-09-01 Tektronix, Inc. Automatic editing of recorded video elements sychronized with a script text read or displayed
US5784058A (en) 1996-05-28 1998-07-21 Sun Microsystems, Inc. User-controllable persistent browser display pages
US6064384A (en) 1996-08-26 2000-05-16 E-Brook Systems Pte Ltd Computer user interface system and method having book image features
US5924104A (en) 1996-10-03 1999-07-13 International Business Machines Corporation Method and apparatus for displaying intradocument links in a computer system
US5890172A (en) * 1996-10-08 1999-03-30 Tenretni Dynamics, Inc. Method and apparatus for retrieving data from a network using location identifiers
GR1002860B (en) * 1997-01-03 1998-02-12 Antiseismic spirals for structures.
US5933139A (en) 1997-01-31 1999-08-03 Microsoft Corporation Method and apparatus for creating help functions
US6141007A (en) 1997-04-04 2000-10-31 Avid Technology, Inc. Newsroom user interface including multiple panel workspaces
US5923326A (en) 1997-06-13 1999-07-13 International Business Machines Corporation Edge docking foster window
US6025841A (en) 1997-07-15 2000-02-15 Microsoft Corporation Method for managing simultaneous display of multiple windows in a graphical user interface
US5982370A (en) 1997-07-18 1999-11-09 International Business Machines Corporation Highlighting tool for search specification in a user interface of a computer system
US5956048A (en) 1997-11-10 1999-09-21 Kerry R. Gaston Electronic book system
US6055538A (en) 1997-12-22 2000-04-25 Hewlett Packard Company Methods and system for using web browser to search large collections of documents
US6151622A (en) 1998-02-02 2000-11-21 International Business Machines Corp. Method and system for portably enabling view synchronization over the world-wide web using frame hierarchies
US6144991A (en) 1998-02-19 2000-11-07 Telcordia Technologies, Inc. System and method for managing interactions between users in a browser-based telecommunications network
US20020013834A1 (en) * 1998-04-20 2002-01-31 Jeffrey Esakov Tracking and graphical display of user activity on an information network
US6154771A (en) 1998-06-01 2000-11-28 Mediastra, Inc. Real-time receipt, decompression and play of compressed streaming video/hypervideo; with thumbnail display of past scenes and with replay, hyperlinking and/or recording permissively intiated retrospectively
US6766494B1 (en) * 1998-06-15 2004-07-20 Fuji Xerox Co., Ltd. Method and system for creating ad-hoc links from free-form ink
US6710790B1 (en) * 1998-08-13 2004-03-23 Symantec Corporation Methods and apparatus for tracking the active window of a host computer in a remote computer display window
US6144375A (en) 1998-08-14 2000-11-07 Praja Inc. Multi-perspective viewer for content-based interactivity
US6076917A (en) 1998-09-30 2000-06-20 Eastman Kodak Company Ink jet printing of color image and annotations
US6631496B1 (en) * 1999-03-22 2003-10-07 Nec Corporation System for personalizing, organizing and managing web information
US6437793B1 (en) * 1999-07-29 2002-08-20 Bitstream Inc. System for rapidly performing scan conversion with anti-aliasing upon outline fonts and other graphic elements
US6904450B1 (en) * 2000-08-09 2005-06-07 Geodata Publishers, Inc. Method and system for customizable network data retrieval

Patent Citations (115)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1987001481A1 (en) 1985-08-30 1987-03-12 Norbert Joseph Stein Electronic book device
US5625833A (en) 1988-05-27 1997-04-29 Wang Laboratories, Inc. Document annotation & manipulation in a data processing system
US5680636A (en) 1988-05-27 1997-10-21 Eastman Kodak Company Document annotation and manipulation in a data processing system
US5146552A (en) 1990-02-28 1992-09-08 International Business Machines Corporation Method for associating annotation with electronically published material
USRE34476E (en) 1990-05-14 1993-12-14 Norwood Donald D Hybrid information management system for handwriting and text
US5239466A (en) 1990-10-04 1993-08-24 Motorola, Inc. System for selectively routing and merging independent annotations to a document at remote locations
US6105044A (en) 1991-07-19 2000-08-15 Enigma Information Systems Ltd. Data processing system and method for generating a representation for and random access rendering of electronic documents
US5983248A (en) 1991-07-19 1999-11-09 Inso Providence Corporation Data processing system and method for generating a representation for and random access rendering of electronic documents
US5666113A (en) 1991-07-31 1997-09-09 Microtouch Systems, Inc. System for using a touchpad input device for cursor control and keyboard emulation
US5632022A (en) * 1991-11-13 1997-05-20 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Encyclopedia of software components
US6052514A (en) 1992-10-01 2000-04-18 Quark, Inc. Distributed publication system with simultaneous separate access to publication data and publication status information
US5434965A (en) 1992-12-23 1995-07-18 Taligent, Inc. Balloon help system
US5920694A (en) 1993-03-19 1999-07-06 Ncr Corporation Annotation of computer video displays
US5838914A (en) 1993-03-19 1998-11-17 Ncr Corporation Collaboration system for allowing computer to draw annotation images on the output of selected program and replicating the annotation images on displays of other computers
US5559942A (en) 1993-05-10 1996-09-24 Apple Computer, Inc. Method and apparatus for providing a note for an application program
US5471568A (en) 1993-06-30 1995-11-28 Taligent, Inc. Object-oriented apparatus and method for scan line conversion of graphic edges
US6243071B1 (en) 1993-11-03 2001-06-05 Apple Computer, Inc. Tool set for navigating through an electronic book
US5802516A (en) 1993-11-03 1998-09-01 Apple Computer, Inc. Method of controlling an electronic book for a computer system
US6389434B1 (en) 1993-11-19 2002-05-14 Aurigin Systems, Inc. System, method, and computer program product for creating subnotes linked to portions of data objects after entering an annotation mode
US5950214A (en) 1993-11-19 1999-09-07 Aurigin Systems, Inc. System, method, and computer program product for accessing a note database having subnote information for the purpose of manipulating subnotes linked to portions of documents
US5729687A (en) 1993-12-20 1998-03-17 Intel Corporation System for sending differences between joining meeting information and public meeting information between participants in computer conference upon comparing annotations of joining and public meeting information
US6094197A (en) 1993-12-21 2000-07-25 Xerox Corporation Graphical keyboard
US5790818A (en) 1993-12-30 1998-08-04 Intel Corporation Remote highlighting of objects in a conferencing system by logically anding a highlight bitmap and a foreground bitmap
US5948040A (en) 1994-06-24 1999-09-07 Delorme Publishing Co. Travel reservation information and planning system
US5434929A (en) 1994-07-12 1995-07-18 Apple Computer, Inc. Method and apparatus for setting character style preferences in a pen-based computer system
US5801687A (en) * 1994-09-30 1998-09-01 Apple Computer, Inc. Authoring tool comprising nested state machines for use in a computer system
US5893126A (en) 1994-09-30 1999-04-06 Intel Corporation Method and apparatus for annotating a computer document incorporating sound
WO1996020908A1 (en) 1994-12-29 1996-07-11 Institut Francais Du Petrole Paraxylene separation process comprising at least two high temperature crystallization stages
US5760773A (en) 1995-01-06 1998-06-02 Microsoft Corporation Methods and apparatus for interacting with data objects using action handles
US6205455B1 (en) 1995-04-27 2001-03-20 Michael Umen & Co. , Inc. Drug document production system
US5719595A (en) 1995-05-09 1998-02-17 Apple Computer, Inc. Method and apparauts for generating a text image on a display with anti-aliasing effect
US6018342A (en) * 1995-07-03 2000-01-25 Sun Microsystems, Inc. Automatically generated content-based history mechanism
US5845262A (en) 1995-07-10 1998-12-01 Hitachi, Ltd. Electronic press information dispatching system
US6199082B1 (en) * 1995-07-17 2001-03-06 Microsoft Corporation Method for delivering separate design and content in a multimedia publishing system
US5687331A (en) 1995-08-03 1997-11-11 Microsoft Corporation Method and system for displaying an animated focus item
US5682439A (en) 1995-08-07 1997-10-28 Apple Computer, Inc. Boxed input correction system and method for pen based computer systems
US6486895B1 (en) * 1995-09-08 2002-11-26 Xerox Corporation Display system for displaying lists of linked documents
US5717860A (en) * 1995-09-20 1998-02-10 Infonautics Corporation Method and apparatus for tracking the navigation path of a user on the world wide web
US5819301A (en) 1995-09-25 1998-10-06 Adobe Systems Incorporated Method and apparatus for reading multi-page electronic documents
US5737599A (en) 1995-09-25 1998-04-07 Rowe; Edward R. Method and apparatus for downloading multi-page electronic documents with hint information
US5860074A (en) 1995-09-25 1999-01-12 Adobe Systems Incorporated Method and apparatus for displaying an electronic document with text over object
US5572643A (en) 1995-10-19 1996-11-05 Judson; David H. Web browser with dynamic display of information objects during linking
US6405221B1 (en) 1995-10-20 2002-06-11 Sun Microsystems, Inc. Method and apparatus for creating the appearance of multiple embedded pages of information in a single web browser display
US5717879A (en) 1995-11-03 1998-02-10 Xerox Corporation System for the capture and replay of temporal data representing collaborative activities
US6018344A (en) * 1995-11-30 2000-01-25 Matsushita Electric Industrial Co., Ltd. History display apparatus
WO1997022109A1 (en) 1995-12-14 1997-06-19 Motorola Inc. Electronic book and method of annotation therefor
US5893132A (en) * 1995-12-14 1999-04-06 Motorola, Inc. Method and system for encoding a book for reading using an electronic book
US5821925A (en) 1996-01-26 1998-10-13 Silicon Graphics, Inc. Collaborative work environment supporting three-dimensional objects and multiple remote participants
US6571295B1 (en) 1996-01-31 2003-05-27 Microsoft Corporation Web page annotating and processing
US6081829A (en) 1996-01-31 2000-06-27 Silicon Graphics, Inc. General purpose web annotations without modifying browser
US5832263A (en) 1996-03-15 1998-11-03 Digidox, Inc. System and method for in-place modification of information recorded in read-only storage using modifiable non-volatile storage associated with an agent
US6035330A (en) * 1996-03-29 2000-03-07 British Telecommunications World wide web navigational mapping system and method
US5835092A (en) * 1996-04-09 1998-11-10 Silicon Graphics, Inc. Mechanism for non-linear browsing of diverse information sources
US6012055A (en) 1996-04-09 2000-01-04 Silicon Graphics, Inc. Mechanism for integrated information search and retrieval from diverse sources using multiple navigation methods
US6122649A (en) 1996-05-30 2000-09-19 Microsoft Corporation Method and system for user defined and linked properties
US6034689A (en) * 1996-06-03 2000-03-07 Webtv Networks, Inc. Web browser allowing navigation between hypertext objects using remote control
US5727129A (en) * 1996-06-04 1998-03-10 International Business Machines Corporation Network system for profiling and actively facilitating user activities
US5918236A (en) * 1996-06-28 1999-06-29 Oracle Corporation Point of view gists and generic gists in a document browsing system
US5854630A (en) * 1996-07-01 1998-12-29 Sun Microsystems, Inc. Prospective view for web backtrack
US6054990A (en) 1996-07-05 2000-04-25 Tran; Bao Q. Computer system with handwriting annotation
WO1998006054A1 (en) 1996-08-05 1998-02-12 Motorola Inc. Book-like interface for browsing on-line documents and methods therefor
US5931912A (en) * 1996-08-09 1999-08-03 International Business Machines Corporation Traversal path-based approach to understanding user-oriented hypertext object usage
US5956034A (en) 1996-08-13 1999-09-21 Softbook Press, Inc. Method and apparatus for viewing electronic reading materials
WO1998009446A2 (en) 1996-08-26 1998-03-05 Seng Beng Ho A browsing system and method for computer information
US5986665A (en) 1996-09-06 1999-11-16 Quantel Limited Electronic graphic system
US5745116A (en) 1996-09-09 1998-04-28 Motorola, Inc. Intuitive gesture-based graphical user interface
US5940080A (en) 1996-09-12 1999-08-17 Macromedia, Inc. Method and apparatus for displaying anti-aliased text
US6049812A (en) * 1996-11-18 2000-04-11 International Business Machines Corp. Browser and plural active URL manager for network computers
US6460058B2 (en) * 1996-12-06 2002-10-01 Microsoft Corporation Object-oriented framework for hyperlink navigation
US6011537A (en) 1997-01-27 2000-01-04 Slotznick; Benjamin System for delivering and simultaneously displaying primary and secondary information, and for displaying only the secondary information during interstitial space
US6018334A (en) * 1997-02-20 2000-01-25 Eckerberg; Mark Computer pointing device
US6091930A (en) 1997-03-04 2000-07-18 Case Western Reserve University Customizable interactive textbook
US6279005B1 (en) 1997-03-04 2001-08-21 Paul Zellweger Method and apparatus for generating paths in an open hierarchical data structure
US6195694B1 (en) * 1997-03-13 2001-02-27 International Business Machines Corporation Server for reconfiguring control of a subset of devices on one or more kiosks
US5937416A (en) 1997-03-25 1999-08-10 Bennethum Computer Systems Method for preserving data in an electronic document
US5978818A (en) 1997-04-29 1999-11-02 Oracle Corporation Automated hypertext outline generation for documents
US5877757A (en) 1997-05-23 1999-03-02 International Business Machines Corporation Method and system for providing user help information in network applications
US5933140A (en) 1997-06-30 1999-08-03 Sun Microsystems, Inc. Child window containing context-based help and a miniaturized web page
US6457013B1 (en) 1997-07-15 2002-09-24 Microsoft Corporation Data formating property modifiers
US6266772B1 (en) 1997-07-22 2001-07-24 Fujitsu Limited Authentication system for electronic data objects to be opened to public, and storage medium
US6301590B1 (en) 1997-08-11 2001-10-09 Viador Method and apparatus for formatting and displaying data from the internet
US6072490A (en) * 1997-08-15 2000-06-06 International Business Machines Corporation Multi-node user interface component and method thereof for use in accessing a plurality of linked records
US6585776B1 (en) 1997-09-08 2003-07-01 International Business Machines Corporation Computer system and method of displaying hypertext documents with internal hypertext link definitions
US6279014B1 (en) 1997-09-15 2001-08-21 Xerox Corporation Method and system for organizing documents based upon annotations in context
EP0902379A2 (en) 1997-09-15 1999-03-17 Xerox Corporation A method and system for organizing documents based upon annotations in context
US6157381A (en) * 1997-11-18 2000-12-05 International Business Machines Corporation Computer system, user interface component and method utilizing non-linear scroll bar
US6037934A (en) 1997-11-21 2000-03-14 International Business Machines Corporation Named bookmark sets
US6243091B1 (en) * 1997-11-21 2001-06-05 International Business Machines Corporation Global history view
US6321244B1 (en) * 1997-12-04 2001-11-20 Siemens Corporate Research, Inc. Style specifications for systematically creating card-based hypermedia manuals
US6560621B2 (en) 1997-12-29 2003-05-06 Intel Corporation World wide web formatting for program output through print function
US6195679B1 (en) * 1998-01-06 2001-02-27 Netscape Communications Corporation Browsing session recording playback and editing system for generating user defined paths and allowing users to mark the priority of items in the paths
US6163778A (en) 1998-02-06 2000-12-19 Sun Microsystems, Inc. Probabilistic web link viability marker and web page ratings
US6421065B1 (en) 1998-02-09 2002-07-16 Microsoft Corporation Access of online information featuring automatic hide/show function
US6038598A (en) 1998-02-23 2000-03-14 Intel Corporation Method of providing one of a plurality of web pages mapped to a single uniform resource locator (URL) based on evaluation of a condition
US6356287B1 (en) 1998-03-20 2002-03-12 Nuvomedia, Inc. Citation selection and routing feature for hand-held content display device
WO1999049383A1 (en) 1998-03-20 1999-09-30 Nuvomedia, Inc. Electronic book system
US6331867B1 (en) 1998-03-20 2001-12-18 Nuvomedia, Inc. Electronic book with automated look-up of terms of within reference titles
US6181344B1 (en) 1998-03-20 2001-01-30 Nuvomedia, Inc. Drag-and-release method for configuring user-definable function key of hand-held computing device
US6490603B1 (en) 1998-03-31 2002-12-03 Datapage Ireland Limited Method and system for producing documents in a structured format
US6535294B1 (en) 1998-06-23 2003-03-18 Discount Labels, Inc. System and method for preparing customized printed products over a communications network
US6370497B1 (en) 1998-06-29 2002-04-09 International Business Machines Corp. Natural language transformations for propagating hypertext label changes
US6018742A (en) 1998-07-07 2000-01-25 Perigis Corporation Constructing a bifurcated database of context-dependent and context-independent data items
US6697997B1 (en) 1998-08-12 2004-02-24 Nippon Telegraph And Telephone Corporation Recording medium with a signed hypertext recorded thereon signed hypertext generating method and apparatus and signed hypertext verifying method and apparatus
US6230171B1 (en) 1998-08-29 2001-05-08 International Business Machines Corporation Markup system for shared HTML documents
US6377983B1 (en) 1998-08-31 2002-04-23 International Business Machines Corporation Method and system for converting expertise based on document usage
US6289362B1 (en) 1998-09-01 2001-09-11 Aidministrator Nederland B.V. System and method for generating, transferring and using an annotated universal address
US6369811B1 (en) 1998-09-09 2002-04-09 Ricoh Company Limited Automatic adaptive document help for paper documents
US6271840B1 (en) 1998-09-24 2001-08-07 James Lee Finseth Graphical search engine visual index
US6393422B1 (en) 1998-11-13 2002-05-21 International Business Machines Corporation Navigation method for dynamically generated HTML pages
US6539370B1 (en) 1998-11-13 2003-03-25 International Business Machines Corporation Dynamically generated HTML formatted reports
US6446110B1 (en) 1999-04-05 2002-09-03 International Business Machines Corporation Method and apparatus for representing host datastream screen image information using markup languages
US6549220B1 (en) * 1999-06-10 2003-04-15 International Business Machines Corporation Method, system, and program for providing pages of information with navigation and content areas
US6397264B1 (en) * 1999-11-01 2002-05-28 Rstar Corporation Multi-browser client architecture for managing multiple applications having a history list
US20020097261A1 (en) * 1999-11-15 2002-07-25 Gottfurcht Elliot A. Apparatus and method for simple wide-area network navigation
US20020099552A1 (en) 2001-01-25 2002-07-25 Darryl Rubin Annotating electronic information with audio clips

Non-Patent Citations (24)

* Cited by examiner, † Cited by third party
Title
"Adobe Acrobat 3.0 Reader Online Guide", Adobe Systems, Inc., pp. 1-110.
"Hucklefine Defined", Apr. 1990, "http://www.ylem.org/artists/mmosher/huck.html", pp. 1-3.
"Tour of Korea Hypercard Stack", 1996, Grose Educational Media, "http://www.entrenet.com/~groedmed/kor2.html", pp. 1-2.
"Tour of Korea Hypercard Stack", 1996, Grose Educational Media, "http://www.entrenet.com/˜groedmed/kor2.html", pp. 1-2.
Bizweb2000.com-screenshots of an e-book, published on May 1999, pp. 1-4 "http://:web.archive.org/web/*/http://www.bizweb2000.com/eshots.htm".
Bizweb2000.com—screenshots of an e-book, published on May 1999, pp. 1-4 "http://:web.archive.org/web/*/http://www.bizweb2000.com/eshots.htm".
Crespo, Chang, Bier: Computer Networks and ISDN Systems "Responsive interaction for a large Web application: the meteror shower architecture in the WebWriter II Editor", 1997, pp. 1508-1517.
Dublin Core Metadata Element Set, Version 1.1: Reference Description 1999.
Dublin Core Metadata Initiative: User Guide Working Draft Jul. 31, 1998 1999.
Dublin Core Resource Types: Structurality DRAFT: Jul. 24, 1997, Feb. 27, 1998.
Explore the Features of the Rocket eBook; wysiwyg://212http://www.rocketbook.com/Products/Tour/index.html.
Graefe, et al: "Designing the muse: A Digital Music Stand for the Symphony Musician", Proc. of Conf on Human Factors In Computing Systems, Apr. 13-18, 1996, pp. 436-441.
Hirotsu et al. "Cmew/U-A Multimedia Web Annotation Sharing System", NTT Network Innovation Laboratories-Japan, IEEE, 1999, pp. 356-359.
Hirotsu et al. "Cmew/U—A Multimedia Web Annotation Sharing System", NTT Network Innovation Laboratories—Japan, IEEE, 1999, pp. 356-359.
Kristensen, A., "Formsheets and the XML, Forms Language" (Mar. 1999).
Kunikazu, T., Patent Abstracts of Japan, Publication No. 11327789 for Color Display and Electronic Blackboard System, published Nov. 30, 1999.
Kuo et al., "A Synchronization Scheme for Multimedia Annotation", Multimedia Information Networking Laboratory, Tamkang University-Taiwan, IEEE, 1997, pp. 594-598.
Kuo et al., "A Synchronization Scheme for Multimedia Annotation", Multimedia Information Networking Laboratory, Tamkang University—Taiwan, IEEE, 1997, pp. 594-598.
Open eBook Forum, Open eBook(TM) Publication Structure 1.0, http://www.ebxwg.org/oebps/oebps1.0/download/oeb1-oebps.htm.
Open eBook Forum, Open eBook™ Publication Structure 1.0, http://www.ebxwg.org/oebps/oebps1.0/download/oeb1-oebps.htm.
Rocket eBook Using the Rocket eBook; http://www.rocketbook.com/Products/Faq/using.html.
Schilit and Price: "Digital Library Information Appliances", ACM Conference on Digital Libraties, Jun. 23, 1992, pp. 217-226.
SOFTBOOK(R) Press The Leader in Internet-Enabled Document Distribution and Reading Systems; http://www.softbook.com/consumer/reader.asp.
SOFTBOOK® Press The Leader in Internet-Enabled Document Distribution and Reading Systems; http://www.softbook.com/consumer/reader.asp.

Cited By (207)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100095201A1 (en) * 1999-08-10 2010-04-15 Sharp Kabushiki Kaisha Electronic book contents recording medium with electronic book contents recorded thereon, electronic book transmission apparatus and electronic book display apparatus
US8627197B2 (en) 1999-12-07 2014-01-07 Microsoft Corporation System and method for annotating an electronic document independently of its content
US20050259120A1 (en) * 2000-05-04 2005-11-24 Stephen Mansfield Method for adding a user-selectable function to a hyperlink
US9569555B2 (en) * 2000-05-04 2017-02-14 Google Inc. Method for adding a user-selectable function to a hyperlink
US20070143439A1 (en) * 2000-05-30 2007-06-21 Alberti Anemometer Llc Personalized multi-service computer environment
US7062475B1 (en) * 2000-05-30 2006-06-13 Alberti Anemometer Llc Personalized multi-service computer environment
US20060253594A1 (en) * 2000-05-30 2006-11-09 Alberti Anemometer Llc Personalized multi-service computer environment
US7596533B2 (en) * 2000-05-30 2009-09-29 Andrew Szabo Personalized multi-service computer environment
US7774358B2 (en) 2000-06-08 2010-08-10 Stg Interactive Multimedia data publishing system
US20030088827A1 (en) * 2000-06-08 2003-05-08 Stg Interactive Multimedia data publishing system
US20060253493A1 (en) * 2000-06-08 2006-11-09 Stg Interactive, A Corporation Of France Multimedia data publishing system
US9613373B2 (en) 2000-12-07 2017-04-04 Paypal, Inc. System and method for retrieving and normalizing product information
US9171056B2 (en) 2000-12-07 2015-10-27 Paypal, Inc. System and method for retrieving and normalizing product information
US8402068B2 (en) 2000-12-07 2013-03-19 Half.Com, Inc. System and method for collecting, associating, normalizing and presenting product and vendor information on a distributed network
US20020107861A1 (en) * 2000-12-07 2002-08-08 Kerry Clendinning System and method for collecting, associating, normalizing and presenting product and vendor information on a distributed network
US9412128B2 (en) 2000-12-07 2016-08-09 Paypal, Inc. System and method for retrieving and normalizing product information
US8768937B2 (en) 2000-12-07 2014-07-01 Ebay Inc. System and method for retrieving and normalizing product information
US20020194280A1 (en) * 2001-06-15 2002-12-19 International Business Machines Corporation Electronic mail system for generating a mail message to multiple recipients with multiple attention levels
US7602379B2 (en) * 2001-06-19 2009-10-13 Hewlett-Packard Development Company, L.P. Digital annotator
US20070180361A1 (en) * 2001-07-11 2007-08-02 International Business Machines Corporation Method and system for dynamic web page breadcrumbing using javascript
US7210094B2 (en) * 2001-07-11 2007-04-24 International Business Machines Corporation Method and system for dynamic web page breadcrumbing using javascript
US20030018665A1 (en) * 2001-07-11 2003-01-23 International Business Machines Corporation Method and system for dynamic web page breadcrumbing using javascript
US8539330B2 (en) 2001-07-11 2013-09-17 International Business Machines Corporation Method and system for dynamic web page breadcrumbing using javascript
US20030135506A1 (en) * 2002-01-16 2003-07-17 Hausheer Kurt J. Method for collating experiences of an interactive internet session
US8103950B2 (en) 2002-01-31 2012-01-24 International Business Machines Corporation Structure and method for linking within a website
US20040205464A1 (en) * 2002-01-31 2004-10-14 International Business Machines Corporation Structure and method for linking within a website
US20070250763A1 (en) * 2002-01-31 2007-10-25 Bates Cary L Structure and method for linking within a website
US7284195B2 (en) * 2002-01-31 2007-10-16 International Business Machines Corporation Structure and method for linking within a website
US20030225858A1 (en) * 2002-05-30 2003-12-04 International Business Machines Corporation Method and apparatus for traversing Web pages in a network data processing system
US20030231220A1 (en) * 2002-06-14 2003-12-18 Fujitsu Limited Novel data processing method and system
US20040001104A1 (en) * 2002-06-28 2004-01-01 Microsoft Corporation Resource browser sessions search
US7225407B2 (en) * 2002-06-28 2007-05-29 Microsoft Corporation Resource browser sessions search
US20040027391A1 (en) * 2002-08-06 2004-02-12 Tu Robert F. Z. Web site navigation under a hierarchical menu structure
US7353460B2 (en) * 2002-08-06 2008-04-01 Robert Tu Consulting Inc. Web site navigation under a hierarchical menu structure
US20040098249A1 (en) * 2002-11-18 2004-05-20 Yaliang Wang Method and system to utilize web resources for language vocabulary learning
US7853899B1 (en) 2002-12-30 2010-12-14 Sap Aktiengesellschaft Configuring and extending a user interface
US20110055738A1 (en) * 2002-12-30 2011-03-03 Frank Damaschke Configurable and Extensible User Interface
US11188978B2 (en) 2002-12-31 2021-11-30 Ebay Inc. Method and system to generate a listing in a network-based commerce system
US20040139143A1 (en) * 2002-12-31 2004-07-15 Canakapalli Sri K. Multi-dimensional navigation for a web browser
US20070106953A1 (en) * 2003-01-06 2007-05-10 Scott Forstall User interface for accessing presentations
US20060265658A1 (en) * 2003-01-06 2006-11-23 Scott Forstall User interface for accessing presentations
US20040133845A1 (en) * 2003-01-06 2004-07-08 Scott Forstall User interface for accessing presentations
US8407574B2 (en) 2003-01-06 2013-03-26 Apple Inc. User interface for accessing presentations
US7823054B2 (en) 2003-01-06 2010-10-26 Apple Inc. Snapback user interface for accessing different document pages directly without going through intermediate pages
US7581164B2 (en) * 2003-01-06 2009-08-25 Apple Inc. User interface for accessing presentations
US20050025390A1 (en) * 2003-05-12 2005-02-03 Osamu Tsujii Information processing apparatus and method
US8775542B2 (en) * 2003-07-04 2014-07-08 Siemens Enterprise Communications Gmbh & Co. Kg Device and method for user-based processing of electronic message comprising file attachments
US20060195526A1 (en) * 2003-07-04 2006-08-31 Thomas Lederer Device and method for user-based processing of electronic message comprising file attachments
US20050080872A1 (en) * 2003-10-08 2005-04-14 Davis Brockton S. Learned upload time estimate module
US7840646B2 (en) 2003-10-08 2010-11-23 Yahoo! Inc. Learned upload time estimate module
US20050197141A1 (en) * 2003-11-10 2005-09-08 Jiang Zhaowei C. 'Back' button schema in mobile applications
US7797529B2 (en) 2003-11-10 2010-09-14 Yahoo! Inc. Upload security scheme
US20050114798A1 (en) * 2003-11-10 2005-05-26 Jiang Zhaowei C. 'Back' button in mobile applications
US20050102381A1 (en) * 2003-11-10 2005-05-12 Jiang Zhaowei C. Upload security scheme
US20050226530A1 (en) * 2004-04-08 2005-10-13 Hajime Murayama Image processing program, image processing method, image processing apparatus and storage medium
US7797724B2 (en) 2004-08-31 2010-09-14 Citrix Systems, Inc. Methods and apparatus for secure online access on a client device
US20090264158A1 (en) * 2004-09-21 2009-10-22 Research In Motion Limited User Interface and Method for Persistent Viewing of a User Selected Folder on a Mobile Device
US8411100B2 (en) * 2004-09-21 2013-04-02 Research In Motion Limited User interface and method for persistent viewing of a user selected folder on a mobile device
US8190676B2 (en) 2004-09-29 2012-05-29 Citrix Systems, Inc. System and method for event detection and re-direction over a network using a presentation level protocol
US8069226B2 (en) 2004-09-30 2011-11-29 Citrix Systems, Inc. System and method for data synchronization over a network using a presentation level protocol
US7523389B2 (en) * 2004-10-19 2009-04-21 International Business Machines Corporation Document display device, method, and program product
US20060085733A1 (en) * 2004-10-19 2006-04-20 International Business Machines Corporation Document display device, method, and program product
US20060236260A1 (en) * 2004-12-09 2006-10-19 Microsoft Corporation Journal display having three dimensional appearance
US8464175B2 (en) * 2004-12-09 2013-06-11 Microsoft Corporation Journal display having three dimensional appearance
US7882447B2 (en) 2005-03-30 2011-02-01 Ebay Inc. Method and system to determine area on a user interface
US20060224954A1 (en) * 2005-03-30 2006-10-05 Corey Chandler Method and system to determine area on a user interface
US9262056B2 (en) 2005-03-30 2016-02-16 Ebay Inc. Methods and systems to browse data items
US10497051B2 (en) 2005-03-30 2019-12-03 Ebay Inc. Methods and systems to browse data items
US11455680B2 (en) 2005-03-30 2022-09-27 Ebay Inc. Methods and systems to process a selection of a browser back button
US20060224406A1 (en) * 2005-03-30 2006-10-05 Jean-Michel Leon Methods and systems to browse data items
US20060224960A1 (en) * 2005-03-30 2006-10-05 Baird-Smith Anselm P Methods and systems to process a selection of a browser back button
US9134884B2 (en) * 2005-03-30 2015-09-15 Ebay Inc. Methods and systems to process a selection of a browser back button
US20110093494A1 (en) * 2005-03-30 2011-04-21 Ebay Inc. Method and system to dynamically browse data items
US11455679B2 (en) 2005-03-30 2022-09-27 Ebay Inc. Methods and systems to browse data items
US8863002B2 (en) 2005-03-30 2014-10-14 Ebay Inc. Method and system to dynamically browse data items
US11461835B2 (en) * 2005-03-30 2022-10-04 Ebay Inc. Method and system to dynamically browse data items
US10559027B2 (en) 2005-03-30 2020-02-11 Ebay Inc. Methods and systems to process a selection of a browser back button
US20060224571A1 (en) * 2005-03-30 2006-10-05 Jean-Michel Leon Methods and systems to facilitate searching a data resource
US20070038952A1 (en) * 2005-06-29 2007-02-15 Erika Reponen Mobile communication terminal
US20070006100A1 (en) * 2005-06-29 2007-01-04 Virpi Roto Mobile communication terminal
US20190095406A1 (en) * 2005-08-03 2019-03-28 Oath Inc. Enhanced favorites service for web browsers and web applications
US20070061755A1 (en) * 2005-09-09 2007-03-15 Microsoft Corporation Reading mode for electronic documents
US20070143688A1 (en) * 2005-12-20 2007-06-21 Cheng Jian H System and method for mark and navigation to facilitate content view
US9933913B2 (en) 2005-12-30 2018-04-03 Apple Inc. Portable electronic device with interface reconfiguration mode
US10884579B2 (en) 2005-12-30 2021-01-05 Apple Inc. Portable electronic device with interface reconfiguration mode
US10915224B2 (en) 2005-12-30 2021-02-09 Apple Inc. Portable electronic device with interface reconfiguration mode
US11650713B2 (en) 2005-12-30 2023-05-16 Apple Inc. Portable electronic device with interface reconfiguration mode
US10359907B2 (en) 2005-12-30 2019-07-23 Apple Inc. Portable electronic device with interface reconfiguration mode
US11449194B2 (en) 2005-12-30 2022-09-20 Apple Inc. Portable electronic device with interface reconfiguration mode
US20070174300A1 (en) * 2006-01-12 2007-07-26 Samsung Electronics Co., Ltd. Method and apparatus for storing and restoring state information of remote user interface
US9094369B2 (en) * 2006-01-12 2015-07-28 Samsung Electronics Co., Ltd. Method and apparatus for storing and restoring state information of remote user interface
US20070186177A1 (en) * 2006-02-03 2007-08-09 Yahoo! Inc. Content navigation interfaces and associated methods
US20070186173A1 (en) * 2006-02-03 2007-08-09 Yahoo! Inc. Instant messenger alerts and organization systems
US20070233377A1 (en) * 2006-04-04 2007-10-04 Brian Salay Content display and navigation interface
US8055444B2 (en) * 2006-04-04 2011-11-08 Yahoo! Inc. Content display and navigation interface
US20070294202A1 (en) * 2006-06-16 2007-12-20 Jos Manuel Accapadi Methodology for file identification and retrieval in directories for categorized files
US20070294277A1 (en) * 2006-06-16 2007-12-20 Jos Manuel Accapadi Methodology for directory categorization for categorized files
US7496595B2 (en) 2006-06-16 2009-02-24 International Business Machines Corporation Methodology for directory categorization for categorized files
US8615535B2 (en) 2006-06-16 2013-12-24 International Business Machines Corporation File identification and retrieval in directories for categorized files
US7483874B2 (en) 2006-06-16 2009-01-27 International Business Machines Corporation File identification and retrieval in directories for categorized files
US8285763B2 (en) 2006-06-16 2012-10-09 International Business Machines Corporation File identification and retrieval in directories for categorized files
US20090100008A1 (en) * 2006-06-16 2009-04-16 International Business Machines Corporation Methodology for File Identification and Retrieval in Directories for Categorized Files
US20080046218A1 (en) * 2006-08-16 2008-02-21 Microsoft Corporation Visual summarization of activity data of a computing session
US10778828B2 (en) 2006-09-06 2020-09-15 Apple Inc. Portable multifunction device, method, and graphical user interface for configuring and displaying widgets
US8881217B2 (en) 2006-09-06 2014-11-04 Verizon Patent And Licensing Inc. Systems and methods for accessing media content
US11240362B2 (en) 2006-09-06 2022-02-01 Apple Inc. Portable multifunction device, method, and graphical user interface for configuring and displaying widgets
US11736602B2 (en) 2006-09-06 2023-08-22 Apple Inc. Portable multifunction device, method, and graphical user interface for configuring and displaying widgets
US10313505B2 (en) 2006-09-06 2019-06-04 Apple Inc. Portable multifunction device, method, and graphical user interface for configuring and displaying widgets
US8316320B2 (en) * 2006-10-03 2012-11-20 Verizon Patent And Licensing Inc. Expandable history tab in interactive graphical user interface systems and methods
US20100251162A1 (en) * 2006-10-03 2010-09-30 Verizon Data Services Inc. Interactive search graphical user interface systems and methods
US8464295B2 (en) 2006-10-03 2013-06-11 Verizon Patent And Licensing Inc. Interactive search graphical user interface systems and methods
US7912829B1 (en) 2006-10-04 2011-03-22 Google Inc. Content reference page
US7908284B1 (en) 2006-10-04 2011-03-15 Google Inc. Content reference page
US8782551B1 (en) * 2006-10-04 2014-07-15 Google Inc. Adjusting margins in book page images
US7979785B1 (en) 2006-10-04 2011-07-12 Google Inc. Recognizing table of contents in an image sequence
US20080098294A1 (en) * 2006-10-23 2008-04-24 Mediq Learning, L.L.C. Collaborative annotation of electronic content
US20080147671A1 (en) * 2006-12-18 2008-06-19 Lampdesk Corporation System for Running Web Applications Offline and Providing Access to Native Services
US20080163127A1 (en) * 2006-12-29 2008-07-03 Microsoft Corporation Enhanced user navigation in a media environment
US8504922B2 (en) 2006-12-29 2013-08-06 Microsoft Corporation Enhanced user navigation to previously visited areas in a media environment
US9367232B2 (en) 2007-01-07 2016-06-14 Apple Inc. Portable multifunction device, method, and graphical user interface supporting user navigations of graphical objects on a touch screen display
US11169691B2 (en) 2007-01-07 2021-11-09 Apple Inc. Portable multifunction device, method, and graphical user interface supporting user navigations of graphical objects on a touch screen display
US10732821B2 (en) 2007-01-07 2020-08-04 Apple Inc. Portable multifunction device, method, and graphical user interface supporting user navigations of graphical objects on a touch screen display
US11586348B2 (en) 2007-01-07 2023-02-21 Apple Inc. Portable multifunction device, method, and graphical user interface supporting user navigations of graphical objects on a touch screen display
US10254949B2 (en) 2007-01-07 2019-04-09 Apple Inc. Portable multifunction device, method, and graphical user interface supporting user navigations of graphical objects on a touch screen display
US9069576B2 (en) 2007-02-13 2015-06-30 Michael G. Buchanan Nestable system and method for accessing, organizing, and interacting with visual representations of data
US20100100852A1 (en) * 2007-02-13 2010-04-22 Buchanan Michael G Nestable system and method for accessing, organizing, and interacting with visual representations of data
US20080244451A1 (en) * 2007-03-30 2008-10-02 Katharina Goering Adaptive dynamic navigational control for navigating within an application
US7877691B2 (en) 2007-03-30 2011-01-25 Sap Ag Adaptive dynamic navigational control for navigating within an application
US20080282199A1 (en) * 2007-05-11 2008-11-13 Demand Media, Inc. Cross taxonomy navigation from a bread crumb in a graphical user interface
US8271901B2 (en) 2007-05-11 2012-09-18 Demand Media, Inc. Cross taxonomy navigation from a bread crumb in a graphical user interface
US20080295021A1 (en) * 2007-05-21 2008-11-27 Laurent An Minh Nguyen Zone-Associated Objects
US8108793B2 (en) * 2007-05-21 2012-01-31 Amazon Technologies, Inc, Zone-associated objects
US10761691B2 (en) 2007-06-29 2020-09-01 Apple Inc. Portable multifunction device with animated user interface transitions
US11507255B2 (en) 2007-06-29 2022-11-22 Apple Inc. Portable multifunction device with animated sliding user interface transitions
US9772751B2 (en) 2007-06-29 2017-09-26 Apple Inc. Using gestures to slide between user interfaces
US11861138B2 (en) 2007-09-04 2024-01-02 Apple Inc. Application menu user interface
US11126321B2 (en) 2007-09-04 2021-09-21 Apple Inc. Application menu user interface
US11010017B2 (en) 2007-09-04 2021-05-18 Apple Inc. Editing interface
US10620780B2 (en) 2007-09-04 2020-04-14 Apple Inc. Editing interface
US11604559B2 (en) 2007-09-04 2023-03-14 Apple Inc. Editing interface
US8005946B2 (en) 2007-09-10 2011-08-23 Microsoft Corporation Managing navigation history for intra-page state transitions
US8239456B2 (en) 2007-09-10 2012-08-07 Microsoft Corporation Managing navigation history for intra-page state transitions
US20090089368A1 (en) * 2007-09-28 2009-04-02 International Business Machines Corporation Automating user's operations
US9355059B2 (en) * 2007-09-28 2016-05-31 International Business Machines Corporation Automating user's operations
US9832285B2 (en) 2007-09-28 2017-11-28 International Business Machines Corporation Automating user's operations
US20090178008A1 (en) * 2008-01-06 2009-07-09 Scott Herz Portable Multifunction Device with Interface Reconfiguration Mode
US10628028B2 (en) 2008-01-06 2020-04-21 Apple Inc. Replacing display of icons in response to a gesture
US9619143B2 (en) * 2008-01-06 2017-04-11 Apple Inc. Device, method, and graphical user interface for viewing application launch icons
US20090204900A1 (en) * 2008-02-13 2009-08-13 International Business Machines Corporation Method And System For Navigation Of Web Sites And Applications
US8826375B2 (en) * 2008-04-14 2014-09-02 Lookwithus.Com Inc. Rich media collaboration system
US20090260060A1 (en) * 2008-04-14 2009-10-15 Lookwithus.Com, Inc. Rich media collaboration system
US20090327973A1 (en) * 2008-04-29 2009-12-31 International Business Machines Corporation Preserving a complete history of a set of application actions when non-linear interactions are permitted
US20100070856A1 (en) * 2008-09-12 2010-03-18 International Business Machines Corporation Method for Graphical Visualization of Multiple Traversed Breadcrumb Trails
US11307763B2 (en) 2008-11-19 2022-04-19 Apple Inc. Portable touch screen device, method, and graphical user interface for using emoji characters
US9342814B2 (en) * 2009-04-07 2016-05-17 Clearslide, Inc. Presentation access tracking system
US20100257456A1 (en) * 2009-04-07 2010-10-07 Clearside, Inc. Presentation access tracking system
US20100306663A1 (en) * 2009-05-27 2010-12-02 International Business Machines Corporation Sequential Clicked Link Display Mechanism
US20110066609A1 (en) * 2009-09-14 2011-03-17 International Business Machines Corporation Crawling Browser-Accessible Applications
US8250059B2 (en) 2009-09-14 2012-08-21 International Business Machines Corporation Crawling browser-accessible applications
US8756214B2 (en) 2009-09-14 2014-06-17 International Business Machines Corporation Crawling browser-accessible applications
US20110091844A1 (en) * 2009-10-20 2011-04-21 Best Roger J Virtual book
US11263679B2 (en) 2009-10-23 2022-03-01 Ebay Inc. Product identification using multiple services
US11500516B2 (en) 2010-04-07 2022-11-15 Apple Inc. Device, method, and graphical user interface for managing folders
US11281368B2 (en) 2010-04-07 2022-03-22 Apple Inc. Device, method, and graphical user interface for managing folders with multiple pages
US11809700B2 (en) 2010-04-07 2023-11-07 Apple Inc. Device, method, and graphical user interface for managing folders with multiple pages
US10788953B2 (en) 2010-04-07 2020-09-29 Apple Inc. Device, method, and graphical user interface for managing folders
US9223475B1 (en) 2010-06-30 2015-12-29 Amazon Technologies, Inc. Bookmark navigation user interface
US9367227B1 (en) * 2010-06-30 2016-06-14 Amazon Technologies, Inc. Chapter navigation user interface
US20120131071A1 (en) * 2010-11-18 2012-05-24 Samsung Electronics Co. Ltd. Apparatus and method for providing e-note function in mobile terminal
US20120159373A1 (en) * 2010-12-15 2012-06-21 Verizon Patent And Licensing, Inc. System for and method of generating dog ear bookmarks on a touch screen device
US20120210237A1 (en) * 2011-02-16 2012-08-16 Computer Associates Think, Inc. Recording A Trail Of Webpages
US8434017B2 (en) 2011-03-21 2013-04-30 Business Objects Software Limited Computer user interface having selectable historical and default values
US20130024804A1 (en) * 2011-07-20 2013-01-24 International Business Machines Corporation Navigation History Tracking In a Content Viewing Environment
US9069743B2 (en) 2011-10-13 2015-06-30 Microsoft Technology Licensing, Llc Application of comments in multiple application functionality content
US10114531B2 (en) 2011-10-13 2018-10-30 Microsoft Technology Licensing, Llc Application of multiple content items and functionality to an electronic content item
US9998509B2 (en) 2011-10-13 2018-06-12 Microsoft Technology Licensing, Llc Application of comments in multiple application functionality content
US9176933B2 (en) 2011-10-13 2015-11-03 Microsoft Technology Licensing, Llc Application of multiple content items and functionality to an electronic content item
US9183314B2 (en) * 2012-04-16 2015-11-10 International Business Machines Corporation Providing browsing history on client for dynamic webpage
US9552142B2 (en) 2012-05-18 2017-01-24 Dropbox, Inc. Systems and methods for displaying file and folder information to a user
US8645466B2 (en) * 2012-05-18 2014-02-04 Dropbox, Inc. Systems and methods for displaying file and folder information to a user
US20130311557A1 (en) * 2012-05-18 2013-11-21 Dropbox, Inc. Systems and methods for displaying file and folder information to a user
US20140164892A1 (en) * 2012-12-11 2014-06-12 Microsoft Corporation Consuming content incrementally
US10250735B2 (en) 2013-10-30 2019-04-02 Apple Inc. Displaying relevant user interface objects
US10972600B2 (en) 2013-10-30 2021-04-06 Apple Inc. Displaying relevant user interface objects
US11316968B2 (en) 2013-10-30 2022-04-26 Apple Inc. Displaying relevant user interface objects
US10275506B1 (en) * 2013-12-20 2019-04-30 Amazon Technologies, Inc. Coordinating data across services
US20150178403A1 (en) * 2013-12-20 2015-06-25 Google Inc. History of Reading Positions in eBooks
US9460221B2 (en) * 2013-12-20 2016-10-04 Google Inc. History of reading positions in eBooks
US20150221037A1 (en) * 2014-02-05 2015-08-06 Wipro Limited System and method for allocting investment fund for an application
US11537679B2 (en) 2014-09-04 2022-12-27 Home Box Office, Inc. Data-driven navigation and navigation routing
US20160070446A1 (en) * 2014-09-04 2016-03-10 Home Box Office, Inc. Data-driven navigation and navigation routing
US20160085878A1 (en) * 2014-09-24 2016-03-24 Lg Electronics Inc. Mobile terminal and method for controlling the same
US9959034B2 (en) * 2014-09-24 2018-05-01 Lg Electronics Inc. Mobile terminal and method for controlling the same
US10084730B2 (en) 2014-10-21 2018-09-25 Unify Gmbh & Co. Kg Apparatus and method for quickly sending messages
US10567318B2 (en) 2014-10-21 2020-02-18 Unify Gmbh & Co. Kg Apparatus and method for quickly sending messages
US10326718B2 (en) 2014-10-21 2019-06-18 Unify Gmbh & Co. Kg Apparatus and method for quickly sending messages
US20160154575A1 (en) * 2014-12-02 2016-06-02 Yingyu Xie Gesture-Based Visualization of Data Grid on Mobile Device
US9904456B2 (en) * 2014-12-02 2018-02-27 Business Objects Software Ltd. Gesture-based visualization of data grid on mobile device
US20160216858A1 (en) * 2015-01-22 2016-07-28 Manzurul Khan Method and program product for an interactive e-book
US10134093B1 (en) * 2015-12-28 2018-11-20 iControl Systems USA, LLC System, method, and computer program for dynamically reconciling a distributor invoice with a retailer receiving invoice for products sold under multiple UPCs and in multiple quantity units
US10825108B1 (en) * 2015-12-28 2020-11-03 iControl Systems USA, LLC System, method, and computer program for dynamically reconciling a distributor invoice with a retailer receiving invoice for products sold under multiple UPCs and in multiple quantity units
US11733656B2 (en) 2016-06-11 2023-08-22 Apple Inc. Configuring context-specific user interfaces
US10739974B2 (en) 2016-06-11 2020-08-11 Apple Inc. Configuring context-specific user interfaces
US11073799B2 (en) 2016-06-11 2021-07-27 Apple Inc. Configuring context-specific user interfaces
US11816325B2 (en) 2016-06-12 2023-11-14 Apple Inc. Application shortcuts for carplay
US11675476B2 (en) 2019-05-05 2023-06-13 Apple Inc. User interfaces for widgets
WO2020237015A1 (en) 2019-05-22 2020-11-26 Sion Power Corporation Electrically coupled electrodes, and associated articles and methods

Also Published As

Publication number Publication date
US7496830B2 (en) 2009-02-24
US20040233235A1 (en) 2004-11-25

Similar Documents

Publication Publication Date Title
US6820111B1 (en) Computer user interface architecture that saves a user's non-linear navigation history and intelligently maintains that history
US7458014B1 (en) Computer user interface architecture wherein both content and user interface are composed of documents with links
US7185274B1 (en) Computer user interface architecture wherein users interact with both content and user interface by activating links
US7243299B1 (en) Methods and apparatus for displaying multiple contexts in electronic documents
US7496856B2 (en) Method and apparatus for capturing and rendering text annotations for non-modifiable electronic content
US6104401A (en) Link filters
KR101083533B1 (en) System and method for user modification of metadata in a shell browser
US6025844A (en) Method and system for creating dynamic link views
US6714214B1 (en) System method and user interface for active reading of electronic content
JP4620922B2 (en) User interface for centralized management and access provision
US5469540A (en) Method and apparatus for generating and displaying multiple simultaneously-active windows
US5488685A (en) Method and apparatus for providing visual cues in a graphic user interface
US7574669B1 (en) User interface control for navigating, selecting, and organizing document pages
JP3973263B2 (en) Method of representing group of graphic objects and computer controlled graphic display system
US9081470B2 (en) Single action selection of data elements
US20100192066A1 (en) Method and system for a graphical user interface
US20050188174A1 (en) Extensible creation and editing of collections of objects
US20080250012A1 (en) In situ search for active note taking
KR20080042877A (en) Reading mode for electronic documents
US9424240B2 (en) Annotations for electronic content
JPH06502734A (en) Computer document as a notebook-type compound document
GB2443241A (en) Data object management
Wang Mac OS X for absolute beginners
JP3651750B2 (en) Document storage retrieval method, document storage retrieval apparatus, and recording medium
Vandome macOS Mojave in easy steps: Covers v 10.14

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RUBIN, DARRYL E.;BAIRD, ANDREW C.;BEEZER, JOHN L.;AND OTHERS;REEL/FRAME:010774/0926;SIGNING DATES FROM 20000217 TO 20000223

AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RUBIN, DARRYL E.;BAIRD, ANDREW C.;BEEZER, JOHN L.;AND OTHERS;REEL/FRAME:011043/0045;SIGNING DATES FROM 20000217 TO 20000223

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0001

Effective date: 20141014

FPAY Fee payment

Year of fee payment: 12