Difference: DpHipeOverview (1 vs. 26)

Revision 262014-02-12 - AlvarGarcia

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"
<-- ANALYTICS CODE - DO NOT EDIT -->
<-- Google Analytics script BEGIN -->
<-- Google Analytics script END -->
Line: 22 to 22
 
Line: 35 to 35
 HIPE embraces the following principles:
  • Tool integration, giving access to all data processing functionality in a unified graphical interface.
  • Single look-and-feel, where window layout, toolbars, buttons, and menus are alike.
Changed:
<
<
  • Customisability, allowing you to decide which windows are relevant and how these windows are layed out on screen.
>
>
  • Customisability, allowing you to decide which windows are relevant and how these windows are laid out on screen.
 
  • User guidance, including command-line echoing of main graphical functionality, allowing you to learn the scripting language while interacting with the system.
  • Extensibility, allowing developers to add new bells-and-whistles which are automatically integrated.
Line: 96 to 96
 

To add a component to the status bar, do the following:

Changed:
<
<
  1. Create the appropriate Swing component. For example, the memory bar is a JProgressBar, the garbage collection button is a JButton, and so on.
>
>
  1. Create the appropriate Swing component. For example, the memory bar is a JProgressBar, the garbage collection button is a JButton, and so on.
 
  1. Register the new component by adding an entry to the __init.py__ file as shown above. You instantiate an Extension object with the following String arguments:
    • A unique name, like "Busy Job Progress Panel".
    • The component class, like "herschel.ia.gui.apps.views.status.BusyJobProgressPanel".

Revision 252012-10-19 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"
Changed:
<
<
<-- Google Analytics script BEGIN -->
<-- Google Analytics script END -->
>
>
<-- ANALYTICS CODE - DO NOT EDIT -->
<-- Google Analytics script BEGIN -->
<-- Google Analytics script END -->

<-- END OF ANALYTICS CODE -->
 
<-- 
  • Set TOPICTITLE = HIPE overview
-->
Line: 147 to 138
 -->

META FILEATTACHMENT attr="h" autoattached="1" comment="Components of HIPE" date="1277459986" name="HipeComponents.png" path="HipeComponents.png" size="47402" user="Main.DavideRizzo" version="1"
Added:
>
>
META FILEATTACHMENT attr="h" autoattached="1" comment="Script for Google Analytics" date="1350658334" name="GoogleAnalytics.txt" path="GoogleAnalytics.txt" size="549" user="Main.DavideRizzo" version="1"
 
META FILEATTACHMENT attr="h" autoattached="1" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" user="Main.JorgoBakker" version="1"
META TOPICMOVED by="DavideRizzo" date="1272527055" from="Hcss.DpHipeOverview" to="Public.DpHipeOverview"

Revision 242012-09-20 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"
Added:
>
>
<-- Google Analytics script BEGIN -->
<-- Google Analytics script END -->
 
<-- 
  • Set TOPICTITLE = HIPE overview
-->

Revision 232012-07-12 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

Revision 222012-05-14 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

Revision 212012-03-22 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

Revision 202011-10-21 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

Revision 192011-06-24 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

Revision 182011-06-24 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"
Changed:
<
<

HIPE Overview

>
>
<-- 
  • Set TOPICTITLE = HIPE overview
-->

PDF Version Portrait Landscape

Help Did you spot something wrong or missing on this page? If you have an account on this TWiki, you can fix it yourself by editing the page. If you don't have an account, you can send a message to the Editorial Board to tell us about it. Thank you in advance!

HIPE overview

 

<-- summary -->
Line: 70 to 78
  Please add your comments!
<--/commentPlugin-->
Added:
>
>
* Thanks for your comment Rik. Writeup on the status bar coming soon! -- DavideRizzo - 24 Jun 2011 - 14:51
<--/commentPlugin-->
  * What about the status bar at the bottom, what kind of information is available there and how can this area be used by developers? -- RikHuygen - 22 Jun 2011 - 15:17
<--/commentPlugin-->

Revision 172011-06-22 - RikHuygen

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 70 to 70
  Please add your comments!
