I think this falls inline with other items we are working toward in
Horizon, namely more pluggable components on panels.
I think creating a directory in openstack_dashboard for these reusable
components makes a lot of sense. And usage should eventually moved to
there.
I would suggest something as
11:40 AM
Subject: [openstack-dev] [Horizon][Tuskar-UI] Location for common
dashboardcode?
Heya,
Tuskar-UI is currently extending classes directly from
openstack-dashboard.
For example, right now
our UI for Flavors extends classes in both
Heya,
Tuskar-UI is currently extending classes directly from openstack-dashboard.
For example, right now
our UI for Flavors extends classes in both
openstack_dashboard.dashboards.admin.flavors.tables and
openstack_dashboard.dashboards.admin.flavors.workflows. In the future, this
sort of
)
openstack-dev@lists.openstack.org,
Date: 05/28/2014 11:40 AM
Subject: [openstack-dev] [Horizon][Tuskar-UI] Location for common
dashboard code?
Heya,
Tuskar-UI is currently extending classes directly from openstack-dashboard.
For example, right now
our UI
:[openstack-dev] [Horizon][Tuskar-UI] Location for common
dashboardcode?
Heya,
Tuskar-UI is currently extending classes directly from openstack-dashboard.
For example, right now
our UI for Flavors extends classes in both
