Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
  • G06F16/33—Querying
  • G06F16/332—Query formulation
  • G06F16/3329—Natural language query formulation
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/24—Querying
  • G06F16/242—Query formulation
  • G06F16/2428—Query predicate definition using graphical user interfaces, including menus and forms
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/017—Gesture based interaction, e.g. based on a set of recognized hand gestures
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
  • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
  • G06F3/0482—Interaction with lists of selectable items, e.g. menus
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
  • G06F3/04842—Selection of displayed objects or displayed text elements
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
  • G06F3/0485—Scrolling or panning
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
  • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/103—Formatting, i.e. changing of presentation of documents
  • G06F40/117—Tagging; Marking up; Designating a block; Setting of attributes
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/30—Creation or generation of source code
  • G06F8/34—Graphical or visual programming
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/451—Execution arrangements for user interfaces
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/451—Execution arrangements for user interfaces
  • G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/48—Program initiating; Program switching, e.g. by interrupt
  • G06F9/4806—Task transfer initiation or dispatching
  • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
  • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
  • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration

Definitions

• At least some embodiments described herein relate to a query building mechanism in which a query builder component assists a user in generating queries to be used to populate user interface elements.
• a user interface control itself issues the query with appropriate query parameters and populates the corresponding user interface element with the appropriate query results.
• the query builder component helps select the appropriate query parameters for the user interface control.
• the query schemas are provided to the query builder component in consistent manner across a wide variety of possible user interface controls. Furthermore, the resulting query is provided in a uniform query format. Accordingly, the query builder component may be used for any user interface control, regardless of whether that user interface control is provided by a system, or by an application that runs in the system. Additionally, the user interface elements may be presented from a single class. Accordingly, the user interface element may appear consistent regardless of the identity of the user interface control, with customization occurring in the query parameters themselves.
• Figure 1 abstractly illustrates an example computing system in which the principles described herein may be employed
• Figure 4 illustrates a process whereby an abstract representation of a query may be transformed by different extensions into different query formats for submission to the underlying data source;
• Figure 5 illustrates an example of how the query builder component may be created via a user gesture
• Figure 6 illustrates an example query builder user interface in the case of a locked query
• Figure 8 illustrates a query builder user interface that may be provided for purposes of changing presentation options for the user interface element
• Figure 9 illustrates a user interface in which multiple data views (one for each query) are offered for a user interface element, and in which the user is given the option of generating further views using the query builder component.
• At least some embodiments described herein relate to a query building mechanism in which a query builder component assists a user in generating queries to be used to populate user interface elements.
• a user interface control itself issues the query with appropriate query parameters and populates the corresponding user interface element with the appropriate query results.
• the query builder component helps select the appropriate query parameters for the user interface control.
• the user interface control provides a query schema to the query builder component. For instance, this might be performed at the request of a user that is viewing a user interface element populated by the user interface control.
• the query schema identifies available query parameters that the user interface control is capable of using to populate a corresponding user interface element.
• the query builder component presents at least some of the available query parameters to the user, such that the user may edit these parameters.
• the query parameters may include query fields, and query rules.
• the query builder component gathers those edits and generates a query therefrom.
• the query schemas are provided to the query builder component in consistent manner across a wide variety of possible user interface controls. Furthermore, the resulting query is provided in a uniform query format. Accordingly, the query builder component may be used for any user interface control, regardless of whether that user interface control is provided by a system, or by an application that runs in the system - so long as the user interface control communicates the schema in the right manner, and is able to interpret the unified query format. Additionally, the user interface elements may be presented from a single class. Accordingly, the user interface element may appear consistent regardless of the identity of the user interface control, with customization occurring in the query parameters themselves.
• the user might be presented with presentation options for presenting the user interface element, but the presentation options may also be limited to options that would allow the user interface to retain a certain look and feel. Accordingly, the principles described herein may permit convenient generation of queries, and repopulation of user interface elements with different data, regardless of there being many different sources for the user interface controls.
• the principles described herein may enable a distributed and composite application in which the user may control information that they see, and otherwise customize the user interface to fit their needs. For instance, for data sets that are projected through different visual experiences (like grids, charts, summaries, and so forth), the user can change the parameters that result in getting that data from the data source. Users do this through a user experience that is standardized over a system.
• the principles described herein may be implemented using a computing system.
• the users may be engaging with a portal that displayed multiple user interface elements using a client computing system.
• the executable logic supporting the portal and providing visualizations thereon may also be performed using a computing system.
• the computing system may even be distributed. Accordingly, a brief description of a computing system will now be provided.
• Computing systems are now increasingly taking a wide variety of forms.
• Computing systems may, for example, be handheld devices, appliances, laptop computers, desktop computers, mainframes, distributed computing systems, or even devices that have not conventionally been considered a computing system.
• the term "computing system” is defined broadly as including any device or system (or combination thereof) that includes at least one physical and tangible processor, and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by the processor.
• the memory may take any form and may depend on the nature and form of the computing system.
• a computing system may be distributed over a network environment and may include multiple constituent computing systems.
• a computing system 100 typically includes at least one processing unit 102 and memory 104.
• the memory 104 may be physical system memory, which may be volatile, non-volatile, or some combination of the two.
• the term “memory” may also be used herein to refer to nonvolatile mass storage such as physical storage media. If the computing system is distributed, the processing, memory and/or storage capability may be distributed as well.
• the term "executable module” or “executable component” can refer to software objects, routines, or methods that may be executed on the computing system. The different components, modules, engines, and services described herein may be implemented as objects or processes that execute on the computing system (e.g., as separate threads).
• embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors of the associated computing system that performs the act direct the operation of the computing system in response to having executed computer- executable instructions.
• such computer-executable instructions may be embodied on one or more computer-readable media that form a computer program product.
• An example of such an operation involves the manipulation of data.
• the computer-executable instructions (and the manipulated data) may be stored in the memory 104 of the computing system 100.
• Computing system 100 may also contain communication channels 108 that allow the computing system 100 to communicate with other message processors over, for example, network 110.
• Embodiments described herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below.
• Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures.
• Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system.
• Computer-readable media that store computer-executable instructions are physical storage media.
• Computer-readable media that carry computer- executable instructions are transmission media.
• embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: computer storage media and transmission media.
• Computer storage media includes RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
• program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (or vice versa).
• computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a "NIC"), and then eventually transferred to computer system RAM and/or to less volatile computer storage media at a computer system.
• a network interface module e.g., a "NIC”
• NIC network interface module
• computer storage media can be included in computer system components that also (or even primarily) utilize transmission media.
• Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
• the computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.
• the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, pagers, routers, switches, and the like.
• the invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks.
• program modules may be located in both local and remote memory storage devices.
• the system offers a user interface (or a "portal") that displays multiple user interface elements that may also be called herein “parts”.
• the part acts as a container for the results of execution of one or more underlying user interface controls (also called herein simply "controls").
• the manner of display of the part may be customized, as may be the ordering and composition of the part with respect to other user interface elements.
• the execution of the controls often involves one or more underlying queries to retrieve information that is displayed in the part, or otherwise processed.
• the user may modify the underlying query that retrieves the information. This allows the users to further control the user experience in fundamental ways, such as defining the actual data that is being displayed. In accordance with the principles described herein, this capability is offered in a consistent way, which honors the constraints of the portal to provide a portal in which many contributors may offer parts without sacrificing a consistent look and feel of the portal. Accordingly, the query customizations described herein may be applied to any part, regardless of the contributor of the part.
• the principles described herein allow the user to filter different sets of displayed data, and do further queries on their data sources. Even though the data sources are different depending on the part, the representation of the query may share a common visual representation. For instance the common visual representation may be a set of conditions connected by logical connectors and, eventually, groupings.
• the query building capability includes a query builder user interface element that is displayed to a user and represents a user interface for authoring queries over data sources.
• the query building capability also includes a query building component that receives query schemas from the user interface control, manifests at least some of the query schemas via the query builder user interface element, and then builds a formal representation of a query based on user edits conducted through user interaction with the query builder user interface element.
• Figure 2 illustrates an environment 200 that shows collaborating elements that facilitate a query building capability.
• the environment 200 includes a user interface control 210, a query builder component 220, a query builder user interface 230, and a user interface element 240.
• the user interface control 210 is queriable in that it may generate a submit queries, and populate the corresponding user interface element 240 with at least a portion of the query results.
• a query builder component 220 exposes an input interface whereby the user interface control 210 may provide a query schema 201 to the query builder component (reference arrow 211).
• the query schema 201 identifies available parameters for composing queries that the corresponding user interface control 210 is capable of using to populate the corresponding user interface element 240.
• the query builder component 220 then proceeds to build a query corresponding to the schema.
• the query builder component 220 may proceed to build a distinct query in response to each of multiple schemas received various different times at the query builder component 220.
• the query builder component may operate as described herein to build multiple queries, each selectable to provide a different view of the user interface element.
• the query builder component 220 builds queries by generating a query builder user interface 230 (reference arrow 212).
• the query builder user interface 230 is built from a particular query builder user interface class and thus there is some similarity in appearance each time the query builder component 230 generates a query builder using interface.
• the query builder user interface 230 may be customized to the corresponding user interface control 210 by presenting at least some of the available query parameters to the user. In the case of query builder user interface 230, a name field, an age field, and a newness status field are presented to the user. At this point, the user may interact with the query builder user interface 230 to edit the query parameters.
• the query builder component 220 determines that a query is to be built based on the edited data in the query builder user interface 230 (reference arrow 213).
• the query builder component 220 then generates a query using the then current values of the available query parameters.
• the query is generated in a pre-existing format recognized by the user interface control 210.
• the user might select the Save button in the query builder user interface 230, causing the query builder component 220 to generate an Abstract Syntax Tree (AST) representation 202 of the query.
• AST Abstract Syntax Tree
• the Abstract Syntax Tree representation is an example of a uniform query format that the user interface element 210 may then access (reference arrow 214) from an output interface of the query builder component 220.
• the user interface control 210 then performs the query and provides the resulting data for presentation in the corresponding user interface element 240 (reference arrow 215).
• Figure 3 illustrates more specific example operations of the user interface control 310, the query builder component 320, and the query builder user interface 330, which may be examples of the respective elements 210, 220 and 230 of Figure 2.
• the "Control UX" represents an example query builder user interface.
• the query builder user interface 330 presents a user experience for authoring queries, the user experience being data driven from the schema provided by the part.
• the query builder user interface 330 presents at least some of the available query parameters to a user.
• the query builder user interface 330 shows date range fields, an "assigned to" field, a state field, and tags fields. Those fields may be defined by the query schema provided by the user interface control 310. Likewise, those queries are grouped in a certain way using logical operators. Such groupings may also be defined by the query schema provided by the user interface control 310. Thus, the schema defines available fields and rules for composing a query, and the query building user interface presents at least some of those fields and rules to a user for editing.
• a visual query created by a user results in an abstract query representation based on a portal-defined Abstract Syntax Tree (AST).
• This Abstract Syntax Tree is created by the query builder component 320, and represents the predicates of the query.
• the query is then passed to the user interface control 310 (i.e., the data layer or the owner of the data).
• the AST format may be uniform across the system so that all data sources and schemas will project the same user experience (e.g., display the same query builder control albeit driven by different data and schemas) and the same predicated definition (e.g., via the AST).
• the user interface control (or some other portion of the data layer) receives the AST and translates to their query format of choice.
• intrinsic parts may be offered by the system itself and have a standard component for execution abstract representations of a predicate in a certain format (e.g., OData).
• an application provider may have provided a set of parts for execution within the system.
• the application provider also includes a component for executing abstract representations of a predicate, but perhaps in a different format than the system.
• the data layer may thus translate the query format to an abstract representation of choice.
• the results are returned to the user interface element (or part) that projects the resulting data set on the screen.
• a primary connecting piece is the abstract predicate representation (AST with the query). Multiple user experiences can end up generating an instance of a predicate following this schema. Predicates can be later translated into different types of queries, depending on the target data source. For instance, the tree can be translated to OData predicates, SQL queries, and so forth.
• the available components (or fields) of the query are metadata-driven. By doing this, different configurations of predicates can be produced using the same stack (e.g. queries for bugs, web sites, team members, etc.).
• the query builder component is data-driven and results in a consistent experience regardless of which entity generated the part.
• Any application can provide a schema associated with any of their parts and as a result of getting a query builder component, the application will get an updated query based on user input.
• the AST that represents the query is a uniform abstraction in the system. Once an application (often referred to as an "extension" herein) receives a query, it is the applications responsibility to get the AST (the query representation) and transform it to a query to their underlying data repository. By default the system provides some converters to popular formats, but applications parse the AST and issue the query to the backend. The query builder itself does not run the query.
• the extension could also decide to not use the query builder control and generating their own UI (built out of our existing controls, so they still have user experience consistency). In this case, the same contracts apply (metadata + AST). This allows for extra flexibility and is an extensibility point.
• the query builder user interface can be initiated by a gesture.
• Figure 5 shows an example where that gesture is a right-click command, but that is just one of an infinitely variety of gestures that might be chosen.
• the query builder is displayed. This option might only be available for user interface controls that honor the query building contract that allows the part to be queriable as previously described.
• the queries generated by the query builder component can have two modes; namely, locked and unlocked.
• Figure 6 illustrates an example query builder user interface in the case of a locked query.
• the implementation is similar to the query building already described.
• the query builder control receives a schema with all the available presentation options. To preserve a consistent look and feel of the portion, the presentation options provided by the schema may be constrained to what is supported by the system. After the user inputs their desired selection, the selection is returned back to the originating part to be applied.
• the query builder control does not have any control over how data is presented in the actual part, but just presents available options and collects preferences from the user.
• Queries created with the query builder control can be saved and associated with the originator. By doing this, a user can have multiple data or presentation views that can be associated to a given part.
• Figure 9 illustrates a user interface in which multiple data views are offered for a part, and in which the user is given the option of generating further views (using the query builder control).
• the principles described herein provide a convenient manner for allowing users to control what data is being presented in a user interface element. Furthermore, such query building may be performed in a consistent manner regardless of whether the user interface element is an intrinsic or extrinsic user interface element. Furthermore, since any user interface element that is queriable may user the query building component, so long as the user interface element abides by the contract with the query builder component, this query building may be enabled in a composable system in which there are many contributors of user interface elements.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Software Systems (AREA)
• Human Computer Interaction (AREA)
• Mathematical Physics (AREA)
• Computational Linguistics (AREA)
• Artificial Intelligence (AREA)
• Data Mining & Analysis (AREA)
• Databases & Information Systems (AREA)
• Audiology, Speech & Language Pathology (AREA)
• General Health & Medical Sciences (AREA)
• Health & Medical Sciences (AREA)
• User Interface Of Digital Computer (AREA)
• Stored Programmes (AREA)
• Image Analysis (AREA)
• Woven Fabrics (AREA)

