Allow editing of selected db expressions

[aowen87]

This was requested by Al Nichols. In his Silo input databases, he defines a slew of fairly complicated expressions involving intermediate expressions as well as a handful of driving constants. He would like to be able to edit the handful of driving constants without having to be exposed to the slew of complicated expressions they are involved in. This involves managing visibility of the expressions in both the GUI menu pull-downs and in the expression window and editability of these expressions. Editability Currently, expressions from the database are not editable. The user would like the ability to edit db expressions. However, the user would like the ability for the database to indicate if a db expression is editable or not. This would involve a Silo enhancement to tag which expressions are editable. It would involve minor adjustments to avtDBMetaData to carry along this tag to Expression window. Note that editability implies visibility. In order to edit an expression from the database, it must be visible in the expression window too. Currently, we have a single check box in expression window which indicates whether to show ALL db expressions or not. The new behavior would be that any db expression which is editable would always appear in the expression window, regardless of the 'show db expressions' check box setting. Visibility Visibility of expressions involves two parts; their appearance in the expression window itself and their apperance in the GUI's pulldown menus (or CLI's DBMetaData I guess). Visibility in the expression window would be handled as described above if its editible, it is always visible otherwise its visible only when the check box to show db expressions is active. The user would like the ability to indicate if expression (variable defined by it actually) appears in the GUI pulldowns or not. For intermediate expression definitions, the resultant pollution of GUI pulldowns is not acceptable. Current best work-around is to define all in a submenu. There is a separate Silo ticket, #541, for specifying which db expressions should be editable.

-----------------------REDMINE MIGRATION----------------------- This ticket was migrated from Redmine. As such, not all information was able to be captured in the transition. Below is a complete record of the original redmine ticket.

Ticket number: 535 Status: Pending Project: VisIt Tracker: Feature Priority: Normal Subject: Allow editing of selected db expressions Assigned to: - Category: - Target version: - Author: Mark Miller Start: 01/05/2011 Due date: % Done: 0% Estimated time: Created: 01/05/2011 11:53 am Updated: 03/28/2011 06:49 pm Likelihood: Severity: Found in version: 2.12.3 Impact: 3 - Medium Expected Use: 3 - Occasional OS: All Support Group: Any Description: This was requested by Al Nichols. In his Silo input databases, he defines a slew of fairly complicated expressions involving intermediate expressions as well as a handful of driving constants. He would like to be able to edit the handful of driving constants without having to be exposed to the slew of complicated expressions they are involved in. This involves managing visibility of the expressions in both the GUI menu pull-downs and in the expression window and editability of these expressions. Editability Currently, expressions from the database are not editable. The user would like the ability to edit db expressions. However, the user would like the ability for the database to indicate if a db expression is editable or not. This would involve a Silo enhancement to tag which expressions are editable. It would involve minor adjustments to avtDBMetaData to carry along this tag to Expression window. Note that editability implies visibility. In order to edit an expression from the database, it must be visible in the expression window too. Currently, we have a single check box in expression window which indicates whether to show ALL db expressions or not. The new behavior would be that any db expression which is editable would always appear in the expression window, regardless of the 'show db expressions' check box setting. Visibility Visibility of expressions involves two parts; their appearance in the expression window itself and their apperance in the GUI's pulldown menus (or CLI's DBMetaData I guess). Visibility in the expression window would be handled as described above if its editible, it is always visible otherwise its visible only when the check box to show db expressions is active. The user would like the ability to indicate if expression (variable defined by it actually) appears in the GUI pulldowns or not. For intermediate expression definitions, the resultant pollution of GUI pulldowns is not acceptable. Current best work-around is to define all in a submenu. There is a separate Silo ticket, #541, for specifying which db expressions should be editable.

Comments: