Abstract: A method creates a data grid component in a GUI. The data grid includes data cells, header cells, corner cells, and may further include footer cells. The data grid component may have headers or footers that contain a scale and/or a ruler that relates to graphs shown in a row or column associated with the header or footer. The scale and/or ruler may be horizontal or vertical. The GUI component may allow for multilevel navigation. One level allows for navigating from component to component in the GUI, including the data grid and any other components. Another level allows for navigating within a component, including in the data grid. Available user navigation inputs include level change commands, for example tied to specific keys.

Abstract: A method creates a data grid component in a GUI. The data grid includes data cells, header cells, corner cells, and may further include footer cells. A header, footer, or corner cell includes a software component that allows a user to enter valid data only, such as a date picker or a time picker. The date picker displays a month, a day, and a year, and has controls for changing the date.

Abstract: A method creates a data grid component in a GUI. The data grid includes data cells, header cells, corner cells, and may further include footer cells. The data grid component may have headers or footers that contain a scale and/or a ruler that relates to graphs shown in a row or column associated with the header or footer. The scale and/or ruler may be horizontal or vertical. The GUI component may allow for multilevel navigation. One level allows for navigating from component to component in the GUI, including the data grid and any other components. Another level allows for navigating within a component, including in the data grid. Available user navigation inputs include level change commands, for example tied to specific keys.

Abstract: A method creates a data grid component in a GUI. The data grid includes data cells, header cells, corner cells, and may further include footer cells. A header, footer, or corner cell includes a software component that allows a user to enter valid data only, such as a date picker or a time picker. The date picker displays a month, a day, and a year, and has controls for changing the date. The data grid component may have headers or footers that contain a scale and/or a ruler that relates to graphs shown in a row or column associated with the header or footer. The scale and/or ruler may be horizontal or vertical. The GUI component may allow for multilevel navigation. One level allows for navigating from component to component in the GUI, including the data grid and any other components. Another level allows for navigating within a component, including in the data grid. Available user navigation inputs include level change commands, for example tied to specific keys.

Abstract: A data grid software component has data cells with a style that may be template-based or individual. A data cell may include a software component to show and interact with a bitmap, a graph, a chart, streaming graphics, or streaming bitmaps. The data grid may have footers, headers, and corner cells each capable of holding another software component to show and interact with several data forms. A header, a footer, and a corner cell can each have a style that is template-based or individual. Headers and footers may have multiple levels. Header parts and footer parts at different levels may have a style that is template-based or individual.

Abstract: A data grid software component has data cells with a style that may be template-based or individual. A data cell may include a software component to show and interact with a bitmap, a graph, a chart, streaming graphics, or streaming bitmaps. The data grid may have footers, headers, and corner cells each capable of holding another software component to show and interact with several data forms. A header, a footer, and a corner cell can each have a style that is template-based or individual. Headers and footers may have multiple levels. Header parts and footer parts at different levels may have a style that is template-based or individual.

Abstract: A data grid software component has data cells with a style that may be template-based or individual. A data cell may include a software component to show and interact with a bitmap, a graph, a chart, streaming graphics, or streaming bitmaps. The data grid may have footers, headers, and corner cells each capable of holding another software component to show and interact with several data forms. A header, a footer, and a corner cell can each have a style that is template-based or individual. Headers and footers may have multiple levels. Header parts and footer parts at different levels may have a style that is template-based or individual.

Abstract: A data grid software component has data cells with a style that may be template-based or individual. A data cell may include a software component to show and interact with a bitmap, a graph, a chart, streaming graphics, or streaming bitmaps. The data grid may have footers, headers, and corner cells each capable of holding another software component to show and interact with several data forms. A header, a footer, and a corner cell can each have a style that is template-based or individual. Headers and footers may have multiple levels. Header parts and footer parts at different levels may have a style that is template-based or individual.

Abstract: According to an aspect of the invention, an apparatus for transporting objects comprises a frame for receiving at least one object, at least one handle coupled to the frame, at least one set of wheels coupled to the frame, at least one track coupled to the frame, wherein the track allows movement of the apparatus in addition to the wheels, and at least one brake mechanism coupled to the frame.