<--/commentPlugin-->
Added:
>
>
* What about the status bar at the bottom, what kind of information is available there and how can this area be used by developers? -- RikHuygen - 22 Jun 2011 - 15:17
<--/commentPlugin-->
 

Revision 162011-04-26 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

<-- summary -->
Deleted:
<
<
HIPE is a powerful data reduction environment, continually improved by dozens of contributors. It provides all the tools users need to download, view, reduce and analyse Herschel data. Moreover, it includes a powerful scripting editor and command line console. Most interactions with the graphical interface are echoed on the command line, so that you can generate scripts to automate your workflow.
 This section explains the philosophy behind the framework and provides a brief overview of its fundamental elements. The aim is to enable you to make contributions to HIPE.
Line: 13 to 11
 

Philosophy

Added:
>
>
HIPE is a powerful data reduction environment, continually improved by dozens of contributors. It provides all the tools users need to download, view, reduce and analyse Herschel data. Moreover, it includes a powerful scripting editor and command line console. Most interactions with the graphical interface are echoed on the command line, so that you can generate scripts to automate your workflow.
 HIPE embraces the following principles:
  • Tool integration, giving access to all data processing functionality in a unified graphical interface.
  • Single look-and-feel, where window layout, toolbars, buttons, and menus are alike.

Revision 152010-09-02 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 68 to 68
 
Added:
>
>
Please add your comments!
<--/commentPlugin-->
 
<--  
-->

Revision 142010-06-25 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 25 to 25
 
HIPE is built-up from several graphical elements, of which the fundamental ones are shown in the following image:
Changed:
<
<
Components of HIPE
>
>
Components of HIPE
 

Editor area

Revision 132010-06-25 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

<-- summary -->
Changed:
<
<
HIPE provides an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualise that data in different ways and select tools to operate on that data. Meanwhile, high-level graphical interactions such as task execution and PAL querying are echoed on the command-line, such that you can generate scripts from these interactions.
>
>
HIPE is a powerful data reduction environment, continually improved by dozens of contributors. It provides all the tools users need to download, view, reduce and analyse Herschel data. Moreover, it includes a powerful scripting editor and command line console. Most interactions with the graphical interface are echoed on the command line, so that you can generate scripts to automate your workflow.
  This section explains the philosophy behind the framework and provides a brief overview of its fundamental elements. The aim is to enable you to make contributions to HIPE.

Deleted:
<
<

History

The first graphical application for analysis and reduction of Herschel data was called JIDE. JIDE was created to provide a graphical entry point to the functionality in the HCSS (Herschel Common Science Software). It evolved from requests of project members (notably the science team, engineering scientists and calibration scientists) and Jython developers. In the end, however, it was deemed unfit as an interactive analysis tool for end users.

After a review in the summer of 2007, management asked the Data Processing User Group to come up with a vision of the application and representation of the functionality that should be given to the end-user. This culminated in a User Vision document.

The Data Processing Architecture Group was then asked to respond to this document, by coming up with a design that would fulfill the User Vision document. Rather than creating a design on paper, this group put together their ideas and interpretations into a prototype. The prototype was then used to validate these ideas against the wishes of the User Group.

The result of this exercise was HIPE. From the prototype stage, HIPE has grown into a powerful data reduction environment thanks to dozens of contributors, and it gets better every day.

 

Philosophy

HIPE embraces the following principles:
Changed:
<
<
  • An integrated application, giving access to all data processing functionality in a unified graphical interface.
  • One look-and-feel, where window layout, toolbars, buttons, and menus are alike.
  • A customizable layout, allowing you to decide which windows are relevant and how these windows are layed-out on screen.
>
>
  • Tool integration, giving access to all data processing functionality in a unified graphical interface.
  • Single look-and-feel, where window layout, toolbars, buttons, and menus are alike.
  • Customisability, allowing you to decide which windows are relevant and how these windows are layed out on screen.
 
  • User guidance, including command-line echoing of main graphical functionality, allowing you to learn the scripting language while interacting with the system.
Changed:
<
<
  • Extensible application, allowing developers to add new bells-and-whistles which are automatically integrated.
>
>
  • Extensibility, allowing developers to add new bells-and-whistles which are automatically integrated.
 
Changed:
<
<

