If field is a checkbox (isBoolean: true) and onChange function is
specified, then call this onChange everytime checkbox is clicked.
reviewed-by: jessica
-If 'defaultValue' is specified for a text field, then put that value
into the text field on load.
-If 'desc' is specified for any field, then use it as a 'title'
attribute to show a tooltip description.
Example:
'icmptype': {
...
defaultValue: '-1',
desc: 'Please specify -1 if you want to allow all'
...
}
-Remove the ACL action from the tier chart item
-Adds an ACL overview list view under the VPC configure menu which
displays each tier and their total # of ACLs.
-Add ACL edit to tier detail view
- (misc) Also add IP address tab to tier detail view
If requireValidation: true is set for a custom action, then only
perform action if multiEdit's form fields are valid. This does not
apply to clicking on existing rules' action buttons.
Syntax:
multiEdit: {
fields: {
testField: {
custom: {
requireValidation: true,
...
},
...
},
...
}
}
Place tagging widget in a separate action and dialog class; it is
indicated by a 'tag' icon for better clarity.
-- This removes the requirement to specify a dummy 'edit' action on
multi-rules; instead, the separate tag action will appear automatically
as long as 'tags' is specified under the multiEdit's properties.
If in a section with multiple subsections, show active subsection in
the breadcrumb.
For example, if in storage->snapshots, display 'Storage - Snapshots'
based on the 'title' attribute for the main section and subsetion.
-- Note: this disables the 'fixSize' functionality which resizes long
breadcrumb trails, due to incompatibility with this new feature. It
is going to be reimplemented anyway, as it is fairly glitchy in its
current incarnation.
Show a generic dialog box for tagger validation, instead of using
jQuery validate
--it conflicted with the detail view's edit fields and prevented
submission unless the key and value fields were filled out.
This change includes the new dialog box for the CloudStack Autoscaler
implementation. It is accessible by a button ('Autoscaler') that
appears under each LB rule.
This also contains changes to the multiEdit widget to support features
required for Autoscaler:
-Fixes context/data passing to custom button widgets
-Fixes data retrieval for select fields
Implement a special form on input text field, for handling tag-based
fields. This will tags as a set of list items, which can be removed
and added to. This is for any comma-delimited field.
Currently, this is only supported on detail view widgets, by adding
'isTag: true' as a new attribute for any tag field. Tags are modified
when clicking the 'edit' action.
This fixes an issue where the page index is not reset back 1 when
activating the search or filter functionality, causing truncation when
trying to scroll down to later pages.
Currently, only icons are rendered on detail view actions. This change
adds support for showing a text label next to specified actions, which
has a button appearance. This is to allow certain actions to be more
visible, in the case where an icon isn't clear enough.
To make an action have a text label, add a 'textLabel' attribute to
the action properties:
editVpc: {
label: 'Edit VPC',
// textLabel property
textLabel: 'label.configure',
action: {
...
}
}
Currently, only icons are rendered on list view actions. This change
adds support for showing a text label next to specified actions, which
has a button appearance. This is to allow certain actions to be more
visible, in the case where an icon isn't clear enough.
To make an action have a text label, add a 'textLabel' attribute to
the action properties:
editVpc: {
label: 'Edit VPC',
// textLabel property
textLabel: 'label.configure',
action: {
...
}
}
To support header-level form items, serialize every form within the
multi-edit div (not just the main table form). For reusability, make
data serialization handled in separate 'getMultiData' function.
Jessica Wang
Brian Federle
Pranav Saxena
bfederle
olgasmola