U.S. patent application number 14/409128 was filed with the patent office on 2017-06-01 for boron nitride nanotubes and process for production thereof.
The applicant listed for this patent is National Research Council of Canada. Invention is credited to Keun Su Kim, Christopher T Kingston, Benoit Simard.
Application Number | 20170152142 14/409128 |
Document ID | / |
Family ID | 51730634 |
Filed Date | 2017-06-01 |
United States Patent
Application |
20170152142 |
Kind Code |
A9 |
Kim; Keun Su ; et
al. |
June 1, 2017 |
BORON NITRIDE NANOTUBES AND PROCESS FOR PRODUCTION THEREOF
Abstract
A value inheritance widget system includes a display device
including a user interface, and a value impact engine coupled to
the display device. The value impact engine is configured to
display at least one widget on a user interface. The widget
includes a value. The value comprises an inherited value. The value
impact engine is further configured to display information of a
scope of inheritance of the value before user interaction with the
widget. The information of the scope of inheritance of the value
includes a number of inheritance levels of the value and a number
of objects impacted by a change to the value. The value impact
engine is further configured to receive a user input changing the
value of the widget and change the value of the widget and the
objects in response to receiving the user input.
Inventors: |
Kim; Keun Su; (Ottawa,
CA) ; Kingston; Christopher T; (Ottawa, CA) ;
Simard; Benoit; (Ottawa, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
National Research Council of Canada |
Ottawa |
|
CA |
|
|
Prior
Publication: |
|
Document Identifier |
Publication Date |
|
US 20160083253 A1 |
March 24, 2016 |
|
|
Family ID: |
51730634 |
Appl. No.: |
14/409128 |
Filed: |
April 4, 2014 |
PCT Filed: |
April 4, 2014 |
PCT NO: |
PCT/CA2014/050340 PCKC 00 |
371 Date: |
December 18, 2014 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61813324 |
Apr 18, 2013 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04L 41/0813 20130101;
H04L 63/083 20130101; B82Y 40/00 20130101; C01P 2004/03 20130101;
C01P 2002/88 20130101; B82Y 30/00 20130101; C01B 21/0641 20130101;
H04L 41/22 20130101; C01B 21/064 20130101; C01P 2004/13 20130101;
C01P 2004/04 20130101; G06F 3/0484 20130101 |
International
Class: |
C01B 21/064 20060101
C01B021/064 |
Claims
1. A process for producing boron nitride nanotubes (BNNTs)
comprising providing one or more sources of boron, nitrogen and
hydrogen to a stable induction plasma to form a reaction mixture of
boron, nitrogen and hydrogen in the plasma, and cooling the
reaction mixture to form BNNTs.
2. The process according to claim 1, wherein the one or more
sources of boron comprises elemental boron, boron nitride, boron
oxide, boric acid, metal borides, ammonia borane, a derivative of
ammonia borane, borazine, a derivative of borazine, borane or any
mixture thereof, and wherein the one or more sources of nitrogen
comprises boron nitride, N.sub.2, NH.sub.3, NH.sub.4OH, borazine or
any mixture thereof, and wherein the one or more sources of
hydrogen comprises H.sub.2, NH.sub.3, NH.sub.4OH, a borane or any
mixture thereof.
3. The process according to claim 1, wherein the one or more
sources of boron comprises hexagonal boron nitride, the one or more
sources of nitrogen comprises a mixture of hexagonal boron nitride
and N.sub.2 and the one or more sources of hydrogen comprises
H.sub.2.
4. (canceled)
5. The process according to claim 1, wherein the one or more
sources of boron is free of metal.
6. (canceled)
7. (canceled)
8. (canceled)
9. (canceled)
10. The process according to claim 1, wherein at least one of the
sources of nitrogen is a gas and at least one of the sources of
hydrogen is a gas and the gases are provided to the stable
induction plasma in a sheath gas.
11. The process according to claim 10, wherein the sheath gas
further comprises an inert gas.
12. (canceled)
13. (canceled)
14. The process according to claim 10, wherein the at least one
source of hydrogen is present in the sheath gas in an amount of
5-20%.
15. (canceled)
16. The process according to claim 10, wherein the at least one
source of nitrogen is present in the sheath gas in an amount of
35-65%.
17. The process according to claim 1, wherein the reaction mixture
is under a pressure of less than 2 atm in the stable induction
plasma.
18. The process according to claim 17, wherein the pressure is
greater than 0.6 atm.
19. (canceled)
20. The process according to claim 17, wherein the pressure is
greater than 0.95 atm.
21. The process according to claim 17, wherein the pressure is in a
range of 0.9 atm to 1.9 atm.
22. The process according to claim 17, wherein the pressure is in a
range of 0.95 atm to 1.9 atm.
23. The process according to claim 17, wherein the pressure is in a
range of 0.9 atm to 1 atm.
24. (canceled)
25. The process according to claim 1, wherein the reaction mixture
is further provided with a metal catalyst.
26. (canceled)
27. The process according to claim 1, wherein the reaction mixture
further comprises a source of carbon and the BNNTs produced are
doped with carbon.
28. (canceled)
29. The process according to claim 1, wherein the stable induction
plasma has a temperature in a range of 7,000-9,000 K at a core of
the plasma.
30. (canceled)
31. (canceled)
32. (canceled)
33. The process according to claim 1, further comprising collecting
the BNNTs by filtration in a filtration zone downstream of the
reaction zone.
34. (canceled)
35. (canceled)
36. A composition comprising a plurality of metal-free boron
nitride nanotubes having an average diameter of 10 nm or less.
37. A free-standing transparent film comprising boron nitride
nanotubes having an average diameter of 10 nm or less.
38. (canceled)
Description
BACKGROUND
[0001] Systems and applications may inherit configuration settings
from disparate systems, applications, or files. This allows an
administrator to change a setting in one place while all systems,
applications, and files that inherit the setting will change as
well. Accurate and relevant information of the inheritance of a
setting is not available before user interaction with the
setting.
SUMMARY
[0002] Embodiments of a value inheritance widget system are
described. In one embodiment, a value inheritance widget system
includes a display device including a user interface, and a value
impact engine coupled to the display device. The value impact
engine is configured to display at least one widget on a user
interface. The widget includes a value. The value may comprise an
inherited value. The value impact engine is further configured to
display information of a scope of inheritance of the value before
user interaction with the widget. The information of the scope of
inheritance of the value includes a number of inheritance levels of
the value and a number of objects impacted by a change to the
value. The value impact engine is further configured to receive a
user input changing the value of the widget and change the value of
the widget in response to receiving the user input. Other
embodiments of the system are also described, as well as
embodiments of a computer program product and a method.
[0003] Other aspects and advantages of embodiments of the present
invention will become apparent from the following detailed
description, taken in conjunction with the accompanying drawings,
illustrated by way of example of the principles of the
invention.
BRIEF DESCRIPTION OF THE DRAWINGS
[0004] FIG. 1 depicts a schematic diagram of one embodiment of a
value inheritance widget system.
[0005] FIG. 2 depicts a schematic diagram of one embodiment of a
computer server system that relies upon levels of inheritance to
which the value inheritance widget system of FIG. 1 may be
applied.
[0006] FIG. 3 depicts one embodiment of a user interface displaying
some widgets and widget states as well as information of a scope of
inheritance.
[0007] FIG. 4 depicts a flow chart diagram of one embodiment of a
method for representing and controlling the impact and scope of a
widget value.
[0008] Throughout the description, similar reference numbers may be
used to identify similar elements.
DETAILED DESCRIPTION
[0009] It will be readily understood that the components of the
embodiments as generally described herein and illustrated in the
appended figures could be arranged and designed in a wide variety
of different configurations. Thus, the following more detailed
description of various embodiments, as represented in the figures,
is not intended to limit the scope of the present disclosure, but
is merely representative of various embodiments. While the various
aspects of the embodiments are presented in drawings, the drawings
are not necessarily drawn to scale unless specifically
indicated.
[0010] The present invention may be embodied in other specific
forms without departing from its spirit or essential
characteristics. The described embodiments are to be considered in
all respects only as illustrative and not restrictive. The scope of
the invention is, therefore, indicated by the appended claims
rather than by this detailed description. All changes which come
within the meaning and range of equivalency of the claims are to be
embraced within their scope.
[0011] Reference throughout this specification to features,
advantages, or similar language does not imply that all of the
features and advantages that may be realized with the present
invention should be or are in any single embodiment of the
invention. Rather, language referring to the features and
advantages is understood to mean that a specific feature,
advantage, or characteristic described in connection with an
embodiment is included in at least one embodiment of the present
invention. Thus, discussions of the features and advantages, and
similar language, throughout this specification may, but do not
necessarily, refer to the same embodiment.
[0012] Furthermore, the described features, advantages, and
characteristics of the invention may be combined in any suitable
manner in one or more embodiments. One skilled in the relevant art
will recognize, in light of the description herein, that the
invention can be practiced without one or more of the specific
features or advantages of a particular embodiment. In other
instances, additional features and advantages may be recognized in
certain embodiments that may not be present in all embodiments of
the invention.
[0013] Reference throughout this specification to "one embodiment,"
"an embodiment," or similar language means that a particular
feature, structure, or characteristic described in connection with
the indicated embodiment is included in at least one embodiment of
the present invention. Thus, the phrases "in one embodiment," "in
an embodiment," and similar language throughout this specification
may, but do not necessarily, all refer to the same embodiment.
[0014] While many embodiments are described herein, at least some
of the described embodiments facilitate efficient administration of
changes to inherited values within systems and applications. Some
embodiments described herein involve displaying information of the
scope of inheritance of a value before user interaction. Displaying
information before user interaction allows administrators to
quickly know the effect of changes before a change is
attempted.
[0015] FIG. 1 depicts a schematic diagram of one embodiment of a
value inheritance widget system 100. The depicted value inheritance
widget system 100 includes various components, described below,
that are capable of performing the functions and operations
described herein. The illustrated value inheritance widget system
100 includes a computer memory device 102, a processing device 104,
input/output devices 106, and a disk storage device 108. The
illustrated value inheritance widget system 100 also includes a
value impact engine 110 and a display device 112. Some or all of
the components of the value inheritance widget system 100 may be
stored on a single computing device or on a network of computing
devices, including a wireless communication network. Although the
value inheritance widget system 100 is shown and described with
certain components and functionality, other embodiments of the
value inheritance widget system 100 may include fewer or more
components to implement less or more functionality.
[0016] The computer memory device 102 may store data and/or
software instructions or computer program instructions for carrying
out the operations described herein. The computer memory device 102
may be external or internal to the system and may include but is
not limited to a hard drive, a CD/DVD recordable drive, a magnetic
tape drive, a disk cartridge drive, a secure digital card, another
type of magnetic or optical drive, a solid-state drive, or another
type of memory device. The processing device 104 is connected to
and in communication with the memory device 102 and may store and
access data on the memory device 102 for performing the operations
described herein. The processor or processing device 104 may also
be connected to the disk storage device 108. The disk storage
device 108 may be implemented to temporarily store data or software
instructions from the memory device 102 or the processor 104. The
disk storage device 108 may include but is not limited to a hard
disk drive, a floppy disk drive, a removable floppy disk, or other
type of optical or magnetic drive, or another persistent storage
device. The functionality of the value impact engine 110 may be
implemented by computer program instructions stored on the computer
memory device 102 and executed by the processing device 104 such as
a CPU.
[0017] A user interface 114 is displayed on the display device 112.
The display device 112 may be any display device 112 for a
computing device. The user interface 114 may be part of an
operating system for the computing device and may allow a user to
interact with the operating system. The user interface 114 may rely
on touch input, traditional mouse pointer input, or any other type
of input system.
[0018] In some embodiments, the value impact engine 110 is
configured to display at least one widget on the user interface
114. In some embodiments, the widget includes a value. In some
embodiments, the value is an inherited value. A widget may be any
graphical device indicating a configuration setting or value for a
system, application, or file that can receive input and can inherit
the configuration setting or value from another system,
application, or file. In some embodiments, the value impact engine
110 is further configured to display information of a scope of
inheritance of the value before user interaction with the widget.
In some embodiments, the information of the scope of inheritance of
the value is displayed on the user interface before a user selects
the widget, changes the value of the widget, or any other user
interaction with the widget.
[0019] In some embodiments, the information of the scope of
inheritance of the value includes a number of inheritance levels of
the value. The inheritance relationship of a value may be simple or
complex. A value or configuration setting may be inherited through
one or multiple levels, files, or applications. In some
embodiments, the information of the scope of inheritance of the
value includes a number of objects impacted by a change to the
value. A change to the value may result in changes to a number
objects within an inheritance chain. In some embodiments, the
number of objects includes those objects that inherit the value
from the widget. In some embodiments, the number of objects
includes all objects within the inheritance chain including objects
that inherit the value and objects from which the value is
inherited.
[0020] In some embodiments, the value impact engine 110 is further
configured to receive a user input changing the value of the
widget. The user input may be a mouse click, a touch input, a
keyboard input, or any other input communicated to a computer
system through an input device. In some embodiments, the value
impact engine 110 is further configured to change the value of the
widget in response to receiving the user input. In some
embodiments, the value impact engine 110 is further configured to
change the value of the widget and the objects in response to
receiving the user input. In some embodiments, all objects
including objects that inherit the value and objects from which the
value is inherited are changed. In some embodiments, all objects
that inherit the value are changed.
[0021] In some embodiments, the value impact engine 110 is further
configured to display information of a scope of inheritance of the
changed value. In some embodiments, the information of the scope of
inheritance of the changed value includes a number of inheritance
levels of the changed value. In some embodiments, the information
of the scope of inheritance of the changed value includes a number
of objects impacted by a change to the changed value.
[0022] In some embodiments, the value impact engine 110 is further
configured to display an authentication segment. A change made to a
value that is inherited y multiple objects may have a large impact,
and in some cases, it may be useful to require user authentication
before changing a parent value. In some cases, the configuration
file for the parent value may reside on a separate system that to
which the user must authenticate. In some embodiments, the
authentication segment includes a request for user identification.
In some embodiments, the authentication segment includes a request
for a password. In some embodiments, the value impact engine 110 is
further configured to receive the user identification before the
value of the widget and the objects are changed. In some
embodiments, the value impact engine 110 is further configured to
receive a password before the value of the widget and the objects
are changed.
[0023] In some embodiments, the value impact engine 110 is further
configured to display the information of the scope of inheritance
of the value at every level of an inheritance chain of the value.
In some embodiments, the value impact engine 110 is further
configured to allow a user to change the value at every level of
the inheritance chain.
[0024] In some embodiments, the value impact engine 110 is further
configured to display a second widget comprising an overridden
value. In some embodiments, the overridden value no longer inherits
a value but still recognizes and indicates an inheritance chain. In
some embodiments, the value impact engine 110 is further configured
to display a visual indicator that the overridden value is
overridden before user interaction with the widget.
[0025] In some embodiments, the value impact engine 110 is further
configured to display a visual indicator that the widget previously
comprised an inherited value. In some embodiments, the value impact
engine 110 is further configured to receive an input to restore the
inherited value. In some embodiments, the value impact engine 110
is further configured to restore the inherited value in response to
receiving the input.
[0026] In addition to the advantages which may be achieved by
implementation of the individual components of the value
inheritance widget system 100, some embodiments of the value
inheritance widget system 100 provide additional advantages over
conventional technology. For example, some embodiments of the value
inheritance widget system 100 allow a user or administrator to
quickly assess the inheritance chain of a value. Embodiments of the
value inheritance widget system 100 allow a user or administrator
know the scope of a change to a widget before interacting with the
widget. Some embodiments of the value inheritance widget system 100
allow a user to efficiently edit configuration settings and
controls without the frustration of pop-up boxes. Some embodiments
of the value inheritance widget system 100 allow a single view of
multiple values in a graphical user interface, while distinguishing
the origin of the values and indicating the scope of impact of a
change to a value before user interaction.
[0027] FIG. 2 depicts a schematic diagram of one embodiment of a
computer server system 200 that relies upon levels of inheritance
to which the value inheritance widget system 100 of FIG. 1 may be
applied. In the depicted computer server system 200, application 1
202 resides on application server 1 210. Application 2 204 resides
on application server 2 212. Application 3 206 resides on
application server 3 214. Application 4 208 resides on application
server 4 216.
[0028] The behavior and operation of applications servers 210-216
may be defined in files consisting of attribute-value pairs. The
attribute-value pairs may specify the names of properties and their
values and may be managed through a graphical user interface.
Settings and values may be inherited from one configuration file to
another. In the depicted computer server system 200, application
server 1 210 uses the configuration settings of configuration file
or configuration data 1 218. Application server 2 212 uses the
configuration settings of configuration file or configuration data
2 220. Application server 3 214 uses the configuration settings of
configuration file or configuration data 3 222. Application server
4 216 uses the configuration settings of configuration file or
configuration data 4 224.
[0029] An administrator of the computer server system 200 may
define common settings shared by multiple servers. Defining common
settings in such a manner allows the administrator to effect a
change in a single place and inherit the change in all settings
within an inheritance chain. The values or settings in
configuration file or configuration data 5 226 are included in both
application server 1 210 and application server 2 212. The
administrator may change a setting in either application server 1
210, or application server 2 212, or both. A change to a value or
setting in configuration file 1 218 will not affect configuration
file 2 220. Likewise, a change to a value or setting in
configuration file 2 220 will not affect configuration file 1 218.
A change to a value or setting in configuration file 5 226 will
affect both configuration file 1 218 and configuration file 2
220.
[0030] Similarly, the values or settings in configuration file or
configuration data 6 228 are included in both application server 3
214 and application server 4 216. An administrator may change a
setting in either application server 3 214, or application server 4
216, or both. A change to a value or setting in configuration file
3 222 will not affect configuration file 4 224. A change to a value
or setting in configuration file 4 224 will not affect
configuration file 3 222. A change to a value or setting in
configuration file 6 228 will affect both configuration file 3 222
and configuration file 4 224.
[0031] The values or settings in configuration file or
configuration data 7 230 are included in all four application
servers 1-4 210-216. A change to a value or setting in
configuration file 7 230 will affect both configuration file 5 226
and configuration file 6 228. An administrator may make changes at
the application level or a higher environment level. For example,
the settings in configuration files 1 218 and 2 220 may define
settings for server behavior in a test environment and
configuration files 3 222 and 4 224 may define settings for a
production environment. The settings of configuration file 7 230
are global and are inherited by both the test environment and the
production environment.
[0032] The inheritance scheme of computer server system 200, as
depicted in FIG. 2, may be applied to more complex schemes and to
any number of levels. While the depiction outlined in FIG. 2 refers
to server configuration settings, the value inheritance widget
system 100 may be applied to any system or application that relies
upon levels of inheritance.
[0033] FIG. 3 depicts one embodiment of a user interface 114 of a
computing device showing some widgets and widget states 302-320 and
information of a scope of inheritance. The widgets 302-320 include
various embodiments of information of a scope of inheritance.
[0034] Widget 302 includes a value, "5.2", in a text input box 324.
For example, the value 5.2 may be a configuration setting for a
server property. While the depicted embodiment shows a text input
box 324, other embodiments may use checkboxes, radio buttons,
dropdown lists, sliders, and other controls. Widget 302 also
includes an inheritance icon 326 which indicates that the value 5.2
is inherited. The inheritance icon 326 also provides a mechanism
for modifying the parent value from which the value 5.2 is
inherited. While the depicted embodiment shows the inheritance icon
326, the visual representation that the value 5.2 is inherited may
take other forms. By selecting the text input box 324, a user may
edit or change the value 5.2 and by doing so will override the
inheritance relationship of the value. By selecting the inheritance
icon 326, a user may access the parent value, which is depicted by
widget 304.
[0035] Widget 304 includes a value, "5.2", in a text input box 324.
Other embodiments may user checkboxes, radio buttons, dropdown
lists, sliders, and other controls. Widget 304 also includes an
inheritance icon 326 indicating that the value 5.2 is inherited
further. Widget 304 also includes an inheritance indicator 328 that
indicates an inheritance level inherits the value 5.2. The
inheritance indicator 328 is depicted as a box, but may be a
recessed box or any other visual indication of inheritance. In this
embodiment, the one level inherits the value 5.2. The widget 304
also includes a visual indication 330 of a number of objects (12)
that inherit the value 5.2, which is the number of objects that are
affected by a change to the value. By selecting the text input box
324, a user may edit or change the value 5.2 and by doing so will
override the inheritance relationship and will change 12 objects
that inherit the value 5.2. By selecting the inheritance icon 326,
a user may access the parent value, which is depicted by widget
306.
[0036] Widget 306 includes a value, "5.2", in a text input box 324.
The value 5.2 is not inherited from another level as the Widget 306
does not include an inheritance icon 326. The widget 306 includes
inheritance indicators 328 and 332 that indicate that two levels
inherit the value 5.2. The widget 304 also includes a visual
indication 330 of a number of objects (46) that inherit the value
5.2, which is the number of objects that are affected by a change
to the value. by selecting the text input box 324, a user may edit
or change the value 5.2 and by doing so will change the 46 objects
that inherit the value 5.2.
[0037] Widget 308 includes a value, "4.7", in a text input box 324.
Widget 308 also includes an inheritance icon 334 indicating that
the value 4.7 is inherited. By selecting the text input box 324, a
user may edit or change the value 4.7 and by doing so will override
the inheritance relationship with the level from which the value is
inherited. Widget 310 shows the text input box 324 after the user
has changed the value from 4.7 to 5.7. Widget 310 also includes a
visual indication 336 that the value 5.7 is an override value and
has overridden the inherited value 4.7. By selecting the visual
indication 336, the value will restore the severed inheritance
relationship and revert back to inheriting the value 4.7.
[0038] Widgets 312 and 314 require authentication before changing a
value. Widget 312 includes a value, "4.7", in a text input box 324.
Widget 312 also includes an inheritance icon 334 indicating that
the value 4.7 is inherited. Widget 312 also includes an inheritance
indicator 328 that indicates an inheritance level inherits the
value 4.7. The widget 312 also includes a visual indication 330 of
a number of objects (16) that inherit the value 4.7, which is the
number of objects that are affected by a change to the value.
Widget 312 also includes an authentication segment 338 and an enter
button 340 that requests that a user name be entered before
changing the value 4.7. Widget 314 includes many of the features
and information that widget 312 includes. Widget 314 includes and
authentication segment 342 and an enter button 346 that requests a
password be entered before changing the value 4.7. In some
embodiments, user identification and a password are required before
changing the value. Widget 316 depicts a widget after
authentication showing an icon 348 indicating that the value may be
changed.
[0039] Widget 318 depicts another embodiment and includes a value
6.8 in a text input box 324. Widget 318 also includes inheritance
indicators 328 and 332 that indicate that two levels inherit the
value 6.8. Widget 318 also includes a visual indication 330 of a
number of objects (7) that inherit the value 6.8, which is the
number of objects that are affected by a change to the value.
Widget 318 also includes icons 350 and 352 that allow a user to
navigate through inheritance levels in either direction.
[0040] Widget 320 includes a value 4.7 in a text input box 324 and
an inheritance indicator 334 which indicates that the value 4.7 is
inherited. Widget 320 also includes an indication of the origin,
"configuration file 7", of the inherited value 354.
[0041] FIG. 4 depicts a flow chart diagram of one embodiment of a
method for representing and controlling an impact and scope of a
widget value 400. Although the method for representing and
controlling an impact and scope of a widget value 400 is described
in conjunction with the value inheritance widget system of FIG. 1
and FIGS. 2-3, embodiments of the method 400 may be implemented
with other types of computer systems.
[0042] At 402, at least one widget 304 is displayed on a user
interface 114. In some embodiments, the widget includes a value. In
some embodiments, the widget includes an inherited value. At 404,
information of the scope of inheritance of the value is displayed
on the user interface 114 before user interaction with the widget.
In some embodiments, the scope of inheritance of the value includes
a number of inheritance levels 328 of the value. In some
embodiments, the scope of inheritance of the value includes a
number of objects 330 impacted by a change to the value. In some
embodiments, the scope of inheritance of the value includes an
origin of the inherited value 354. At 406, a user input is
receiving changing the value of the widget 304. At 408, the value
is changed in response to receiving the user input. In some
embodiments, the value of the widget and the objects are changed in
response to receiving the user input. In some embodiments, the
display of values is changed in response to the change of the
value. The depicted method for representing and controlling an
impact and scope of a widget value 400 then ends.
[0043] Some embodiments include displaying information of a scope
of inheritance of the changed value. In some embodiments, the
information of the scope of inheritance of the changed value
includes a number of inheritance levels 328 of the changed value.
In some embodiments, the information of the scope of inheritance of
the changed value includes a number of objects 330 impacted by a
change to the changed value. Some embodiments include displaying an
authentication segment 342 within the widget 314. In some
embodiments, the authentication segment 338 includes a request for
user identification. In some embodiments, the authentication
segment 342 includes a request for a password. Some embodiments
include receiving the user identification and/or the password
before changing the value of the widget 314.
[0044] Some embodiments include displaying the information of the
scope of inheritance of the value at every level of an inheritance
chain. Some embodiments allow a user to change the value at every
level of the inheritance chain. Some embodiments include displaying
an overridden value and a visual indication that the overridden
value is overridden before user interaction with the widget 310.
Some embodiments further include displaying a visual indication 336
that the overridden widget previously included an inherited value.
Some embodiments include receiving an input to restore the
inherited value and restoring the inherited value.
[0045] In the above description, specific details of various
embodiments are provided. However, some embodiments may be
practiced with less than all of these specific details. In other
instances, certain methods, procedures, components, structures,
and/or functions are described in no more detail than to enable the
various embodiments of the invention, for the sake of brevity and
clarity.
[0046] Although specific embodiments of the invention have been
described and illustrated, the invention is not to be limited to
the specific forms or arrangements of parts so described and
illustrated. The scope of the invention is to be defined by the
claims appended hereto and their equivalents.
[0047] An embodiment of a value inheritance widget system includes
at least one processor coupled directly or indirectly to memory
elements through a system bus such as a data, address, and/or
control bus. The memory elements can include local memory employed
during actual execution of the program code, bulk storage, and
cache memories which provide temporary storage of at least some
program code in order to reduce the number of times code must be
retrieved from bulk storage during execution.
[0048] It should also be noted that at least some of the operations
for the methods may be implemented using software instructions
stored on a computer useable storage medium for execution by a
computer. As an example, an embodiment of a computer program
product includes a computer useable storage medium to store a
computer readable program that, when executed on a computer, causes
the computer to perform operations, including an operation to
monitor a pointer movement in a web page. The web page displays one
or more content feeds. In one embodiment, operations to report the
pointer movement in response to the pointer movement comprising an
interaction gesture are included in the computer program product.
In a further embodiment, operations are included in the computer
program product for tabulating a quantity of one or more types of
interaction with one or more content feeds displayed by the web
page.
[0049] Although the operations of the method(s) herein are shown
and described in a particular order, the order of the operations of
each method may be altered so that certain operations may be
performed in an inverse order or so that certain operations may be
performed, at least in part, concurrently with other operations. In
another embodiment, instructions or sub-operations of distinct
operations may be implemented in an intermittent and/or alternating
manner.
[0050] Embodiments of the invention can take the form of an
entirely hardware embodiment, an entirely software embodiment, or
an embodiment containing both hardware and software elements. In
one embodiment, the invention is implemented in software, which
includes but is not limited to firmware, resident software,
microcode, etc.
[0051] Furthermore, embodiments of the invention can take the form
of a computer program product accessible from a computer-usable or
computer-readable medium providing program code for use by or in
connection with a computer or any instruction execution system. For
the purposes of this description, a computer-usable or computer
readable medium can be any apparatus that can contain, store,
communicate, propagate, or transport the program for use by or in
connection with the instruction execution system, apparatus, or
device.
[0052] The computer-useable or computer-readable medium can be an
electronic, magnetic, optical, electromagnetic, infrared, or
semiconductor system (or apparatus or device), or a propagation
medium. Examples of a computer-readable medium include a
semiconductor or solid state memory, magnetic tape, a removable
computer diskette, a random access memory (RAM), a read-only memory
(ROM), a rigid magnetic disk, and an optical disk. Current examples
of optical disks include a compact disk with read only memory
(CD-ROM), a compact disk with read/write (CD-R/W), and a digital
video disk (DVD).
[0053] Input/output or I/O devices (including but not limited to
keyboards, displays, pointing devices, etc.) can be coupled to the
system either directly or through intervening I/O controllers.
Additionally, network adapters also may be coupled to the system to
enable the data processing system to become coupled to other data
processing systems or remote printers or storage devices through
intervening private or public networks. Modems, cable modems, and
Ethernet cards are just a few of the currently available types of
network adapters.
* * * * *