The Application

>
>

The application

 
Changed:
<
<
HIPE is built-up from several graphical elements, of which the fundamental ones are shown in the picture below:
Elements within HIPE application
>
>
HIPE is built-up from several graphical elements, of which the fundamental ones are shown in the following image:

Components of HIPE

 
Changed:
<
<

Editor Area

>
>

Editor area

 
Changed:
<
<
The editor area is the location for visualization of the contents of user resources. Resources may be an image, a spectrum, dataset or a product. Another type of resource can be a user script, or a task execution. The editor can show e.g. a SimpleImage as an image or as a browsable product.
>
>
In the editor area you can do the following:

  • Editing and executing Jython scripts.
  • Running tasks via their graphical interface.
  • Viewing and modifying data (tables, products, images, spectra) via specialised tools.
 

Views

Changed:
<
<
Views provide the means the look at the resources -or parts of them- in different ways. One can think of a console, a help window, an overview of all variables in your session and so forth.
>
>
Views are windows within HIPE, each with a specialised task (for instance, listing variables or displaying log messages). Look at the Window --> Show Views menu for a list of available views.
 
Changed:
<
<
The prototype provides a suite of views as a hint to developers. Some views are extendible (such as the Outline View).
>
>
Some views, such as the Outline view, are extensible.
 

Perspectives

Changed:
<
<
A perspective is a collection of graphical windows organized in a way to focus the user on doing a specific job within the whole suite of jobs that a user can and will do within the system. It may consists of one or more views and optionally the editor area; these windows are then organized in tabbed panes and split panes.

The prototype provides some standard perspectives like a full-fledged work-bench as well as a classic JIDE perspective.

>
>
A perspective is a collection of related views. The views can be organised in tabbed panes and split panes.
 
Changed:
<
<

Menus and Tool bars

>
>

Menus and toolbars

 
Changed:
<
<
The application provides two types of menus and tool bars:
  • the main menu and tool bar may provide access to global functionality as well as the editor area.
  • a view's menu (in the form of a pull-down menu) and tool bar provide access to functionality which is specific to that view.
>
>
HIPE provides two types of menus and tool bars:
  • The main menu and toolbar provide access to global functionality as well as to the editor area.
  • A view's menu and toolbar provide access to functionality specific to that view.
 
Changed:
<
<

Site Events

>
>

Site events

 
Changed:
<
<
Views communicate with each other by means of events. There are three pieces for implementing this mechanism:
>
>
Views communicate with each other by means of events. There are three elements to this mechanism:
 
Changed:
<
<
  • The events, which must extend SiteEvent, provide the information of something happened within the application, like a selection event, a variables changed event, etc.
  • The event handler, provided to the views, for dispatching the events.
  • The event listeners, which take proper actions on the events occurred.
>
>
  • The events, which must extend SiteEvent. Events signal that something has happened within the application, like a selection event, a variables changed event, and so on.
  • The event handler, provided to the views, for dispatching events.
  • The event listeners, which take action once an event occurs.
 

Deleted:
<
<
 
<--  
-->
Changed:
<
<
META FILEATTACHMENT attachment="hipe-elements.jpg" attr="h" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" stream="hipe-elements.jpg" user="Main.JorgoBakker" version="1"
>
>
META FILEATTACHMENT attr="h" autoattached="1" comment="Components of HIPE" date="1277459986" name="HipeComponents.png" path="HipeComponents.png" size="47402" user="Main.DavideRizzo" version="1"
META FILEATTACHMENT attr="h" autoattached="1" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" user="Main.JorgoBakker" version="1"
 
META TOPICMOVED by="DavideRizzo" date="1272527055" from="Hcss.DpHipeOverview" to="Public.DpHipeOverview"

Revision 122010-06-21 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

<-- summary -->
Changed:
<
<
HIPE provides an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualise that data in different ways and select tools to operate on that data. Meanwhile, high-level graphical interactions such as task execution and PAL querying are echoed on the command-line, such that you can generate scripts from these interactions.
>
>
HIPE provides an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualise that data in different ways and select tools to operate on that data. Meanwhile, high-level graphical interactions such as task execution and PAL querying are echoed on the command-line, such that you can generate scripts from these interactions.
  This section explains the philosophy behind the framework and provides a brief overview of its fundamental elements. The aim is to enable you to make contributions to HIPE.

