CA2388150A1 - Toggleable widget for a user interface - Google Patents
Toggleable widget for a user interface Download PDFInfo
- Publication number
- CA2388150A1 CA2388150A1 CA002388150A CA2388150A CA2388150A1 CA 2388150 A1 CA2388150 A1 CA 2388150A1 CA 002388150 A CA002388150 A CA 002388150A CA 2388150 A CA2388150 A CA 2388150A CA 2388150 A1 CA2388150 A1 CA 2388150A1
- Authority
- CA
- Canada
- Prior art keywords
- user
- value
- widget
- entry field
- toggleable
- 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
- 238000000034 method Methods 0.000 claims description 34
- 230000008859 change Effects 0.000 claims description 2
- 239000002131 composite material Substances 0.000 abstract description 2
- 238000013459 approach Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000002730 additional effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000035807 sensation Effects 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/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/0489—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 dedicated keyboard keys or combinations thereof
- G06F3/04895—Guidance during keyboard input operation, e.g. prompting
Abstract
A composite interface widget for toggleable entry fields that minimizes real estate and allows the entry field to toggle between a special kind of input that is either a predefined value or a value specified by the user. The widget presents a local or noninherited state which enables the widget to have an entry field with editing capability; alternatively, the widget offers an inherit state having a read-only entry field that displays a preset input string. The user is given a small concise button or other icon to toggle between the two states. The programmer specifies the initial state, the string to display in the inherit mode, and the initial value for the local or noninherit mode. The programmer can subsequently query if the user chose the inherit mode or chose the local mode and, if so, what local value was entered.
Description
14 .d .; . n~ I I
TOGGLEABLE WIDGET FOR A USER INTERFACE
TECHNICAL FIELD
This invention relates generally to the field of computer user interfaces and more particularly relates to a widget or an entry field from which a user can toggle on an inherited value or on a noninherited value which then allows the user to enter another value.
BACKGROUND OF THE INVENTION
A user interface is that by which a computer user interacts with a computer and its various programs called applications. A nearly universal format of user interface for personal computer systems and personal digital assistants (PDAs) is a visual interface - called a graphical user interface:
GUI (pronounced goo' eee). Other user interfaces may be tactile or may be aural. Typically with graphical user interfaces, the user controls a graphical pointer such as a mouse, a track ball, a glidepad, or stylus to interact with a display of a graphical user interface.
Depending upon the actions allowed by the application or operating system software, the user can select a feature of the graphical display such as an icon or an entry field by positioning the graphical pointer over the feature and making a selection utilizing the graphical pointing device. These features have come to be called widgets.
The actions available to a user following selection of a widget can depend upon a number of factors including the type of widget that was selected and the order of the selection in the current interaction scenario. For example, if the user selects a icon on the desktop or within a window with a single click of a mouse button, the user can typically relocate the icon within the graphical display utilizing the well-known drag-and-drop technique. Alternatively, if the selected widget is a menu bar choice, a dropdown menu may be displayed permitting the user to make a single selection from among the choices listing in the dropdown menu. In response to either the selection of a point outside of the dropdown menu indicating that the user does not wish to select any choice listed in the dropdown menu or the selection of a dropdown menu choice, the dropdown menu closes automatically.
Object-oriented programming (OOP) is becoming the normative computer programming paradigm because it allows programmers to approach their programming tasks more intuitively by using objects rather than procedures as the fundamental building blocks for creating computer programs. Objects are small reusable sections of program code that can be quickly and easily combined to create new and many different applications across a network irrespective of the computer processor's architecture and/or operating system. Conceptually, an obj ect is an entity that is able to save information, referred to as its state, and offers a number of behaviors or functions to either examine or affect this state. An object may model the attributes or characteristics of the real-world object and, in many cases, may also model its behavior. For example, an OOP employee object may have certain attributes of a real employee, such as a name, an address, and an employee number, etc. and could respond as a real employee such that the employee object could provide the employee's address when asked for that information or provide the employee's status, e.g., "on vacation," when asked for status information. Another example may be a calendar object which may be used in several applications such as a scheduling application, a presentation application, and/or 75 a data base application to calculate employee's vacation and pay, etc.
A fundamental concept in OOP is the class. A class is a template or prototype that defines a type of object and specifies the attributes and methods associated with objects or members of the class. Objects of the same class have the same definition for their operations and information structures. An object is created or instantiated at runtime, i.e., when the computer executes a statement in the program.
Encapsulation, inheritance and polymorphism are three important concepts that further differentiate OOP from procedural programming. Encapsulation means keeping the data structure and the methods/functions that process the data together in the same class.
Inheritance is the ability to derive a new class from one or more existing classes. The new class, known as a subclass, inherits or incorporates all properties of a parent class including its attributes and its methods. The new class or subclass may be further defined to include additional properties. An example of inheritance might be that a new class square inherits all the attributes and methods of objects in the class rectangle, but the new class square can be modified so that the methods to calculate area or perimeter can be particularized using polymorphism. Polymorphism is that concept of OOP that allows the same name to be used in a parent class and an inherited or subclass but the subclass may provide a different version of a method with the same name the exists in the base class, such as calculation of the area of a square.
Often when writing graphical user interfaces for applications or application development tools, the user is prompted for a special kind of input. This special input may be a predefined value or a user-specified value. Designing a user interface for these special inputs requires special considerations. There needs to be an entry field to allow the user to enter a specific local value, such as a port number, userid or owner name. That entry field, moreover, should be disabled unless the user enters a value other than the inherited or special value.
Graphical user interfaces have presented options to enter predefined and user input data in several ways. A typical option for input on a graphical user interface is a checkbox. A checkbox with a label such as "Use default value" may be combined with an entry field.
The programmer listens for that checkbox to be selected and, when selected, toggles the entry field between read-only, i.e., read the value in the checkbox, and write-capable, i.e., read that value entered by the user. In the case of the checkbox, the programmer has to toggle the contents of the entry field between the special value and the last-user-entered value. The disadvantage of the checkbox is that it requires additional programming effort, and more user-interface real estate is required to show both the checkbox and the entry field.
Another option is to use a combination input field known as an editable dropdown which is an entry field where the user can type in a value or activate a dropdown list containing only one entry - the special value. When selected, the special value from the list replaces the contents of the entry field. The user then can either type a local value into the entry field or select the special value from the dropdown list. The dropdown list requires additional programming effort.
The programmer has to disable error checking when the special value is selected and reenable error checking when the f ~ I
user starts typing. From the user point of view, this is not an intuitive use of dropdown list boxes, as these are typically used for a multiple selection design pattern, not a binary decision design pattern. The user expects to see multiple values in a list box, not a single value.
There are additional problems associated with both the checkbox and the dropdown approach. The checkbox approach requires a lot of real estate to visually show both the button with its label text, and the entry field. The dropdown list is difficult if the special value is a different data type than what the user is allowed to specify. For example, with a port number, the user entry will be restricted to numbers. Yet the special value " first available" is not a number, it is a string.
Placing that string in the entry field of a dropdown list causes the error-checking code to flag it as 70 invalid because it is not a positive integer value. Special case coding thus is required every time the case changes which becomes tricky for the programmer, especially if the special value string is translated into multiple languages. Furthermore, using a full-function dropdown to list a single choice is overkill for the problem. Typically dropdown lists contain multiple values from which to choose.
75 Just the fact there are multiple approaches to this common design problem indicates the need for a user interface widget designed and optimized for binary decision making wherein the decision may involve different data types. If used consistently, then user quickly learns that he is being asked to make a binary decision between a special value and user-entered value of his choice. This makes the product more usable and is less confusing to the user.
These needs and others that will become apparent to one skilled in the art are satisfied by a method for presenting two options on a user interface of a microprocessor logic device, comprising:
presenting an entry field for input of data; presenting a toggleable switch to activate the entry field;
allowing a user to input data in the entry field when the toggleable switch is activated in a first 25 position; and deactivating the entry field and displaying an inherited value in the entry field when the toggleable switch is in a second position. Depending upon the position of the toggleable switch, either the input data or the inherited value is transferred to an executing application requiring that data. The transfer may occur through a network, which may be the Internet.
The microprocessor logic device may be any of a number of devices, e.g., stand-alone computer, a personal digital assistant, a wireless telephone, an interactive television.
In any event, the toggleable switch may be part of a user interface, which if it is a graphical user interface, the inherited value may be communicated to the user by invoking hover help to set forth the inherited value and/or requesting special input data from the user.
The user interface may be of a different sensory input and so the step of communicating the inherited value to the user may further take advantage of a voice or aural tones, or tactile sensations.
The data input by the user may be of a different data type than the inherited value. When the toggleable switch is in the second position the inherited value may be inherited from a parent class in object oriented programming and the user input data when in the first position is not necessarily an inherited value from the parent class. The entry field, moreover, may invoke error-checking when in the first position.
Features of the invention may further be considered a widget for use with an application having a user device on a logical device, comprising: a switch to manage an entry field wherein when the switch is in an inheritable mode the widget presents an entry field that is a read-only entry field displaying a preset value determined by the application; and when the switch is in a local mode, the widget presents an write-enable entry field to allow the user to enter a different value.
The invention may further be considered a program product user interface, the program product comprising a signal-bearing medium carrying thereon a user interface having a toggleable widget, the toggleable widget comprising: a field having a first choice that is an inherited default noneditable choice; and a toggle to change the field to one having a second choice entered by a user.
BRIEF DESCRIPTION OF THE DRAWING
Figures la and 1b are examples of a graphical user interface that can take advantage of a toggleable widget in accordance with an embodiment of the invention. It is suggested that Figures la and 1b be printed on the face of the patent.
Figure 2 is a simplified flow chart of a method to initialize a toggleable widget in accordance with an embodiment of the invention.
Figure 3 is a simplified flow chart of a method in which a toggleable widget is used in accordance with an embodiment of the invention.
Figure 4 is a simplified flow chart in which a toggleable widget stores a value and returns the value to an application in accordance with an embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
Refernng to the Drawing, wherein like numbers denote like parts throughout the several views and as will be described in detail below, aspects of the preferred embodiment pertain to a unique user interface having a toggleable widget implementable on a logic or microprocessor device. The user interface may be graphical, such as is used on visual displays associated with computer monitors, laptops, personal computers, personal digital assistants, cellular phones, interactive television, home logic devices, and other displays. The user interface could also be aural, such as a speech recognition input interface or tactile for touch. In an alternative embodiment, the invention may be implemented as a computer program-product for use with a user interface. The programs defining the functions of the toggleable widget can be delivered to the computer and/or to a microprocessor or logic device having a user interface via a variety of signal-bearing media, which include, but are not limited to:
(a) information permanently stored on non-writable storage media, e.g., read only memory devices within either computer such as CD-ROM disks readable by CD-ROM drive; (b) alterable information stored on writeable storage media, e.g., floppy disks within diskette drive or hard-disk drive; or (c) information conveyed to a computer by a telephone or a cable media network, including wireless ~~r.I ~ ~i. i,~~., i ~ ~i ~ I
communications. Such signal-bearing media, when carrying computer-readable instructions that direct the functions of the present invention, represent alternative embodiments of the present invention.
The preferred embodiment of the invention has features containing a graphical user interface with a toggleable entry field which minimizes real estate, i.e., not only lines of code and memory space necessary to implement the toggleable widget but also, if a graphical user interface, the screen area consumed by the toggleable widget. The toggleable widget allows the entry field to toggle between two totally different states: a "local state" which makes it a regular entry field, and an "inherit state" which makes it a read-only entry field that displays a pre-set string. The user is shown a small, concise button to toggle between the states. An alternative voice or touch interface and method could also be used to implement the choice, such as "press or say one for the default/inherit value." The programmer specifies the initial state, also referred to as mode, whether it be local or inherit; the string to display in inherit mode; and the initial value for local mode. The programmer can subsequently query if the user chose the inherit mode or chose the local mode and if so, what local value she/he typed in.
With respect to Figure 1 a, a graphical user interface 100 having a toggleable widget 122 in accordance with features of the invention is shown. Other entry fields, such as the Parent Profile 102, the System Type 104, and the Host Name 106, have prior art dropdown lists 110 for entry fields. The graphical user interface 100 has a "Default User Id" field 120 that uses the new toggleable entry field widget 122 that allows the user to choose between, e.g., the inherited value that is currently set in this user's user preferences settings or a unique explicit value which in the example set forward is the connection definition. If the user chooses the inherited value Coulthar, as is shown in the entry field 126, then that inherited value passes its value onto all subsequent connection definitions. Notice the arrow button 124 to the left of the entry field 126. When the arrow 124 points left, this widget 122 is in "inherit" mode and the capability to enter data in entry field 126 is disabled. The widget's current inherit value Coulthar specified by the programmer is displayed. When the arrow button 124 is clicked by the user, it toggles to local mode and points to the right as shown in Figure 1b. The entry field 126 then becomes enabled and the user can enter a value that is specific to this field which, in the example of Figures la and 1b, is a connection definition or user id.
To create the widget using OOP, the programmer instantiates the widget and calls methods on it to set the local value, the inherited value, and the initial state of the toggle button. See, for example, the flow chart of Figure 2 in which initialization of the widget 122 occurs, not necessarily in OOP but can be programmed according to the flow chart in a myriad of programming paradigms.
In step 210, the programmer sets or instantiates the inherited value using code and in step 220, the inherited value is stored in the variable associated with the entry field. In step 212, the programmer codes a noninherited value that is stored in the variable in step 222. In step 214, the programmer codes the initial state of the widget/entry field and in step 224, the initial state is stored in the variable. If, in step 226, the initial state is "inherit," then in step 228, the entry field is initialized to the inherited value so that inherited value appears to the user in the entry field 126 of Figure 1 a when the user interface first appears. The toggle button points to the left and the entry field becomes uneditable. If, however, the initial state has been coded and stored to be the noninherited value, then in step 230, the entry field displays the noninherited value to the user and the toggle button points to the right.
Other indicators beside left and right arrows may indicate if the widget is in an inheritable or noninheritable mode, e.g., the toggle button could have an "up" or a "down"
arrow, an "I" for inherit or a "D" for default, or and "E" for Enter, depending upon the user interface, the language, and/or convention. The embodiment of the invention is not limited to specific icons that the programmer may use to indicate the mode of the entry field. The programmer also has the option of setting tool tip text, or hover help, individually for both the entry field and the toggle button. An example of hover help set and shown for the toggle button is seen in Figure 1b at 130.
Again, the binary decision to be made by the user is apparent in the hover help 130. Also optionally, the programmer can call a method to enable the code to return to a specific state/mode the user toggles between local and inherit modes.
. ' ~ 4 . .~ . I I
The programmer's code then displays the widget to the user and, when appropriate, calls methods to read the user-entered local value, the inherit value, and the state or mode of the toggle button, whether local or inherit. When the user toggles back and forth between modes, the widget itself remembers the last entered local value in its memory and restores it in the entry field when toggling back to local mode.
This widget makes it very easy for the programmer to code user interfaces that allow the user to choose between a preset value or enter in their own value. The programmer need only code a single widget and call a couple of methods to configure the widget. There is no need to code multiple widgets or do special case coding every time the value changes for the two possible states, as is the case with dropdown lists. Further, if the special value is a string such as first available port and the user-entered value must be numeric, such as a positive-integer value, the programmer's job is easy.
Examples of special inputs may be a port number in which the user can either select the special value first available or explicitly enter a numeric port number. Another example of a tool or an application requiring a special input from the user may be the entry of a default userid for remotely signing onto 95 a computer network. A particular request to sign on may allow the user to choose between using the default or allow the user to type in a specific userid just for this request.
Yet, a third example of an application or tool requiring a special input value may be one which presents a hierarchy of objects such as a Java programmer's tool that shows methods within classes within projects. Certain properties, such as the current owner, may be inherited to all objects in the hierarchy. For each object the tool allows the user to either inherit that property from its parent object or override the parent's value with a new value local to that child object. In other words, a user can choose to have all class objects inherit their owner property from their parent object or override the owner property for one class while inheriting it for all the others. If an inherited property is changed at the parent level, all child objects automatically use the new inherited value unless they have overridden that value locally.
A further advantage is that the error-checking code is enabled only when the widget is in local mode and is disabled when the widget is in inherit mode. The toggleable widget, moreover, benefits the end user in that the composite widget of the toggleable button and an entry field does not take up any more real-estate than a regular entry field. The simplified flow chart of Figure 3 illustrates the ease 1 I.~; a~ I I
of use during runtime of the widget and method of choosing between the inherit/noninherit mode.
There are two choices: a special value in the inherit or default mode, or a value entered by the user in the local mode. The widget's disabling of the entry field in the inherit or default mode illustrates that the choice is binary.
In Figure 3 it is the toggleable button 124 in Figures la and 1b that in step 310 triggers the inquiry from which of the two modes the information will be derived. If, as in step 312, the toggleable button is pointed to the direction or has the appropriate indicator for the local or noninherited mode, the entry field may be set to the last noninherited value, the toggle button or indicator is set for the noninherited or local mode, and the entry field is editable. If, however, the button is toggled to the inherit or default mode as in step 314, the value in the entry field is set to the last noninherited value, the contents of the entry field are reset to the inherit or default value, and entry field becomes noneditable.
Figure 4 is a simplified flow chart of an example by which the information chosen or entered by the user in a graphical user interface embodiment is returned to the application. In step 410, the state of the toggleable widget is evaluated. If, in step 420, the toggle button points to the left or is otherwise enabled in the inherit mode , the graphical user interface returns the preset or inherited or default value to the application. If the toggle indicator is pointed to the right or is otherwise enabled in the noninherit mode, as in step 430, then the special value entered by the user in the entry field is read and, in step 432, that value is returned to the application. Note again that the dual nature of the toggleable widget is illustrated in that there may be two different data types, not just two values, for which to choose.
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example and not limitation and that variations are possible. For instance, while the toggle button has been shown to be pointing to the right/left for the local/inherit modes, respectively, it need not be so. Two different yet self teaching icons are all this is required. Moreover, the invention is not intended to be limited to an inherit mode in the ' 1 ' I'. '., ~. ~..i ~j'~~~ 91 context of object oriented programming. Examples of use in other than OOP
include prompting for the first available porx Thus, the toggle need not toggle only between an inherited and a local override value; rather it may toggle between a special case value and all other values. In essence, the toggleable widget allows the user to decide between a value A that is the special case and is not editable and is offered as an alternative to entering a value, or a value B
that is a non-special case range of option, prompted by an entry field or other appropriate widget for which error checking applies. As discussed earlier, while illustrated as a graphical user interface, the user interface may embody speech, speech recognition and/or touch capabilities, such as in "Press or say A to choose the first available port [or inherited value] or enter or say the value or name assigned to a specific 90 port." This embodiment is particularly useful with mobile devices having a limited user interface.
Again, the toggleable widget can be combined to have more than one interface or means by which to enter data; note that the above embodiment encompasses both speech and tactile. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
TOGGLEABLE WIDGET FOR A USER INTERFACE
TECHNICAL FIELD
This invention relates generally to the field of computer user interfaces and more particularly relates to a widget or an entry field from which a user can toggle on an inherited value or on a noninherited value which then allows the user to enter another value.
BACKGROUND OF THE INVENTION
A user interface is that by which a computer user interacts with a computer and its various programs called applications. A nearly universal format of user interface for personal computer systems and personal digital assistants (PDAs) is a visual interface - called a graphical user interface:
GUI (pronounced goo' eee). Other user interfaces may be tactile or may be aural. Typically with graphical user interfaces, the user controls a graphical pointer such as a mouse, a track ball, a glidepad, or stylus to interact with a display of a graphical user interface.
Depending upon the actions allowed by the application or operating system software, the user can select a feature of the graphical display such as an icon or an entry field by positioning the graphical pointer over the feature and making a selection utilizing the graphical pointing device. These features have come to be called widgets.
The actions available to a user following selection of a widget can depend upon a number of factors including the type of widget that was selected and the order of the selection in the current interaction scenario. For example, if the user selects a icon on the desktop or within a window with a single click of a mouse button, the user can typically relocate the icon within the graphical display utilizing the well-known drag-and-drop technique. Alternatively, if the selected widget is a menu bar choice, a dropdown menu may be displayed permitting the user to make a single selection from among the choices listing in the dropdown menu. In response to either the selection of a point outside of the dropdown menu indicating that the user does not wish to select any choice listed in the dropdown menu or the selection of a dropdown menu choice, the dropdown menu closes automatically.
Object-oriented programming (OOP) is becoming the normative computer programming paradigm because it allows programmers to approach their programming tasks more intuitively by using objects rather than procedures as the fundamental building blocks for creating computer programs. Objects are small reusable sections of program code that can be quickly and easily combined to create new and many different applications across a network irrespective of the computer processor's architecture and/or operating system. Conceptually, an obj ect is an entity that is able to save information, referred to as its state, and offers a number of behaviors or functions to either examine or affect this state. An object may model the attributes or characteristics of the real-world object and, in many cases, may also model its behavior. For example, an OOP employee object may have certain attributes of a real employee, such as a name, an address, and an employee number, etc. and could respond as a real employee such that the employee object could provide the employee's address when asked for that information or provide the employee's status, e.g., "on vacation," when asked for status information. Another example may be a calendar object which may be used in several applications such as a scheduling application, a presentation application, and/or 75 a data base application to calculate employee's vacation and pay, etc.
A fundamental concept in OOP is the class. A class is a template or prototype that defines a type of object and specifies the attributes and methods associated with objects or members of the class. Objects of the same class have the same definition for their operations and information structures. An object is created or instantiated at runtime, i.e., when the computer executes a statement in the program.
Encapsulation, inheritance and polymorphism are three important concepts that further differentiate OOP from procedural programming. Encapsulation means keeping the data structure and the methods/functions that process the data together in the same class.
Inheritance is the ability to derive a new class from one or more existing classes. The new class, known as a subclass, inherits or incorporates all properties of a parent class including its attributes and its methods. The new class or subclass may be further defined to include additional properties. An example of inheritance might be that a new class square inherits all the attributes and methods of objects in the class rectangle, but the new class square can be modified so that the methods to calculate area or perimeter can be particularized using polymorphism. Polymorphism is that concept of OOP that allows the same name to be used in a parent class and an inherited or subclass but the subclass may provide a different version of a method with the same name the exists in the base class, such as calculation of the area of a square.
Often when writing graphical user interfaces for applications or application development tools, the user is prompted for a special kind of input. This special input may be a predefined value or a user-specified value. Designing a user interface for these special inputs requires special considerations. There needs to be an entry field to allow the user to enter a specific local value, such as a port number, userid or owner name. That entry field, moreover, should be disabled unless the user enters a value other than the inherited or special value.
Graphical user interfaces have presented options to enter predefined and user input data in several ways. A typical option for input on a graphical user interface is a checkbox. A checkbox with a label such as "Use default value" may be combined with an entry field.
The programmer listens for that checkbox to be selected and, when selected, toggles the entry field between read-only, i.e., read the value in the checkbox, and write-capable, i.e., read that value entered by the user. In the case of the checkbox, the programmer has to toggle the contents of the entry field between the special value and the last-user-entered value. The disadvantage of the checkbox is that it requires additional programming effort, and more user-interface real estate is required to show both the checkbox and the entry field.
Another option is to use a combination input field known as an editable dropdown which is an entry field where the user can type in a value or activate a dropdown list containing only one entry - the special value. When selected, the special value from the list replaces the contents of the entry field. The user then can either type a local value into the entry field or select the special value from the dropdown list. The dropdown list requires additional programming effort.
The programmer has to disable error checking when the special value is selected and reenable error checking when the f ~ I
user starts typing. From the user point of view, this is not an intuitive use of dropdown list boxes, as these are typically used for a multiple selection design pattern, not a binary decision design pattern. The user expects to see multiple values in a list box, not a single value.
There are additional problems associated with both the checkbox and the dropdown approach. The checkbox approach requires a lot of real estate to visually show both the button with its label text, and the entry field. The dropdown list is difficult if the special value is a different data type than what the user is allowed to specify. For example, with a port number, the user entry will be restricted to numbers. Yet the special value " first available" is not a number, it is a string.
Placing that string in the entry field of a dropdown list causes the error-checking code to flag it as 70 invalid because it is not a positive integer value. Special case coding thus is required every time the case changes which becomes tricky for the programmer, especially if the special value string is translated into multiple languages. Furthermore, using a full-function dropdown to list a single choice is overkill for the problem. Typically dropdown lists contain multiple values from which to choose.
75 Just the fact there are multiple approaches to this common design problem indicates the need for a user interface widget designed and optimized for binary decision making wherein the decision may involve different data types. If used consistently, then user quickly learns that he is being asked to make a binary decision between a special value and user-entered value of his choice. This makes the product more usable and is less confusing to the user.
These needs and others that will become apparent to one skilled in the art are satisfied by a method for presenting two options on a user interface of a microprocessor logic device, comprising:
presenting an entry field for input of data; presenting a toggleable switch to activate the entry field;
allowing a user to input data in the entry field when the toggleable switch is activated in a first 25 position; and deactivating the entry field and displaying an inherited value in the entry field when the toggleable switch is in a second position. Depending upon the position of the toggleable switch, either the input data or the inherited value is transferred to an executing application requiring that data. The transfer may occur through a network, which may be the Internet.
The microprocessor logic device may be any of a number of devices, e.g., stand-alone computer, a personal digital assistant, a wireless telephone, an interactive television.
In any event, the toggleable switch may be part of a user interface, which if it is a graphical user interface, the inherited value may be communicated to the user by invoking hover help to set forth the inherited value and/or requesting special input data from the user.
The user interface may be of a different sensory input and so the step of communicating the inherited value to the user may further take advantage of a voice or aural tones, or tactile sensations.
The data input by the user may be of a different data type than the inherited value. When the toggleable switch is in the second position the inherited value may be inherited from a parent class in object oriented programming and the user input data when in the first position is not necessarily an inherited value from the parent class. The entry field, moreover, may invoke error-checking when in the first position.
Features of the invention may further be considered a widget for use with an application having a user device on a logical device, comprising: a switch to manage an entry field wherein when the switch is in an inheritable mode the widget presents an entry field that is a read-only entry field displaying a preset value determined by the application; and when the switch is in a local mode, the widget presents an write-enable entry field to allow the user to enter a different value.
The invention may further be considered a program product user interface, the program product comprising a signal-bearing medium carrying thereon a user interface having a toggleable widget, the toggleable widget comprising: a field having a first choice that is an inherited default noneditable choice; and a toggle to change the field to one having a second choice entered by a user.
BRIEF DESCRIPTION OF THE DRAWING
Figures la and 1b are examples of a graphical user interface that can take advantage of a toggleable widget in accordance with an embodiment of the invention. It is suggested that Figures la and 1b be printed on the face of the patent.
Figure 2 is a simplified flow chart of a method to initialize a toggleable widget in accordance with an embodiment of the invention.
Figure 3 is a simplified flow chart of a method in which a toggleable widget is used in accordance with an embodiment of the invention.
Figure 4 is a simplified flow chart in which a toggleable widget stores a value and returns the value to an application in accordance with an embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
Refernng to the Drawing, wherein like numbers denote like parts throughout the several views and as will be described in detail below, aspects of the preferred embodiment pertain to a unique user interface having a toggleable widget implementable on a logic or microprocessor device. The user interface may be graphical, such as is used on visual displays associated with computer monitors, laptops, personal computers, personal digital assistants, cellular phones, interactive television, home logic devices, and other displays. The user interface could also be aural, such as a speech recognition input interface or tactile for touch. In an alternative embodiment, the invention may be implemented as a computer program-product for use with a user interface. The programs defining the functions of the toggleable widget can be delivered to the computer and/or to a microprocessor or logic device having a user interface via a variety of signal-bearing media, which include, but are not limited to:
(a) information permanently stored on non-writable storage media, e.g., read only memory devices within either computer such as CD-ROM disks readable by CD-ROM drive; (b) alterable information stored on writeable storage media, e.g., floppy disks within diskette drive or hard-disk drive; or (c) information conveyed to a computer by a telephone or a cable media network, including wireless ~~r.I ~ ~i. i,~~., i ~ ~i ~ I
communications. Such signal-bearing media, when carrying computer-readable instructions that direct the functions of the present invention, represent alternative embodiments of the present invention.
The preferred embodiment of the invention has features containing a graphical user interface with a toggleable entry field which minimizes real estate, i.e., not only lines of code and memory space necessary to implement the toggleable widget but also, if a graphical user interface, the screen area consumed by the toggleable widget. The toggleable widget allows the entry field to toggle between two totally different states: a "local state" which makes it a regular entry field, and an "inherit state" which makes it a read-only entry field that displays a pre-set string. The user is shown a small, concise button to toggle between the states. An alternative voice or touch interface and method could also be used to implement the choice, such as "press or say one for the default/inherit value." The programmer specifies the initial state, also referred to as mode, whether it be local or inherit; the string to display in inherit mode; and the initial value for local mode. The programmer can subsequently query if the user chose the inherit mode or chose the local mode and if so, what local value she/he typed in.
With respect to Figure 1 a, a graphical user interface 100 having a toggleable widget 122 in accordance with features of the invention is shown. Other entry fields, such as the Parent Profile 102, the System Type 104, and the Host Name 106, have prior art dropdown lists 110 for entry fields. The graphical user interface 100 has a "Default User Id" field 120 that uses the new toggleable entry field widget 122 that allows the user to choose between, e.g., the inherited value that is currently set in this user's user preferences settings or a unique explicit value which in the example set forward is the connection definition. If the user chooses the inherited value Coulthar, as is shown in the entry field 126, then that inherited value passes its value onto all subsequent connection definitions. Notice the arrow button 124 to the left of the entry field 126. When the arrow 124 points left, this widget 122 is in "inherit" mode and the capability to enter data in entry field 126 is disabled. The widget's current inherit value Coulthar specified by the programmer is displayed. When the arrow button 124 is clicked by the user, it toggles to local mode and points to the right as shown in Figure 1b. The entry field 126 then becomes enabled and the user can enter a value that is specific to this field which, in the example of Figures la and 1b, is a connection definition or user id.
To create the widget using OOP, the programmer instantiates the widget and calls methods on it to set the local value, the inherited value, and the initial state of the toggle button. See, for example, the flow chart of Figure 2 in which initialization of the widget 122 occurs, not necessarily in OOP but can be programmed according to the flow chart in a myriad of programming paradigms.
In step 210, the programmer sets or instantiates the inherited value using code and in step 220, the inherited value is stored in the variable associated with the entry field. In step 212, the programmer codes a noninherited value that is stored in the variable in step 222. In step 214, the programmer codes the initial state of the widget/entry field and in step 224, the initial state is stored in the variable. If, in step 226, the initial state is "inherit," then in step 228, the entry field is initialized to the inherited value so that inherited value appears to the user in the entry field 126 of Figure 1 a when the user interface first appears. The toggle button points to the left and the entry field becomes uneditable. If, however, the initial state has been coded and stored to be the noninherited value, then in step 230, the entry field displays the noninherited value to the user and the toggle button points to the right.
Other indicators beside left and right arrows may indicate if the widget is in an inheritable or noninheritable mode, e.g., the toggle button could have an "up" or a "down"
arrow, an "I" for inherit or a "D" for default, or and "E" for Enter, depending upon the user interface, the language, and/or convention. The embodiment of the invention is not limited to specific icons that the programmer may use to indicate the mode of the entry field. The programmer also has the option of setting tool tip text, or hover help, individually for both the entry field and the toggle button. An example of hover help set and shown for the toggle button is seen in Figure 1b at 130.
Again, the binary decision to be made by the user is apparent in the hover help 130. Also optionally, the programmer can call a method to enable the code to return to a specific state/mode the user toggles between local and inherit modes.
. ' ~ 4 . .~ . I I
The programmer's code then displays the widget to the user and, when appropriate, calls methods to read the user-entered local value, the inherit value, and the state or mode of the toggle button, whether local or inherit. When the user toggles back and forth between modes, the widget itself remembers the last entered local value in its memory and restores it in the entry field when toggling back to local mode.
This widget makes it very easy for the programmer to code user interfaces that allow the user to choose between a preset value or enter in their own value. The programmer need only code a single widget and call a couple of methods to configure the widget. There is no need to code multiple widgets or do special case coding every time the value changes for the two possible states, as is the case with dropdown lists. Further, if the special value is a string such as first available port and the user-entered value must be numeric, such as a positive-integer value, the programmer's job is easy.
Examples of special inputs may be a port number in which the user can either select the special value first available or explicitly enter a numeric port number. Another example of a tool or an application requiring a special input from the user may be the entry of a default userid for remotely signing onto 95 a computer network. A particular request to sign on may allow the user to choose between using the default or allow the user to type in a specific userid just for this request.
Yet, a third example of an application or tool requiring a special input value may be one which presents a hierarchy of objects such as a Java programmer's tool that shows methods within classes within projects. Certain properties, such as the current owner, may be inherited to all objects in the hierarchy. For each object the tool allows the user to either inherit that property from its parent object or override the parent's value with a new value local to that child object. In other words, a user can choose to have all class objects inherit their owner property from their parent object or override the owner property for one class while inheriting it for all the others. If an inherited property is changed at the parent level, all child objects automatically use the new inherited value unless they have overridden that value locally.
A further advantage is that the error-checking code is enabled only when the widget is in local mode and is disabled when the widget is in inherit mode. The toggleable widget, moreover, benefits the end user in that the composite widget of the toggleable button and an entry field does not take up any more real-estate than a regular entry field. The simplified flow chart of Figure 3 illustrates the ease 1 I.~; a~ I I
of use during runtime of the widget and method of choosing between the inherit/noninherit mode.
There are two choices: a special value in the inherit or default mode, or a value entered by the user in the local mode. The widget's disabling of the entry field in the inherit or default mode illustrates that the choice is binary.
In Figure 3 it is the toggleable button 124 in Figures la and 1b that in step 310 triggers the inquiry from which of the two modes the information will be derived. If, as in step 312, the toggleable button is pointed to the direction or has the appropriate indicator for the local or noninherited mode, the entry field may be set to the last noninherited value, the toggle button or indicator is set for the noninherited or local mode, and the entry field is editable. If, however, the button is toggled to the inherit or default mode as in step 314, the value in the entry field is set to the last noninherited value, the contents of the entry field are reset to the inherit or default value, and entry field becomes noneditable.
Figure 4 is a simplified flow chart of an example by which the information chosen or entered by the user in a graphical user interface embodiment is returned to the application. In step 410, the state of the toggleable widget is evaluated. If, in step 420, the toggle button points to the left or is otherwise enabled in the inherit mode , the graphical user interface returns the preset or inherited or default value to the application. If the toggle indicator is pointed to the right or is otherwise enabled in the noninherit mode, as in step 430, then the special value entered by the user in the entry field is read and, in step 432, that value is returned to the application. Note again that the dual nature of the toggleable widget is illustrated in that there may be two different data types, not just two values, for which to choose.
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example and not limitation and that variations are possible. For instance, while the toggle button has been shown to be pointing to the right/left for the local/inherit modes, respectively, it need not be so. Two different yet self teaching icons are all this is required. Moreover, the invention is not intended to be limited to an inherit mode in the ' 1 ' I'. '., ~. ~..i ~j'~~~ 91 context of object oriented programming. Examples of use in other than OOP
include prompting for the first available porx Thus, the toggle need not toggle only between an inherited and a local override value; rather it may toggle between a special case value and all other values. In essence, the toggleable widget allows the user to decide between a value A that is the special case and is not editable and is offered as an alternative to entering a value, or a value B
that is a non-special case range of option, prompted by an entry field or other appropriate widget for which error checking applies. As discussed earlier, while illustrated as a graphical user interface, the user interface may embody speech, speech recognition and/or touch capabilities, such as in "Press or say A to choose the first available port [or inherited value] or enter or say the value or name assigned to a specific 90 port." This embodiment is particularly useful with mobile devices having a limited user interface.
Again, the toggleable widget can be combined to have more than one interface or means by which to enter data; note that the above embodiment encompasses both speech and tactile. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
Claims (20)
1. A method for presenting two options on a user interface of a microprocessor logic device, comprising:
(a) presenting an entry field for input of data;
(b) presenting a toggleable switch to activate the entry field;
(c) allowing a user to input data in the entry field when the toggleable switch is activated in a first position; and (d) deactivating the entry field and displaying an inherited value in the entry field when the toggleable switch is in a second position.
(a) presenting an entry field for input of data;
(b) presenting a toggleable switch to activate the entry field;
(c) allowing a user to input data in the entry field when the toggleable switch is activated in a first position; and (d) deactivating the entry field and displaying an inherited value in the entry field when the toggleable switch is in a second position.
2. The method of claim 1, further comprising the steps of (a) communicating either the input data or the inherited value, depending upon the position of the toggleable switch, to an executing application.
3. The method of claim 2, wherein the executing application is connected to the microprocessor logic device through a network.
4. The method of claim 3, wherein the network is the Internet.
5. The method of claim 1, wherein the microprocessor logic device is a stand-alone computer.
6. The method of claim 1, wherein the microprocessor logic device is a personal digital assistant.
7. The method of claim 1, wherein the microprocessor logic device is a wireless telephone.
8. The method of claim 1, further comprising the steps of:
(a) communicating the inherited value to the user.
(a) communicating the inherited value to the user.
9. The method of claim 8, wherein the step of communicating the inherited value to the user further comprises implementing a graphical user interface on the microprocessor logic device.
10. The method of claim 9, further comprising invoking hover help to set forth the inherited value and/or requesting input data from the user.
11. The method of claim 8, wherein the step of communicating the inherited value to the user further uses a voice or aural tones.
12. The method of claim 8, wherein the step of communicating the inherited value to the user further uses a tactile widget.
13. The method of claim 1, wherein the input data is of a different data type than the inherited value.
14. The method of claim 1, further comprising:
(a) enabling error checking when the toggleable switch is in the first position.
(a) enabling error checking when the toggleable switch is in the first position.
15. The method of claim 2, wherein when the toggleable switch is in the second position, the inherited value is inherited from a parent class in object oriented programming; and when the toggleable switch is in the first position, the input data is not an inherited value from the parent class.
16. A widget for use with an application having a user device on a logical device, comprising:
(a) a switch to manage an entry field wherein when the switch is in an inheritable mode, the widget presents an entry field that is a read-only entry field displaying a preset value determined by the application; and (b) when the switch is in a local mode, the widget presents an write-enable entry field to allow the user to enter a different value.
(a) a switch to manage an entry field wherein when the switch is in an inheritable mode, the widget presents an entry field that is a read-only entry field displaying a preset value determined by the application; and (b) when the switch is in a local mode, the widget presents an write-enable entry field to allow the user to enter a different value.
17. The widget of claim 16, wherein the preset value and the different value are of different data types.
18. The widget of claim 16, wherein the write-enable entry field engages error-checking capabilities.
19. A program product user interface, the program product comprising a signal-bearing medium carrying thereon a user interface having a toggleable widget, the toggleable widget comprising:
(a) a field having a first choice that is an inherited default noneditable choice; and (b) a toggle to change the field to one having a second choice entered by a user.
(a) a field having a first choice that is an inherited default noneditable choice; and (b) a toggle to change the field to one having a second choice entered by a user.
20. The program product of claim 19, further comprising an error checker to check for errors in the second choice entered by the user.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002388150A CA2388150A1 (en) | 2002-05-29 | 2002-05-29 | Toggleable widget for a user interface |
| US10/286,583 US7107546B2 (en) | 2002-05-29 | 2002-10-31 | Toggleable widget for a user interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002388150A CA2388150A1 (en) | 2002-05-29 | 2002-05-29 | Toggleable widget for a user interface |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2388150A1 true CA2388150A1 (en) | 2003-11-29 |
Family
ID=29555383
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002388150A Abandoned CA2388150A1 (en) | 2002-05-29 | 2002-05-29 | Toggleable widget for a user interface |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US7107546B2 (en) |
| CA (1) | CA2388150A1 (en) |
Families Citing this family (88)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8590013B2 (en) | 2002-02-25 | 2013-11-19 | C. S. Lee Crawford | Method of managing and communicating data pertaining to software applications for processor-based devices comprising wireless communication circuitry |
| CA2391717A1 (en) | 2002-06-26 | 2003-12-26 | Ibm Canada Limited-Ibm Canada Limitee | Transferring data and storing metadata across a network |
| US9053239B2 (en) | 2003-08-07 | 2015-06-09 | International Business Machines Corporation | Systems and methods for synchronizing software execution across data processing systems and platforms |
| US7472350B2 (en) * | 2003-10-02 | 2008-12-30 | International Business Machines Corporation | Displaying and managing inherited values |
| US7490295B2 (en) | 2004-06-25 | 2009-02-10 | Apple Inc. | Layer for accessing user interface elements |
| US8453065B2 (en) | 2004-06-25 | 2013-05-28 | Apple Inc. | Preview and installation of user interface elements in a display environment |
| US8566732B2 (en) | 2004-06-25 | 2013-10-22 | Apple Inc. | Synchronization of widgets and dashboards |
| US7761800B2 (en) | 2004-06-25 | 2010-07-20 | Apple Inc. | Unified interest layer for user interface |
| US8302020B2 (en) | 2004-06-25 | 2012-10-30 | Apple Inc. | Widget authoring and editing environment |
| US7779384B2 (en) * | 2004-12-22 | 2010-08-17 | International Business Machines Corporation | Managing visual renderings of typing classes in a model driven development environment |
| US8543931B2 (en) | 2005-06-07 | 2013-09-24 | Apple Inc. | Preview including theme based installation of user interface elements in a display environment |
| US20060287986A1 (en) * | 2005-06-21 | 2006-12-21 | W.W. Grainger, Inc. | System and method for facilitating use of a selection guide |
| US10015630B2 (en) | 2016-09-15 | 2018-07-03 | Proximity Grid, Inc. | Tracking people |
| US10390212B2 (en) | 2016-09-15 | 2019-08-20 | Proximity Grid, Inc. | Tracking system having an option of not being trackable |
| US7761400B2 (en) | 2005-07-22 | 2010-07-20 | John Reimer | Identifying events |
| US8924869B2 (en) * | 2005-08-12 | 2014-12-30 | Barry Fellman | Service for generation of customizable display widgets |
| US7954064B2 (en) | 2005-10-27 | 2011-05-31 | Apple Inc. | Multiple dashboards |
| US7743336B2 (en) | 2005-10-27 | 2010-06-22 | Apple Inc. | Widget security |
| US9104294B2 (en) | 2005-10-27 | 2015-08-11 | Apple Inc. | Linked widgets |
| US8543824B2 (en) | 2005-10-27 | 2013-09-24 | Apple Inc. | Safe distribution and use of content |
| US7752556B2 (en) | 2005-10-27 | 2010-07-06 | Apple Inc. | Workflow widgets |
| JP4747792B2 (en) * | 2005-11-10 | 2011-08-17 | ソニー株式会社 | Information processing apparatus and method for initializing setting items thereof |
| US8571999B2 (en) | 2005-11-14 | 2013-10-29 | C. S. Lee Crawford | Method of conducting operations for a social network application including activity list generation |
| US7707514B2 (en) | 2005-11-18 | 2010-04-27 | Apple Inc. | Management of user interface elements in a display environment |
| US8204952B2 (en) | 2007-02-02 | 2012-06-19 | Facebook, Inc. | Digital file distribution in a social network system |
| US8027943B2 (en) * | 2007-08-16 | 2011-09-27 | Facebook, Inc. | Systems and methods for observing responses to invitations by users in a web-based social network |
| US20090049127A1 (en) * | 2007-08-16 | 2009-02-19 | Yun-Fang Juan | System and method for invitation targeting in a web-based social network |
| US7945653B2 (en) * | 2006-10-11 | 2011-05-17 | Facebook, Inc. | Tagging digital media |
| US8402094B2 (en) | 2006-08-11 | 2013-03-19 | Facebook, Inc. | Providing a newsfeed based on user affinity for entities and monitored actions in a social network environment |
| US8225376B2 (en) | 2006-07-25 | 2012-07-17 | Facebook, Inc. | Dynamically generating a privacy summary |
| US8171128B2 (en) * | 2006-08-11 | 2012-05-01 | Facebook, Inc. | Communicating a newsfeed of media content based on a member's interactions in a social network environment |
| US7827208B2 (en) | 2006-08-11 | 2010-11-02 | Facebook, Inc. | Generating a feed of stories personalized for members of a social network |
| US8296373B2 (en) * | 2007-02-02 | 2012-10-23 | Facebook, Inc. | Automatically managing objectionable behavior in a web-based social network |
| US8549651B2 (en) * | 2007-02-02 | 2013-10-01 | Facebook, Inc. | Determining a trust level in a social network environment |
| US7809805B2 (en) * | 2007-02-28 | 2010-10-05 | Facebook, Inc. | Systems and methods for automatically locating web-based social network members |
| US7669123B2 (en) * | 2006-08-11 | 2010-02-23 | Facebook, Inc. | Dynamically providing a news feed about a user of a social network |
| US7797256B2 (en) * | 2006-08-02 | 2010-09-14 | Facebook, Inc. | Generating segmented community flyers in a social networking system |
| WO2007070676A2 (en) | 2005-12-14 | 2007-06-21 | Facebook, Inc. | Systems and methods for social mapping |
| US20080189292A1 (en) * | 2007-02-02 | 2008-08-07 | Jed Stremel | System and method for automatic population of a contact file with contact content and expression content |
| JP2009521752A (en) | 2005-12-23 | 2009-06-04 | フェイスブック，インク． | System and method for generating a social timeline |
| US9459622B2 (en) | 2007-01-12 | 2016-10-04 | Legalforce, Inc. | Driverless vehicle commerce network and community |
| US8965409B2 (en) | 2006-03-17 | 2015-02-24 | Fatdoor, Inc. | User-generated community publication in an online neighborhood social network |
| US9037516B2 (en) | 2006-03-17 | 2015-05-19 | Fatdoor, Inc. | Direct mailing in a geo-spatial environment |
| US9071367B2 (en) | 2006-03-17 | 2015-06-30 | Fatdoor, Inc. | Emergency including crime broadcast in a neighborhood social network |
| US9373149B2 (en) | 2006-03-17 | 2016-06-21 | Fatdoor, Inc. | Autonomous neighborhood vehicle commerce network and community |
| US9064288B2 (en) | 2006-03-17 | 2015-06-23 | Fatdoor, Inc. | Government structures and neighborhood leads in a geo-spatial environment |
| US9002754B2 (en) | 2006-03-17 | 2015-04-07 | Fatdoor, Inc. | Campaign in a geo-spatial environment |
| US9070101B2 (en) | 2007-01-12 | 2015-06-30 | Fatdoor, Inc. | Peer-to-peer neighborhood delivery multi-copter and method |
| US9098545B2 (en) | 2007-07-10 | 2015-08-04 | Raj Abhyanker | Hot news neighborhood banter in a geo-spatial social network |
| US20070226643A1 (en) * | 2006-03-23 | 2007-09-27 | International Business Machines Corporation | System and method for controlling obscuring traits on a field of a display |
| WO2008094168A1 (en) * | 2007-02-02 | 2008-08-07 | Facebook, Inc. | System and method for giving gifts and displaying assets in a social network environment |
| US8904340B2 (en) * | 2007-02-13 | 2014-12-02 | International Business Machines Corporation | Use of temporary optimized settings to reduce cycle time of automatically created spreadsheets |
| WO2008103447A2 (en) | 2007-02-21 | 2008-08-28 | Facebook, Inc. | Implementation of a structured query language interface in a distributed database |
| WO2008112293A1 (en) | 2007-03-13 | 2008-09-18 | Facebook, Inc. | Systems and methods for network authentication |
| US7827265B2 (en) * | 2007-03-23 | 2010-11-02 | Facebook, Inc. | System and method for confirming an association in a web-based social network |
| CA2687089C (en) | 2007-05-24 | 2015-07-07 | Facebook, Inc. | Systems and methods for providing privacy settings for applications associated with a user profile |
| BRPI0811720A2 (en) | 2007-05-24 | 2014-11-04 | Facebook Inc | METHOD AND SYSTEM FOR PROVIDING CUSTOM PLATFORM TO ACCESS THE INTERNET APPLICATION THROUGH SOCIAL NETWORK AND COMPUTER PROGRAM. |
| WO2008147572A1 (en) * | 2007-05-31 | 2008-12-04 | Facebook, Inc. | Systems and methods for auction based polling |
| CA2687520C (en) * | 2007-06-12 | 2015-07-28 | Facebook, Inc. | Personalized social networking application content |
| US8954871B2 (en) | 2007-07-18 | 2015-02-10 | Apple Inc. | User-centric widgets and dashboards |
| US8095883B2 (en) * | 2007-08-03 | 2012-01-10 | International Business Machines Corporation | Indicating the default value for a property to enhance user feedback |
| US8667415B2 (en) | 2007-08-06 | 2014-03-04 | Apple Inc. | Web widgets |
| US8732846B2 (en) | 2007-08-15 | 2014-05-20 | Facebook, Inc. | Platform for providing a social context to software applications |
| US8645424B2 (en) * | 2007-12-19 | 2014-02-04 | Sam Stanley Miller | System for electronically recording and sharing medical information |
| US8255822B2 (en) * | 2007-12-21 | 2012-08-28 | Microsoft Corporation | Incorporated handwriting input experience for textboxes |
| US8887066B1 (en) | 2008-04-02 | 2014-11-11 | Facebook, Inc. | Communicating plans for users of a social networking system |
| US8769490B2 (en) * | 2008-09-16 | 2014-07-01 | Oracle International Corporation | Desktop widget engine emulator component for a rapid application development tool |
| US9063740B2 (en) * | 2008-09-16 | 2015-06-23 | Oracle International Corporation | Web widget component for a rapid application development tool |
| US8719896B2 (en) * | 2008-09-16 | 2014-05-06 | Oracle International Corporation | Widget host container component for a rapid application development tool |
| US8527897B2 (en) * | 2009-01-26 | 2013-09-03 | International Business Machines Corporation | System, method, and computer program product for toggling back and forth between unformatted and formatted editable views of data |
| US20110093890A1 (en) * | 2009-10-21 | 2011-04-21 | John Araki | User control interface for interactive digital television |
| DE102009057082A1 (en) * | 2009-12-04 | 2011-06-09 | Volkswagen Ag | Method for displaying widget object on display surface utilized as user interface for displaying e.g. actual information about weather to motor vehicle driver, involves automatically changing object from one condition to another condition |
| CA2716843C (en) * | 2010-10-06 | 2017-11-07 | Ibm Canada Limited - Ibm Canada Limitee | Combined properties dialog from different sources |
| US9069550B2 (en) * | 2010-11-29 | 2015-06-30 | International Business Machines Corporation | System and method for adjusting inactivity timeout settings on a display device |
| US9836721B2 (en) | 2011-11-21 | 2017-12-05 | Facebook, Inc. | Defining future plans in connection with objects in a social networking system |
| CN103971036B (en) * | 2013-01-28 | 2017-03-01 | 深圳学无国界教育科技有限公司 | Page column authority control system and method |
| US9439367B2 (en) | 2014-02-07 | 2016-09-13 | Arthi Abhyanker | Network enabled gardening with a remotely controllable positioning extension |
| US9457901B2 (en) | 2014-04-22 | 2016-10-04 | Fatdoor, Inc. | Quadcopter with a printable payload extension system and method |
| US9004396B1 (en) | 2014-04-24 | 2015-04-14 | Fatdoor, Inc. | Skyteboard quadcopter and method |
| US9022324B1 (en) | 2014-05-05 | 2015-05-05 | Fatdoor, Inc. | Coordination of aerial vehicles through a central server |
| US9971985B2 (en) | 2014-06-20 | 2018-05-15 | Raj Abhyanker | Train based community |
| US9441981B2 (en) | 2014-06-20 | 2016-09-13 | Fatdoor, Inc. | Variable bus stops across a bus route in a regional transportation network |
| US9451020B2 (en) | 2014-07-18 | 2016-09-20 | Legalforce, Inc. | Distributed communication of independent autonomous vehicles to provide redundancy and performance |
| US20180330325A1 (en) | 2017-05-12 | 2018-11-15 | Zippy Inc. | Method for indicating delivery location and software for same |
| WO2018222245A1 (en) * | 2017-06-02 | 2018-12-06 | Apple Inc. | Cooperative health management system |
| DK201970532A1 (en) | 2019-05-06 | 2021-05-03 | Apple Inc | Activity trends and workouts |
| US11152100B2 (en) | 2019-06-01 | 2021-10-19 | Apple Inc. | Health application user interfaces |
| DK181037B1 (en) | 2020-06-02 | 2022-10-10 | Apple Inc | User interfaces for health applications |
Family Cites Families (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5546527A (en) | 1994-05-23 | 1996-08-13 | International Business Machines Corporation | Overriding action defaults in direct manipulation of objects on a user interface by hovering a source object |
| US6139198A (en) | 1994-10-04 | 2000-10-31 | International Business Machines Corporation | System and method for enabling tracing of program execution in an object-oriented system |
| US6141792A (en) | 1994-10-31 | 2000-10-31 | International Business Machines Corporation | Object oriented framework for specifying the format of compiler output with a template facility |
| US5732219A (en) | 1995-03-17 | 1998-03-24 | Vermeer Technologies, Inc. | Computer system and computer-implemented process for remote editing of computer files |
| JPH09244837A (en) | 1996-03-11 | 1997-09-19 | Nec Corp | Simulator and input data processing method for the same |
| US6085034A (en) | 1996-03-18 | 2000-07-04 | International Business Machines Corporation | Constructor based object initialization with overrides |
| US6151609A (en) | 1996-08-16 | 2000-11-21 | Electronic Data Systems Corporation | Remote editor system |
| US6041179A (en) | 1996-10-03 | 2000-03-21 | International Business Machines Corporation | Object oriented dispatch optimization |
| US5973670A (en) * | 1996-12-31 | 1999-10-26 | International Business Machines Corporation | Tactile feedback controller for computer cursor control device |
| US5913065A (en) | 1997-01-31 | 1999-06-15 | Sun Microsystems, Inc. | System, method and article of manufacture for creating hierarchical folder components for use in a java application or applet |
| US5884078A (en) | 1997-01-31 | 1999-03-16 | Sun Microsystems, Inc. | System, method and article of manufacture for creating an object oriented component having multiple bidirectional ports for use in association with a java application or applet |
| US5913063A (en) | 1997-02-26 | 1999-06-15 | Oracle Corporation | Drag and drop object subclassing |
| US6158044A (en) | 1997-05-21 | 2000-12-05 | Epropose, Inc. | Proposal based architecture system |
| US5974413A (en) * | 1997-07-03 | 1999-10-26 | Activeword Systems, Inc. | Semantic user interface |
| US6195794B1 (en) | 1997-08-12 | 2001-02-27 | International Business Machines Corporation | Method and apparatus for distributing templates in a component system |
| US6044398A (en) | 1997-11-21 | 2000-03-28 | International Business Machines Corporation | Virtual dynamic browsing system and method for automated web server and testing |
| DE69814155T2 (en) * | 1997-12-16 | 2003-10-23 | Microsoft Corp | SYSTEM AND METHOD FOR VIRTUAL INPUT |
| US6085228A (en) | 1998-04-17 | 2000-07-04 | Sun Microsystems, Inc. | Methods and apparatus for a property editing mechanism for a network computer environment |
| GB2340008A (en) * | 1998-07-24 | 2000-02-09 | Ibm | Method and tool for generating and displayin a descriptive annotation of selec ted application data |
| US6341359B1 (en) * | 1998-12-14 | 2002-01-22 | International Business Machines Corporation | Self-diagnosing and self correcting data entry components |
| US6657645B2 (en) * | 1999-06-11 | 2003-12-02 | Microsoft Corporation | System, method, and computer-readable medium for displaying keyboard cues in a window |
| US6589290B1 (en) * | 1999-10-29 | 2003-07-08 | America Online, Inc. | Method and apparatus for populating a form with data |
| EP1205843A3 (en) * | 2000-11-13 | 2004-10-20 | Canon Kabushiki Kaisha | User interfaces |
| US6907580B2 (en) * | 2000-12-14 | 2005-06-14 | Microsoft Corporation | Selection paradigm for displayed user interface |
| US20020133440A1 (en) * | 2001-03-13 | 2002-09-19 | Annuitynet, Inc. | Method of automating the process of purchasing and managing annuities |
| US20030040340A1 (en) * | 2001-08-27 | 2003-02-27 | Smethers Paul A. | Graphical user interface features of a browser in a hand-held wireless communication device |
| US7810038B2 (en) * | 2002-05-03 | 2010-10-05 | International Business Machines Corporation | Method for modifying a GUI for an application |
-
2002
- 2002-05-29 CA CA002388150A patent/CA2388150A1/en not_active Abandoned
- 2002-10-31 US US10/286,583 patent/US7107546B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| US20030222918A1 (en) | 2003-12-04 |
| US7107546B2 (en) | 2006-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7107546B2 (en) | Toggleable widget for a user interface | |
| US6100885A (en) | Supporting modification of properties via a computer system's user interface | |
| US10248294B2 (en) | Modal-less interface enhancements | |
| US7490314B2 (en) | System and method for exposing tasks in a development environment | |
| US9092162B2 (en) | Graphical user interface for viewing or editing an executable block diagram model | |
| EP0817012B1 (en) | Selection of operations in a computer system | |
| US6966039B1 (en) | Method for facilitating microcontroller programming | |
| US8196096B2 (en) | .Net ribbon model for a ribbon user interface | |
| US5764226A (en) | Reusable and modifiable data entry interface part | |
| Henry et al. | Integrating gesture and snapping into a user interface toolkit | |
| US20020175955A1 (en) | Graphical user interface having contextual menus | |
| US8504930B1 (en) | User interface substitution | |
| WO2015112476A1 (en) | User interface modification and usage tracking | |
| US5802334A (en) | Method for displaying object oriented class information and content information | |
| US9703443B2 (en) | Method and system for creating a free-form visual user interface element | |
| Grundy et al. | Developing adaptable user interfaces for component-based systems | |
| US6335745B1 (en) | Method and system for invoking a function of a graphical object in a graphical user interface | |
| US20090037831A1 (en) | Indicating the default value for a property to enhance user feedback | |
| WO1995031771A1 (en) | Support for custom user-interaction elements in a graphical, event-driven computer system | |
| EP1743232B1 (en) | Generic user interface command architecture | |
| EP0603095A2 (en) | Method and apparatus for managing a windowing environment in an object oriented programming system | |
| US7188320B1 (en) | Graphical user interface for wireless communications | |
| US7823079B2 (en) | Computer readable recording medium recorded with graphics editing program, and graphics editing apparatus | |
| Wang et al. | A formal specification of interaction widgets hierarchy framework | |
| KR20040018663A (en) | method for controlling icon in display system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued | ||
| FZDE | Discontinued |
Effective date: 20100531 |