Hiya,
That makes sense. Just to take a concrete example - in tuskar-ui, our
flavors' table code
(https://github.com/openstack/tuskar-ui/blob/master/tuskar_ui/infrastructure/flavors/tables.py)
uses the following code from openstack_dashboard.dashboards.admin.flavors.tables
(https://github.com/ope
e dashboard
>> panels, it's reasonable that tuskar-ui should be dependent on the
>> dashboard.
>>
>> Doug Fish
>>
>>
>>
>>
>>
>> From:Tzu-Mainn Chen
>> To: "OpenStack Development Mailing List (not for usage questions)"
>
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
on the
>> dashboard.
>>
>> Doug Fish
>>
>>
>>
>>
>>
>> From:Tzu-Mainn Chen
>> To:"OpenStack Development Mailing List (not for usage questions)"
>>,
>> Date:05/28/2014 11:4
;
>
>
>
> From: Tzu-Mainn Chen
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 05/28/2014 11:40 AM
> Subject: [openstack-dev] [Horizon][Tuskar-UI] Location for common
> dashboard code?
>
>
g the dashboard
panels, it's reasonable that tuskar-ui should be dependent on the
dashboard.
Doug Fish
From: Tzu-Mainn Chen
To: "OpenStack Development Mailing List (not for usage questions)"
,
Date: 05/28/2014 11:40 AM
Subject: [openstack-dev] [Horizon][
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 patte
