Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ. As of October 27th, please open all new issues in the Red Hat Customer Portal .
unify the create container wizards into a single create container wizard that lets you pick child container / SSH / cloud - plus have a number of instances to create
Created: 25/May/12 12:22 PM
Updated: 19/Sep/12 08:24 AM
the FMC wizard is a little simpler as it lets you create all 3 kinds of container from the same wizard.
We should probably also remember the previous selection too; so its only really 1 more click by unifying the 3 wizards together. They can also have the same shared page for container name, number of containers, profile(s), version etc.
Description
the FMC wizard is a little simpler as it lets you create all 3 kinds of container from the same wizard.
We should probably also remember the previous selection too; so its only really 1 more click by unifying the 3 wizards together. They can also have the same shared page for container name, number of containers, profile(s), version etc.
the create container actions are used in various contexts; there is always a Fabric node - but sometimes there's a Root Container node available (that can be reused for the selection on the Child container option), sometimes there's a Version selected, sometimes there's a Profile available.
e.g. on the Profile containers view; we know the Profile to be defaulted. On the Fabric status page; the current selection defines the Profile to default.
So we should be careful to ensure that the context in which the generic CreateContainerAction is used - allows the root container to be set/unset based on selections, similarly for the ProfileNode and VersionNode - so that the maximum amount of things can be auto-defaulted in the wizard to avoid the user having to re-select things
James Strachan added a comment - 25/May/12 12:49 PM Some notes for whoever does this refactor:
the create container actions are used in various contexts; there is always a Fabric node - but sometimes there's a Root Container node available (that can be reused for the selection on the Child container option), sometimes there's a Version selected, sometimes there's a Profile available.
e.g. on the Profile containers view; we know the Profile to be defaulted. On the Fabric status page; the current selection defines the Profile to default.
So we should be careful to ensure that the context in which the generic CreateContainerAction is used - allows the root container to be set/unset based on selections, similarly for the ProfileNode and VersionNode - so that the maximum amount of things can be auto-defaulted in the wizard to avoid the user having to re-select things
Improvement
Open
Major
unify the create container wizards into a single create container wizard that lets you pick child container / SSH / cloud - plus have a number of instances to create
the create container actions are used in various contexts; there is always a Fabric node - but sometimes there's a Root Container node available (that can be reused for the selection on the Child container option), sometimes there's a Version selected, sometimes there's a Profile available.
e.g. on the Profile containers view; we know the Profile to be defaulted. On the Fabric status page; the current selection defines the Profile to default.
So we should be careful to ensure that the context in which the generic CreateContainerAction is used - allows the root container to be set/unset based on selections, similarly for the ProfileNode and VersionNode - so that the maximum amount of things can be auto-defaulted in the wizard to avoid the user having to re-select things