GUI for data pipeline

• US 7,529,764 B2
• Filed: 01/12/2004
• Issued: 05/05/2009
• Est. Priority Date: 01/12/2004
• Status: Expired due to Fees

• Current Assignee: Hitachi Global Storage Technologies Incorporated (Western Digital Corporation)
• Original Assignee: Hitachi Global Storage Technologies Netherlands BV (Western Digital Corporation)
• Inventors: Gutsche, Ralf
• Primary Examiner(s): Lu; Kuen S
• Application Number:
  US10/756,123
• Publication Number:
  US 20050154729A1
• Time in Patent Office: 1,940 Days
• Field of Search: 707 1- 2, 707/100, 707/102, 707/104.1, 707/200, 709230-232, 709/200, 717141-142, 717/118, 717/160, 717/149, 717104-105, 717110-111, 714/38, 715/765, 715/747, 715/762, 715/825, 715735-737, 715/763, 712/1
• US Class Current: 1/1
• CPC Class Codes: G06F 3/0483 Interaction with page-structured environments, e.g. book metaphor
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A graphical user interface (GUI) for a Pipeline architecture includes providing a way for generating and modifying Pipelines without writing any JAVA code apart from an initial core code.

Claims

1. A graphical user interface (GUI) for configuring pipelines, the GUI displayable on a user computer monitor and stored on a computer memory and comprising:

at least one pipe input set window configured to permit a user to define a type of pipe input set data;

at least one GUI page based on the type, the GUI page being generated by translating the type using a configuration file to a class and using Java reflection to generate an instance of the class, the instance producing the GUI page; and

using the GUI page to configure a data pipeline, and the GUI further comprising at least one Pipe Output Set tab for defining PipeOutputSet representative of a type of output data from the pipeline.

2. The GUI of claim 1, wherein at least the pipe input set window and GUI page require no programming apart from an initial core code.

3. The GUI of claim 1, wherein the GUI is an incremental GUI wherein GUI pages for new pipe components can be added incrementally without changing existing code.

4. The GUI of claim 3, wherein at least one new pipe module is based on a pre-existing module type.

5. The GUI of claim 3, wherein at least one new pipe module is based on a new user-defined component type.

6. The GUI of claim 1, wherein the GUI defines a set of interfaces, each interface including plural functions, the GUI including a GUI representation part and a storage part, the GUI representation part defining how something is displayed and the storage part defining how GUI parameters are stored in an external storage.