tuskar-ui/tuskar_ui/workflows.py
Radomir Dopieralski d491e06d9a Create/edit flavors directly in the resource class form.
The formset in the resource class create/edit form now starts empty,
and allows the user to create or edit the flavors of that class
directly. Flavor templates are no longer used.

The formset starts with a single empty row at the end, for adding a new
flavor, and a "Delete" column with checkboxes for deleting existing
flavors.

If javascript is available, there is a link for adding more empty rows
and the empty line from the end is removed, and the checkboxes are
replaced with a cross icon, for deleting the rows instantly.

All traces of flavor templates have been removed from tuskar-ui.

The Max VMs field has been temporarily removed -- it will be added in
further iterations.

Change-Id: I1ff4c9f90657c62e7c5f45a4b7874524b9df204c
Implements: blueprint remove-flavor-templates
2013-09-17 15:36:55 +02:00

213 lines
8.4 KiB
Python

# vim: tabstop=4 shiftwidth=4 softtabstop=4
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
import logging
from django import template
# FIXME: TableStep
from django.utils import datastructures
import horizon.workflows
LOG = logging.getLogger(__name__)
class FormsetStep(horizon.workflows.Step):
"""
A workflow step that can render Django FormSets.
This distinct class is required due to the complexity involved in handling
both dynamic tab loading, dynamic table updating and table actions all
within one view.
.. attribute:: formset_definitions
An iterable of tuples of {{ formset_name }} and formset class
which this tab will contain. Equivalent to the
:attr:`~horizon.tables.MultiTableView.table_classes` attribute on
:class:`~horizon.tables.MultiTableView`. For each tuple you
need to define a corresponding ``get_{{ formset_name }}_data`` method
as with :class:`~horizon.tables.MultiTableView`.
"""
formset_definitions = None
def __init__(self, workflow):
super(FormsetStep, self).__init__(workflow)
if not self.formset_definitions:
class_name = self.__class__.__name__
raise NotImplementedError("You must define a formset_definitions "
"attribute on %s" % class_name)
self._formsets = {}
self._formset_data_loaded = False
def prepare_action_context(self, request, context):
"""
Passes the formsets to the action for validation and data extraction.
"""
formsets = self.load_formset_data(request.POST or None)
context['_formsets'] = formsets
return context
def load_formset_data(self, post_data=None):
"""
Calls the ``get_{{ formset_name }}_data`` methods for each formse
class and creates the formsets. Returns a dictionary with the formsets.
This is called from prepare_action_context.
"""
# Mark our data as loaded so we can check it later.
self._formset_data_loaded = True
for formset_name, formset_class in self.formset_definitions:
# Fetch the data function.
func_name = "get_%s_data" % formset_name
data_func = getattr(self, func_name, None)
if data_func is None:
cls_name = self.__class__.__name__
raise NotImplementedError("You must define a %s method "
"on %s." % (func_name, cls_name))
# Load the data and create the formsets.
initial = data_func()
self._formsets[formset_name] = formset_class(
data=post_data,
initial=initial,
prefix=formset_name,
)
return self._formsets
def render(self):
""" Renders the step. """
step_template = template.loader.get_template(self.template_name)
extra_context = {"form": self.action,
"step": self}
if issubclass(self.__class__, FormsetStep):
extra_context.update(self.get_context_data(self.workflow.request))
context = template.RequestContext(self.workflow.request, extra_context)
return step_template.render(context)
def get_context_data(self, request):
"""
Adds a ``{{ formset_name }}_formset`` item to the context for each
formset in the ``formset_definitions`` attribute.
If only one table class is provided, a shortcut ``formset`` context
variable is also added containing the single formset.
"""
context = {}
# The data should have been loaded by now.
if not self._formset_data_loaded:
raise RuntimeError("You must load the data with load_formset_data"
"before displaying the step.")
for formset_name, formset in self._formsets.iteritems():
context["%s_formset" % formset_name] = formset
# If there's only one formset class, add a shortcut name as well.
if len(self._formsets) == 1:
context["formset"] = formset
return context
# FIXME: TableStep
class TableStep(horizon.workflows.Step):
"""
A :class:`~horizon.workflows.Step` class which knows how to deal with
:class:`~horizon.tables.DataTable` classes rendered inside of it.
This distinct class is required due to the complexity involved in handling
both dynamic tab loading, dynamic table updating and table actions all
within one view.
.. attribute:: table_classes
An iterable containing the :class:`~horizon.tables.DataTable` classes
which this tab will contain. Equivalent to the
:attr:`~horizon.tables.MultiTableView.table_classes` attribute on
:class:`~horizon.tables.MultiTableView`. For each table class you
need to define a corresponding ``get_{{ table_name }}_data`` method
as with :class:`~horizon.tables.MultiTableView`.
"""
table_classes = None
def __init__(self, workflow):
super(TableStep, self).__init__(workflow)
if not self.table_classes:
class_name = self.__class__.__name__
raise NotImplementedError("You must define a table_class "
"attribute on %s" % class_name)
# Instantiate our table classes but don't assign data yet
table_instances = [(table._meta.name,
table(workflow.request, needs_form_wrapper=False))
for table in self.table_classes]
self._tables = datastructures.SortedDict(table_instances)
self._table_data_loaded = False
def render(self):
""" Renders the step. """
step_template = template.loader.get_template(self.template_name)
extra_context = {"form": self.action,
"step": self}
# FIXME: TableStep:
if issubclass(self.__class__, TableStep):
extra_context.update(self.get_context_data(self.workflow.request))
context = template.RequestContext(self.workflow.request, extra_context)
return step_template.render(context)
def load_table_data(self):
"""
Calls the ``get_{{ table_name }}_data`` methods for each table class
and sets the data on the tables.
"""
# We only want the data to be loaded once, so we track if we have...
if not self._table_data_loaded:
for table_name, table in self._tables.items():
# Fetch the data function.
func_name = "get_%s_data" % table_name
data_func = getattr(self, func_name, None)
if data_func is None:
cls_name = self.__class__.__name__
raise NotImplementedError("You must define a %s method "
"on %s." % (func_name, cls_name))
# Load the data.
table.data = data_func()
table._meta.has_more_data = self.has_more_data(table)
# Mark our data as loaded so we don't run the loaders again.
self._table_data_loaded = True
def get_context_data(self, request):
"""
Adds a ``{{ table_name }}_table`` item to the context for each table
in the :attr:`~horizon.tabs.TableTab.table_classes` attribute.
If only one table class is provided, a shortcut ``table`` context
variable is also added containing the single table.
"""
context = {}
# If the data hasn't been manually loaded before now,
# make certain it's loaded before setting the context.
self.load_table_data()
for table_name, table in self._tables.items():
# If there's only one table class, add a shortcut name as well.
if len(self.table_classes) == 1:
context["table"] = table
context["%s_table" % table_name] = table
return context
def has_more_data(self, table):
return False