In addition to the main sectionPreFilter in the cloudStack UI, allow a
per-section 'preFilter' which is called if the navigation section is
not returned in sectionPreFilter. This is used primarily to support
plugin sections which will not be displayed by default.
When adding an item, show all returned fields if noSelect is
true. This prevents hidden conditional form fields from having their
row data hidden, such as if an ICMP rule is added and the TCP
start/end port form fields are hidden due to space constraints.
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
Fixes issue where tooltip overlaps form due to variable input
widths. To fix, a new option 'attachTo' can be specified, which will
attach to the closest parent element matching the option's selector.
Fixes a bug where the loading state is not immediataly set for the
detail view on performing certain custom UI actions, particularly
enable static NAT.
This passes a separate 'start' function to the custom widgets, which
triggers the loading state, and 'complete' when the action
completes (i.e., the server call is done)
For compact detail view (quickview), don't execute tabFilter, as only
the first tab is rendered in all cases. This prevents excessive API
calls from being made, slowing performance.
After adding a new instance row, in some cases the list view's context
is not passed fully to the quickview, which broke certain sections.
This ensures that the full context stored in the list widget is passed
to the quickview.
-Adds tooltips to all dialog-based form fields, to describe what each
field represents. The tooltip appears on focus of the field, and
hides once the field is blurred.
-Documentation content is pulled from a new namespace
'cloudStack.docs', under docs.js. A new attribute, 'docID' is then
specified on each createForm field to link the field to a specific
tooltip string.
-If no docID is specified, then no tooltip is rendered.
-This only applies to the 'generic' forms that are rendered using the
createForm widget
-This still needs to be localized
Conflicts:
ui/index.jsp
ui/scripts/configuration.js
ui/scripts/network.js
ui/scripts/ui/dialog.js
ui/scripts/vpc.js
Fix case where quick view was removed instead of hidden by a dialog
before performing an action, which casued the list view row to not
update on completion
On hover of a breadcrumb, show an overlay effect which focuses on that
particular panel, hiding all panels after it.
This allows a user to see the content of previous breadcrumbs that the
user loaded.
In some cases, clicking out of an overlayed dialog will cause an open
quick view to become stuck. This fixes via a new class 'hovered-elem'
which, when attached to any DOM element, will have its 'mouseleave'
triggered once the dialog is closed.
For any list view that has a corresponding detail view, adds a tooltip
to display the compact overview of the detail view contents, including
all available actions. This avoids a user from having to click into a
new panel to see more details and actions for an item.
This will happen automatically for any list view with a 'detailView'
sub-option, and will append a new column to the end of each item
row. If 'noCompact: true' is specified in the detailView's options,
then the quick view will not be rendered.
** Note: This also removes the existing list actions for the instances
and zones tables.
Example, to show a quick view:
listView: {
detailView: {
// Specify noCompact: true to not render a quick view
//
// noCompact: true
...
},
...
}
Conflicts:
ui/scripts/ui/widgets/detailView.js