Applications Claiming Priority (24)

Publications (1)

Family

ID=52741177

Family Applications (7)

Family Applications Before (2)

Family Applications After (4)

Country Status (17)

Families Citing this family (38)

Citations (2)

Family Cites Families (180)

• 2014
  • 2014-04-01 US US14/231,862 patent/US9792354B2/en active Active
  • 2014-04-01 US US14/231,912 patent/US20150095849A1/en not_active Abandoned
  • 2014-04-01 US US14/231,891 patent/US9483549B2/en not_active Expired - Fee Related
  • 2014-04-01 US US14/231,883 patent/US9672276B2/en not_active Expired - Fee Related
  • 2014-04-01 US US14/231,917 patent/US20150095846A1/en not_active Abandoned
  • 2014-04-01 US US14/231,873 patent/US20150095812A1/en not_active Abandoned
  • 2014-04-01 US US14/231,880 patent/US20150095365A1/en not_active Abandoned
  • 2014-04-01 US US14/231,846 patent/US20150095842A1/en not_active Abandoned
  • 2014-04-01 US US14/231,869 patent/US9754018B2/en not_active Expired - Fee Related
  • 2014-04-01 US US14/231,905 patent/US9727636B2/en not_active Expired - Fee Related
  • 2014-04-01 US US14/231,897 patent/US9805114B2/en not_active Expired - Fee Related
  • 2014-08-28 TW TW103129730A patent/TW201528106A/zh unknown
  • 2014-09-24 TW TW103133045A patent/TW201516834A/zh unknown
  • 2014-09-24 TW TW103133046A patent/TW201528108A/zh unknown
  • 2014-09-25 WO PCT/US2014/057324 patent/WO2015048206A1/en not_active Ceased
  • 2014-09-25 WO PCT/US2014/057321 patent/WO2015048203A1/en not_active Ceased
  • 2014-09-25 CN CN201480054050.6A patent/CN105593813B/zh active Active
  • 2014-09-25 WO PCT/US2014/057322 patent/WO2015048204A1/en not_active Ceased
  • 2014-09-25 KR KR1020167008327A patent/KR102186865B1/ko not_active Expired - Fee Related
  • 2014-09-25 EP EP14825480.8A patent/EP3053031A1/en not_active Ceased
  • 2014-09-25 EP EP14783733.0A patent/EP3053027A1/en not_active Ceased
  • 2014-09-25 CN CN201480053811.6A patent/CN105683907B/zh active Active
  • 2014-09-25 CN CN201480054151.3A patent/CN105683909B/zh active Active
  • 2014-09-25 WO PCT/US2014/057323 patent/WO2015048205A1/en not_active Ceased
  • 2014-09-25 EP EP14783734.8A patent/EP3053028B1/en active Active
  • 2014-09-25 TW TW103133249A patent/TW201528103A/zh unknown
  • 2014-09-29 JP JP2016518686A patent/JP6465870B2/ja not_active Expired - Fee Related
  • 2014-09-29 CA CA2922725A patent/CA2922725A1/en not_active Abandoned
  • 2014-09-29 RU RU2016111610A patent/RU2686822C2/ru not_active IP Right Cessation
  • 2014-09-29 MX MX2016004113A patent/MX2016004113A/es unknown
  • 2014-09-29 CN CN201480054049.3A patent/CN105593812A/zh active Pending
  • 2014-09-29 EP EP14783748.8A patent/EP3053029A1/en not_active Ceased
  • 2014-09-29 JP JP2016518687A patent/JP6446038B2/ja not_active Expired - Fee Related
  • 2014-09-29 CN CN201480053988.6A patent/CN105683908B/zh not_active Expired - Fee Related
  • 2014-09-29 CN CN201480053821.XA patent/CN105659199A/zh active Pending
  • 2014-09-29 EP EP14786398.9A patent/EP3053030A1/en not_active Withdrawn
  • 2014-09-29 WO PCT/US2014/057938 patent/WO2015048600A1/en not_active Ceased
  • 2014-09-29 WO PCT/US2014/057940 patent/WO2015048602A1/en not_active Ceased
  • 2014-09-29 AU AU2014324618A patent/AU2014324618A1/en not_active Abandoned
  • 2014-09-29 RU RU2016111604A patent/RU2679540C2/ru not_active IP Right Cessation
  • 2014-09-29 EP EP14790838.8A patent/EP3053017A1/en not_active Withdrawn
  • 2014-09-29 SG SG10201802632SA patent/SG10201802632SA/en unknown
  • 2014-09-29 BR BR112016004551A patent/BR112016004551A8/pt not_active Application Discontinuation
  • 2014-09-29 KR KR1020167008368A patent/KR20160064115A/ko not_active Withdrawn
  • 2014-09-29 KR KR1020167008352A patent/KR20160063340A/ko not_active Withdrawn
  • 2014-09-29 MX MX2016003946A patent/MX2016003946A/es unknown
  • 2014-09-29 CA CA2922985A patent/CA2922985A1/en not_active Abandoned
  • 2014-09-29 HK HK16110904.6A patent/HK1222731A1/zh unknown
  • 2014-09-29 SG SG11201601888UA patent/SG11201601888UA/en unknown
  • 2014-09-29 WO PCT/US2014/057939 patent/WO2015048601A1/en not_active Ceased
  • 2014-09-29 AU AU2014324620A patent/AU2014324620A1/en not_active Abandoned
• 2016
  • 2016-02-05 PH PH12016500256A patent/PH12016500256A1/en unknown
  • 2016-03-01 IL IL244368A patent/IL244368A0/en unknown
  • 2016-03-30 CL CL2016000729A patent/CL2016000729A1/es unknown

Patent Citations (2)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events