Revision 112010-06-09 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 15 to 15
 
The first graphical application for analysis and reduction of Herschel data was called JIDE. JIDE was created to provide a graphical entry point to the functionality in the HCSS (Herschel Common Science Software). It evolved from requests of project members (notably the science team, engineering scientists and calibration scientists) and Jython developers. In the end, however, it was deemed unfit as an interactive analysis tool for end users.
Changed:
<
<
After a review in the summer of 2007, management asked the Data Processing User Group to come up with a vision of the application and representation of the functionality that should be given to the end-user. This culminated into a User Vision document (private link).
>
>
After a review in the summer of 2007, management asked the Data Processing User Group to come up with a vision of the application and representation of the functionality that should be given to the end-user. This culminated in a User Vision document.
  The Data Processing Architecture Group was then asked to respond to this document, by coming up with a design that would fulfill the User Vision document. Rather than creating a design on paper, this group put together their ideas and interpretations into a prototype. The prototype was then used to validate these ideas against the wishes of the User Group.

Revision 102010-05-17 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 80 to 80
 
Added:
>
>
<--  
-->
 
META FILEATTACHMENT attachment="hipe-elements.jpg" attr="h" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" stream="hipe-elements.jpg" user="Main.JorgoBakker" version="1"
META TOPICMOVED by="DavideRizzo" date="1272527055" from="Hcss.DpHipeOverview" to="Public.DpHipeOverview"

Revision 92010-04-29 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 2 to 2
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Deleted:
<
<
 
<-- summary -->
Changed:
<
<
The new data processing application, HIPE, strives to provide an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualize that data in different ways and select tools to operate on that data. Meanwhile, high-level graphical interactions such as task execution and PAL querying are echoed on the command-line, such that you can generate scripts from these interactions.
>
>
HIPE provides an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualise that data in different ways and select tools to operate on that data. Meanwhile, high-level graphical interactions such as task execution and PAL querying are echoed on the command-line, such that you can generate scripts from these interactions.
 
Changed:
<
<
This section tries to explain the philosophy behind the framework to the developers, and to provide a brief overview of its fundamental elements. Hopefully that enables you -as a developer- to make contributions to HIPE.
>
>
This section explains the philosophy behind the framework and provides a brief overview of its fundamental elements. The aim is to enable you to make contributions to HIPE.
 

History

Changed:
<
<
We are all familiar with JIDE, an application providing a graphical entry point to the functionality in the HCSS software. This application has naturally grown from requests of users (notably the project science team, engineering scientists and calibratation scientists) and jython developers, but it was deemed not the be in a state to bring it to the end-user as a user-friendly interactive analysis tool.
>
>
The first graphical application for analysis and reduction of Herschel data was called JIDE. JIDE was created to provide a graphical entry point to the functionality in the HCSS (Herschel Common Science Software). It evolved from requests of project members (notably the science team, engineering scientists and calibration scientists) and Jython developers. In the end, however, it was deemed unfit as an interactive analysis tool for end users.
 
Changed:
<
<
After the review in the summer of 2007, management has asked the DP User Group to come up with a user vision of the application and representation of the functionality that should be given to the end-user. This culminated into a User Vision document.
>
>
After a review in the summer of 2007, management asked the Data Processing User Group to come up with a vision of the application and representation of the functionality that should be given to the end-user. This culminated into a User Vision document (private link).
 
Changed:
<
<
The DP Architecture Group was then asked to respond to this document, by coming up with a design that would fulfill spirit as laid down within the User Vision document. Rather than creating a design on paper, this group has put together their ideas and interpretations into a prototype for two reasons:
  • to have a means to feed their ideas back to the user group (is this what you want?) and
  • to cast these ideas into a working system in order to understand the relations required within the resulting design.
>
>
The Data Processing Architecture Group was then asked to respond to this document, by coming up with a design that would fulfill the User Vision document. Rather than creating a design on paper, this group put together their ideas and interpretations into a prototype. The prototype was then used to validate these ideas against the wishes of the User Group.
 
