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 mundane as ³openstack_dashboard/common². David On 5/28/14, 10:36 AM, "Tzu-Mainn Chen" <[email protected]> wrote: >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 pattern will >increase; we anticipate doing similar things with Heat code in >openstack-dashboard. > >However, since tuskar-ui is intended to be a separate dashboard that has >the potential to live >away from openstack-dashboard, it does feel odd to directly extend >openstack-dashboard dashboard >components. Is there a separate place where such code might live? >Something similar in concept >to >https://github.com/openstack/horizon/tree/master/openstack_dashboard/usage > ? > > >Thanks, >Tzu-Mainn Chen > >_______________________________________________ >OpenStack-dev mailing list >[email protected] >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
