The current issue is that we can’t force Angular when we have so little code ourselves. The framework is fairly solid now, but there is little in the way of code examples; launch instance, which last I checked has a few major bugs, the unfinished (?) identity dashboard and a few metadata modals IIRC.
I strongly advise people to write new code with AngularJS, but I don’t support enforcing it as a hard requirement for Horizon/ Horizon plugins… yet :) Rob From: niuzhenguo <niuzhen...@huawei.com<mailto:niuzhen...@huawei.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, 7 July 2015 08:16 To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Mistral][Horizon][Tuskar-ui] Mistral Dashboard Hi folks, As Horizon is moving towards an Angular application, I think it’s high time that we should make a standard for other projects which want to horizon compatible on whether they should based on Angular Dashboard or the current Horizon framework. For new project, I think it makes more sense to build the dashboard on Angular. But for “old” project like Mistral-Dashboard and Tuskar-UI, they works fine with Django framework now, do they have to move towards Angular also, and when that should be done. -zhenguo
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
