US20110099183A1 - Search-based filtering for property grids - Google Patents
Search-based filtering for property grids Download PDFInfo
- Publication number
- US20110099183A1 US20110099183A1 US12/983,824 US98382411A US2011099183A1 US 20110099183 A1 US20110099183 A1 US 20110099183A1 US 98382411 A US98382411 A US 98382411A US 2011099183 A1 US2011099183 A1 US 2011099183A1
- Authority
- US
- United States
- Prior art keywords
- property
- categories
- grid
- search term
- match
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
Definitions
- Some property grids attempt to mitigate this problem by providing two views of the property grid: a first view that is categorized such that, if the user can find the category for the property he wants to edit, then the number of properties that they have to search is reduced to only those in the category; and a second view that is arranged alphabetically by property name, allowing the user to search visually if he knows the name of the property.
- the user can only effectively search the categorized view if he knows how to categorize the property for which he is looking in the same way that the creators of the categorization did. For this reason most users tend to use a property grid in the alphabetically sorted view. But in the alphabetically sorted view the user must first know the name of the property and then visually search a long list of entries to find the property for which they are looking. This adds overhead or cognitive load to every operation the user wishes to perform in the property grid.
- the present examples provide search-based filtering of a property grid.
- Such filtering allows the user to enter a search term into an easily recognized search text box or apply a user or pre-defined term to a property grid, thus reducing the set of properties visible so that the user has a smaller list to search to find the one on which they desire to operate.
- the search term is typically applied to all properties shown in the property grid. Elements that match the search term are made visible in an updated property grid while those that do not match are not presented.
- the search term may be applied to more than just the name of the property. It may be applied to a category within which the property appears, the type of the property, or any of a number of attributes or tags that may be applied to the property.
- FIG. 1 is block diagram showing an example search-based filter system for property grids typically used in conjunction with a user interface design and development tool or the like.
- FIG. 2 is a diagram showing an example input property grid such as the input property grid described in connection with FIG. 1 .
- FIG. 3 Is a diagram showing an example updated property grid such as the updated property grid described in connection with FIG. 1 .
- FIG. 4 is a block diagram showing an example method of filtering a property grid based on a search term.
- FIG. 5 is a block diagram showing an example computing environment in which the technologies described herein may be implemented.
- FIG. 1 is block diagram showing an example search-based filter (“SBF”) system 100 for property grids typically used in conjunction with a user interface design and development tool or the like.
- SPF system 100 typically accepts a search term 110 as an input from a user. Such a user may be a person and/or a system or the like and the term 110 may be submitted via any suitable interface, such as a user interface (“UI”), an application programming interface (“API”), or the like.
- UI user interface
- API application programming interface
- SBF system 100 also typically interacts with a property grid 120 . Such a property grid 120 may be considered an input property grid.
- SBF system 100 typically provides an updated property grid 140 based on the results of the filtering.
- Input property grid 120 typically represents selected objects 130 rather than all objects present in the UI tool.
- SBF system 100 typically includes a search string parser (“SSP”) 102 that accepts search term 110 .
- Search term 110 may be a single or compound term. For example, a user may filter a property grid using the search term “width”. Alternatively, the user may filter based on several terms such as “width height depth”.
- SSP 102 generally parses the search term string provided by the user into filter 104 , providing input validation and error checking as is common in the art.
- SBF system 100 also typically includes filter 104 that maintains a set of search predicates based on the parses search term string provided by SSP 102 .
- Filter 104 may be applied to an input property grid to search for elements matching the search predicates. For example, given the search term “width”, a single search predicate representing the term “width” is maintained by filter 104 . Alternatively, for given the search term “width height depth”, three search terms are maintained: one for “width”, a second for “height” and a third for “depth”.
- Filter 104 generally searches the input property grid 120 for metadata that either match or contain the search predicates. In one example, such metadata may include properties names, categories, and/or types. Additionally or alternatively, other metadata may be used.
- SBF system 100 includes ApplyFilter Method (“AFM”) 106 .
- AFM 106 checks with filter 104 to see if a match exists between the search term 110 and each property of each category that is currently editable. Generally a category is editable if it is currently presented in property grid 120 , such as when an associated object is selected in a host UI tool. For each category or property match, the result is stored in search results data store (“SRDS”) 108 .
- SRDS search results data store
- SBF system 100 updates the property grid with the results stored in SRDS 108 resulting in updated property grid 140 .
- SRDS 108 may be any suitable data storage mechanism coupled to SBF system 100 , and may or may not be an integral component of SBF system 100 .
- FIG. 2 is a diagram showing an example input property grid 200 such as the input property grid 120 described in connection with FIG. 1 .
- Example fields 202 and 204 indicate the name and type respectively of the object currently selected for which the properties displayed in property grid 200 apply. Alternative display mechanisms may be employed when multiple objects are selected.
- Example categories Brushes 220 , Appearance 230 , and Layout 240 are shown including various property editing tools.
- Appearance category 230 is shown with common properties 232 and a control 234 operable to display advanced properties when selected by a user.
- common properties are those properties of the category designated by the object creator or the like to be most commonly accessed by a user. Such common properties are typically displayed by default in a property grid.
- advanced properties are generally those properties of the category designated less likely to be commonly accessed. Such advanced properties are typically hidden by default, but accessible via a control, such as control 234 , of the property grid.
- Layout category 240 includes a common property Width 242 .
- property grid 200 includes a search term field 210 operable to accept a search term such as search term 110 described in connection with FIG. 1 .
- a property editor is typically some form of edit control used to edit a property value, such as the input field of Width property 242 shown containing the value 134 .
- the term property editor generally refers to a UI mechanism operable to display the name or identifier or the like of the property along with a means of editing the property value.
- Such an editing means may be a simple edit field or input field or the like, or a sophisticated graphical editing mechanism, or any other appropriate editing means.
- FIG. 3 Is a diagram showing an example updated property grid 300 such as the updated property grid 140 described in connection with FIG. 1 .
- the search term “width” has been entered in search term field 310 .
- updated property grid 300 presents to the user only those categories and/or properties that match the search term. For example, given input property grid 200 of FIG. 1 , and the search term “width” as shown in search term field 310 , updated property grid 300 presents Layout category 340 with matching common property Width 342 and matching advanced properties MaxWidth 344 and MinWidth 346 .
- common property area 341 presents the only matching common property 342 and that advanced property area 343 is automatically presented (as indicated by control 345 and the presence of advanced property area 343 ) with the only matching advanced properties 344 and 346 .
- no other categories or properties match search term 310 .
- any number of categories and/or properties may match a search term or portion thereof and be presented in an updated property grid.
- FIG. 4 is a block diagram showing an example method 400 of filtering a property grid based on a search term.
- a search term is provided, such as search term 110 of FIG. 1 , and is parsed into one or more search predicates for use in filtering.
- Filter is typically applied to categories and properties currently presented in an input property grid, including common and advanced properties even if not currently visible in the property grid. Such currently presented categories and properties are typically those associated with currently selected objects in a host UI tool.
- Blocks 402 and 404 typically indicate applying a filter to each category of the input property grid.
- the filter iterates over each category associated with the currently selected objects. For each such category, method 400 typically continues at block 406 .
- Block 406 typically indicates applying the filter to the category to test for a search predicate match. Testing is generally performed for each search predicate. In one example, testing for a match is performed on multiple pieces of metadata associated with the category, including category name and type. Alternatively or additionally, other metadata may be tested. If there is a match, method 400 typically continues at block 408 ; otherwise method 400 typically continues at block 410 .
- Block 408 typically indicates marking the matching category. In one example, this includes storing information about the matching category in a data store, such as SRDS 108 of FIG. 1 . Once marked, method 400 typically continues at block 410 .
- Block 410 typically indicates applying a filter to each property of the current category (per block 404 ; matching or not per block 406 ) of the input property grid.
- the filter iterates over each property associated with the currently selected objects. For each such property, method 400 typically continues at block 412 .
- Block 412 typically indicates applying the filter to the property to test for a search predicate match.
- Testing is generally performed for each search predicate. In one example, testing for a match is performed on multiple pieces of metadata associated with the property, including property name, category, and type. Alternatively or additionally, other metadata may be tested. In one example, if a search predicate is located in a tested piece of metadata, the property is considered matching. For example, the advanced property name “MaxWidth” 344 is considered a match to the search predicate “width”. Note that case may be ignored. If there is a match, method 400 typically continues at block 414 ; otherwise method 400 typically continues at block 422 .
- Block 414 typically indicates marking the matching property. In one example, this includes storing information about the matching property in a data store, such as SRDS 108 of FIG. 1 . Once marked, method 400 typically continues at block 416 .
- Block 416 typically indicates determining is the matching property is an advanced property. If the property is advanced, then method 400 typically continues at block 418 ; otherwise the matching property is a common property and method 400 typically continues at block 420 .
- Block 418 typically indicates marking the category associated with the advanced property as including a matching advanced property. In one example, this includes storing information about the category and matching advanced property in a data store, such as SRDS 108 of FIG. 1 . Once marked, method 400 typically continues at block 422 .
- Block 422 typically indicates marking the category associated with the common property as including a matching advanced property. In one example, this includes storing information about the category and matching advanced property in a data store, such as SRDS 108 of FIG. 1 . Once marked, method 400 typically continues at block 422 .
- Block 422 typically indicates iterating through all properties of the current category (per block 404 ). For the next property, iteration typically continues at block 410 . Once all properties have been iterated, method 400 typically continues at block 424 .
- Block 424 typically indicates notifying any custom property editors associated with the current category of any related category and/or property matches. Such a notification may be used by a custom editor to appropriately configure UI attributes such as tabs containing matching properties, etc. Such notifications are generally provided by the present invention. Such configuration is generally a function of the editor and not of the present invention. A custom property editor is generally an editor not native to a property grid. Once appropriate notifications have been provided, method 400 typically continues at block 428 .
- Block 428 typically indicates iterating through all categories of the input property grid. For the next category, iteration typically continues at block 404 . Once all categories have been iterated, method 400 typically continues at block 430 .
- Block 430 typically indicates updating the property grid based on the filtering results. In one example, this includes reading filter results including information about matching categories and properties from a data store such as SRDS 108 of FIG. 1 . In general, the updated property grid presents only those categories and/or properties matching the search term. In one example, the property grid will continue to present a filtered view so long as the search term field (i.e., search term field 310 of FIG. 3 ) includes an input value. Once the search term field is cleared, the property grid reverts back to its original state.
- the search term field i.e., search term field 310 of FIG. 3
- FIG. 5 is a block diagram showing an example computing environment 500 in which the technologies described herein may be implemented.
- a suitable computing environment may be implemented with numerous general purpose or special purpose systems. Examples of well known systems may include, but are not limited to, cell phones, personal digital assistants (“PDA”), personal computers (“PC”), hand-held or laptop devices, microprocessor-based systems, multiprocessor systems, servers, workstations, consumer electronic devices, set-top boxes, and the like.
- PDA personal digital assistants
- PC personal computers
- microprocessor-based systems multiprocessor systems
- servers workstations
- consumer electronic devices set-top boxes, and the like.
- Computing environment 500 typically includes a general-purpose computing system in the form of a computing device 501 coupled to various components, such as peripheral devices 502 , 503 , 504 and the like.
- System 500 may couple to various other components, such as input devices 503 , including voice recognition, touch pads, buttons, keyboards and/or pointing devices, such as a mouse or trackball, via one or more input/output (“I/O”) interfaces 512 .
- the components of computing device 501 may include one or more processors (including central processing units (“CPU”), graphics processing units (“GPU”), microprocessors (“ ⁇ P”), and the like) 507 , system memory 509 , and a system bus 508 that typically couples the various components.
- processors including central processing units (“CPU”), graphics processing units (“GPU”), microprocessors (“ ⁇ P”), and the like
- Processor 507 typically processes or executes various computer-executable instructions to control the operation of computing device 501 and to communicate with other electronic and/or computing devices, systems or environment (not shown) via various communications connections such as a network connection 514 or the like.
- System bus 508 represents any number of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a serial bus, an accelerated graphics port, a processor or local bus using any of a variety of bus architectures, and the like.
- System memory 509 may include computer readable media in the form of volatile memory, such as random access memory (“RAM”), and/or non-volatile memory, such as read only memory (“ROM”) or flash memory (“FLASH”).
- RAM random access memory
- ROM read only memory
- FLASH flash memory
- a basic input/output system (“BIOS”) may be stored in non-volatile or the like.
- System memory 509 typically stores data, computer-executable instructions and/or program modules comprising computer-executable instructions that are immediately accessible to and/or presently operated on by one or more of the processors 507 .
- Mass storage devices 504 and 510 may be coupled to computing device 501 or incorporated into computing device 501 via coupling to the system bus.
- Such mass storage devices 504 and 510 may include non-volatile RAM, a magnetic disk drive which reads from and/or writes to a removable, non-volatile magnetic disk (e.g., a “floppy disk”) 505 , and/or an optical disk drive that reads from and/or writes to a non-volatile optical disk such as a CD ROM, DVD ROM 506 .
- a mass storage device, such as hard disk 510 may include non-removable storage medium.
- Other mass storage devices may include memory cards, memory sticks, tape storage devices, and the like.
- Any number of computer programs, files, data structures, and the like may be stored in mass storage 510 , other storage devices 504 , 505 , 506 and system memory 509 (typically limited by available space) including, by way of example and not limitation, operating systems, application programs, data files, directory structures, computer-executable instructions, and the like.
- Output components or devices may be coupled to computing device 501 , typically via an interface such as a display adapter 511 .
- Output device 502 may be a liquid crystal display (“LCD”).
- Other example output devices may include printers, audio outputs, voice outputs, cathode ray tube (“CRT”) displays, tactile devices or other sensory output mechanisms, or the like.
- Output devices may enable computing device 501 to interact with human operators or other machines, systems, computing environments, or the like.
- a user may interface with computing environment 500 via any number of different I/O devices 503 such as a touch pad, buttons, keyboard, mouse, joystick, game pad, data port, and the like.
- I/O devices may be coupled to processor 507 via I/O interfaces 512 which may be coupled to system bus 508 , and/or may be coupled by other interfaces and bus structures, such as a parallel port, game port, universal serial bus (“USB”), fire wire, infrared (“IR”) port, and the like.
- I/O interfaces 512 may be coupled to system bus 508 , and/or may be coupled by other interfaces and bus structures, such as a parallel port, game port, universal serial bus (“USB”), fire wire, infrared (“IR”) port, and the like.
- USB universal serial bus
- IR infrared
- Computing device 501 may operate in a networked environment via communications connections to one or more remote computing devices through one or more cellular networks, wireless networks, local area networks (“LAN”), wide area networks (“WAN”), storage area networks (“SAN”), the Internet, radio links, optical links and the like.
- Computing device 501 may be coupled to a network via network adapter 513 or the like, or, alternatively, via a modem, digital subscriber line (“DSL”) link, integrated services digital network (“ISDN”) link, Internet link, wireless link, or the like.
- DSL digital subscriber line
- ISDN integrated services digital network
- Communications connection 514 typically provides a coupling to communications media, such as a network.
- Communications media typically provide computer-readable and computer-executable instructions, data structures, files, program modules and other data using a modulated data signal, such as a carrier wave or other transport mechanism.
- modulated data signal typically means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communications media may include wired media, such as a wired network or direct-wired connection or the like, and wireless media, such as acoustic, radio frequency, infrared, or other wireless communications mechanisms.
- Power source 590 such as a battery or a power supply, typically provides power for portions or all of computing environment 500 .
- power source 590 may be a battery.
- power source 590 may be a power supply designed to connect to an alternating current (“AC”) source, such as via a wall outlet.
- AC alternating current
- an electronic badge may be comprised of a coil of wire along with a simple processing unit 507 or the like, the coil configured to act as power source 590 when in proximity to a card reader device or the like.
- a coil may also be configure to act as an antenna coupled to the processing unit 507 or the like, the coil antenna capable of providing a form of communication between the electronic badge and the card reader device.
- Such communication may not involve networking, but may alternatively be general or special purpose communications via telemetry, point-to-point, RF, IR, audio, or other means.
- An electronic card may not include display 502 , I/O device 503 , or many of the other components described in connection with FIG. 5 .
- Other mobile devices that may not include many of the components described in connection with FIG. 5 , by way of example and not limitation, include electronic bracelets, electronic tags, implantable devices, and the like.
- a remote computer or storage device may store computer-readable and computer-executable instructions in the form of software applications and data.
- a local computer may access the remote computer or storage device via the network and download part or all of a software application or data and may execute any computer-executable instructions.
- the local computer may download pieces of the software or data as needed, or distributively process the software by executing some of the instructions at the local computer and some at remote computers and/or devices.
- DSP digital signal processor
- PLA programmable logic array
- discrete circuits and the like.
- DSP digital signal processor
- electronic apparatus may include computing devices or consumer electronic devices comprising any software, firmware or the like, or electronic devices or circuits comprising no software, firmware or the like.
- firmware typically refers to executable instructions, code, data, applications, programs, or the like maintained in an electronic device such as a ROM.
- software generally refers to executable instructions, code, data, applications, programs, or the like maintained in or on any form of computer-readable media.
- computer-readable media typically refers to system memory, storage devices and their associated media, and the like.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Library & Information Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
Technologies for search-based filtering of a property grid. Such filtering allows a user to enter a search term into an easily recognized search text box, or apply a user or pre-defined term to a property grid, thus reducing the set of properties visible so that the user has a smaller list to search to find the one on which they desire to operate. The search term is typically applied to all properties shown in the property grid. Elements that match the search term are made visible in an updated property grid while those that do not match are not presented. Also, the search term may be applied to more than just the name of the property. It may be applied to a category within which the property appears, the type of the property, or any of a number of attributes or tags that may be applied to the property.
Description
- This application claims benefit of and is a Continuation of U.S. patent application Ser. No. 11/770,719, filed Jun. 28, 2007, which is incorporated herein by reference in its entirety.
- It is common for user interface design and development tools to make use of a “property grid” to provide a user one place to look for the properties of selected objects. Via such a property grid the user can inspect the values of properties and edit properties as appropriate. While such a property grid allows the user to easily discover where a property can be edited, there are often so many properties that the user must spend time finding the particular property that he wants to inspect or edit.
- Some property grids attempt to mitigate this problem by providing two views of the property grid: a first view that is categorized such that, if the user can find the category for the property he wants to edit, then the number of properties that they have to search is reduced to only those in the category; and a second view that is arranged alphabetically by property name, allowing the user to search visually if he knows the name of the property.
- There are several issues with this approach. First, the user can only effectively search the categorized view if he knows how to categorize the property for which he is looking in the same way that the creators of the categorization did. For this reason most users tend to use a property grid in the alphabetically sorted view. But in the alphabetically sorted view the user must first know the name of the property and then visually search a long list of entries to find the property for which they are looking. This adds overhead or cognitive load to every operation the user wishes to perform in the property grid.
- The following presents a simplified summary of the disclosure in order to provide a basic understanding to the reader. This summary is not an extensive overview of the disclosure and it does not identify key/critical elements of the invention or delineate the scope of the invention. Its sole purpose is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later.
- To solve the problems described herein above, the present examples provide search-based filtering of a property grid. Such filtering allows the user to enter a search term into an easily recognized search text box or apply a user or pre-defined term to a property grid, thus reducing the set of properties visible so that the user has a smaller list to search to find the one on which they desire to operate. The search term is typically applied to all properties shown in the property grid. Elements that match the search term are made visible in an updated property grid while those that do not match are not presented. Also, the search term may be applied to more than just the name of the property. It may be applied to a category within which the property appears, the type of the property, or any of a number of attributes or tags that may be applied to the property.
- Many of the attendant features will be more readily appreciated as the same become better understood by reference to the following detailed description considered in connection with the accompanying drawings.
- The present description will be better understood from the following detailed description considered in connection with the accompanying drawings, wherein:
-
FIG. 1 is block diagram showing an example search-based filter system for property grids typically used in conjunction with a user interface design and development tool or the like. -
FIG. 2 is a diagram showing an example input property grid such as the input property grid described in connection withFIG. 1 . -
FIG. 3 . Is a diagram showing an example updated property grid such as the updated property grid described in connection withFIG. 1 . -
FIG. 4 is a block diagram showing an example method of filtering a property grid based on a search term. -
FIG. 5 is a block diagram showing an example computing environment in which the technologies described herein may be implemented. - Like reference numerals are used to designate like parts in the accompanying drawings.
- The detailed description provided below in connection with the accompanying drawings is intended as a description of the present examples and is not intended to represent the only forms in which the present examples may be constructed or utilized. The description sets forth at least some of the functions of the examples and/or the sequence of steps for constructing and operating examples. However, the same or equivalent functions and sequences may be accomplished by different examples.
- Although the present examples are described and illustrated herein as being implemented in a computing environment, the environment described is provided as an example and not a limitation. As those skilled in the art will appreciate, the present examples are suitable for application in a variety of different types of computing environments.
-
FIG. 1 is block diagram showing an example search-based filter (“SBF”)system 100 for property grids typically used in conjunction with a user interface design and development tool or the like.SPF system 100 typically accepts asearch term 110 as an input from a user. Such a user may be a person and/or a system or the like and theterm 110 may be submitted via any suitable interface, such as a user interface (“UI”), an application programming interface (“API”), or the like.SBF system 100 also typically interacts with aproperty grid 120. Such aproperty grid 120 may be considered an input property grid. Once filtering based onsearch term 110 has taken place,SBF system 100 typically provides an updatedproperty grid 140 based on the results of the filtering.Input property grid 120 typically representsselected objects 130 rather than all objects present in the UI tool. -
SBF system 100 typically includes a search string parser (“SSP”) 102 that acceptssearch term 110.Search term 110 may be a single or compound term. For example, a user may filter a property grid using the search term “width”. Alternatively, the user may filter based on several terms such as “width height depth”. SSP 102 generally parses the search term string provided by the user intofilter 104, providing input validation and error checking as is common in the art. - SBF
system 100 also typically includesfilter 104 that maintains a set of search predicates based on the parses search term string provided by SSP 102.Filter 104 may be applied to an input property grid to search for elements matching the search predicates. For example, given the search term “width”, a single search predicate representing the term “width” is maintained byfilter 104. Alternatively, for given the search term “width height depth”, three search terms are maintained: one for “width”, a second for “height” and a third for “depth”.Filter 104 generally searches theinput property grid 120 for metadata that either match or contain the search predicates. In one example, such metadata may include properties names, categories, and/or types. Additionally or alternatively, other metadata may be used. - In one example,
SBF system 100 includes ApplyFilter Method (“AFM”) 106. In this example, AFM 106 checks withfilter 104 to see if a match exists between thesearch term 110 and each property of each category that is currently editable. Generally a category is editable if it is currently presented inproperty grid 120, such as when an associated object is selected in a host UI tool. For each category or property match, the result is stored in search results data store (“SRDS”) 108. Upon completion of the matching by AFM 106, SBFsystem 100 updates the property grid with the results stored in SRDS 108 resulting in updatedproperty grid 140. SRDS 108 may be any suitable data storage mechanism coupled toSBF system 100, and may or may not be an integral component ofSBF system 100. -
FIG. 2 is a diagram showing an exampleinput property grid 200 such as theinput property grid 120 described in connection withFIG. 1 . Example fields 202 and 204 indicate the name and type respectively of the object currently selected for which the properties displayed inproperty grid 200 apply. Alternative display mechanisms may be employed when multiple objects are selected. Example categories Brushes 220,Appearance 230, andLayout 240 are shown including various property editing tools. For example,Appearance category 230 is shown withcommon properties 232 and acontrol 234 operable to display advanced properties when selected by a user. In general, common properties are those properties of the category designated by the object creator or the like to be most commonly accessed by a user. Such common properties are typically displayed by default in a property grid. Alternatively, advanced properties are generally those properties of the category designated less likely to be commonly accessed. Such advanced properties are typically hidden by default, but accessible via a control, such ascontrol 234, of the property grid. As an example,Layout category 240 includes acommon property Width 242. Finally,property grid 200 includes asearch term field 210 operable to accept a search term such assearch term 110 described in connection withFIG. 1 . - A property editor is typically some form of edit control used to edit a property value, such as the input field of
Width property 242 shown containing thevalue 134. As used herein, the term property editor generally refers to a UI mechanism operable to display the name or identifier or the like of the property along with a means of editing the property value. Such an editing means may be a simple edit field or input field or the like, or a sophisticated graphical editing mechanism, or any other appropriate editing means. -
FIG. 3 . Is a diagram showing an example updatedproperty grid 300 such as the updatedproperty grid 140 described in connection withFIG. 1 . Note that the search term “width” has been entered insearch term field 310. Based on the entered search term, updatedproperty grid 300 presents to the user only those categories and/or properties that match the search term. For example, giveninput property grid 200 ofFIG. 1 , and the search term “width” as shown insearch term field 310, updatedproperty grid 300presents Layout category 340 with matchingcommon property Width 342 and matching advanced properties MaxWidth 344 andMinWidth 346. Note thatcommon property area 341 presents the only matchingcommon property 342 and thatadvanced property area 343 is automatically presented (as indicated bycontrol 345 and the presence of advanced property area 343) with the only matchingadvanced properties search term 310. In alternative examples, any number of categories and/or properties may match a search term or portion thereof and be presented in an updated property grid. -
FIG. 4 is a block diagram showing anexample method 400 of filtering a property grid based on a search term. In general, a search term is provided, such assearch term 110 ofFIG. 1 , and is parsed into one or more search predicates for use in filtering. Filter is typically applied to categories and properties currently presented in an input property grid, including common and advanced properties even if not currently visible in the property grid. Such currently presented categories and properties are typically those associated with currently selected objects in a host UI tool. -
Blocks method 400 typically continues atblock 406. - Block 406 typically indicates applying the filter to the category to test for a search predicate match. Testing is generally performed for each search predicate. In one example, testing for a match is performed on multiple pieces of metadata associated with the category, including category name and type. Alternatively or additionally, other metadata may be tested. If there is a match,
method 400 typically continues atblock 408; otherwisemethod 400 typically continues atblock 410. - Block 408 typically indicates marking the matching category. In one example, this includes storing information about the matching category in a data store, such as
SRDS 108 ofFIG. 1 . Once marked,method 400 typically continues atblock 410. - Block 410 typically indicates applying a filter to each property of the current category (per
block 404; matching or not per block 406) of the input property grid. In one example, the filter iterates over each property associated with the currently selected objects. For each such property,method 400 typically continues atblock 412. - Block 412 typically indicates applying the filter to the property to test for a search predicate match. Testing is generally performed for each search predicate. In one example, testing for a match is performed on multiple pieces of metadata associated with the property, including property name, category, and type. Alternatively or additionally, other metadata may be tested. In one example, if a search predicate is located in a tested piece of metadata, the property is considered matching. For example, the advanced property name “MaxWidth” 344 is considered a match to the search predicate “width”. Note that case may be ignored. If there is a match,
method 400 typically continues atblock 414; otherwisemethod 400 typically continues atblock 422. - Block 414 typically indicates marking the matching property. In one example, this includes storing information about the matching property in a data store, such as
SRDS 108 ofFIG. 1 . Once marked,method 400 typically continues atblock 416. - Block 416 typically indicates determining is the matching property is an advanced property. If the property is advanced, then
method 400 typically continues atblock 418; otherwise the matching property is a common property andmethod 400 typically continues atblock 420. - Block 418 typically indicates marking the category associated with the advanced property as including a matching advanced property. In one example, this includes storing information about the category and matching advanced property in a data store, such as
SRDS 108 ofFIG. 1 . Once marked,method 400 typically continues atblock 422. - Block 422 typically indicates marking the category associated with the common property as including a matching advanced property. In one example, this includes storing information about the category and matching advanced property in a data store, such as
SRDS 108 ofFIG. 1 . Once marked,method 400 typically continues atblock 422. - Block 422 typically indicates iterating through all properties of the current category (per block 404). For the next property, iteration typically continues at
block 410. Once all properties have been iterated,method 400 typically continues atblock 424. - Block 424 typically indicates notifying any custom property editors associated with the current category of any related category and/or property matches. Such a notification may be used by a custom editor to appropriately configure UI attributes such as tabs containing matching properties, etc. Such notifications are generally provided by the present invention. Such configuration is generally a function of the editor and not of the present invention. A custom property editor is generally an editor not native to a property grid. Once appropriate notifications have been provided,
method 400 typically continues atblock 428. - Block 428 typically indicates iterating through all categories of the input property grid. For the next category, iteration typically continues at
block 404. Once all categories have been iterated,method 400 typically continues atblock 430. - Block 430 typically indicates updating the property grid based on the filtering results. In one example, this includes reading filter results including information about matching categories and properties from a data store such as
SRDS 108 ofFIG. 1 . In general, the updated property grid presents only those categories and/or properties matching the search term. In one example, the property grid will continue to present a filtered view so long as the search term field (i.e.,search term field 310 ofFIG. 3 ) includes an input value. Once the search term field is cleared, the property grid reverts back to its original state. -
FIG. 5 is a block diagram showing anexample computing environment 500 in which the technologies described herein may be implemented. A suitable computing environment may be implemented with numerous general purpose or special purpose systems. Examples of well known systems may include, but are not limited to, cell phones, personal digital assistants (“PDA”), personal computers (“PC”), hand-held or laptop devices, microprocessor-based systems, multiprocessor systems, servers, workstations, consumer electronic devices, set-top boxes, and the like. -
Computing environment 500 typically includes a general-purpose computing system in the form of acomputing device 501 coupled to various components, such asperipheral devices System 500 may couple to various other components, such asinput devices 503, including voice recognition, touch pads, buttons, keyboards and/or pointing devices, such as a mouse or trackball, via one or more input/output (“I/O”) interfaces 512. The components ofcomputing device 501 may include one or more processors (including central processing units (“CPU”), graphics processing units (“GPU”), microprocessors (“μP”), and the like) 507,system memory 509, and asystem bus 508 that typically couples the various components.Processor 507 typically processes or executes various computer-executable instructions to control the operation ofcomputing device 501 and to communicate with other electronic and/or computing devices, systems or environment (not shown) via various communications connections such as anetwork connection 514 or the like.System bus 508 represents any number of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a serial bus, an accelerated graphics port, a processor or local bus using any of a variety of bus architectures, and the like. -
System memory 509 may include computer readable media in the form of volatile memory, such as random access memory (“RAM”), and/or non-volatile memory, such as read only memory (“ROM”) or flash memory (“FLASH”). A basic input/output system (“BIOS”) may be stored in non-volatile or the like.System memory 509 typically stores data, computer-executable instructions and/or program modules comprising computer-executable instructions that are immediately accessible to and/or presently operated on by one or more of theprocessors 507. -
Mass storage devices computing device 501 or incorporated intocomputing device 501 via coupling to the system bus. Suchmass storage devices DVD ROM 506. Alternatively, a mass storage device, such ashard disk 510, may include non-removable storage medium. Other mass storage devices may include memory cards, memory sticks, tape storage devices, and the like. - Any number of computer programs, files, data structures, and the like may be stored in
mass storage 510,other storage devices - Output components or devices, such as
display device 502, may be coupled tocomputing device 501, typically via an interface such as adisplay adapter 511.Output device 502 may be a liquid crystal display (“LCD”). Other example output devices may include printers, audio outputs, voice outputs, cathode ray tube (“CRT”) displays, tactile devices or other sensory output mechanisms, or the like. Output devices may enablecomputing device 501 to interact with human operators or other machines, systems, computing environments, or the like. A user may interface withcomputing environment 500 via any number of different I/O devices 503 such as a touch pad, buttons, keyboard, mouse, joystick, game pad, data port, and the like. These and other I/O devices may be coupled toprocessor 507 via I/O interfaces 512 which may be coupled tosystem bus 508, and/or may be coupled by other interfaces and bus structures, such as a parallel port, game port, universal serial bus (“USB”), fire wire, infrared (“IR”) port, and the like. -
Computing device 501 may operate in a networked environment via communications connections to one or more remote computing devices through one or more cellular networks, wireless networks, local area networks (“LAN”), wide area networks (“WAN”), storage area networks (“SAN”), the Internet, radio links, optical links and the like.Computing device 501 may be coupled to a network vianetwork adapter 513 or the like, or, alternatively, via a modem, digital subscriber line (“DSL”) link, integrated services digital network (“ISDN”) link, Internet link, wireless link, or the like. -
Communications connection 514, such as a network connection, typically provides a coupling to communications media, such as a network. Communications media typically provide computer-readable and computer-executable instructions, data structures, files, program modules and other data using a modulated data signal, such as a carrier wave or other transport mechanism. The term “modulated data signal” typically means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communications media may include wired media, such as a wired network or direct-wired connection or the like, and wireless media, such as acoustic, radio frequency, infrared, or other wireless communications mechanisms. -
Power source 590, such as a battery or a power supply, typically provides power for portions or all ofcomputing environment 500. In the case of thecomputing environment 500 being a mobile device or portable device or the like,power source 590 may be a battery. Alternatively, in thecase computing environment 500 is a desktop computer or server or the like,power source 590 may be a power supply designed to connect to an alternating current (“AC”) source, such as via a wall outlet. - Some mobile devices may not include many of the components described in connection with
FIG. 5 . For example, an electronic badge may be comprised of a coil of wire along with asimple processing unit 507 or the like, the coil configured to act aspower source 590 when in proximity to a card reader device or the like. Such a coil may also be configure to act as an antenna coupled to theprocessing unit 507 or the like, the coil antenna capable of providing a form of communication between the electronic badge and the card reader device. Such communication may not involve networking, but may alternatively be general or special purpose communications via telemetry, point-to-point, RF, IR, audio, or other means. An electronic card may not includedisplay 502, I/O device 503, or many of the other components described in connection withFIG. 5 . Other mobile devices that may not include many of the components described in connection withFIG. 5 , by way of example and not limitation, include electronic bracelets, electronic tags, implantable devices, and the like. - Those skilled in the art will realize that storage devices utilized to provide computer-readable and computer-executable instructions and data can be distributed over a network. For example, a remote computer or storage device may store computer-readable and computer-executable instructions in the form of software applications and data. A local computer may access the remote computer or storage device via the network and download part or all of a software application or data and may execute any computer-executable instructions. Alternatively, the local computer may download pieces of the software or data as needed, or distributively process the software by executing some of the instructions at the local computer and some at remote computers and/or devices.
- Those skilled in the art will also realize that, by utilizing conventional techniques, all or portions of the software's computer-executable instructions may be carried out by a dedicated electronic circuit such as a digital signal processor (“DSP”), programmable logic array (“PLA”), discrete circuits, and the like. The term “electronic apparatus” may include computing devices or consumer electronic devices comprising any software, firmware or the like, or electronic devices or circuits comprising no software, firmware or the like.
- The term “firmware” typically refers to executable instructions, code, data, applications, programs, or the like maintained in an electronic device such as a ROM. The term “software” generally refers to executable instructions, code, data, applications, programs, or the like maintained in or on any form of computer-readable media. The term “computer-readable media” typically refers to system memory, storage devices and their associated media, and the like.
- In view of the many possible embodiments to which the principles of the present invention and the forgoing examples may be applied, it should be recognized that the examples described herein are meant to be illustrative only and should not be taken as limiting the scope of the present invention. Therefore, the invention as described herein contemplates all such embodiments as may come within the scope of the following claims and any equivalents thereto.
Claims (20)
1. A method of filtering a property grid based on a search term, the method comprising:
determining, by a computer and based on applying a filter to the property grid, that at least one of a plurality of categories of the property grid corresponds to at least one predicate parsed from the search term;
filtering the property grid wherein the filtering comprises marking the corresponding at least one of the plurality of categories;
displaying, by the computer, the filtered property grid wherein the displaying comprises displaying the marked at least one of the plurality of categories but not displaying any unmarked of the plurality of categories of the property grid.
2. The method of claim 1 wherein the applying the filter includes testing for a category match between multiple pieces of category metadata of each of the plurality of categories and the at least one predicate parsed from the search term.
3. The method of claim 2 wherein the determining is further based on the category match.
4. The method of claim 1 wherein the applying the filter includes testing for a property match between multiple pieces of property metadata of each property of each of the plurality of categories and the at least one predicate parsed from the search term.
5. The method of claim 4 wherein the filtering further comprising marking, in response to the testing for a property match, each property that corresponds to a property match.
6. The method of claim 5 wherein the filtering further comprises marking every category of the plurality of categories that includes at least one of the marked properties.
7. The method of claim 5 wherein the displaying further comprises displaying the marked properties.
8. At least one computer storage medium storing computer-executable instructions that, when executed by a computer, cause the computer to perform a method of filtering a property grid based on a search term, the method comprising:
determining, based on applying a filter to the property grid, that at least one of a plurality of categories of the property grid corresponds to at least one predicate parsed from the search term;
filtering the property grid wherein the filtering comprises marking the corresponding at least one of the plurality of categories;
displaying the filtered property grid wherein the displaying comprises displaying the marked at least one of the plurality of categories but not displaying any unmarked of the plurality of categories of the property grid.
9. The at least one computer storage medium of claim 8 wherein the applying the filter includes testing for a category match between multiple pieces of category metadata of each of the plurality of categories and the at least one predicate parsed from the search term.
10. The at least one computer storage medium of claim 9 wherein the determining is further based on the category match.
11. The at least one computer storage medium of claim 8 wherein the applying the filter includes testing for a property match between multiple pieces of property metadata of each property of each of the plurality of categories and the at least one predicate parsed from the search term.
12. The at least one computer storage medium of claim 11 wherein the filtering further comprises marking, in response to the testing for a property match, each property that corresponds to a property match.
13. The at least one computer storage medium of claim 12 wherein the filtering further comprises marking every category of the plurality of categories that includes at least one of the marked properties.
14. The at least one computer storage medium of claim 12 wherein the displaying further comprises displaying the marked properties.
15. A system for filtering a property grid based on a search term, the method comprising:
a computer,
a filter method implemented by the computer and configured for determining, based on applying a filter to the property grid, that at least one of a plurality of categories of the property grid corresponds to at least one predicate parsed from the search term;
the system configured for filtering the property grid wherein the filtering comprises marking the corresponding at least one of the plurality of categories;
the system further configured for displaying the filtered property grid wherein the displaying comprises displaying the marked at least one of the plurality of categories but not displaying any unmarked of the plurality of categories of the property grid.
16. The method of claim 15 wherein the applying the filter includes testing for a category match between multiple pieces of category metadata of each of the plurality of categories and the at least one predicate parsed from the search term.
17. The method of claim 16 wherein the determining is further based on the category match.
18. The method of claim 15 wherein the applying the filter includes testing for a property match between multiple pieces of property metadata of each property of each of the plurality of categories and the at least one predicate parsed from the search term.
19. The method of claim 18 wherein the filtering further comprises marking, in response to the testing for a property match, each property that corresponds to a property match.
20. The method of claim 19 wherein the filtering further comprises marking every category of the plurality of categories that includes at least one of the marked properties, and wherein the displaying further comprises displaying the marked properties.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/983,824 US20110099183A1 (en) | 2007-06-28 | 2011-01-03 | Search-based filtering for property grids |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/770,719 US7890523B2 (en) | 2007-06-28 | 2007-06-28 | Search-based filtering for property grids |
US12/983,824 US20110099183A1 (en) | 2007-06-28 | 2011-01-03 | Search-based filtering for property grids |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/770,719 Continuation US7890523B2 (en) | 2007-06-28 | 2007-06-28 | Search-based filtering for property grids |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110099183A1 true US20110099183A1 (en) | 2011-04-28 |
Family
ID=40161840
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/770,719 Active 2028-04-25 US7890523B2 (en) | 2007-06-28 | 2007-06-28 | Search-based filtering for property grids |
US12/983,824 Abandoned US20110099183A1 (en) | 2007-06-28 | 2011-01-03 | Search-based filtering for property grids |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/770,719 Active 2028-04-25 US7890523B2 (en) | 2007-06-28 | 2007-06-28 | Search-based filtering for property grids |
Country Status (1)
Country | Link |
---|---|
US (2) | US7890523B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103123632A (en) * | 2011-11-21 | 2013-05-29 | 阿里巴巴集团控股有限公司 | Determining method for searching headword and device of searching headword, searching method and searching equipment |
US20190261150A1 (en) * | 2016-06-29 | 2019-08-22 | Cisco Technology, Inc. | Presence indicator signal |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8001076B2 (en) | 2005-07-12 | 2011-08-16 | International Business Machines Corporation | Ranging scalable time stamp data synchronization |
US8510088B2 (en) * | 2008-09-30 | 2013-08-13 | Uchicago Argonne Llc | Flexible evaluator for vehicle propulsion systems |
US8898589B2 (en) | 2011-06-30 | 2014-11-25 | International Business Machines Corporation | Flattening a subset of configuration user interface (UI) panels in a hierarchy of UI panels |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5317742A (en) * | 1991-06-21 | 1994-05-31 | Racal-Datacom, Inc. | Dynamic translation of network management primitives to queries to a database |
US5832459A (en) * | 1994-08-19 | 1998-11-03 | Andersen Consulting Llp | Computerized source searching system and method for use in an order entry system |
US6043817A (en) * | 1995-06-30 | 2000-03-28 | Microsoft Corporation | Method and apparatus for arranging displayed graphical representations on a computer interface |
US6215489B1 (en) * | 1998-09-30 | 2001-04-10 | Harris Corporation | Service creation environment (Meta Model Editor) |
US6226692B1 (en) * | 1995-12-15 | 2001-05-01 | Object Dynamics Corporation | Method and system for constructing software components and systems as assemblies of independent parts |
US20030001892A1 (en) * | 2001-06-14 | 2003-01-02 | International Business Machines Corporation | Property editor graphical user interface apparatus, method and computer program product |
US20040230572A1 (en) * | 2001-06-22 | 2004-11-18 | Nosa Omoigui | System and method for semantic knowledge retrieval, management, capture, sharing, discovery, delivery and presentation |
US20050015405A1 (en) * | 2003-07-18 | 2005-01-20 | Microsoft Corporation | Multi-valued properties |
US20060074730A1 (en) * | 2004-10-01 | 2006-04-06 | Microsoft Corporation | Extensible framework for designing workflows |
US20060150148A1 (en) * | 2004-12-16 | 2006-07-06 | Openspan, Inc. | System and method for non-programmatically constructing software solutions |
US20060155639A1 (en) * | 2000-06-03 | 2006-07-13 | Joan Lynch | System and method for automated process of deal structuring |
US7096465B1 (en) * | 1999-05-17 | 2006-08-22 | Invensys Systems, Inc. | Process control configuration system with parameterized objects |
US20060200466A1 (en) * | 2003-03-27 | 2006-09-07 | Microsoft Corporation | System and Method for Filtering and Organizing Items Based on Common Elements |
US20060206866A1 (en) * | 1999-05-17 | 2006-09-14 | Invensys Systems, Inc. | Methods and apparatus for control configuration using live data |
US20060271441A1 (en) * | 2000-11-14 | 2006-11-30 | Mueller Raymond J | Method and apparatus for dynamic rule and/or offer generation |
US20070038610A1 (en) * | 2001-06-22 | 2007-02-15 | Nosa Omoigui | System and method for knowledge retrieval, management, delivery and presentation |
US20070055680A1 (en) * | 2005-07-29 | 2007-03-08 | Craig Statchuk | Method and system for creating a taxonomy from business-oriented metadata content |
US20080126349A1 (en) * | 2006-06-30 | 2008-05-29 | Microsoft Corporation | Arbitration mechanisms to deal with conflicting applications and user data |
US7523090B1 (en) * | 2004-01-23 | 2009-04-21 | Niku | Creating data charts using enhanced SQL statements |
US7526425B2 (en) * | 2001-08-14 | 2009-04-28 | Evri Inc. | Method and system for extending keyword searching to syntactically and semantically annotated data |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7137102B2 (en) * | 2000-08-09 | 2006-11-14 | Fujitsu Limited | Program development device utilizing component, program development method and medium |
US7464386B2 (en) | 2004-05-17 | 2008-12-09 | Microsoft Corporation | Data controls architecture |
US20050289099A1 (en) * | 2004-06-28 | 2005-12-29 | Sap Aktiengesellschaft | System and method for searching software repositories |
US7451432B2 (en) | 2004-10-01 | 2008-11-11 | Microsoft Corporation | Transformation of componentized and extensible workflow to a declarative format |
US7802186B2 (en) | 2004-10-06 | 2010-09-21 | Microsoft Corporation | Property independent in-place editing |
US7475384B2 (en) | 2004-10-19 | 2009-01-06 | Microsoft Corporation | Binding to types |
JP4863450B2 (en) * | 2005-03-29 | 2012-01-25 | キヤノン株式会社 | Information processing apparatus for customizing device driver program and device driver program customization method |
US7562070B2 (en) | 2005-04-01 | 2009-07-14 | Microsoft Corporation | Method and system for aggregating rules that define values for the same property associated with the same document element |
US20070011183A1 (en) * | 2005-07-05 | 2007-01-11 | Justin Langseth | Analysis and transformation tools for structured and unstructured data |
US8275810B2 (en) * | 2005-07-05 | 2012-09-25 | Oracle International Corporation | Making and using abstract XML representations of data dictionary metadata |
-
2007
- 2007-06-28 US US11/770,719 patent/US7890523B2/en active Active
-
2011
- 2011-01-03 US US12/983,824 patent/US20110099183A1/en not_active Abandoned
Patent Citations (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5317742A (en) * | 1991-06-21 | 1994-05-31 | Racal-Datacom, Inc. | Dynamic translation of network management primitives to queries to a database |
US5832459A (en) * | 1994-08-19 | 1998-11-03 | Andersen Consulting Llp | Computerized source searching system and method for use in an order entry system |
US6043817A (en) * | 1995-06-30 | 2000-03-28 | Microsoft Corporation | Method and apparatus for arranging displayed graphical representations on a computer interface |
US6226692B1 (en) * | 1995-12-15 | 2001-05-01 | Object Dynamics Corporation | Method and system for constructing software components and systems as assemblies of independent parts |
US20010037412A1 (en) * | 1995-12-15 | 2001-11-01 | Miloushev Vladimir I. | Method and system for constructing software components and systems as assemblies of independent parts |
US6215489B1 (en) * | 1998-09-30 | 2001-04-10 | Harris Corporation | Service creation environment (Meta Model Editor) |
US20060206866A1 (en) * | 1999-05-17 | 2006-09-14 | Invensys Systems, Inc. | Methods and apparatus for control configuration using live data |
US7096465B1 (en) * | 1999-05-17 | 2006-08-22 | Invensys Systems, Inc. | Process control configuration system with parameterized objects |
US20060155639A1 (en) * | 2000-06-03 | 2006-07-13 | Joan Lynch | System and method for automated process of deal structuring |
US20060271441A1 (en) * | 2000-11-14 | 2006-11-30 | Mueller Raymond J | Method and apparatus for dynamic rule and/or offer generation |
US20030001892A1 (en) * | 2001-06-14 | 2003-01-02 | International Business Machines Corporation | Property editor graphical user interface apparatus, method and computer program product |
US20040230572A1 (en) * | 2001-06-22 | 2004-11-18 | Nosa Omoigui | System and method for semantic knowledge retrieval, management, capture, sharing, discovery, delivery and presentation |
US20070038610A1 (en) * | 2001-06-22 | 2007-02-15 | Nosa Omoigui | System and method for knowledge retrieval, management, delivery and presentation |
US20070081197A1 (en) * | 2001-06-22 | 2007-04-12 | Nosa Omoigui | System and method for semantic knowledge retrieval, management, capture, sharing, discovery, delivery and presentation |
US7526425B2 (en) * | 2001-08-14 | 2009-04-28 | Evri Inc. | Method and system for extending keyword searching to syntactically and semantically annotated data |
US20060200466A1 (en) * | 2003-03-27 | 2006-09-07 | Microsoft Corporation | System and Method for Filtering and Organizing Items Based on Common Elements |
US20050015405A1 (en) * | 2003-07-18 | 2005-01-20 | Microsoft Corporation | Multi-valued properties |
US7523090B1 (en) * | 2004-01-23 | 2009-04-21 | Niku | Creating data charts using enhanced SQL statements |
US20060074730A1 (en) * | 2004-10-01 | 2006-04-06 | Microsoft Corporation | Extensible framework for designing workflows |
US20060150148A1 (en) * | 2004-12-16 | 2006-07-06 | Openspan, Inc. | System and method for non-programmatically constructing software solutions |
US20070055680A1 (en) * | 2005-07-29 | 2007-03-08 | Craig Statchuk | Method and system for creating a taxonomy from business-oriented metadata content |
US20080126349A1 (en) * | 2006-06-30 | 2008-05-29 | Microsoft Corporation | Arbitration mechanisms to deal with conflicting applications and user data |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103123632A (en) * | 2011-11-21 | 2013-05-29 | 阿里巴巴集团控股有限公司 | Determining method for searching headword and device of searching headword, searching method and searching equipment |
US20190261150A1 (en) * | 2016-06-29 | 2019-08-22 | Cisco Technology, Inc. | Presence indicator signal |
US10616744B2 (en) * | 2016-06-29 | 2020-04-07 | Cisco Technology, Inc. | Presence indicator signal |
Also Published As
Publication number | Publication date |
---|---|
US20090006367A1 (en) | 2009-01-01 |
US7890523B2 (en) | 2011-02-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN112035667B (en) | Knowledge graph display method and device and terminal equipment | |
US9633063B2 (en) | Methods and apparatus for automated redaction of content in a document | |
CA2684822C (en) | Data transformation based on a technical design document | |
US8255387B2 (en) | Systems and methods for modeling partitioned tables as logical indexes | |
EP1875388B1 (en) | Classification dictionary updating apparatus, computer program product therefor and method of updating classification dictionary | |
US20070005634A1 (en) | Templates in a schema editor | |
US20090132952A1 (en) | Localized thumbnail preview of related content during spatial browsing | |
CN107357593A (en) | Source code file construction method, device, electric terminal and readable storage medium storing program for executing | |
US20110099183A1 (en) | Search-based filtering for property grids | |
CN106919711A (en) | The method and apparatus of the markup information based on artificial intelligence | |
WO2009002901A2 (en) | Object model based mapping | |
US20040044954A1 (en) | Data-bidirectional spreadsheet | |
US7587380B2 (en) | Rule processing method, apparatus, and computer-readable medium to generate valid combinations for selection | |
US20140032480A1 (en) | Form template refactoring | |
JP4719212B2 (en) | Method and apparatus for constructing representations of objects and entities | |
US8984455B1 (en) | Methods for generating schematic diagrams and apparatuses using the same | |
CN108133048A (en) | file ordering method, device and mobile terminal | |
CN108228611A (en) | Document information copies method and apparatus | |
CN113687827B (en) | Data list generation method, device and equipment based on widget and storage medium | |
US8959489B2 (en) | Arbitrary object editing | |
JP6836077B2 (en) | Information processing device and its processing method and program | |
CN110018828A (en) | Source code inspection method, device and terminal device | |
CN109618044A (en) | Backlog reminding method and device | |
US7386570B2 (en) | Method, system and program product for providing high performance data lookup | |
JP2024095584A (en) | Methods for loading datasets containing images |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034766/0509 Effective date: 20141014 |