Changed:
<
<
The result of this exercise is HIPE, a prototype that is rapidly growing towards main stream code.
>
>
The result of this exercise was HIPE. From the prototype stage, HIPE has grown into a powerful data reduction environment thanks to dozens of contributors, and it gets better every day.
 

Philosophy

Changed:
<
<
HIPE tries to embrace several aspects that affects both users as well as developers:
  • an integrated application - giving access to all data processing functionality in a unified graphical interface
  • one look-and-feel - where window layout, toolbars, buttons, and menus are alike
  • a customizable layout - allow the user to decide which windows are relevant and how these windows are layed-out on screen
  • user guidance - including command-line echoing of main graphical functionality, allowing the user to learn the scripting language by interacting with the system interactively
  • extendible application - allow the developer to add new bells-and-whistles which are automatically integrated
>
>
HIPE embraces the following principles:
  • An integrated application, giving access to all data processing functionality in a unified graphical interface.
  • One look-and-feel, where window layout, toolbars, buttons, and menus are alike.
  • A customizable layout, allowing you to decide which windows are relevant and how these windows are layed-out on screen.
  • User guidance, including command-line echoing of main graphical functionality, allowing you to learn the scripting language while interacting with the system.
  • Extensible application, allowing developers to add new bells-and-whistles which are automatically integrated.
 

The Application

Revision 82010-04-29 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 16 to 16
 
We are all familiar with JIDE, an application providing a graphical entry point to the functionality in the HCSS software. This application has naturally grown from requests of users (notably the project science team, engineering scientists and calibratation scientists) and jython developers, but it was deemed not the be in a state to bring it to the end-user as a user-friendly interactive analysis tool.
Changed:
<
<
After the review in the summer of 2007, management has asked the DP User Group to come up with a user vision of the application and representation of the functionality that should be given to the end-user. This culminated into a User Vision document.
>
>
After the review in the summer of 2007, management has asked the DP User Group to come up with a user vision of the application and representation of the functionality that should be given to the end-user. This culminated into a User Vision document.
 
Changed:
<
<
The DP Architecture Group was then asked to respond to this document, by coming up with a design that would fulfill spirit as laid down within the User Vision document. Rather than creating a design on paper, this group has put together their ideas and interpretations into a prototype for two reasons:
>
>
The DP Architecture Group was then asked to respond to this document, by coming up with a design that would fulfill spirit as laid down within the User Vision document. Rather than creating a design on paper, this group has put together their ideas and interpretations into a prototype for two reasons:
 
  • to have a means to feed their ideas back to the user group (is this what you want?) and
  • to cast these ideas into a working system in order to understand the relations required within the resulting design.
Line: 84 to 84
 

META FILEATTACHMENT attachment="hipe-elements.jpg" attr="h" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" stream="hipe-elements.jpg" user="Main.JorgoBakker" version="1"
Added:
>
>
META TOPICMOVED by="DavideRizzo" date="1272527055" from="Hcss.DpHipeOverview" to="Public.DpHipeOverview"

Revision 72009-12-02 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 25 to 25
 The result of this exercise is HIPE, a prototype that is rapidly growing towards main stream code.
Added:
>
>
 

Philosophy

HIPE tries to embrace several aspects that affects both users as well as developers:
Line: 79 to 81
 
Added:
>
>
 
META FILEATTACHMENT attachment="hipe-elements.jpg" attr="h" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" stream="hipe-elements.jpg" user="Main.JorgoBakker" version="1"

Revision 62009-02-04 - JaimeSaiz

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 7 to 7
 
<-- summary -->
The new data processing application, HIPE, strives to provide an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualize that data in different ways and select tools to operate on that data. Meanwhile, high-level graphical interactions such as task execution and PAL querying are echoed on the command-line, such that you can generate scripts from these interactions.
Changed:
<
<
This section tries to explain the developers philosophy behind the framework and to provide a brief overview of the fundamental elements of the framework. Hopefully that enables you -as a developer- to make contributions to HIPE.
>
>
This section tries to explain the philosophy behind the framework to the developers, and to provide a brief overview of its fundamental elements. Hopefully that enables you -as a developer- to make contributions to HIPE.
 

Line: 16 to 16
 
We are all familiar with JIDE, an application providing a graphical entry point to the functionality in the HCSS software. This application has naturally grown from requests of users (notably the project science team, engineering scientists and calibratation scientists) and jython developers, but it was deemed not the be in a state to bring it to the end-user as a user-friendly interactive analysis tool.
Changed:
<
<
After the review in the summer of 2007, management has asked the DP User Group to come up with a user vision of the application and representation of the functionality that should be given the end-user. This culminated into a User Vision document.
>
>
After the review in the summer of 2007, management has asked the DP User Group to come up with a user vision of the application and representation of the functionality that should be given to the end-user. This culminated into a User Vision document.
  The DP Architecture Group was then asked to respond to this document, by coming up with a design that would fulfill spirit as laid down within the User Vision document. Rather than creating a design on paper, this group has put together their ideas and interpretations into a prototype for two reasons:
  • to have a means to feed their ideas back to the user group (is this what you want?) and
Line: 27 to 27
 

Philosophy

Changed:
<
<
HIPE tries to embrace several aspects which affects both users as well as developers:
>
>
HIPE tries to embrace several aspects that affects both users as well as developers:
 
  • an integrated application - giving access to all data processing functionality in a unified graphical interface
  • one look-and-feel - where window layout, toolbars, buttons, and menus are alike
  • a customizable layout - allow the user to decide which windows are relevant and how these windows are layed-out on screen
Line: 43 to 43
 

Editor Area

Changed:
<
<
The editor area is the location for visualization of the contents of user resources. Resources may be an image, a spectrum, dataset or a product. Another type of resource can be a user script, or a task execution. The editor can show e.g. an ImageDataset as an image or as a browsable dataset.
>
>
The editor area is the location for visualization of the contents of user resources. Resources may be an image, a spectrum, dataset or a product. Another type of resource can be a user script, or a task execution. The editor can show e.g. a SimpleImage as an image or as a browsable product.
 

Views

Views provide the means the look at the resources -or parts of them- in different ways. One can think of a console, a help window, an overview of all variables in your session and so forth.
Changed:
<
<
The prototype a suite of views as a hint to developers. Some views are extendible (such as the Outline View)
>
>
The prototype provides a suite of views as a hint to developers. Some views are extendible (such as the Outline View).
 

Perspectives

Line: 70 to 70
 

Site Events

Changed:
<
<
TODO
>
>
Views communicate with each other by means of events. There are three pieces for implementing this mechanism:

  • The events, which must extend SiteEvent, provide the information of something happened within the application, like a selection event, a variables changed event, etc.
  • The event handler, provided to the views, for dispatching the events.
  • The event listeners, which take proper actions on the events occurred.
 

Revision 52008-01-15 - JorgoBakker

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

<-- summary -->
Changed:
<
<
The new data processing application, HIPE, strives to provide an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualize that data in different ways and select tools to operate on that data.
>
>
The new data processing application, HIPE, strives to provide an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualize that data in different ways and select tools to operate on that data. Meanwhile, high-level graphical interactions such as task execution and PAL querying are echoed on the command-line, such that you can generate scripts from these interactions.
  This section tries to explain the developers philosophy behind the framework and to provide a brief overview of the fundamental elements of the framework. Hopefully that enables you -as a developer- to make contributions to HIPE.
Line: 68 to 68
 
  • a view's menu (in the form of a pull-down menu) and tool bar provide access to functionality which is specific to that view.
Added:
>
>

Site Events

TODO
 

META FILEATTACHMENT attachment="hipe-elements.jpg" attr="h" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" stream="hipe-elements.jpg" user="Main.JorgoBakker" version="1"

Revision 42008-01-15 - JorgoBakker

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 13 to 13
 

History

Added:
>
>
 We are all familiar with JIDE, an application providing a graphical entry point to the functionality in the HCSS software. This application has naturally grown from requests of users (notably the project science team, engineering scientists and calibratation scientists) and jython developers, but it was deemed not the be in a state to bring it to the end-user as a user-friendly interactive analysis tool.

After the review in the summer of 2007, management has asked the DP User Group to come up with a user vision of the application and representation of the functionality that should be given the end-user. This culminated into a User Vision document.

Line: 22 to 23
 
  • to cast these ideas into a working system in order to understand the relations required within the resulting design.

The result of this exercise is HIPE, a prototype that is rapidly growing towards main stream code.

Added:
>
>
 

Philosophy

Added:
>
>
 HIPE tries to embrace several aspects which affects both users as well as developers:
  • an integrated application - giving access to all data processing functionality in a unified graphical interface
  • one look-and-feel - where window layout, toolbars, buttons, and menus are alike
  • a customizable layout - allow the user to decide which windows are relevant and how these windows are layed-out on screen
  • user guidance - including command-line echoing of main graphical functionality, allowing the user to learn the scripting language by interacting with the system interactively
  • extendible application - allow the developer to add new bells-and-whistles which are automatically integrated
Added:
>
>
 

The Application

Changed:
<
<
>
>
 HIPE is built-up from several graphical elements, of which the fundamental ones are shown in the picture below:
Elements within HIPE application

Editor Area

Changed:
<
<
The editor area is the location for visualization of the contents of user resources. Resources may be an image, a spectrum, dataset or a product. Another type of resource can be a user script, or a task execution. The editor can show e.g. an ImageDataset as an image or as a browsable dataset.
>
>
The editor area is the location for visualization of the contents of user resources. Resources may be an image, a spectrum, dataset or a product. Another type of resource can be a user script, or a task execution. The editor can show e.g. an ImageDataset as an image or as a browsable dataset.
 

Views

Changed:
<
<
[DpHipeViews][Views]] provide the means the look at the resources -or parts of them- in different ways. One can think of a console, a help window, an overview of all variables in your session and so forth.
>
>
Views provide the means the look at the resources -or parts of them- in different ways. One can think of a console, a help window, an overview of all variables in your session and so forth.
  The prototype a suite of views as a hint to developers. Some views are extendible (such as the Outline View)
Added:
>
>
 

Perspectives

Added:
>
>
 A perspective is a collection of graphical windows organized in a way to focus the user on doing a specific job within the whole suite of jobs that a user can and will do within the system. It may consists of one or more views and optionally the editor area; these windows are then organized in tabbed panes and split panes.

The prototype provides some standard perspectives like a full-fledged work-bench as well as a classic JIDE perspective.

Added:
>
>
 

Menus and Tool bars

Added:
>
>
  The application provides two types of menus and tool bars:
  • the main menu and tool bar may provide access to global functionality as well as the editor area.
  • a view's menu (in the form of a pull-down menu) and tool bar provide access to functionality which is specific to that view.
Added:
>
>

 
META FILEATTACHMENT attachment="hipe-elements.jpg" attr="h" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" stream="hipe-elements.jpg" user="Main.JorgoBakker" version="1"

Revision 32008-01-14 - JorgoBakker

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 41 to 41
 The editor area is the location for visualization of the contents of user resources. Resources may be an image, a spectrum, dataset or a product. Another type of resource can be a user script, or a task execution. The editor can show e.g. an ImageDataset as an image or as a browsable dataset.

Views

Changed:
<
<
Views provide the means the look at the resources -or parts of them- in different ways. One can think of a console, a help window, an overview of all variables in your session and so forth.
>
>
[DpHipeViews][Views]] provide the means the look at the resources -or parts of them- in different ways. One can think of a console, a help window, an overview of all variables in your session and so forth.
  The prototype a suite of views as a hint to developers. Some views are extendible (such as the Outline View)

Perspectives

Changed:
<
<
A perspective is a collection of graphical windows organized in a way to focus the user on doing a specific job within the whole suite of jobs that a user can and will do within the system. It may consists of one or more views and optionally the editor area; these windows are then organized in tabbed panes and split panes.
>
>
A perspective is a collection of graphical windows organized in a way to focus the user on doing a specific job within the whole suite of jobs that a user can and will do within the system. It may consists of one or more views and optionally the editor area; these windows are then organized in tabbed panes and split panes.
  The prototype provides some standard perspectives like a full-fledged work-bench as well as a classic JIDE perspective.
Line: 56 to 56
 
  • the main menu and tool bar may provide access to global functionality as well as the editor area.
  • a view's menu (in the form of a pull-down menu) and tool bar provide access to functionality which is specific to that view.
Deleted:
<
<

-- JorgoBakker - 21 Dec 2007

 
META FILEATTACHMENT attachment="hipe-elements.jpg" attr="h" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" stream="hipe-elements.jpg" user="Main.JorgoBakker" version="1"

Revision 22007-12-23 - JorgoBakker

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Overview

Line: 12 to 12
 
Added:
>
>

History

We are all familiar with JIDE, an application providing a graphical entry point to the functionality in the HCSS software. This application has naturally grown from requests of users (notably the project science team, engineering scientists and calibratation scientists) and jython developers, but it was deemed not the be in a state to bring it to the end-user as a user-friendly interactive analysis tool.
 
Added:
>
>
After the review in the summer of 2007, management has asked the DP User Group to come up with a user vision of the application and representation of the functionality that should be given the end-user. This culminated into a User Vision document.

The DP Architecture Group was then asked to respond to this document, by coming up with a design that would fulfill spirit as laid down within the User Vision document. Rather than creating a design on paper, this group has put together their ideas and interpretations into a prototype for two reasons:

  • to have a means to feed their ideas back to the user group (is this what you want?) and
  • to cast these ideas into a working system in order to understand the relations required within the resulting design.

The result of this exercise is HIPE, a prototype that is rapidly growing towards main stream code.

Philosophy

HIPE tries to embrace several aspects which affects both users as well as developers:
  • an integrated application - giving access to all data processing functionality in a unified graphical interface
  • one look-and-feel - where window layout, toolbars, buttons, and menus are alike
  • a customizable layout - allow the user to decide which windows are relevant and how these windows are layed-out on screen
  • user guidance - including command-line echoing of main graphical functionality, allowing the user to learn the scripting language by interacting with the system interactively
  • extendible application - allow the developer to add new bells-and-whistles which are automatically integrated

The Application

HIPE is built-up from several graphical elements, of which the fundamental ones are shown in the picture below:
Elements within HIPE application

Editor Area

The editor area is the location for visualization of the contents of user resources. Resources may be an image, a spectrum, dataset or a product. Another type of resource can be a user script, or a task execution. The editor can show e.g. an ImageDataset as an image or as a browsable dataset.

Views

Views provide the means the look at the resources -or parts of them- in different ways. One can think of a console, a help window, an overview of all variables in your session and so forth.

The prototype a suite of views as a hint to developers. Some views are extendible (such as the Outline View)

Perspectives

A perspective is a collection of graphical windows organized in a way to focus the user on doing a specific job within the whole suite of jobs that a user can and will do within the system. It may consists of one or more views and optionally the editor area; these windows are then organized in tabbed panes and split panes.

The prototype provides some standard perspectives like a full-fledged work-bench as well as a classic JIDE perspective.

Menus and Tool bars

The application provides two types of menus and tool bars:

  • the main menu and tool bar may provide access to global functionality as well as the editor area.
  • a view's menu (in the form of a pull-down menu) and tool bar provide access to functionality which is specific to that view.
 

-- JorgoBakker - 21 Dec 2007 \ No newline at end of file

Added:
>
>
META FILEATTACHMENT attachment="hipe-elements.jpg" attr="h" comment="Elements within HIPE application" date="1198419929" name="hipe-elements.jpg" path="hipe-elements.jpg" size="110303" stream="hipe-elements.jpg" user="Main.JorgoBakker" version="1"

Revision 12007-12-21 - JorgoBakker

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="DpHipe"

HIPE Overview

<-- summary -->
The new data processing application, HIPE, strives to provide an integrated suite of graphical interfaces that can interact with each other. It allows for interactively choosing your active data in your session, visualize that data in different ways and select tools to operate on that data.

This section tries to explain the developers philosophy behind the framework and to provide a brief overview of the fundamental elements of the framework. Hopefully that enables you -as a developer- to make contributions to HIPE.

-- JorgoBakker - 21 Dec 2007

 
This site is powered by the TWiki collaboration platform Powered by Perl